On Tuesday, 22 October 2019 10:09:53 BST Neil Bothwick wrote: > On 22 October 2019 08:58:01 BST, Mick <michaelkintz...@gmail.com> wrote:
> >With manual copying/naming of kernels I can overwrite any non-booting > >kernels > >with the latest compiled example, without moving links around. What is > >the > >recommended solution to the above problem? > > Be more careful when configuring your kernels ;} Yes, that would be advisable. :-) TBH I have not had a non-booting kernel for some time now, but you never know what might bite you at the next turn. On new machines it could take a few kernel rebuilds before I end up with an optimal configuration, but once the kernel recipe for a particular system settles I do not as a rule experience any major problems. > I haven't used the symlink approach for some time. I use a script to > generate the entries for GRUB or systemd-boot. As I use a script to build > and install the kernel in the first place, there are no extra steps as one > script calls the other. I think I'll carry on with my manual kernel copying and naming approach. On modern UEFI machines I run efibootmgr to add/delete kernels and do not use a separate boot manager, or initrd images. So, it's not as if I have to automate what is already a rather simpler approach to upgrading kernels. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
