On Sat, 26 Dec 2020 22:48:54 -0500, Walter Dnes wrote: > I've got two scripts in /usr/src that I run from /usr/src/linux. > The script "makeover" is run just after "make menuconfig" and > includes (amongst other things) > > make && \ > make modules_install && \ > cp arch/x86_64/boot/bzImage /boot/kernel.experimental && \ > cp System.map /boot/System.map.experimental && \ > cp .config /boot/config.experimental && \
> Obviously won't need the "lilo" command. Replace all references to > "/boot" with "/boot/EFI" and the kernels go to /boot/EFI which leaves > just the question of how to set up grub. Kernels still go to /boot if you are using a boot manager. > I'd like a text-based menu > that defaults to the production kernel if no keypress after 15 seconds. > Question: does grub have to be re-run or otherwise re-initialised when > I overwrite a kernel with a newer one of the same name? No. I understand why someone used to GRUB would want to continue with it on a UEFI system, but you have no experience of it so why are you picking the boot manager that is hardest to configure, not to mention the most bloated? Referencing your sig, GRUB is the desktop environment of boot managers, the boot loader equivalent of emacs :) -- Neil Bothwick One-seventh of life is spent on Monday.
pgpjY4sJcPT9l.pgp
Description: OpenPGP digital signature
