On Sunday 25 September 2005 09:40, Petter Reinholdtsen wrote: > Why the serious severity? lilo is not the default boot loader, so > this only affect expert installs. Because LILO is the default installer in some cases (/ on XFS IIRC) and is also ofter prefered by users for RAID installs. Also, it is a clear regression from Sarge. > > In commit r29833 the value of link_in_boot was changed from false to > > true for i386 and amd64. This change make lilo-installer fail as > > lilo.conf is configured to expect symlinks for the kernel and initrd > > in / (if boot is not a separate partition). > > I suggest reassigning this to the lilo package, asking it to generate > a lilo.conf file pointing into /boot/ instead of expecting symlinks in > /. That should be lilo-installer, not lilo, as it is lilo-installer that creates the lilo.conf. However, I would first like to hear what the problem was for AMD64 that prompted the change in the first place and make sure that RAID and LVM installs will not be broken by changing things that way.
Attachment:
pgpVpwlBzpLIB.pgp
Description: PGP signature