On Saturday, 26 October 2019 17:31:28 GMT Mick wrote: > If your intention is to use systemd- boot as the Boot Manager of choice, I > would try moving all kernels and associated files to your /boot/<machine- > id>/ subdirectory. > > Then create corresponding /boot/loader/entries/*.conf files, which according > to the systemd boot loader specification should be named like so: > > /boot/loader/entries/4eec63dc92f83de25e1e2e485d7f6536-4.19.72-gentoo.conf > > /boot/loader/entries/<machine-id>-<kernel_version>.<os-release-ID>.conf > > For <kernel_version> use the output of 'uname -r'. > > For <os-release-ID> use the ID field of /etc/os-release. You may 'find > uname -r' and os-release-ID are the same on your Gentoo installation. > > The contents of the file should look like so: > > title 08-gentoo-4.19.72-rescue (My rescue kernel) > version 4.19.72-gentoo > machine-id 4eec63dc92f83de25e1e2e485d7f6536 > options root=/dev/nvme0n1p4 net.ifnames=0 > architecture x64 > linux /4eec63dc92f83de25e1e2e485d7f6536/4.19.72-gentoo/linux > initrd /4eec63dc92f83de25e1e2e485d7f6536/4.19.72-gentoo/initrd > > For 'title' you can use the PRETTY_NAME in /etc/os-release, or whatever you > want displayed in the boot menu to differentiate visibly this menu entry > from all others. > > For 'version' you can use the kernel version you want to boot with, but it > is an optional field. > > Machine-id is also optional, but it helps to differentiate between various > installations. > > 'linux' and 'initrd' fields show the relative path(s) where your vmlinuz and > initrd.img files are stored. > > I hope the above works for you with systemd-boot and helps customise its > boot menu to your liking.
Thanks for the advice. I've also read the Boot Loader Specification [1] :) The scheme you and it outline seem not to allow me to create menu entries that use the same kernel but with different options, such as run level. That's one reason why I didn't use that approach. The other was its reader- unfriendliness - why use a simple, descriptive name when you could use a 32- digit hex string instead? I may come back with other ideas or problems later... 1. https://systemd.io/BOOT_LOADER_SPECIFICATION.html -- Regards, Peter.
