## Boot Loader Entry Identifiers
- While boot loader entries may be named relatively freely, it's highly
- recommended to follow the following rules when picking identifiers for the
- entries, so that programs (and users) can derive basic context and meaning from
- the identifiers as passed in `LoaderEntries`, `LoaderEntryDefault`,
- `LoaderEntryOneShot`, `LoaderEntrySelected`, and possibly show nicely localized
- names for them in UIs.
+ While boot loader entries may be named relatively freely,
+ it's highly recommended to follow the following rules when picking identifiers for the entries,
+ so that programs (and users) can derive basic context and meaning from the identifiers
+ as passed in `LoaderEntries`, `LoaderEntryDefault`, `LoaderEntryOneShot`, `LoaderEntrySelected`,
+ and possibly show nicely localized names for them in UIs.
1. When boot loader entries are defined through the
- [Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/)
+ [BOOT.1 Boot Loader Specification](https://uapi-group.org/specifications/specs/boot_loader_specification/)
files, the identifier should be derived directly from the file name,
but with the `.conf` (Type #1 snippets) or `.efi` (Type #2 images)
suffix removed.