mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-23 10:13:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

man: fix LoaderDevicePathUUID + LoaderImageIdentifier descriptions

Browse Source 
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.
This commit is contained in:
Lennart Poettering 2024-07-15 15:48:42 +02:00
parent 66d3605896
commit 8b5ad0ba41
1 changed files with 16 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
man/systemd-boot.xml
View File

@ -429,13 +429,15 @@
<varlistentry> <varlistentry>
<term><varname>LoaderDevicePartUUID</varname></term> <term><varname>LoaderDevicePartUUID</varname></term>
<listitem><para>Contains the partition UUID of the EFI System Partition the boot loader was run from. Set by <listitem><para>Contains the partition UUID of the partition the boot loader has been started from on
the boot the current boot (usually a EFI System Partition). Set by the boot loader. (Note that
loader. <citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry> <command>systemd-stub</command> will set this too, if not set yet, to support systems that directly
uses this information to automatically find the disk booted from, in order to discover various other partitions boot into a unified kernel image, bypassing any boot loader.)
on the same disk automatically.</para> <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>
<varlistentry> <varlistentry>
@ -516,12 +518,15 @@
<varlistentry> <varlistentry>
<term><varname>LoaderImageIdentifier</varname></term> <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 <listitem><para>The file system path to the EFI executable of the boot loader for the current boot,
Partition's root directory. Set by the boot loader. Use relative to the partition's root directory (i.e. relative to the partition indicated by
<citerefentry><refentrytitle>bootctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> to view this <varname>LoaderDevicePartUUID</varname>, see above). Set by the boot loader. (Note that
data.</para> <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>
<varlistentry> <varlistentry>