From: Luca Boccassi <bluca@debian.org>
Date: Wed, 17 Dec 2025 23:00:59 +0000 (+0000)
Subject: Boot loader menu docs and tweaks (#39842)
X-Git-Tag: v259~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b262ded0bd4b3628c84bdf42f8d47b368646d4d0;p=thirdparty%2Fsystemd.git

Boot loader menu docs and tweaks (#39842)
---

b262ded0bd4b3628c84bdf42f8d47b368646d4d0
diff --cc docs/BOOT_LOADER_INTERFACE.md
index 82dd534a657,659c6ce195e..37ec443d9db
--- a/docs/BOOT_LOADER_INTERFACE.md
+++ b/docs/BOOT_LOADER_INTERFACE.md
@@@ -128,15 -165,14 +165,14 @@@ variables
  
  ## 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.