vmlinuz and init.img sys links

[vinnywright]

it appears during the do-release-upgrade the location of the system links "/vmlinuz and /init.img got changed .

from /var/log/dist-upgrade/20191019-1925/apt.term.log

Setting up linux-image-5.0.0-32-generic (5.0.0-32.34) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.15.0-38-generic
I: /initrd.img.old is now a symlink to boot/initrd.img-4.15.0-38-generic
I: /vmlinuz is now a symlink to boot/vmlinuz-5.0.0-32-generic
I: /initrd.img is now a symlink to boot/initrd.img-5.0.0-32-generic

this brakes my custom boot entry for this SSD that uses the /system links , I can boot the new kernels that get installed but I half to press "e" at the grub prompt to hand edit the boot lines to point to /boot , not a big deal BUT , why

it happens as regular occurrence now

from /var/log/apt/term.log

I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.3.0-18-generic
I: /boot/initrd.img.old is now a symlink to initrd.img-5.3.0-18-generic
I: /boot/vmlinuz is now a symlink to vmlinuz-5.3.0-19-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.3.0-19-generic

I have not been able to figure out why this is happening , the system links being put in /boot instead of /

do any of yall have a clue ?

VINNY

[jlittle]

Thank you for that heads up, Vinny. My release upgrade to eoan sailed past that one thanks to the warning.
The links are indeed in /boot, which is IMO cleaner and simpler.

[vinnywright]

ya , I just changed my custom menu entry to point to those , that install I referenced in the OP has no grub installed and is on a hole disk BTRFS filesystem so grubs OS-prober on the install that controls/has grub dose not see it .

why for years and years and years of placing the system links in / it suddenly changes now is the question , change for the sake of change maybe.

just like /mnt , for ever the place for user mounts , now we have things auto mounting to /media , change for the sake of change.

VINNY