On Sun 01 Mar 2020 at 08:41:09 -0500, Felix Miata wrote: > Brian composed on 2020-03-01 13:26 (UTC): > > > On Sat 29 Feb 2020 at 19:15:12 -0600, David Wright wrote: > > >> On Sat 29 Feb 2020 at 19:17:39 (+0100), Mikhail Morfikov wrote: > > >>> # ls -al / > >>> ... > >>> lrwxrwxrwx 1 root root 29 2020-02-14 17:22:18 initrd.img -> > >>> boot/initrd.img-5.4.0-4-amd64 > >>> lrwxrwxrwx 1 root root 27 2020-02-24 00:37:53 initrd.img.old -> > >>> boot/initrd.img-5.5.4-amd64 > >>> ... > >>> lrwxrwxrwx 1 root root 26 2020-02-14 17:22:18 vmlinuz -> > >>> boot/vmlinuz-5.4.0-4-amd64 > >>> lrwxrwxrwx 1 root root 24 2020-02-24 00:37:53 vmlinuz.old -> > >>> boot/vmlinuz-5.5.4-amd64 > > >>> So I have a question here: what's the purpose of the links? > > >> They're a convenience. If you want them kept in /boot, then edit > >> /etc/kernel-img.conf and linux-update-symlinks will recreate them > >> there when the kernel is updated. Ditto if you want them removed. > > > They are also useful to reference on the linux and initrd lines when > > booting with GRUB to rescue a system. I'd leave them there. > > + + + :-) > > Grub does not like symlinks to un-versioned kernel and initrd in /boot/.
I am probably missing your point but I have just booted successfully with: root='hd1,msdos5' linux /vmlinuz.old root=/dev/sdb5 initrd /initrd.img.old -- Brian.
