View source for LILO

The <b>LI</b>nux boot <b>LO</b>ader.

[[GRUB]] is superior to LILO in almost every way.

== Rescuing on Linux ==


After doing an apt-get upgrade on Debian 3.1, my OS upgraded my 
kernel and LILO, but there was a problem. I used knoppix to rescue my system.
 
I remebered my hard drive was hda, so I did 
 # fdisk /dev/hda
to see my partition table:
hda1 = /boot
hda3 = /
hda4 = /backup
I carefully exited fdisk without making any changes.
 # mount /dev/hda3 /mnt/hda3
This means my regular root (/) partition is now mounted.
 # chroot /mnt/hda3
Essentially this means pretend /mnt/hda3 is my / now while I fix things.
 # mount /dev/hda1 /boot
 # mount /dev/hda4 /backup
As you can see, I mounted my other partitions as their normal mount points on
my disk.
Now you can do what you wish, but most likely:
 # lilo -v
to rerun lilo in verbose mode. When I did this, I found the /vmlinuz in 
lilo.conf didn't exist, so I changed the conf to use /boot/bzImage which
I verified existed first.
In my case,  I then did an 
 # apt-get update && apt-get upgrade
as well, but that is a little risky in a chrooted environment, as things like
your hostname and domainname are not defined for example. 

Once you've rerun lilo without errors, you can umount everything and reboot.