summaryrefslogtreecommitdiffstats
path: root/rescue/rescue-doc
blob: e6514b462a60e37a07fc30724d62e6623f7c381f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
#!/usr/bin/perl

# From MDK::Common:
sub output { my $f = shift; open(my $F, ">$f") or die "output in file $f failed: $!\n"; print $F $_ foreach @_ }

output('/tmp/rescue-doc-contents', q(
     Information regarding problems not directly addressed
                     by this rescue.


Are you certain "rescue mode" is the best tool for your specific
problem?

The rescue system on this CD is a very basic text-based
environment for rescuing systems that no longer boot. You will
not find an easy-to-use graphical environment in this rescue
system, nor the detection/configuration libraries.


The vast majority of problems that can affect a Linux system are
much easier to repair on a running system than by booting into
"rescue mode". In fact, there are very few problems which aren't
easier to resolve in the comfortable environment of a fully
installed system than in this spartan "rescue system" shell.
Some of the most common problems include:

- bad or missing X (video display) configuration
- adding/removing/reconfiguring hardware
- repairing problems caused by installing third-party software
  with the "--force" and "--nodeps" options

The general rule of thumb is: "If you can boot into the Linux
system without using rescue mode or this CD, there is no real
reason to use the rescue CD".


However, if you can no longer boot into the system, the rescue
system is the right tool. Some common examples include:

- If you previously changed some parameters in the /etc/fstab and
  the system will no longer boot, fix the offending line while in
  rescue mode, then try to boot normally into your system.

- If the problem cannot be completely resolved in rescue mode
  (for example, if you need to reconfigure the video display),
  just modify what's necessary to boot into a running system,
  then complete the fix from there.

For more information on troubleshooting your system,
please consult the official manuals, the documentation on
wiki.mageia.org or support forum at forum.mageia.org.

<press 'q' (qwerty keyboard) to continue>
));

exec 'less /tmp/rescue-doc-contents';