I am sorry, but I'm afraid my previous analysis in this bug report is completely wrong.
The kernel image maintainer scripts are not supposed to run lilo directly. They trigger an initramfs update, and that should in turn cause lilo to run after it's finished. The initramfs update must do this regardless of why it was run, and having the kernel scripts run lilo would therefore be useless. And now for the weird stuff: This did suddenly work for me with the 2.6.26-19 upgrade. I got: Setting up linux-image-2.6.26-2-686 (2.6.26-19) ... Running depmod. Running mkinitramfs-kpkg. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.26-17lenny2 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.26-17lenny2 was configured last, according to dpkg) update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.26-2-686 Added Linux * Added LinuxOLD But I cannot understand what may have changed. My /etc/kernel-img.conf is still and has always been: # Kernel Image management overrides # See kernel-img.conf(5) for details do_symlinks = Yes do_initrd = Yes do_bootloader = yes And initramfs-tools have not been upgraded since the last time this failed according to the dpkg log. But the dpkg log above shows something very interesting: This time I got a "status triggers-pending initramfs-tools 0.92o" which I did not see on the previous kernel image upgrade: adler:/tmp# egrep 'linux-image|initramfs-tools' /var/log/dpkg.log{.1,} /var/log/dpkg.log.1:2009-08-15 01:00:40 upgrade linux-image-2.6.26-2-686 2.6.26-17lenny1 2.6.26-17lenny2 /var/log/dpkg.log.1:2009-08-15 01:00:40 status half-configured linux-image-2.6.26-2-686 2.6.26-17lenny1 /var/log/dpkg.log.1:2009-08-15 01:00:41 status unpacked linux-image-2.6.26-2-686 2.6.26-17lenny1 /var/log/dpkg.log.1:2009-08-15 01:00:41 status half-installed linux-image-2.6.26-2-686 2.6.26-17lenny1 /var/log/dpkg.log.1:2009-08-15 01:00:47 status half-installed linux-image-2.6.26-2-686 2.6.26-17lenny1 /var/log/dpkg.log.1:2009-08-15 01:00:49 status unpacked linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log.1:2009-08-15 01:00:49 status unpacked linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log.1:2009-08-15 01:00:53 configure linux-image-2.6.26-2-686 2.6.26-17lenny2 2.6.26-17lenny2 /var/log/dpkg.log.1:2009-08-15 01:00:53 status unpacked linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log.1:2009-08-15 01:00:53 status half-configured linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log.1:2009-08-15 01:01:27 status installed linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log:2009-09-06 01:00:53 upgrade linux-image-2.6.26-2-686 2.6.26-17lenny2 2.6.26-19 /var/log/dpkg.log:2009-09-06 01:00:53 status half-configured linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log:2009-09-06 01:00:55 status unpacked linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log:2009-09-06 01:00:55 status half-installed linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log:2009-09-06 01:01:07 status half-installed linux-image-2.6.26-2-686 2.6.26-17lenny2 /var/log/dpkg.log:2009-09-06 01:01:09 status unpacked linux-image-2.6.26-2-686 2.6.26-19 /var/log/dpkg.log:2009-09-06 01:01:09 status unpacked linux-image-2.6.26-2-686 2.6.26-19 /var/log/dpkg.log:2009-09-06 01:01:26 configure linux-image-2.6.26-2-686 2.6.26-19 2.6.26-19 /var/log/dpkg.log:2009-09-06 01:01:26 status unpacked linux-image-2.6.26-2-686 2.6.26-19 /var/log/dpkg.log:2009-09-06 01:01:27 status half-configured linux-image-2.6.26-2-686 2.6.26-19 /var/log/dpkg.log:2009-09-06 01:02:02 status installed linux-image-2.6.26-2-686 2.6.26-19 /var/log/dpkg.log:2009-09-06 01:02:03 status triggers-pending initramfs-tools 0.92o /var/log/dpkg.log:2009-09-06 01:02:08 trigproc initramfs-tools 0.92o 0.92o /var/log/dpkg.log:2009-09-06 01:02:08 status half-configured initramfs-tools 0.92o /var/log/dpkg.log:2009-09-06 01:02:55 status installed initramfs-tools 0.92o Why? Or rather: Why doesn't it always do that? Bjørn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org