Bug#826045: systemd: New kernels are not booted

[Andre Heider]

On 30/01/2022 21:51, Michael Biebl wrote:
> For anyone interested, I've submitted
> https://salsa.debian.org/systemd-team/systemd/-/merge_requests/138
> 
> Which also ships some very basic /etc/kernel hooks and a simplistic 
> postinst.
> 
> Would welcome feedback / follow-up fixes if needed.

That looks nice, thanks for working on this!

I'm still using the very same scripts I posted above, it's still working 
like a charm after 5 years with all the kernel updates and whatnot :)

I haven't tested your PR, and I lack the confirmed account on salsa to 
comment there, so I'll add it here, including answers to questions over 
there:

- removing sd-boot from the root fs won't render the system unbootable, 
since sd-boot needs to be installed to the efi partition. There's 
`bootctl remove` for that

- likewise with updating it. `bootctl status` reports "systemd-boot 
247.9-4" here, while the systemd package is already at 250.3-2, I'd have 
to `bootctl update` it to update it to that version

- checking if sd-boot is used can be checked via bootctl and should 
probably be used by the containing scripts instead of test -d /boot/efi:
$ bootctl is-installed; echo $?
yes
0

- contrary to the comments on salsa `kernel-install` is not part of your 
new package and I think it makes sense to move there. While it's using 
the "Boot Loader Specification", it's only used for stuff that's already 
part of this package. Even if there's a need for it without using 
sd-boot, one can install the sd-boot package without actually using it 
for booting the box (assuming the package scripts don't enforce it)

Regards,
Andre