On Mo, 06.05.19 09:20, Dridi Boukelmoune (dridi.boukelmoune(a)gmail.com) wrote:
On Sun, May 5, 2019 at 1:45 PM Zbigniew Jędrzejewski-Szmek
<zbyszek(a)in.waw.pl> wrote:
<snip>
> This makes the assumption, which was also made earlier in the thread,
> that it's somehow impossible to check what bootloader is installed.
> Why? My bootloader is happy to tell me its version:
> $ bootctl
> ...
> Current Boot Loader:
> Product: systemd-boot 241-565-g43d51bb
> Features: ✓ Boot counting
> ✓ Menu timeout control
> ✓ One-shot menu timeout control
> ✓ Default entry control
> ✓ One-shot entry control
> File: /EFI/systemd/systemd-bootx64.efi
> ...
> Nowadays it's gives the exact git commit it's built from, in the past
> it was just the release version, but either is enough. Therefore
> 'bootctl update' can fairly reliably *update*, i.e. do the installation
> if the thing we have is newer than the version already installed.
That's news to me, and unfortunately it doesn't look as nifty on my system:
...
Current Boot Loader:
Product: n/a
Features: ✗ Boot counting
✗ Menu timeout control
✗ One-shot menu timeout control
✗ Default entry control
✗ One-shot entry control
ESP: n/a
File: └─n/a
That only works properly on distros that implement the boot loader
spec and the boot loader interface properly:
https://systemd.io/BOOT_LOADER_SPECIFICATION
https://systemd.io/BOOT_LOADER_INTERFACE
Unfortunately, Fedora/grub do not support either.
(Which is a pity of course, since it also means there's no working
"systemctl --boot-loader-entry=" support in Fedora, nor "sytemctl
kexec" support).
Lennart
--
Lennart Poettering, Berlin