On a given system we can have the following symlinks
/vmlinuz.old -> boot/vmlinuz-4.15.0-144-lowlatency
/vmlinuz -> boot/vmlinuz-4.15.0-144-generic
/boot/vmlinuz.old -> vmlinuz-4.15.0-144-lowlatency
/boot/vmlinuz -> vmlinuz-4.15.0-144-generic
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929255
Title:
update-initrd-links creates incorrect symlinks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
