From fdd193ff22a07053a20780ea141acfd82808bcd5 Mon Sep 17 00:00:00 2001 From: WilliButz Date: Thu, 1 Oct 2026 16:09:16 +0200 Subject: [PATCH] docs: mention LoaderInfo efivar in BLI (cherry picked from commit cfb11e1feb3c944fb0274c8a326a55b406f09582) --- docs/BOOT_LOADER_INTERFACE.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/BOOT_LOADER_INTERFACE.md b/docs/BOOT_LOADER_INTERFACE.md index efe5c1cce2..a3a79bbf86 100644 --- a/docs/BOOT_LOADER_INTERFACE.md +++ b/docs/BOOT_LOADER_INTERFACE.md @@ -197,6 +197,10 @@ Variables will be listed below using the Linux efivarfs naming, first sets the variable, and its presence suppresses a second measurement of the same data into the same PCR during the same boot. +* The EFI variable `LoaderInfo-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f` + contains the version string of the boot loader that was booted, + e.g. `systemd-boot 262`. It is formatted as a NUL-terminated UTF-16 string. + If `LoaderTimeInitUSec` and `LoaderTimeExecUSec` are set, `systemd-analyze` will include them in its boot-time analysis. If `LoaderDevicePartUUID` is set, systemd will mount the ESP that was used for the boot to `/boot`, but only if