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

Bug#690353: d-i: lilo cannot be used - lack of initrd entry

Hello Joachim,

here's what Holger replied:

Holger Wansing <linux@wansing-online.de> (23/10/2012):
> I tested the lilo bootloader on a x86 Virtual Box with the beta3
> netinst CD image:
> - Installation was a complete success.
> - Booting the new system also works without problems.
>   (The /etc/lilo.conf also contains the initrd line.)
> So, no problem with lilo on x86 AFAICS.

I thought the fix could be:
| lilo-installer (1.38) unstable; urgency=low
|   * Fix detection of initrd.img when generating lilo.conf.
|     Change test -e to -L, as the symlink is absolute for some reason
|     and so appears broken from within the d-i environment.
|     Thanks, Ivo De Decker. Closes: #678421
|  -- Joey Hess <joeyh@debian.org>  Sat, 25 Aug 2012 16:02:25 -0400

but that one migrated to testing the day before we built beta2's
installer images:
 * [2012-08-27] lilo-installer 1.38 MIGRATED to testing (Britney)
 * 20120828 to unstable: Cyril Brulebois <kibi@debian.org>

So beta2 should have this bug fix. Additionally, I don't see anything
in later lilo-installer releases that would explain the bug in beta2
getting fixed in beta3. Are you sure you didn't try beta1?

Anyway, a confirmation that the bug doesn't affect beta3 would be


Attachment: signature.asc
Description: Digital signature

Reply to: