I’ve been testing EOS, and I have a KVM with 3 EOS installs on one disk.
Systemd-boot is using EndeavourOS as the title for each loader entry, and sort-key prefix.
With one EOS install on a disk that is fine. With 3 and 3 fallback all with the same base name it is a bit unwieldy.
I have /etc/kernel/entry-token setup, and that is working for the /efi/entry-token path for linux and initrds, and this has the nice property that the machine-id string disappears from my /efi, replaced by my install instance name/hostname from the entry-token.
For multiple installs I think entry-token would be a better title and sort-key prefix, and I already have it in the file system, and kernel-install uses it, but seems like /etc/kernel/install.d/90-loaderentry.install would need to change to accommodate that, and maybe kernel-install too, and maybe 90*fallback too, I haven’t perused sort-key much as yet.
@dalto as the owner of the package is that interesting to you, me hacking the package a bit and sending you a PR, for a what is I’m sure a very edge case?
The other way I thought was maybe just creating a local 91-loaderentry-hack.install and hacking the already built entries with sed -i? Can be simple, and local system only hack.
Does anyone have any other ideas how to accomplish this with minimal impact and maximum supportability. I generally like to just drop files in place via ansible, so the 91 option appeals.
I looked at the EOS wiki and Arch wiki, and found nothing at this level of detail