[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#239627: mails stupid debconf note to user when lilo is installed in d-i



Joey Hess <joeyh@debian.org> writes:

> 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?

That syntaxis is deprecated. If you look at the manual page, you
will notice that you can simply put anything like install=bmp,
install=menu or install=text and lilo will know what to do with 
that options.

If lilo-installer is using that kind of syntaxis with the default 
lilo.conf file, it should really change that.

>
> -- 
> see shy jo

-- 
Andrés Roldán <aroldan@debian.org>
GPG Key-ID: 0xB29396EB
http://people.fluidsignal.com/~aroldan

Attachment: pgpvDf2F94krf.pgp
Description: PGP signature


Reply to: