The generated lilo.conf also points to /initrd.img. However, at least after installing a new custom-built kernel-image, the links are named /initrd and /initrd.old, so lilo still complains on that.
After having complained about the devfs issues, that is. I did not see that mentionned here, but since devfs is not mounted by default, lilo refuses to run. Not counting that the device names in lilo.conf are non-devfs ones... "Obviously", mounting devfs and (temporarily) editing lilo.conf, just the time to reboot and edit lilo.conf back to normal (non-devfs), and things are OK again... Regards, -- Yann Dirson <[EMAIL PROTECTED]> http://www.alcove.com/ Technical support manager Responsable de l'assistance technique Senior Free-Software Consultant Consultant senior en Logiciels Libres Debian developer ([EMAIL PROTECTED]) Développeur Debian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
