Skip to content

Add profile reference in the Bootloader spec #165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
poettering merged 1 commit into from
Oct 13, 2025
Merged

Add profile reference in the Bootloader spec #165

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions specs/boot_loader_specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -335,6 +335,13 @@ The following keys are recognized:

Example: `architecture aa64`

* `profile` refers to the profile number to use in multi-profile EFI programs.
See the section `multi-profile UKIs` in [the UKI Specification](unified_kernel_image.md)
for more information.
Comment thread
Itxaka marked this conversation as resolved.
This should only be used when `uki` or `uki-url` is set to a multi-profile UKI. Behaviour is undefined for any other cases.
Copy link
Copy Markdown
Member

@behrmann behrmann Sep 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@poettering Is "undefined" the best way to go here? "implementation-defined" might do the same and be more easier understood by readers, but I maybe we can just define a reasonable semantic here so that people always know what will happen.

Copy link
Copy Markdown
Collaborator

@poettering poettering Oct 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "undefined" is ok'ish. I think it makes sense to allow implementations to either ignore the field in this case or generate error or warning. "undefined" seems ok.


Example: `profile 1`

Each boot loader menu entry drop-in snippet must include at least a `linux` or an `efi`
key. Here is an example for a complete drop-in file:

Expand Down