| 1 |
On Saturday, 26 October 2019 17:31:28 GMT Mick wrote: |
| 2 |
|
| 3 |
> If your intention is to use systemd- boot as the Boot Manager of choice, I |
| 4 |
> would try moving all kernels and associated files to your /boot/<machine- |
| 5 |
> id>/ subdirectory. |
| 6 |
> |
| 7 |
> Then create corresponding /boot/loader/entries/*.conf files, which according |
| 8 |
> to the systemd boot loader specification should be named like so: |
| 9 |
> |
| 10 |
> /boot/loader/entries/4eec63dc92f83de25e1e2e485d7f6536-4.19.72-gentoo.conf |
| 11 |
> |
| 12 |
> /boot/loader/entries/<machine-id>-<kernel_version>.<os-release-ID>.conf |
| 13 |
> |
| 14 |
> For <kernel_version> use the output of 'uname -r'. |
| 15 |
> |
| 16 |
> For <os-release-ID> use the ID field of /etc/os-release. You may 'find |
| 17 |
> uname -r' and os-release-ID are the same on your Gentoo installation. |
| 18 |
> |
| 19 |
> The contents of the file should look like so: |
| 20 |
> |
| 21 |
> title 08-gentoo-4.19.72-rescue (My rescue kernel) |
| 22 |
> version 4.19.72-gentoo |
| 23 |
> machine-id 4eec63dc92f83de25e1e2e485d7f6536 |
| 24 |
> options root=/dev/nvme0n1p4 net.ifnames=0 |
| 25 |
> architecture x64 |
| 26 |
> linux /4eec63dc92f83de25e1e2e485d7f6536/4.19.72-gentoo/linux |
| 27 |
> initrd /4eec63dc92f83de25e1e2e485d7f6536/4.19.72-gentoo/initrd |
| 28 |
> |
| 29 |
> For 'title' you can use the PRETTY_NAME in /etc/os-release, or whatever you |
| 30 |
> want displayed in the boot menu to differentiate visibly this menu entry |
| 31 |
> from all others. |
| 32 |
> |
| 33 |
> For 'version' you can use the kernel version you want to boot with, but it |
| 34 |
> is an optional field. |
| 35 |
> |
| 36 |
> Machine-id is also optional, but it helps to differentiate between various |
| 37 |
> installations. |
| 38 |
> |
| 39 |
> 'linux' and 'initrd' fields show the relative path(s) where your vmlinuz and |
| 40 |
> initrd.img files are stored. |
| 41 |
> |
| 42 |
> I hope the above works for you with systemd-boot and helps customise its |
| 43 |
> boot menu to your liking. |
| 44 |
|
| 45 |
Thanks for the advice. I've also read the Boot Loader Specification [1] :) |
| 46 |
|
| 47 |
The scheme you and it outline seem not to allow me to create menu entries |
| 48 |
that use the same kernel but with different options, such as run level. That's |
| 49 |
one reason why I didn't use that approach. The other was its reader- |
| 50 |
unfriendliness - why use a simple, descriptive name when you could use a 32- |
| 51 |
digit hex string instead? |
| 52 |
|
| 53 |
I may come back with other ideas or problems later... |
| 54 |
|
| 55 |
1. https://systemd.io/BOOT_LOADER_SPECIFICATION.html |
| 56 |
|
| 57 |
-- |
| 58 |
Regards, |
| 59 |
Peter. |
Archives