as per:
https://titlecase.com/
same scheme can be used to prepare OS media for cases where the firmware
includes a boot loader.
same scheme can be used to prepare OS media for cases where the firmware
includes a boot loader.
The target audience for this specification is:
The target audience for this specification is:
* UI developers, to implement user interfaces that list and select among the
available boot options
* UI developers, to implement user interfaces that list and select among the
available boot options
Everything described below is located on one or two partitions. The boot loader
or user-space programs reading the boot loader configuration should locate them
Everything described below is located on one or two partitions. The boot loader
or user-space programs reading the boot loader configuration should locate them
features such as symlinks, hardlinks, access control or case sensitivity are
supported.
features such as symlinks, hardlinks, access control or case sensitivity are
supported.
This specification defines two types of boot loader entries. The first type is
text based, very simple, and suitable for a variety of firmware, architecture
This specification defines two types of boot loader entries. The first type is
text based, very simple, and suitable for a variety of firmware, architecture
On EFI, any such images shall be added to the list of valid boot entries.
On EFI, any such images shall be added to the list of valid boot entries.
Note that these configurations snippets do not need to be the only
configuration source for a boot loader. It may extend this list of entries with
Note that these configurations snippets do not need to be the only
configuration source for a boot loader. It may extend this list of entries with
-## Locating boot entries
+## Locating Boot Entries
A _boot loader_ locates `$BOOT` and `$XBOOTLDR`, then simply reads all the
files `$BOOT/loader/entries/*.conf` and `$XBOOTLDR/loader/entries/*.conf`, and
A _boot loader_ locates `$BOOT` and `$XBOOTLDR`, then simply reads all the
files `$BOOT/loader/entries/*.conf` and `$XBOOTLDR/loader/entries/*.conf`, and
have multiple such boot entries that differ only by the boot counting data, we
would sort them by `n`._
have multiple such boot entries that differ only by the boot counting data, we
would sort them by `n`._
-### Alphanumerical order
+### Alphanumerical Order
Free-form strings and machine IDs should be compared using a method equivalent
to [strcmp(3)](https://man7.org/linux/man-pages/man3/strcmp.3.html) on their
UTF-8 representations. If just one of the strings is unspecified or empty, it
compares lower. If both strings are unspecified or empty, they compare equal.
Free-form strings and machine IDs should be compared using a method equivalent
to [strcmp(3)](https://man7.org/linux/man-pages/man3/strcmp.3.html) on their
UTF-8 representations. If just one of the strings is unspecified or empty, it
compares lower. If both strings are unspecified or empty, they compare equal.
The following method should be used to compare version strings. The algorithm
is based on rpm's `rpmvercmp()`, but not identical.
The following method should be used to compare version strings. The algorithm
is based on rpm's `rpmvercmp()`, but not identical.