[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:

> Package: lilo, lilo-installer
> Severity: normal
> Tags: d-i
> When lilo-installer installs lilo in the debian installer, lilo tries to
> display a debconf note warning the user that they need to run
> /sbin/lilo. Since it is running in noninteractive mode, debconf mails

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.

> this note to root (exim redirects it to user mail). Then lilo-installer
> goes on and runs lilo to make the system bootable; exactly what the
> note was warning needs to be done.
> This is especially annoying if the DNS of the machine is messed up, then
> there is a blue screen in d-i while lilo is installed, waiting for a DNS
> timeout. 
> This needs to be integrated better. If lilo truely needs to display this
> note (why? grub does not display a similar note), then there needs to be
> some mechanism for lilo to be told that it is being installed by
> lilo-installer, and that lilo-installer will take care of this and the
> note need not be displayed in this case.
> -- 
> see shy jo

Andrés Roldán <aroldan@debian.org>
GPG Key-ID: 0xB29396EB

Attachment: pgp7bT0p8lHmV.pgp
Description: PGP signature

Reply to: