Lines Matching refs:it
47 configuration of it freely. Other Linux installs have to be manually
75 system, it provides a boot options logic that can offer similar
76 functionality. Here's why we think that it is not enough for our uses:
85 menu item information on disk, it is always available, regardless if the BIOS
104 partition with the type id of 0xEA already exists it should be used as
108 (let's say 500MB), and it should be used as `$BOOT`.
112 GUID of `bc13c2ff-59e6-4262-a352-b275fd6f7172`, already exists, it should
117 (let's say 250MB) and otherwise qualifies, it should be used as `$BOOT`.
162 directory inside the file system (see below), but it doesn't intend to define
194 installations. More specifically it is suggested to include the machine ID
218 entries with the same title it is a good idea to show more than just the raw
226 easily and show it first or preselect it automatically. This field is
238 possibly suffixed. This field is optional. If set, it is used as primary
291 increase compatibility with EFI systems it is highly recommended only to
295 Conversely, in order to increase compatibility it is recommended to install
297 i.e. it is a good idea that both images shipped as UEFI PE images and those
319 contents: if it exists and contains the mentioned string, it shall assume a
320 standards compliant implementation is in place. If it exists but contains a
321 different string it shall assume non-standard semantics are implemented. If the
381 menu with this. On EFI, it then extends this with any unified kernel images
383 example a "Reboot into firmware" option. Optionally it may sort the menu based
385 uses the file name to identify specific items, for example in case it supports
390 installer_ installs the kernel and initrd images to `$BOOT` (it is recommended
392 and then generates a configuration snippet for it, placing this in
395 private property of the kernel package and should be removed along with it.
398 installer creates the combined image and drops it into `$BOOT/EFI/Linux/`. This
400 with it.
408 creating a partition and file system for it) and pre-creates the
409 `/loader/entries/` directory in it. It then installs an appropriate boot loader
410 that can read these snippets. Finally, it installs one or more kernel packages.
426 runtime without explicit configuration (like `systemd-boot` does it), or via