On Wed Feb 16 2000 at 16:08, Bernhard Rosenkraenzer wrote:
> On Wed, 16 Feb 2000, Bob Tennent wrote:
>
> > What's happened to this? The Official Red Hat Linux Reference
> > Guide still talks about it. The CD still asks for it if you want
> > to rescue your system. But it's not on the CD nor at the Red Hat
> > site, for > 6.0, as far as I can see.
>
> 6.2 will have a working rescue mode.
Yes, rescue.img did disappear for rh61, but unfortunately the docs
(and the installer screens) weren't updated to reflect the changes.
> For 6.1, get ftp://people.redhat.com/bero/rescue-6.1/rescue.img
It isn't strictly necessary to have a rescue disk image, it's all done
from the installation boot image. But while this is a very neat
concept and effectively makes the rescue.img obselete, the initial
implementation in rh61 is a little problematical and the setup needs
some fine-tuning.
Below is a description of how to use rescue mode for rh61.
I had a peek at the rh62beta last week, and I noted that rescue.img
isn't there... so I presume that rescue mode from the installer
images is now firmly the way it will go. Cool.
Cheers
Tony
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
Tony Nugent <[EMAIL PROTECTED]> Systems Administrator, RHCE
GrowZone OnLine (a project of) GrowZone Development Network
POBox 475 Toowoomba Oueensland Australia 4350 Ph: 07 4637 8322
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
[... taken from an email I sent to someone else who needed to have a
"rescue mode" to recover their lilo boot loader after a windows
application rewrote the MBR ...]
For using rescue mode in redhat 6.1, use the *installation* boot
images and start off as if you are doing an actual installation.
However, where you get the initial greeting screen, at the LILO prompt
use "rescue text" instead of any of the other options listed there.
You'll go through the initial motions of an install with a couple of
menus, then drop into a bash shell prompt. Actually two - Left-Alt-F1
and another console on Left-Alt-F2
Do something like this:
cd /dev
mknod hda b 3 0
mknod hda1 b 3 1
mknod hda2 b 3 2
... and so on. Unfortunately the character devices for the hard
drive(s) and their partitions are missing, so they need to be
recreated before they can be mounted. (Eek, they forgot about them! :)
For hdb, the parameters for the devices start at "b 3 64" for hdb, 65
for hdb1 and so on.
You might need to use fdisk to find out what partitions you have...
fdisk -l /dev/hda
Create a mount point:
mkdir /r
Mount the root partition of your linux installation onto that point:
mount -t ext2 /dev/hda3 /r
If you have the /boot directory set up in a small separate partition,
then mount this too, onto the /boot directory on your linux root
partition...
mount -t ext2 /dev/hda2 /r/boot
Now check what's in the lilo.conf file....
cd /r/etc
cat lilo.conf
If pico is available, then you can edit this file with it (use the -w
switch to stop it from auto-wrapping long lines when you save the
file). Small, brain-dead editor, but last time I looked that's what
redhat had there :) vi might be there too, I forget, but most people
who have never used it before find it confusing (until the basics are
explained, then it's easy).
You might want to change this line:
boot=/dev/hda
to
boot=/dev/fd0
# boot=/dev/hda
This will tell lilo to write a boot sector to a floppy disk instead of
into the master boot record of the hard drive. So any time you want
to run linux, use the boot sector on this disk to do it (and it is
quick, since only the boot sector is read from it). The MBR will boot
windows "as usual".
Now you need to run lilo to make the actual boot sector...
/r/sbin/lilo -r /r
Always use the version of lilo that comes with your installation.
Another way to do this is:
/r/usr/sbin/chroot /r /sbin/lilo
which can be more successful in some circumstances.
Aside... you can also do this:
/r/usr/sbin/chroot /r /bin/bash -l
... and you are running a bash shell change-rooted to your actual
installation image. ("exit" to return out of here, btw). Not for the
faint-at-heart, but very powerful. You can even - if you really want
to go insane - manually get your system up and running to some degree
from here, including networking -- now try doing THAT with windoze!!
:-)
All done. Almost...
cd /
sync
umount /r/boot
umount /r
reboot
And away you go....
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
