Regards
Thomas E. Kamire Systems Engineer Kenya Airways Ltd, P.O. BOX 41010 Nairobi, Kenya Tel: +254+2+32822311 Cell: +254 722 483 253 [EMAIL PROTECTED] "Lets Make Things Better - Together" -----Original Message----- From: Nathanael Nerode [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 30, 2004 7:17 AM To: Subject: Re: Bug#239627: mails stupid debconf note to user when lilo is installed in d-i Joey Hess wrote: > Andrés Roldán wrote: >> If you look into the lilo.config file on debian directory of the lilo >> source, you will notice that this warning is being displayed because >> there is a file called /boot/boot.b being either a symbolic link or a >> normal file. Those files were used by lilo prior to 22.3.3 versions >> and you _really_ need to rerun lilo if you are upgrading from such >> lower versions. This is the case when upgrading from woody to sarge. >> That's why this debconf note is there. >> >> The question is, why are those files there when installing a new >> system? Newer versions of lilo don't create that file. If >> lilo-installer is creating it, I'd really want to know why. > > Could it have anything to do with the lilo.conf file having > install=/boot/boot.b in it? Probably. It shouldn't; it shouldn't really have any "install=" line at all by default, for a current version -- or "install=menu", which is much like the default -- or "install=bmp", which is correct if there's a "bitmap=" option in the file. -- Make sure your vote will count. http://www.verifiedvoting.org/
