This may help:
>From the KERNEL-HOWTO. The directory paths are not exactly the same as
Mandrake installations, so you may need to mess about a little. Also,
sounds like you already have a boot disk so you can skip all of that.
If you can't get things fired up from this, then post the exact error
messages you get when you try to run /sbin/lilo.
Ooops! The best thing you can do here is to boot off of a floppy disk or
CDROM and prepare another bootable floppy (such as `make zdisk' would do).
You need to know where your root (/) filesystem is and what type it is
(e.g. second extended, minix). In the example below, you also need to know
what filesystem your /usr/src/linux source tree is on, its type, and where
it is normally mounted.
In the following example, / is /dev/hda1, and the filesystem which holds
/usr/src/linux is /dev/hda3, normally mounted at /usr. Both are second
extended filesystems. The working kernel image in
/usr/src/linux/arch/i386/boot is called bzImage.
The idea is that if there is a functioning bzImage, it is possible to use
that for the new floppy. Another alternative, which may or may not work
better (it depends on the particular method in which you messed up your
system) is discussed after the example.
First, boot from a boot/root disk combo or rescue disk, and mount the
filesystem which contains the working kernel image:
mkdir /mnt
mount -t ext2 /dev/hda3 /mnt
If mkdir tells you that the directory already exists, just ignore it.
Now, cd to the place where the working kernel image was. Note that
/mnt + /usr/src/linux/arch/i386/boot - /usr = /mnt/src/linux/arch/i386/boot
Place a formatted disk in drive ``A:'' (not your boot or root disk!), dump
the image to the disk, and configure it for your root filesystem:
cd /mnt/src/linux/arch/i386/boot
dd if=bzImage of=/dev/fd0
rdev /dev/fd0 /dev/hda1
cd to / and unmount the normal /usr filesystem:
cd /
umount /mnt
You should now be able to reboot your system as normal from this floppy.
Don't forget to run lilo (or whatever it was that you did wrong) after the
reboot!
As mentioned above, there is another common alternative. If you happened to
have a working kernel image in / (/vmlinuz for example), you can use that
for a boot disk. Supposing all of the above conditions, and that my kernel
image is /vmlinuz, just make these alterations to the example above: change
/dev/hda3 to /dev/hda1 (the / filesystem), /mnt/src/linux to /mnt, and
if=bzImage to if=vmlinuz. The note explaining how to derive /mnt/src/linux
may be ignored.
Steve Flynn
IBM MVS Operations Analyst
"Antoniou, Stylianos" <[EMAIL PROTECTED]> on 22/02/2000 14:43:09
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc: (bcc: Steve Flynn/UK/Contr/IBM)
Subject: RE: [newbie] Load lilo with rescue disks
I have changed my Windows partitions. So I cannot boot in Linux now ( I
have
a dual boot machine). Trying to load the boot disks I messed up lilo. So I
need to changed fstab with vi and to reistall lilo.
Stelios Antoniou
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: 22 February 2000 13:00
To: [EMAIL PROTECTED]
Subject: Re: [newbie] Load lilo with rescue disks
Why not? What errors do you get when you run lilo again?
I've never actualy seen my current installation panic - what
did you do to
cause the catastrophic failure? Unix is pretty good at
protecting itself
from unexecpected events - to cause a panic something fairly
nasty must
have happened.....
Steve Flynn
IBM MVS Operations Analyst
"Antoniou, Stylianos" <[EMAIL PROTECTED]> on 22/02/2000
12:23:14
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
cc: (bcc: Steve Flynn/UK/Contr/IBM)
Subject: [newbie] Load lilo with rescue disks
Hi there,
I caused a kernel panic, I booted with the rescue disks and
I want to run
lilo. Unfortunately, I cannot run it by simply typing
/sbin/lilo. What am I
missing?
Thanks in advance,
Stelios Antoniou
