Bug 1198618 - systemd-boot: openSUSE branding
Summary: systemd-boot: openSUSE branding
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: systemd maintainers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 1198583
  Show dependency treegraph
 
Reported: 2022-04-19 12:03 UTC by Ludwig Nussel
Modified: 2022-11-09 15:23 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ludwig Nussel 2022-04-19 12:03:46 UTC
systemd-boot calls itself "Linux Boot Manager". Maybe it should brand itself according to /etc/os-release. Upstream issue:
https://github.com/systemd/systemd/issues/17044
Comment 1 Ludwig Nussel 2022-04-20 08:56:50 UTC
the subdirectory on the ESP is also "systemd", should be opensuse probably
Comment 2 Franck Bui 2022-11-07 17:38:03 UTC
(In reply to Ludwig Nussel from comment #0)
> systemd-boot calls itself "Linux Boot Manager". Maybe it should brand itself
> according to /etc/os-release. Upstream issue:
> https://github.com/systemd/systemd/issues/17044

This seems to have been addressed by the introduction of the new option "--efi-boot-option-description=", which should be available when v252 will be released (hopefully soon).

Note that according to the man page, there is usually no need to change the description "Linux Boot Manager" though.

Ludwig are you OK to close this report ?
Comment 3 Franck Bui 2022-11-07 17:41:01 UTC
(In reply to Ludwig Nussel from comment #1)
> the subdirectory on the ESP is also "systemd", should be opensuse probably

It should be possible with "--entry-token=" (available since v251).

Actually I just did the test with v252 and couldn't find "systemd". By default $machine-id is created.
Comment 4 Ludwig Nussel 2022-11-08 13:29:38 UTC
(In reply to Franck Bui from comment #2)
> (In reply to Ludwig Nussel from comment #0)
> > systemd-boot calls itself "Linux Boot Manager". Maybe it should brand itself
> > according to /etc/os-release. Upstream issue:
> > https://github.com/systemd/systemd/issues/17044
> 
> This seems to have been addressed by the introduction of the new option
> "--efi-boot-option-description=", which should be available when v252 will
> be released (hopefully soon).

That helps if you call it manually maybe. I assume the distro will call bootctl install unattended somehow. Eg after package installation to update the bootloader. So it somehow has to remember what to pass. Therefore either a config file is needed or a different value has to be built in.
 
> Note that according to the man page, there is usually no need to change the
> description "Linux Boot Manager" though.

Well, upstream thinks there's only one instance of sd-boot. In practice it's installed by a specific distribution so in the end different distros will again compete about that entry. So IMO we should still label that with openSUSE.

> Ludwig are you OK to close this report ?

I'd like to keep this open to track the missing feature.
Comment 5 Ludwig Nussel 2022-11-08 13:30:24 UTC
(In reply to Franck Bui from comment #3)
> (In reply to Ludwig Nussel from comment #1)
> > the subdirectory on the ESP is also "systemd", should be opensuse probably
> 
> It should be possible with "--entry-token=" (available since v251).
> 
> Actually I just did the test with v252 and couldn't find "systemd". By
> default $machine-id is created.

machine id is used for the location where kernels are stored. systemd-boot installs itself as EFI/systemd/systemd-bootx64.efi
Comment 6 Franck Bui 2022-11-09 15:23:29 UTC
(In reply to Ludwig Nussel from comment #4)
> Well, upstream thinks there's only one instance of sd-boot. In practice it's
> installed by a specific distribution so in the end different distros will
> again compete about that entry. So IMO we should still label that with
> openSUSE.

Then can you please start a discussion on this topic with upstream ?

Otherwise I fear that your feature request won't be addressed, especially since BZ is supposed to track issues only.

Thanks.