Hi there.
I've got a multi-boot system for which I maintain my own (Grub2) grub.cfg.
I've got Debian Lenny, Debian Squeeze and Ubuntu partitions inside an
encrypted LVM2 logical volume,
a booting nicely.
I just have to watch out if one of them tries to "update" grub.cfg,
completely trashing it.
Anyway, this puts me under the radar regarding submitting a bug report,
so here I am, writing this.
I just did an apt-get upgrade in Squeeze and one of the deferred hooks
failed:
Processing triggers for initramfs-tools ...
/boot/initrd.img-26.32.5-amd64.squeeze does not exist. Cannot update.
The initrd image I have for Squeeze is "2.6.32-5-amd64.squeeze" and the
only way I can update it is to use
update-initramfs -t -u -v -k 2.6.32-5-amd64
and then rename it.
The grub.cfg entry for Squeeze is
linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/VgCompaq-squeeze
resume=/dev/mapper/VgCompaq-swap ro quiet vga=0x317
cryptopts=target=sda4_crypt,source=UUID=41d45178-c0d4-4d8f-a190-1c56b6328318,key=none,rootdev,lvm=VgCompaq-squeeze
initrd /initrd.img-2.6.32-5-amd64.squeeze
Where does the update-initramfs hook get the kernel name from?
Philip
