Bugzilla – Bug 1198598
systemd-boot: shim installation
Last modified: 2023-04-28 10:21:42 UTC
`bootctl install` currently only installs systemd-boot into the efi partition. If we want to be able to boot on systems that only have the MS cert we'd need bootctl to also take care of shim somehow. Shim currently hardcodes grub.efi so systemd-boot would have to be installed with that name or shim needs adjustments. Probably discussion with upstream needed.
Upstream discussion for supporting multiple second stage loaders: RFE: add support for multiple second stage loaders https://github.com/rhboot/shim/issues/472
So as far I understood this should be "fixed" by adding support for multiple boot loader in shim, right ? If so, Joey, can you take this bug over ?
well, bootctl install would have to copy shim in any case which it currently does not. With the current shim sd-boot would have to install itself as grub.efi but that's cosmetics until alternative names are implemented
I will continue to watch the status on shim upstream.
Getting bootctl install to actually also install shim may take a bit. Maybe we need to disable bootctl install and just use a script for now https://github.com/systemd/systemd/issues/27234 https://github.com/systemd/systemd/pull/27322 What's the status about shim not hardcoding grub.efi though? Any chance to get that fixed?
(In reply to Ludwig Nussel from comment #5) > Getting bootctl install to actually also install shim may take a bit. Maybe > we need to disable bootctl install and just use a script for now > > https://github.com/systemd/systemd/issues/27234 > https://github.com/systemd/systemd/pull/27322 > > What's the status about shim not hardcoding grub.efi though? Any chance to > get that fixed? Unfortunately no news on supporting multiple boot loaders. Peter Jones is open on this topic on upstream. But currently no definite design and no code. At least it's not public. Dennis and me will try to reactivate the topic on upstream.