Bug#1031118: systemd-boot should create boot loader entries for the installed kernels

[Marco d'Itri]

On Feb 12, Michael Biebl <biebl at debian.org> wrote:

> I think this only makes sense if systemd-boot is actually the active
> bootloader, which is why the existing hook scripts also have a "bootctl
> is-installed --quiet || exit 0" check.
I think that you are right, but then we currently have a significant 
usability problem because "bootctl install" does not generate the 
configuration by itself.

Are there still any reasons at this point why systemd-boot should not be 
enabled if the package is installed?
What grub does is ask a debconf question, but is there any NEED to 
actually ask a debconf question, considering that we do not have all the 
complexity of BIOS systems anymore and bootctl can automatically figure 
where sd-boot needs to be installed?

Also: at least we need to run "bootctl update" on package updates.

-- 
ciao,
Marco
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20230212/8644c9b0/attachment.sig>