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

2023-02-12 Thread Luca Boccassi
On Sun, 12 Feb 2023 12:40:55 + Luca Boccassi 
wrote:
> On Sun, 12 Feb 2023 12:40:19 +0100 Marco d'Itri  wrote:
> > Also: at least we need to run "bootctl update" on package updates.
> 
> Ah good point, completely forgot about this, will send a MR.

https://salsa.debian.org/systemd-team/systemd/-/merge_requests/191

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


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

2023-02-12 Thread Luca Boccassi
On Sun, 12 Feb 2023 12:40:19 +0100 Marco d'Itri  wrote:
> On Feb 12, Michael Biebl  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?

I agree, we should just make it enable itself on install, like we did
for systemd-resolved. It's a separate package, not pulled in by
anything - if you install it, it means you want to use it.
It's been available in testing for a while, and apart from a few fixes
for the scripts at the beginning, there's been no complaints so far.

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

Ah good point, completely forgot about this, will send a MR.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part


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

2023-02-12 Thread Marco d'Itri
On Feb 12, Michael Biebl  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


signature.asc
Description: PGP signature


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

2023-02-12 Thread Michael Biebl

Control: tags -1 + moreinfo
Control: severity -1 + wishlist

Am 12.02.23 um 02:29 schrieb Marco d'Itri:

Package: systemd-boot
Version: 252.5-2
Severity: normal

systemd-boot.postinst should create boot loader entries for the
currently installed kernels.

Something like this should work:

for kernel in /boot/vmlinuz-*; do
   kernel-install add "${kernel#*/vmlinuz-}" "$kernel"
done



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.


See also

https://salsa.debian.org/systemd-team/systemd/-/merge_requests/138#note_299022


https://salsa.debian.org/systemd-team/systemd/-/merge_requests/138/diffs?commit_id=6f8062cbb37508fe386da500f99d2e7313390c80


OpenPGP_signature
Description: OpenPGP digital signature


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

2023-02-11 Thread Marco d'Itri
Package: systemd-boot
Version: 252.5-2
Severity: normal

systemd-boot.postinst should create boot loader entries for the 
currently installed kernels.

Something like this should work:

for kernel in /boot/vmlinuz-*; do
  kernel-install add "${kernel#*/vmlinuz-}" "$kernel"
done

-- 
ciao,
Marco


signature.asc
Description: PGP signature