Bug#535331: ditto
On Fri, Oct 23, 2009 at 11:54:21AM +0200, Josip Rodin wrote:
> Hi,
>
> I've experienced the same problem. I've got two lenny machines which have
> GPT paritition tables and Linux root on LVM, and they can't use anything but
> LILO (there are some novelty hacks for GRUB but I haven't been able to test
> them yet because this is in production). I have kernel-img.conf set up
> right, but after upgrading linux-image-2.6.26-2-686, I just get the "not
> updating symbolic links" messages and no triggers or boot loaders are run.
> If left unattended, this typically renders these two systems unbootable.
>
> It really looks like a failure to define the $loader variable in the
> predefined variables section. If I just put 'lilo' in there and re-run
> dpkg-reconfigure linux-image-2.6.26-2-686, the output changes to:
>
> Running depmod.
> Running mkinitramfs-kpkg.
> Not updating initrd symbolic links since we are being updated/reinstalled
> (2.6.26-19lenny1 was configured last, according to dpkg)
> Not updating image symbolic links since we are being updated/reinstalled
> (2.6.26-19lenny1 was configured last, according to dpkg)
> You already have a LILO configuration in /etc/lilo.conf
> Running boot loader as requested
> Testing lilo.conf ...
> Testing successful.
> Installing the partition boot sector...
> Running /sbin/lilo ...
> Installation successful.
>
> This is what would be expected. The run_lilo() function goes out of its way
> to determine whether the existence of /etc/lilo.conf is sufficient reason to
> run lilo, so there doesn't appear to be any reason to completely omit it.
from the affected box:
cat /etc/kernel-img.conf
Reply to: