summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatthew Garrett <matthew.garrett@nebula.com>2014-07-09 13:54:48 -0400
committerMatthew Garrett <matthew.garrett@nebula.com>2014-07-09 14:13:15 -0400
commit3bbf87315a2d77bfc0a657389c7e2f626d9a5f1e (patch)
tree7ccf1f9493c0921616c11db7816b5a4458aec4fc
parent38b7338aa5baa4b17c8e82c0b31ddc8cc4bbc442 (diff)
Provide guidance on naming of chainload fragments
OS installers may want to create fragments to permit the chainloading of other operating systems, but ideally only one such fragment will exist for each target no matter how many operating systems are installed. Provide some guidance on consistent naming.
-rw-r--r--MatthewGarrett/BootLoaderSpec.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/MatthewGarrett/BootLoaderSpec.mdwn b/MatthewGarrett/BootLoaderSpec.mdwn
index 2944c36a..ca6ea377 100644
--- a/MatthewGarrett/BootLoaderSpec.mdwn
+++ b/MatthewGarrett/BootLoaderSpec.mdwn
@@ -134,7 +134,7 @@ A _kernel installer package_ installs the kernel and initrd images to either `$B
A _UI application_ intended to show available boot options shall operate similar to a boot loader, but might apply additional filters, for example by filtering out the booted OS via the machine ID, or by suppressing all but the newest kernel versions.
-An _OS installer_ picks the right place for `$BOOT` as defined above (possibly creating a partition and file system for it), and pre-creates the `/org/freedesktop/bls/entries/` directory in it. It then installs an appropriate boot loader that can read these snippets. Finally it installs one or more kernel packages. On POSIX-style operating systems, $BOOT must be accessible via /boot/bls - this may be either a mountpoint or a symlink (eg, /boot/bls may be a symlink to /boot/efi)
+An _OS installer_ picks the right place for `$BOOT` as defined above (possibly creating a partition and file system for it), and pre-creates the `/org/freedesktop/bls/entries/` directory in it. It then installs an appropriate boot loader that can read these snippets. Finally it installs one or more kernel packages. On POSIX-style operating systems, $BOOT must be accessible via /boot/bls - this may be either a mountpoint or a symlink (eg, /boot/bls may be a symlink to /boot/efi). It is acceptable to create boot fragments to chainload operating systems that are unaware of this specification. Such entries should be created using a consistent naming scheme that does not embed the machine-id - for example, use the OS name followed by the chained filesystem ID (eg, macosx-9004e695-2e0f-4230-9a9e-e90bb1e88e17.conf) or "ESP" in the case of $BOOT (eg, ubuntu-ESP.conf).
## Out of Focus