On Wed, 05 Nov 2008 23:19:41 +0900, Paul Wise <[EMAIL PROTECTED]> wrote: > Please paste the error output you got. If it was just the WARNING lines > then that is intentional - the postinst cannot know if you are using an > initrd but you don't have links in the root directory.
Hello, I get these WARNINGS WARNING: kernel & initrd not found in the root directory (/vmlinuz & /initrd.img) WARNING: Do NOT reboot or LILO may fail to boot if your kernel+initrd is large. WARNING: Please read /usr/share/doc/lilo/README.Debian You are right. The "problem" is that I do not have an initrd.img link in my root. Of course if you KNOW that this is okay, you can just call lilo manually afterwards and it won't complain. What about checking for the existence of an /initrd.img only if it is configured in the conf file? Right now lilo is not called at all, which is a more serious problem in my opinion since this did not happen with earlier versions. Kind regards, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
