Lines Matching refs:loader

19 can cooperatively manage a boot loader configuration directory, that accepts
21 between various boot loader implementations, operating systems, and userspace
23 firmware includes a boot loader. The target audience for this specification is:
25 * Boot loader developers, to write a boot loader that directly reads its
45   to fight over which boot loader becomes the primary one in possession of the
46   MBR, and only that one installation can then update the boot loader
49   loader in their own partition headers. In this new scheme as all
50   installations share a loader directory no manual configuration has to take
58 * Userspace code can sanely parse boot loader configuration which is essential
61   code can parse the boot loader configuration, too, this allows for UIs that
144 This specification defines two types of boot loader entries. The first type is
151 Not all boot loader entries will apply to all systems. For example, Type #1
155 match the local platform and what the boot loader can support, and hide them
156 from the user. Only entries matching the feature set of boot loader and system
161 this specification. This specification only defines semantics of the `/loader/`
169 if files or directories other than `/loader/` are found in the top level
178 * `$BOOT/loader/` is the directory containing all files needed for Type #1
181 * `$BOOT/loader/entries/` is the directory containing the drop-in
184 **Note:** _In all cases the `/loader/` directory should be located directly in
186 `/loader/` directory should be located directly in the root directory of the
189 Inside the `$BOOT/loader/entries/` directory each OS vendor may drop one or
198 `$BOOT/loader/entries/6a9857a393724b7a981ebb5b8495b9ea-3.8.0-2.fc19.x86_64.conf`.
201 restricted boot loader environments, and to minimize conflicting character use
217   be descriptive and does not have to be unique. If a boot loader discovers two
225   version sorts, so that the boot loader UI can determine the newest version
266   applied by the boot loader. Multiple overlays are separated by spaces and
280     # /boot/loader/entries/6a9857a393724b7a981ebb5b8495b9ea-3.8.0-2.fc19.x86_64.conf
306 read from other partitions/disks the boot loader can do this in its own native
313 are also using the /loader/entries/ directory, but place files in them that are
314 not valid by this specification. In order to minimize confusion a boot loader
315 implementation may place a file /loader/entries.srel next to the
316 /loader/entries/ directory containing the ASCII string "type1" (suffixed
327 loader, a kernel image, an initramfs image, and the kernel command line. See
351 used the same as `title` and `version` in the "boot loader specification"
361 configuration source for a boot loader. It may extend this list of entries with
368 configuration snippets, use boot-loader specific solutions for that. In the
380 simply reads all files `$BOOT/loader/entries/*.conf`, and populates its boot
386 storing away default entry information somewhere. A boot loader should
393 `$BOOT/loader/entries/xyz.conf`, with xyz as concatenation of machine id and
403 similar to a boot loader, but might apply additional filters, for example by
409 `/loader/entries/` directory in it. It then installs an appropriate boot loader
419   communicate to the boot loader the default boot loader entry temporarily or
431   previous boot loader logic was largely handled by in distribution-specific