Rescure - Debian LILO failure after upgraded to 3.1

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Tue Jun 21 17:15:07 UTC 2005


On Tue, Jun 21, 2005 at 12:49:48PM -0400, Phillip Qin wrote:
> Yeah, I forgot to run lilo after I changed lilo.conf from
> install=/boot/boot-menu.b To install=menu.

The simple setup solution is:

apt-get install grub
grub-install /dev/hda (or whatever you use for your boot loader)
update-grub
apt-get remove --purge lilo

Then if you want debian kernels to auto add and remove when installed
and removed, you make sure you have this:

/etc/kernel-img.conf:
do_symlinks = no
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
postinst_hook = /sbin/update-grub
postrm_hook   = /sbin/update-grub

The hook lines are the key along with the line to make it not try to run
lilo.  This is the default setup on Debian sarge for new installs, and
is just wonderful.

You just have to boot your system first to get back in to fix it.   A
grub floppy or a rescue disk should do it.

Lennart Sorensen
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml





More information about the Legacy mailing list