On Mon, 2019-07-29 at 01:38 +0200, Marc Lehmann wrote: > On Sat, Jul 27, 2019 at 11:19:06PM +0100, Ben Hutchings > <b...@decadent.org.uk> wrote: > > > images for all kernels, in 0.133, it is a nop. > > > > Not quite. In older versions, "-k all" would apply to every initramfs > > image that initramfs-tools remembered generating (as recorded in > > /var/lib/initramfs-tools). > > Well, I guess the phrase "all kernel versions known to update-initramfs" > is not very precise,e specially as it's not clear how to make kernel > versons known to it :)
I updated this wording in the latest version, to properly describe the current behaviour. > > > The reason is that get_sorted_versions now only lists kernels with > > > existing initrd images, which makes the -c option somewhat useless. > > > > Yes, though I can't see how the previous behaviour was useful either. > > Do you delete existing initramfs images, using something other than > > "update-initramfs -d", before you run "update-initramfs -k all -c"? > > Not explicitly, but the result is that the file is not there when I run the > command. > > The workaround in place now enumerates all installed kernel versions > explicitly via upsate-initramfs -c -k xxxx. I think I'll change "-k all -c" to do that. This is not exactly the same as the old behaviour, because kernel packages may explicitly disable initramfs generation during installation and initramfs-tools used to remember that. But I think it won't be too surprising that "-k all -c" really applies to all installed kernel versions in future. Ben. -- Ben Hutchings You can't have everything. Where would you put it?
signature.asc
Description: This is a digitally signed message part
