From ef4976dc25a57ca4836a2937ba35bd5f7d487397 Mon Sep 17 00:00:00 2001 From: Emil Velikov Date: Mon, 2 Oct 2023 17:56:42 +0100 Subject: [PATCH] man: document LoaderEntryLastBooted The option was introduced with systemd v250 although it went undocumented. It effectively sits between Default and OneShot, in term of priority. It is repeatedly updated as long as loader.conf default is "@saved" and the OneShot is not set. v2: - squash some typos v3: - special mention to default @saved + loader.conf reference - reword update side, to avoid misleading that it's needlessly overwritten Signed-off-by: Emil Velikov --- man/systemd-boot.xml | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml index 67208806f97..b6efd8927c9 100644 --- a/man/systemd-boot.xml +++ b/man/systemd-boot.xml @@ -461,6 +461,27 @@ + + LoaderEntryLastBooted + + The identifier of the boot loader entry last attempted. Set and read by the boot loader, + only when /loader/loader.conf has default set to @saved. See + loader.conf5. + + The boot loader will ensure LoaderEntryLastBooted is up-to date for every boot, + updating it as needed and will omit changing it all together when LoaderEntryOneShot + is set. + + The boot loader reads the variable, which takes higher priority than + LoaderEntryDefault. The variable is ignored when LoaderEntryOneShot + is set. + + LoaderEntryLastBooted cannot be used as indication that the last boot was + successful or not. + + + + LoaderEntrySelected -- 2.47.3