which is controlled by /etc/kernel-img.conf setting link_in_boot. The compiled-in default, and the setting that installers set has changed. Thus depending which release one installed either cases might be present.
And they should all work.
Testing the proposed patch:
linknames() {
tgt_kernel="$1"
echo old "initrd.img${tgt_kernel#vmlinu?}"
echo new "${tgt_kernel%/*}/initrd.img${tgt_kernel#*vmlinu?}"
}
linknames boot/vmlinuz-5.11
linknames vmlinuz-5.11
produces
old initrd.imgboot/vmlinuz-5.11
new boot/initrd.img-5.11
old initrd.img-5.11
new vmlinuz-5.11/initrd.img-5.11
meaning it fixes the case of link_in_boot = no; but regresses the link_in_boot = yes case.
On a given system we can have the following symlinks
/vmlinuz.old -> boot/vmlinuz- 4.15.0- 144-lowlatency 4.15.0- 144-generic 4.15.0- 144-lowlatency 4.15.0- 144-generic
/vmlinuz -> boot/vmlinuz-
/boot/vmlinuz.old -> vmlinuz-
/boot/vmlinuz -> vmlinuz-
which is controlled by /etc/kernel- img.conf setting link_in_boot. The compiled-in default, and the setting that installers set has changed. Thus depending which release one installed either cases might be present.
And they should all work.
Testing the proposed patch:
linknames() { img${tgt_ kernel# vmlinu? }" kernel% /*}/initrd. img${tgt_ kernel# *vmlinu? }"
tgt_kernel="$1"
echo old "initrd.
echo new "${tgt_
}
linknames boot/vmlinuz-5.11
linknames vmlinuz-5.11
produces
old initrd. imgboot/ vmlinuz- 5.11 img-5.11 5.11/initrd. img-5.11
new boot/initrd.
old initrd.img-5.11
new vmlinuz-
meaning it fixes the case of link_in_boot = no; but regresses the link_in_boot = yes case.