Skip to content

BLS: say that initrd may be split at whitespace for compat #163

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

BLS: say that initrd may be split at whitespace for compat #163

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
11 changes: 8 additions & 3 deletions specs/boot_loader_specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,13 +264,18 @@ The following keys are recognized:

Example: `linux /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/linux`

* `initrd` specifies the initrd to use when executing the kernel (`cpio` image).
The value is a path relative to the root of the file system
containing the boot entry snippet itself.
* `initrd` specifies an initrd to use when executing the kernel (`cpio` image).
The value is a path
relative to the root of the file system containing the boot entry snippet itself.
This key may appear more than once,
in which case all specified images are used,
in the order they are listed.

To increase robustness,
an implementation *should* split the path at whitespace
and treat each part as a separate path.
A warning *should* be emitted in that case.

Example:

initrd /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/initrd
Expand Down