On 22 October 2019 08:58:01 BST, Mick <michaelkintz...@gmail.com> wrote: >On Tuesday, 22 October 2019 00:44:00 BST Neil Bothwick wrote: >> On Tue, 22 Oct 2019 00:42:25 +0100, Neil Bothwick wrote: >> > make install will create symlinks for vmlinuz and vmlinuz.old to >the >> > latest and previous kernel, doing much of what you need. You need >/boot >> > to be on a filesystem that supports symlinks and ISTR that it only >> > updates the symlinks if already present but doesn't create them >from >> > scratch. >> >> I think you need sys-apps/debianutils installed too. > >Last time I used this symlink-ing approach to vmlinuz I came across a >problem, >which I didn't have time to resolve and went back to my manual approach >of >copying kernels into /boot: > >I eagerly compile a new kernel. It is installed/copied into vmlinuz >and its >predecessor which worked fine is copied into vmlimuz.old. I try to >boot it >and discover I didn't configure it as carefully as I should have done - >it >won't boot. I boot into vmlinuz.old and reconfigure the kernel, which >is now >installed into vmlinuz and the recently configured and non-booting >kernel is >copied into vmlinuz.old. Disaster strikes as the newly reconfigured >kernel >won't boot either! I now have two recently configured and non-booting >kernels >vmlinuz and vmlinuz.old and no other working kernel to boot with. > >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 ;} 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. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
