Lines Matching refs:of
15 robust, simple, works without rewriting configuration files and is free of
40 * To make the boot more robust, as no explicit rewriting of configuration files
42 * To allow an out of the box boot experience on any platform without the need
43 of traditional firmware mechanisms (e.g. BIOS calls, UEFI Boot Services)
45 to fight over which boot loader becomes the primary one in possession of the
47 configuration of it freely. Other Linux installs have to be manually
51 place, and all participants implicitly cooperate due to removal of name
53 without interfering with the entries of other installed operating systems.
56 configuration files. For the sake of uniformity, we should do the same for
64 * To unify and thus simplify configuration of the various boot loaders around,
65 which makes configuration of the boot loading process easier for users,
89 of boot options is defined on disk, and not in EFI variables alone.
104 partition with the type id of 0xEA already exists it should be used as
107 new partition with type id of 0xEA shall be created, of a suitable size
112 GUID of `bc13c2ff-59e6-4262-a352-b275fd6f7172`, already exists, it should
115 Partition (or ESP for short), i.e. a partition with GPT type UID of
129 because the mounting of `$BOOT` is then dependent on and requires the mounting
130 of the intermediate file system.
133 of a system. Instead of maintaining one `$BOOT` per installed OS (as `/boot/`
144 This specification defines two types of boot loader entries. The first type is
145 text based, very simple and suitable for a variety of firmware, architecture
148 is useful to cryptographically sign them as one file for the purpose of
156 from the user. Only entries matching the feature set of boot loader and system
160 Note that the `$BOOT` partition is not supposed to be exclusive territory of
161 this specification. This specification only defines semantics of the `/loader/`
163 ownership of the whole file system exclusively. Boot loaders, firmware, and
168 setup. Implementations of this specification must be able to operate correctly
172 multiple users of the file system unlikely.
185 the root of the file system. Specifically, if `$BOOT` is the ESP, then
186 `/loader/` directory should be located directly in the root directory of the
191 item. The file name of the file is used for identification of the boot item but
197 identifier (The ID field of `/etc/os-release`). Example:
204 ".". Also, the file names should have a length of at least one and at most 255
211 first word of a line is used as key and shall be separated by one or more
216 initialize this from the `PRETTY_NAME` of `/etc/os-release`. This name should
228 * `machine-id` shall contain the machine ID of the OS `/etc/machine-id`. This
237 from `IMAGE_ID=` or `ID=` from `/etc/os-release` of the relevant entry,
244 typically sorted by the `.conf` file name of the entry.
265 * `devicetree-overlay` refers to a list of device tree overlays that should be
307 configuration, using its own specific device path language, and this is out of
312 Unfortunately, there are implementations of boot loading infrastructure that
328 the description of the `--uefi` option in
331 extension `.efi`. Support for images of this type is of course specific to
336 Type #1 described above (but use a different file name suffix of `.efi` instead
337 of `.conf`).
339 Images of this type have the advantage that all metadata and payload that makes
341 cryptographically as one for the purpose of EFI SecureBoot.
346 * `.osrel` section with an embedded copy of the
352 entries. The `.cmdline` section is used instead of the `options` field. `linux`
356 On EFI, any such images shall be added to the list of valid boot entries.
361 configuration source for a boot loader. It may extend this list of entries with
367 operating systems in mind, starting Windows or macOS is out of focus with these
393 `$BOOT/loader/entries/xyz.conf`, with xyz as concatenation of machine id and
395 private property of the kernel package and should be removed along with it.
399 file is also private property of the kernel package and should be removed along
413 ## Out of Focus
415 There are a couple of items that are out of focus for this specification:
421 out of focus for this specification.
424 story and should probably happen outside of this specification. For example,