diff options
| author | Lennart Poettering <lennart@poettering.net> | 2024-07-15 15:48:42 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2024-09-11 06:47:16 +0200 |
| commit | 8b5ad0ba41dee20cf039d5fd9a4a5af05be43c96 (patch) | |
| tree | 1f8b2ccf0180bb4229b03b1692ca907cfa69fef0 /man/systemd-boot.xml | |
| parent | bootctl: show new sd-boot/sd-stub feature flags (diff) | |
| download | systemd-8b5ad0ba41dee20cf039d5fd9a4a5af05be43c96.tar.xz systemd-8b5ad0ba41dee20cf039d5fd9a4a5af05be43c96.zip | |
man: fix LoaderDevicePathUUID + LoaderImageIdentifier descriptions
First of all, these were always set, i.e. since sd-boot was merged into
our tree, i.e. v220. Let's say so explicitly.
Also, let's be more accurate, regarding which partition this referes to:
it's usually "the" ESP, but given that you can make firmware boot from
arbitrary disks, it could be any other partition too. Hence, be
explicit on this.
Also, clarify tha sd-stub will set this too, if sd-boot never set it.
Diffstat (limited to '')
| -rw-r--r-- | man/systemd-boot.xml | 27 |
1 files changed, 16 insertions, 11 deletions
diff --git a/man/systemd-boot.xml b/man/systemd-boot.xml index cc4504926c..0da919b127 100644 --- a/man/systemd-boot.xml +++ b/man/systemd-boot.xml @@ -429,13 +429,15 @@ <varlistentry> <term><varname>LoaderDevicePartUUID</varname></term> - <listitem><para>Contains the partition UUID of the EFI System Partition the boot loader was run from. Set by - the boot - loader. <citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry> - uses this information to automatically find the disk booted from, in order to discover various other partitions - on the same disk automatically.</para> + <listitem><para>Contains the partition UUID of the partition the boot loader has been started from on + the current boot (usually a EFI System Partition). Set by the boot loader. (Note that + <command>systemd-stub</command> will set this too, if not set yet, to support systems that directly + boot into a unified kernel image, bypassing any boot loader.) + <citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry> + uses this information to automatically find the disk booted from, in order to discover various other + partitions on the same disk automatically.</para> - <xi:include href="version-info.xml" xpointer="v240"/></listitem> + <xi:include href="version-info.xml" xpointer="v220"/></listitem> </varlistentry> <varlistentry> @@ -516,12 +518,15 @@ <varlistentry> <term><varname>LoaderImageIdentifier</varname></term> - <listitem><para>The path of executable of the boot loader used for the current boot, relative to the EFI System - Partition's root directory. Set by the boot loader. Use - <citerefentry><refentrytitle>bootctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> to view this - data.</para> + <listitem><para>The file system path to the EFI executable of the boot loader for the current boot, + relative to the partition's root directory (i.e. relative to the partition indicated by + <varname>LoaderDevicePartUUID</varname>, see above). Set by the boot loader. (Note that + <command>systemd-stub</command> will set this too, if not set yet, to support systems that directly + boot into a unified kernel image, bypassing any boot loader.) Use + <citerefentry><refentrytitle>bootctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> to view + this data.</para> - <xi:include href="version-info.xml" xpointer="v240"/></listitem> + <xi:include href="version-info.xml" xpointer="v220"/></listitem> </varlistentry> <varlistentry> |