From 889cb0ab7539280a4069056f155ab1a233bdf0a0 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Tue, 19 Jun 2018 13:52:04 +0200 Subject: Add description of field correspondence --- doc/BOOT_LOADER_SPECIFICATION.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/BOOT_LOADER_SPECIFICATION.md b/doc/BOOT_LOADER_SPECIFICATION.md index 7c48b83aea..d31bd341f7 100644 --- a/doc/BOOT_LOADER_SPECIFICATION.md +++ b/doc/BOOT_LOADER_SPECIFICATION.md @@ -91,8 +91,10 @@ A unified kernel image is a single UEFI executable combining an UEFI stub loader A valid unified kernel image must contain two PE sections: -* `.osrel` section with an embedded copy of the [os-release](https://www.freedesktop.org/software/systemd/man/os-release.html) file describing the image * `.cmdline` section with the kernel command line +* `.osrel` section with an embedded copy of the [os-release](https://www.freedesktop.org/software/systemd/man/os-release.html) file describing the image + +The `PRETTY_NAME=` and `VERSION_ID=` fields in the embedded os-release file are used the same as `title` and `version` in the "boot loader specification" entries. The `.cmdline` section is used instead of the `options` field. `linux` and `initrd` fields are not necessary, and there is no counterpart for the `machine-id` field. Any such images shall be added to the list of valid boot entries. -- cgit v1.2.3