dasharo/systemd
0
0
Fork 0
mirror of https://github.com/Dasharo/systemd.git synced 2026-03-06 15:02:31 -08:00
Code Issues Packages Projects Releases Wiki Activity

man: add version info

Browse Source 
This tries to add information about when each option was added. It goes
back to version 183.

The version info is included from a separate file to allow generating it,
which would allow more control on the formatting of the final output.
This commit is contained in:
Abderrahim Kitouni
2023-08-22 17:52:36 +01:00
parent 4623eecb2f
commit ec07c3c80b
197 changed files with 6649 additions and 1529 deletions
Download Patch File Download Diff File Expand all files Collapse all files

68
man/bootctl.xml
View File

@@ -67,7 +67,9 @@
<para>Hint: use <command>systemctl reboot --firmware-setup</command> to reboot into firmware setup
once. See
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -100,14 +102,18 @@
<listitem><para>Removes a boot loader entry including the files it refers to. Takes a single boot
loader entry ID string or a glob pattern as argument. Referenced files such as kernel or initrd are
only removed if no other entry refers to them.</para></listitem>
only removed if no other entry refers to them.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
<term><option>cleanup</option></term>
<listitem><para>Removes files from the ESP and XBOOTLDR partitions that belong to the entry token but
are not referenced in any boot loader entries.</para></listitem>
are not referenced in any boot loader entries.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -244,13 +250,17 @@
<listitem><para>Takes a kernel image as argument. Checks what kind of kernel the image is. Returns
one of <literal>uki</literal>, <literal>pe</literal>, and <literal>unknown</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
<term><option>kernel-inspect</option> <replaceable>kernel</replaceable></term>
<listitem><para>Takes a kernel image as argument. Prints details about the image.</para></listitem>
<listitem><para>Takes a kernel image as argument. Prints details about the image.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -268,7 +278,9 @@
<listitem><para>Takes a directory path as an argument. All
paths will be prefixed with the given alternate
<replaceable>root</replaceable> path, including config search
paths. </para></listitem>
paths. </para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -281,7 +293,9 @@
table, following the <ulink url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions
Specification</ulink>. For further information on supported disk images, see
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
switch of the same name.</para></listitem>
switch of the same name.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="image-policy-open" />
@@ -293,7 +307,9 @@
(the default), <literal>image</literal> or <literal>host</literal>. With <literal>auto</literal>
binaries will be picked from the specified directory or image, and if not found they will be picked
from the host. With <literal>image</literal> or <literal>host</literal> no fallback search will be
performed if the binaries are not found in the selected source.</para></listitem>
performed if the binaries are not found in the selected source.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -335,12 +351,16 @@
(e.g. <filename>/dev/nvme0n1</filename>). If the root file system is <literal>tmpfs</literal> (or a
similar in-memory file system), the block device backing <filename>/usr/</filename> is returned if
applicable. If the root file system is a network file system (e.g. NFS, CIFS) the operation will
fail.</para></listitem>
fail.</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--no-variables</option></term>
<listitem><para>Do not touch the firmware's boot loader list stored in EFI variables.</para></listitem>
<listitem><para>Do not touch the firmware's boot loader list stored in EFI variables.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
@@ -348,7 +368,9 @@
<listitem><para>Ignore failure when the EFI System Partition cannot be found, when EFI variables
cannot be written, or a different or newer boot loader is already installed. Currently only applies
to <command>is-installed</command>, <command>update</command>, and <command>random-seed</command>
verbs.</para></listitem>
verbs.</para>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
<varlistentry>
@@ -356,7 +378,9 @@
<term><option>--quiet</option></term>
<listitem><para>Suppress printing of the results of various commands and also the hints about ESP
being unavailable.</para></listitem>
being unavailable.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
<varlistentry>
@@ -368,7 +392,9 @@
entry token, as specified with <option>--entry-token=</option> parameter described below, and is
placed immediately below the <varname>$BOOT</varname> root directory (i.e. beneath the file system
returned by the <option>--print-boot-path</option> option, see above). Defaults to
<literal>no</literal>.</para></listitem>
<literal>no</literal>.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
<varlistentry>
@@ -413,12 +439,16 @@
on the same medium, and they can update their boot loader entries independently. When using another
identifier (such as the OS ID or the OS image ID), parallel installations of the same OS would try to
use the same entry name. To support parallel installations, the installer must use a different entry
token when adding a second installation.</para></listitem>
token when adding a second installation.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--all-architectures</option></term>
<listitem><para>Install binaries for all supported EFI architectures (this implies <option>--no-variables</option>).</para></listitem>
<listitem><para>Install binaries for all supported EFI architectures (this implies <option>--no-variables</option>).</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -431,7 +461,9 @@
found on the various disks installed in the system. Specifically distributions should not use this flag
to install a branded entry in the boot option list. However in situations with multiple disks, each with
their own ESP partition, it can be beneficial to make it easier to identify the bootloader being used in
the firmware's boot option menu.</para></listitem>
the firmware's boot option menu.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -439,7 +471,9 @@
<listitem><para>Dry run for <option>--unlink</option> and <option>--cleanup</option>.</para>
<para>In dry run mode, the unlink and cleanup operations only print the files that would get deleted
without actually deleting them.</para></listitem>
without actually deleting them.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="no-pager"/>

94
man/busctl.xml
View File

@@ -50,7 +50,9 @@
names. By default, shows both unique and well-known names, but
this may be changed with the <option>--unique</option> and
<option>--acquired</option> switches. This is the default
operation if no command is specified.</para></listitem>
operation if no command is specified.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -60,7 +62,9 @@
bus service (if one is specified by its unique or well-known
name), a process (if one is specified by its numeric PID), or
the owner of the bus (if no parameter is
specified).</para></listitem>
specified).</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@@ -71,7 +75,9 @@
to or from this peer, identified by its well-known or unique
name. Otherwise, show all messages on the bus. Use
<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>
to terminate the dump.</para></listitem>
to terminate the dump.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@@ -84,7 +90,9 @@
Make sure to redirect standard output to a file or pipe. Tools like
<citerefentry project='die-net'><refentrytitle>wireshark</refentrytitle><manvolnum>1</manvolnum></citerefentry>
may be used to dissect and view the resulting
files.</para></listitem>
files.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@@ -94,7 +102,9 @@
services. If <replaceable>SERVICE</replaceable> is specified,
show object tree of the specified services only. Otherwise,
show all object trees of all services on the bus that acquired
at least one well-known name.</para></listitem>
at least one well-known name.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@@ -104,7 +114,9 @@
signals of the specified object (identified by its path) on
the specified service. If the interface argument is passed, the
output is limited to members of the specified
interface.</para></listitem>
interface.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -116,7 +128,9 @@
string is required, followed by the arguments, individually
formatted as strings. For details on the formatting used, see
below. To suppress output of the returned data, use the
<option>--quiet</option> option.</para></listitem>
<option>--quiet</option> option.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@@ -125,7 +139,9 @@
<listitem><para>Emit a signal. Takes an object path, interface name and method name. If parameters
shall be passed, a signature string is required, followed by the arguments, individually formatted as
strings. For details on the formatting used, see below. To specify the destination of the signal,
use the <option>--destination=</option> option.</para></listitem>
use the <option>--destination=</option> option.</para>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
</varlistentry>
<varlistentry>
@@ -137,7 +153,9 @@
specified at once, in which case their values will be shown one
after the other, separated by newlines. The output is, by
default, in terse format. Use <option>--verbose</option> for a
more elaborate output format.</para></listitem>
more elaborate output format.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@@ -146,13 +164,17 @@
<listitem><para>Set the current value of an object
property. Takes a service name, object path, interface name,
property name, property signature, followed by a list of
parameters formatted as strings.</para></listitem>
parameters formatted as strings.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
<term><command>help</command></term>
<listitem><para>Show command syntax help.</para></listitem>
<listitem><para>Show command syntax help.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -170,7 +192,9 @@
<replaceable>ADDRESS</replaceable> instead of using suitable
defaults for either the system or user bus (see
<option>--system</option> and <option>--user</option>
options).</para></listitem>
options).</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -180,7 +204,9 @@
column containing the names of containers they belong to.
See
<citerefentry><refentrytitle>systemd-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -189,14 +215,18 @@
<listitem><para>When showing the list of peers, show only
"unique" names (of the form
<literal>:<replaceable>number</replaceable>.<replaceable>number</replaceable></literal>).
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--acquired</option></term>
<listitem><para>The opposite of <option>--unique</option> —
only "well-known" names will be shown.</para></listitem>
only "well-known" names will be shown.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -205,6 +235,8 @@
<listitem><para>When showing the list of peers, show only
peers which have actually not been activated yet, but may be
started automatically if accessed.</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@@ -215,7 +247,9 @@
subset matching <replaceable>MATCH</replaceable>.
See
<citerefentry><refentrytitle>sd_bus_add_match</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -225,6 +259,8 @@
<para>When used with the <command>capture</command> command,
specifies the maximum bus message size to capture
("snaplen"). Defaults to 4096 bytes.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -234,6 +270,8 @@
<listitem>
<para>When used with the <command>tree</command> command, shows a
flat list of object paths instead of a tree.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -257,6 +295,8 @@
<para>When used with the <command>call</command> or
<command>get-property</command> command, shows output in a
more verbose format.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -267,6 +307,8 @@
<para>When used with the <command>introspect</command> call, dump the XML description received from
the D-Bus <constant>org.freedesktop.DBus.Introspectable.Introspect</constant> call instead of the
normal output.</para>
<xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
@@ -279,6 +321,8 @@
redundant whitespace or line breaks) or <literal>pretty</literal> (for a pretty version of the same, with
indentation and line breaks). Note that transformation from D-Bus marshalling to JSON is done in a loss-less
way, which means type information is embedded into the JSON object tree.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@@ -289,6 +333,8 @@
<para>Equivalent to <option>--json=pretty</option> when invoked interactively from a terminal. Otherwise
equivalent to <option>--json=short</option>, in particular when the output is piped to some other
program.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@@ -307,6 +353,8 @@
code. To only suppress output of the reply message payload,
use <option>--quiet</option> above. Defaults to
<literal>yes</literal>.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -319,6 +367,8 @@
called service, should it not be running yet but is
configured to be auto-started. Defaults to
<literal>yes</literal>.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -331,6 +381,8 @@
authorization while executing the operation, if the security
policy is configured for this. Defaults to
<literal>yes</literal>.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -347,6 +399,8 @@
tool does not wait for any reply message then. When not
specified or when set to 0, the default of
<literal>25s</literal> is assumed.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -361,6 +415,8 @@
shown is possibly inconsistent, as the data read from
<filename>/proc/</filename> might be more recent than the rest of
the credential information. Defaults to <literal>yes</literal>.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
@@ -371,6 +427,8 @@
<para>Controls whether to wait for the specified <constant>AF_UNIX</constant> bus socket to appear in the
file system before connecting to it. Defaults to off. When enabled, the tool will watch the file system until
the socket is created and then connect to it.</para>
<xi:include href="version-info.xml" xpointer="v237"/>
</listitem>
</varlistentry>
@@ -380,6 +438,8 @@
<listitem>
<para>Takes a service name. When used with the <command>emit</command> command, a signal is
emitted to the specified service.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@@ -394,6 +454,8 @@
<listitem>
<para>Do not ellipsize the output in <command>list</command> command.</para>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>

16
man/coredump.conf.xml
View File

@@ -72,7 +72,9 @@
to disk first. Thus, unless <varname>ProcessSizeMax=</varname> is set to 0 (see below), the core will
be written to <filename>/var/lib/systemd/coredump/</filename> either way (under a temporary filename,
or even in an unlinked file), <varname>Storage=</varname> thus only controls whether to leave it
there even after it was processed.</para></listitem>
there even after it was processed.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -81,6 +83,8 @@
<listitem><para>Controls compression for external
storage. Takes a boolean argument, which defaults to
<literal>yes</literal>.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@@ -94,6 +98,8 @@
<para>Setting <varname>Storage=none</varname> and <varname>ProcessSizeMax=0</varname>
disables all coredump handling except for a log entry.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@@ -108,7 +114,9 @@
lowered relative to the default, but not increased. Unit suffixes are allowed just as in
<option>ProcessSizeMax=</option>.</para>
<para><varname>ExternalSizeMax=infinity</varname> sets the core size to unlimited.</para></listitem>
<para><varname>ExternalSizeMax=infinity</varname> sets the core size to unlimited.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -128,7 +136,9 @@
core dumps are processed. Note that old core dumps are also
removed based on time via
<citerefentry><refentrytitle>systemd-tmpfiles</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
Set either value to 0 to turn off size-based cleanup.</para></listitem>
Set either value to 0 to turn off size-based cleanup.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>

98
man/coredumpctl.xml
View File

@@ -58,12 +58,16 @@
<varlistentry>
<term>TIME</term>
<listitem><para>The timestamp of the crash, as reported by the kernel.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
<varlistentry>
<term>PID</term>
<listitem><para>The identifier of the process that crashed.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
@@ -71,13 +75,17 @@
<term>UID</term>
<term>GID</term>
<listitem><para>The user and group identifiers of the process that crashed.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
<varlistentry>
<term>SIGNAL</term>
<listitem><para>The signal that caused the process to crash, when applicable.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -93,13 +101,17 @@
stored in its entirety, <literal>error</literal> means that the core file
cannot be accessed, most likely because of insufficient permissions, and
<literal>missing</literal> means that the core was stored in a file, but
this file has since been removed.</para></listitem>
this file has since been removed.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
<term>EXE</term>
<listitem><para>The full path to the executable. For backtraces of scripts
this is the name of the interpreter.</para></listitem>
this is the name of the interpreter.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
</variablelist>
@@ -138,7 +150,9 @@
will be used. This may be changed using the <option>--debugger=</option>
option or the <varname>$SYSTEMD_DEBUGGER</varname> environment
variable. Use the <option>--debugger-arguments=</option> option to pass extra
command line arguments to the debugger.</para></listitem>
command line arguments to the debugger.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
</variablelist>
@@ -162,28 +176,36 @@
<term><option>-1</option></term>
<listitem><para>Show information of the most recent core dump only, instead of listing all known core
dumps. Equivalent to <option>--reverse -n 1</option>.</para></listitem>
dumps. Equivalent to <option>--reverse -n 1</option>.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
<term><option>-n</option> <replaceable>INT</replaceable></term>
<listitem><para>Show at most the specified number of entries. The specified parameter must be an
integer greater or equal to 1.</para></listitem>
integer greater or equal to 1.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
<term><option>-S</option></term>
<term><option>--since</option></term>
<listitem><para>Only print entries which are since the specified date.</para></listitem>
<listitem><para>Only print entries which are since the specified date.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
<term><option>-U</option></term>
<term><option>--until</option></term>
<listitem><para>Only print entries which are until the specified date.</para></listitem>
<listitem><para>Only print entries which are until the specified date.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -191,7 +213,9 @@
<term><option>--reverse</option></term>
<listitem><para>Reverse output so that the newest entries are displayed first.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -200,7 +224,9 @@
<listitem><para>Print all possible data values the specified
field takes in matching core dump entries of the
journal.</para></listitem>
journal.</para>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
</varlistentry>
<varlistentry>
@@ -217,7 +243,9 @@
<listitem><para>Use the given debugger for the <command>debug</command>
command. If not given and <varname>$SYSTEMD_DEBUGGER</varname> is unset, then
<citerefentry project='man-pages'><refentrytitle>gdb</refentrytitle><manvolnum>1</manvolnum></citerefentry>
will be used. </para></listitem>
will be used. </para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -226,7 +254,9 @@
<listitem><para>Pass the given <replaceable>ARGS</replaceable> as extra command line arguments
to the debugger. Quote as appropriate when <replaceable>ARGS</replaceable> contain whitespace.
(See Examples.)</para></listitem>
(See Examples.)</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@@ -237,7 +267,9 @@
files matching <replaceable>GLOB</replaceable> instead of the
default runtime and system journal paths. May be specified
multiple times, in which case files will be suitably
interleaved.</para></listitem>
interleaved.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -245,14 +277,18 @@
<term><option>--directory=</option><replaceable>DIR</replaceable></term>
<listitem><para>Use the journal files in the specified <option>DIR</option>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--root=<replaceable>ROOT</replaceable></option></term>
<listitem><para>Use root directory <option>ROOT</option> when searching for coredumps.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -265,7 +301,9 @@
table, following the <ulink url="https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions
Specification</ulink>. For further information on supported disk images, see
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
switch of the same name.</para></listitem>
switch of the same name.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="image-policy-open" />
@@ -276,14 +314,18 @@
<listitem><para>Suppresses informational messages about lack
of access to journal files and possible in-flight coredumps.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
<term><option>--all</option></term>
<listitem><para>Look at all available journal files in <filename>/var/log/journal/</filename>
(excluding journal namespaces) instead of only local ones.</para></listitem>
(excluding journal namespaces) instead of only local ones.</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -299,7 +341,9 @@
<listitem><para>Process ID of the
process that dumped
core. An integer.</para></listitem>
core. An integer.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -307,7 +351,9 @@
<listitem><para>Name of the executable (matches
<option>COREDUMP_COMM=</option>). Must not contain slashes.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -315,7 +361,9 @@
<listitem><para>Path to the executable (matches
<option>COREDUMP_EXE=</option>). Must contain at least one
slash. </para></listitem>
slash. </para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -324,7 +372,9 @@
<listitem><para>General journalctl match filter, must contain an equals
sign (<literal>=</literal>). See
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -344,7 +394,9 @@
<varlistentry>
<term><varname>$SYSTEMD_DEBUGGER</varname></term>
<listitem><para>Use the given debugger for the <command>debug</command>
command. See the <option>--debugger=</option> option.</para></listitem>
command. See the <option>--debugger=</option> option.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
</variablelist>
</refsect1>

54
man/crypttab.xml
View File

@@ -348,6 +348,8 @@
default is to queue these requests and process them asynchronously.</para>
<para>This requires kernel 5.9 or newer.</para>
<xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -357,6 +359,8 @@
default is to queue these requests and process them asynchronously.</para>
<para>This requires kernel 5.9 or newer.</para>
<xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
@@ -498,6 +502,8 @@
<option>veracrypt-pim=</option> is not checked against these bounds.
<ulink url="https://www.veracrypt.fr/en/Personal%20Iterations%20Multiplier%20%28PIM%29.html">See
documentation</ulink> for more information.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
@@ -536,7 +542,9 @@
<term><option>headless=</option></term>
<listitem><para>Takes a boolean argument, defaults to false. If true, never query interactively
for the password/PIN. Useful for headless systems.</para></listitem>
for the password/PIN. Useful for headless systems.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
<varlistentry>
@@ -559,7 +567,9 @@
(<literal>*</literal>) is echoed for each character typed. Regardless of
which mode is chosen, if the user hits the tabulator key (<literal>↹</literal>)
at any time, or the backspace key (<literal>⌫</literal>) before any other
data has been entered, then echo is turned off.</para></listitem>
data has been entered, then echo is turned off.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
<varlistentry>
@@ -628,7 +638,9 @@
<para>Note that many security tokens that implement FIDO2 also implement PKCS#11, suitable for
unlocking volumes via the <option>pkcs11-uri=</option> option described above. Typically the newer,
simpler FIDO2 standard is preferable.</para></listitem>
simpler FIDO2 standard is preferable.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@@ -640,7 +652,9 @@
must be of LUKS2 type, and the CID is read from the LUKS2 JSON token header. Use
<citerefentry><refentrytitle>systemd-cryptenroll</refentrytitle><manvolnum>1</manvolnum></citerefentry>
for enrolling a FIDO2 token in the LUKS2 header compatible with this automatic
mode.</para></listitem>
mode.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@@ -649,7 +663,9 @@
<listitem><para>Takes a string, configuring the FIDO2 Relying Party (rp) for the FIDO2 unlock
operation. If not specified <literal>io.systemd.cryptsetup</literal> is used, except if the LUKS2
JSON token header contains a different value. It should normally not be necessary to override
this.</para></listitem>
this.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@@ -680,7 +696,9 @@
used to unlock the volume. When the randomized key is encrypted the current values of the selected
PCRs (see below) are included in the operation, so that different PCR state results in different
encrypted keys and the decrypted key can only be recovered if the same PCR state is
reproduced.</para></listitem>
reproduced.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@@ -692,7 +710,9 @@
<command>systemd-cryptenroll</command> writes it there. If not used (and no metadata in the LUKS2
JSON token header defines it), defaults to a list of a single entry: PCR 7. Assign an empty string to
encode a policy that binds the key to no PCRs, making the key accessible to local programs regardless
of the current PCR state.</para></listitem>
of the current PCR state.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@@ -700,7 +720,9 @@
<listitem><para>Takes a boolean argument, defaults to <literal>false</literal>. Controls whether
TPM2 volume unlocking is bound to a PIN in addition to PCRs. Similarly, this option is only useful
when TPM2 enrollment metadata is not available.</para></listitem>
when TPM2 enrollment metadata is not available.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
<varlistentry>
@@ -715,7 +737,9 @@
unlock a LUKS2 volume with a signed TPM2 PCR enrollment a suitable signature file
<filename>tpm2-pcr-signature.json</filename> is searched for in <filename>/etc/systemd/</filename>,
<filename>/run/systemd/</filename>, <filename>/usr/lib/systemd/</filename> (in this
order).</para></listitem>
order).</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -727,7 +751,9 @@
the specified PCR. The volume key is measured along with the activated volume name and its UUID. This
functionality is particularly useful for the encrypted volume backing the root file system, as it
then allows later TPM objects to be securely bound to the root file system and hence the specific
installation.</para></listitem>
installation.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@@ -737,7 +763,9 @@
<option>tpm2-measure-pcr=</option> above. Multiple banks may be specified, separated by a colon
character. If not specified automatically determines available and used banks. Expects a message
digest name (e.g. <literal>sha1</literal>, <literal>sha256</literal>, …) as argument, to identify the
bank.</para></listitem>
bank.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@@ -749,7 +777,9 @@
for supported formats). Defaults to 30s. Once the specified timeout elapsed authentication via
password is attempted. Note that this timeout applies to waiting for the security device to show up —
it does not apply to the PIN prompt for the device (should one be needed) or similar. Pass 0 to turn
off the time-out and wait forever.</para></listitem>
off the time-out and wait forever.</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>

168
man/file-hierarchy.xml
View File

@@ -51,7 +51,9 @@
<listitem><para>The file system root. Usually writable, but
this is not required. Possibly a temporary file system
(<literal>tmpfs</literal>). Not shared with other hosts
(unless read-only). </para></listitem>
(unless read-only). </para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -64,7 +66,9 @@
should be considered read-only, except when a new kernel or
boot loader is installed. This directory only exists on
systems that run on physical or emulated hardware that
requires boot loaders.</para></listitem>
requires boot loaders.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -73,7 +77,9 @@
Partition (ESP), the latter is mounted here. Tools that need to operate on the EFI system partition should look
for it at this mount point first, and fall back to <filename>/boot/</filename> — if the former doesn't qualify
(for example if it is not a mount point or does not have the correct file system type
<constant>MSDOS_SUPER_MAGIC</constant>).</para></listitem>
<constant>MSDOS_SUPER_MAGIC</constant>).</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -84,7 +90,9 @@
applications should not make assumptions about this directory
being fully populated or populated at all, and should fall
back to defaults if configuration is
missing.</para></listitem>
missing.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -101,7 +109,9 @@
Applications should generally not reference this directory
directly, but via the per-user <varname>$HOME</varname>
environment variable, or via the home directory field of the
user database.</para></listitem>
user database.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -110,7 +120,9 @@
user's home directory is located outside of
<filename>/home/</filename> in order to make sure the root user
may log in even without <filename>/home/</filename> being
available and mounted.</para></listitem>
available and mounted.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -120,7 +132,9 @@
this directory is organized internally. Generally writable,
and possibly shared among systems. This directory might become
available or writable only very late during
boot.</para></listitem>
boot.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -143,6 +157,8 @@
project='man-pages'><refentrytitle>mkdtemp</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
and similar calls. For more details, see <ulink url="https://systemd.io/TEMPORARY_DIRECTORIES">Using
/tmp/ and /var/tmp/ Safely</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -157,7 +173,9 @@
<term><filename>/run/</filename></term>
<listitem><para>A <literal>tmpfs</literal> file system for system packages to place runtime data,
socket files, and similar. This directory is flushed on boot, and generally writable for privileged
programs only. Always writable.</para></listitem>
programs only. Always writable.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -165,7 +183,9 @@
<listitem><para>Runtime system logs. System components may
place private logs in this directory. Always writable, even
when <filename>/var/log/</filename> might not be accessible
yet.</para></listitem>
yet.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -178,7 +198,9 @@
<varname>$XDG_RUNTIME_DIR</varname> environment variable, as
documented in the <ulink
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
Base Directory Specification</ulink>.</para></listitem>
Base Directory Specification</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -194,7 +216,9 @@
Usually read-only, but this is not required. Possibly shared
between multiple hosts. This directory should not be modified
by the administrator, except when installing or removing
vendor-supplied packages.</para></listitem>
vendor-supplied packages.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -204,13 +228,17 @@
It is recommended not to place binaries in this directory that
are not useful for invocation from a shell (such as daemon
binaries); these should be placed in a subdirectory of
<filename>/usr/lib/</filename> instead.</para></listitem>
<filename>/usr/lib/</filename> instead.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><filename>/usr/include/</filename></term>
<listitem><para>C and C++ API header files of system
libraries.</para></listitem>
libraries.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -222,7 +250,9 @@
from a shell. Such binaries may be for any architecture
supported by the system. Do not place public libraries in this
directory, use <varname>$libdir</varname> (see below),
instead.</para></listitem>
instead.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -239,7 +269,9 @@
architecture-dependent, too. To query
<varname>$libdir</varname> for the primary architecture of the
system, invoke:
<programlisting># systemd-path system-library-arch</programlisting></para></listitem>
<programlisting># systemd-path system-library-arch</programlisting></para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
@@ -249,13 +281,17 @@
such as documentation, man pages, time zone information, fonts
and other resources. Usually, the precise location and format
of files stored below this directory is subject to
specifications that ensure interoperability.</para></listitem>
specifications that ensure interoperability.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><filename>/usr/share/doc/</filename></term>
<listitem><para>Documentation for the operating system or
system packages.</para></listitem>
system packages.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -266,7 +302,9 @@
be placed in <filename>/etc/</filename>. This is useful to
compare the local configuration of a system with vendor
defaults and to populate the local configuration with
defaults.</para></listitem>
defaults.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -275,7 +313,9 @@
<listitem><para>Similar to
<filename>/usr/share/factory/etc/</filename>, but for vendor
versions of files in the variable, persistent data directory
<filename>/var/</filename>.</para></listitem>
<filename>/var/</filename>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
</variablelist>
@@ -293,7 +333,9 @@
system might start up without this directory being populated. Persistency is recommended, but
optional, to support ephemeral systems. This directory might become available or writable only very
late during boot. Components that are required to operate during early boot hence shall not
unconditionally rely on this directory.</para></listitem>
unconditionally rely on this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -302,13 +344,17 @@
components may place non-essential data in this directory.
Flushing this directory should have no effect on operation of
programs, except for increased runtimes necessary to rebuild
these caches.</para></listitem>
these caches.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><filename>/var/lib/</filename></term>
<listitem><para>Persistent system data. System components may
place private data in this directory.</para></listitem>
place private data in this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -319,13 +365,17 @@
<citerefentry project='man-pages'><refentrytitle>syslog</refentrytitle><manvolnum>3</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>sd_journal_print</refentrytitle><manvolnum>3</manvolnum></citerefentry>
calls.</para></listitem>
calls.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><filename>/var/spool/</filename></term>
<listitem><para>Persistent system spool data, such as printer
or mail queues.</para></listitem>
or mail queues.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -347,6 +397,8 @@
project='man-pages'><refentrytitle>mkdtemp</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
and similar calls should be used. For further details about this directory, see <ulink
url="https://systemd.io/TEMPORARY_DIRECTORIES">Using /tmp/ and /var/tmp/ Safely</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -367,7 +419,9 @@
<citerefentry><refentrytitle>systemd-udevd</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
and should not be written to by other components. A number of
special purpose virtual file systems might be mounted below
this directory.</para></listitem>
this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -385,7 +439,9 @@
programs) or <varname>$XDG_RUNTIME_DIR</varname> (for user
programs) instead of POSIX shared memory segments, since these
directories are not world-writable and hence not vulnerable to
security-sensitive name clashes.</para></listitem>
security-sensitive name clashes.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -396,7 +452,9 @@
where normal files may be stored. For details, see
<citerefentry project='man-pages'><refentrytitle>proc</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
A number of special purpose virtual file systems might be
mounted below this directory.</para></listitem>
mounted below this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -406,7 +464,9 @@
configure the settings in this API file tree is via
<citerefentry><refentrytitle>sysctl.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>
files. In sandboxed/containerized setups, this directory is
generally mounted read-only.</para></listitem>
generally mounted read-only.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -417,7 +477,9 @@
where normal files may be stored. In sandboxed/containerized
setups, this directory is generally mounted read-only. A number
of special purpose virtual file systems might be mounted below
this directory.</para></listitem>
this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -437,7 +499,9 @@
cgroup2 will not have resource controllers attached. In
sandboxed/containerized setups, this directory may either not exist or
may include a subset of functionality.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -454,7 +518,9 @@
<listitem><para>These compatibility symlinks point to
<filename>/usr/bin/</filename>, ensuring that scripts and
binaries referencing these legacy paths correctly find their
binaries.</para></listitem>
binaries.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -463,7 +529,9 @@
<listitem><para>This compatibility symlink points to
<filename>/usr/lib/</filename>, ensuring that programs
referencing this legacy path correctly find their
resources.</para></listitem>
resources.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -474,7 +542,9 @@
binaries referencing this legacy path correctly find their
dynamic loader. This symlink only exists on architectures
whose ABI places the dynamic loader in this
path.</para></listitem>
path.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -483,7 +553,9 @@
<listitem><para>This compatibility symlink points to
<filename>/run/</filename>, ensuring that programs referencing
this legacy path correctly find their runtime
data.</para></listitem>
data.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
</variablelist>
@@ -509,7 +581,9 @@
directory. Flushing this directory should have no effect on operation of programs, except for
increased runtimes necessary to rebuild these caches. If an application finds
<varname>$XDG_CACHE_HOME</varname> set, it should use the directory specified in it instead of this
directory.</para></listitem>
directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -518,7 +592,9 @@
<listitem><para>Application configuration. When a new user is created, this directory will be empty
or not exist at all. Applications should fall back to defaults should their configuration in this
directory be missing. If an application finds <varname>$XDG_CONFIG_HOME</varname> set, it should use
the directory specified in it instead of this directory.</para></listitem>
the directory specified in it instead of this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -529,14 +605,18 @@
shell; these should be placed in a subdirectory of <filename>~/.local/lib/</filename> instead. Care
should be taken when placing architecture-dependent binaries in this place, which might be
problematic if the home directory is shared between multiple hosts with different
architectures.</para></listitem>
architectures.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><filename>~/.local/lib/</filename></term>
<listitem><para>Static, private vendor data that is compatible with all
architectures.</para></listitem>
architectures.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -544,7 +624,9 @@
<listitem><para>Location for placing public dynamic libraries. The architecture identifier to use is
defined on <ulink url="https://wiki.debian.org/Multiarch/Tuples">Multiarch Architecture Specifiers
(Tuples)</ulink> list.</para></listitem>
(Tuples)</ulink> list.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -553,7 +635,9 @@
<listitem><para>Resources shared between multiple packages, such as fonts or artwork. Usually, the
precise location and format of files stored below this directory is subject to specifications that
ensure interoperability. If an application finds <varname>$XDG_DATA_HOME</varname> set, it should use
the directory specified in it instead of this directory.</para></listitem>
the directory specified in it instead of this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -562,7 +646,9 @@
<listitem><para>Application state. When a new user is created, this directory will be empty or not
exist at all. Applications should fall back to defaults should their state in this directory be
missing. If an application finds <varname>$XDG_STATE_HOME</varname> set, it should use the directory
specified in it instead of this directory.</para></listitem>
specified in it instead of this directory.</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>
</variablelist>

272
man/homectl.xml
View File

File diff suppressed because it is too large Load Diff

8
man/homed.conf.xml
View File

@@ -57,7 +57,9 @@
to <literal>luks</literal>. Otherwise defaults to <literal>subvolume</literal> if
<filename>/home/</filename> is on a btrfs file system, and <literal>directory</literal>
otherwise. Note that the storage selected on the <command>homectl</command> command line always takes
precedence.</para></listitem>
precedence.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -67,7 +69,9 @@
<literal>ext4</literal> or <literal>xfs</literal>. If not specified defaults to
<literal>btrfs</literal>. This setting has no effect if a different storage mechanism is used. The
file system type selected on the <command>homectl</command> command line always takes
precedence.</para></listitem>
precedence.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
</variablelist>

22
man/hostnamectl.xml
View File

@@ -84,7 +84,9 @@
<para>The static and transient hostnames must each be either a single DNS label (a string composed of
7-bit ASCII lower-case characters and no spaces or dots, limited to the format allowed for DNS domain
name labels), or a sequence of such labels separated by single dots that forms a valid DNS FQDN. The
hostname must be at most 64 characters, which is a Linux limitation (DNS allows longer names).</para></listitem>
hostname must be at most 64 characters, which is a Linux limitation (DNS allows longer names).</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
<varlistentry>
@@ -96,7 +98,9 @@
graphical applications to visualize this host. The icon name
should follow the <ulink
url="https://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html">Icon
Naming Specification</ulink>.</para></listitem>
Naming Specification</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
<varlistentry>
@@ -119,6 +123,8 @@
<literal>vm</literal> and
<literal>container</literal> for virtualized systems that lack
an immediate physical chassis.</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
@@ -135,6 +141,8 @@
<literal>staging</literal>,
<literal>production</literal>.
</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
@@ -149,6 +157,8 @@
location of the system, if it is known and applicable. This
may be as generic as <literal>Berlin, Germany</literal> or as
specific as <literal>Left Rack, 2nd Shelf</literal>.</para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
</variablelist>
@@ -164,7 +174,9 @@
<term><option>--no-ask-password</option></term>
<listitem><para>Do not query the user for authentication for
privileged operations.</para></listitem>
privileged operations.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -176,7 +188,9 @@
switches is specified, <command>hostnamectl</command> will print out just this selected hostname.</para>
<para>If used with <command>hostname</command>, only the selected hostnames will be updated. When more
than one of these switches are specified, all the specified hostnames will be updated. </para></listitem>
than one of these switches are specified, all the specified hostnames will be updated. </para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<xi:include href="user-system-options.xml" xpointer="host" />

24
man/integritytab.xml
View File

@@ -69,7 +69,9 @@
<listitem><para>
Allow the use of discard (TRIM) requests for the device.
This option is available since the Linux kernel version 5.7.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
@@ -83,7 +85,9 @@
<ulink url="https://docs.kernel.org/admin-guide/device-mapper/dm-integrity.html">the dm-integrity documentation</ulink>.
Note that without a journal, if there is a crash, it is possible that the integrity tags and data will not match. If used, the journal-*
options below will have no effect if passed.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>
<varlistentry>
@@ -92,7 +96,9 @@
<listitem><para>
Journal watermark in percent. When the journal percentage exceeds this watermark, the journal flush will be started. Setting a value of
"0%" uses default value.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
@@ -101,7 +107,9 @@
<listitem><para>
Commit time in milliseconds. When this time passes (and no explicit flush operation was issued), the journal is written. Setting a value of
zero uses default value.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
@@ -111,7 +119,9 @@
Specify a separate block device that contains existing data. The second field specified in the
integritytab for block device then will contain calculated integrity tags and journal for data-device,
but not the end user data.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
@@ -119,7 +129,9 @@
<listitem><para>
The algorithm used for integrity checking. The default is crc32c. Must match option used during format.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
</variablelist>

4
man/iocost.conf.xml
View File

@@ -58,7 +58,9 @@
attached to the devices. If a device does not have the specified solution, the first one
listed in <varname>IOCOST_SOLUTIONS</varname> is used instead.</para>
<para>E.g. <literal>TargetSolution=isolated-bandwidth</literal>.</para></listitem>
<para>E.g. <literal>TargetSolution=isolated-bandwidth</literal>.</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>
</variablelist>
</refsect1>

24
man/journal-remote.conf.xml
View File

@@ -56,32 +56,42 @@
<term><varname>Seal=</varname></term>
<listitem><para>Periodically sign the data in the journal using Forward Secure Sealing.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v229"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>SplitMode=</varname></term>
<listitem><para>One of <literal>host</literal> or <literal>none</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>ServerKeyFile=</varname></term>
<listitem><para>SSL key in PEM format.</para></listitem>
<listitem><para>SSL key in PEM format.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>ServerCertificateFile=</varname></term>
<listitem><para>SSL certificate in PEM format.</para></listitem>
<listitem><para>SSL certificate in PEM format.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>TrustedCertificateFile=</varname></term>
<listitem><para>SSL CA certificate.</para></listitem>
<listitem><para>SSL CA certificate.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
@@ -108,7 +118,9 @@
this limit is reached; active files will stay around. This
means that, in effect, there might still be more journal files
around in total than this limit after a vacuuming operation is
complete.</para></listitem>
complete.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
</variablelist>

20
man/journal-upload.conf.xml
View File

@@ -53,25 +53,33 @@
of <option>--url=</option> option in
<citerefentry><refentrytitle>systemd-journal-upload</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for the description of possible values. There is no default value, so either this
option or the command-line option must be always present to make an upload.</para></listitem>
option or the command-line option must be always present to make an upload.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>ServerKeyFile=</varname></term>
<listitem><para>SSL key in PEM format.</para></listitem>
<listitem><para>SSL key in PEM format.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>ServerCertificateFile=</varname></term>
<listitem><para>SSL CA certificate in PEM format.</para></listitem>
<listitem><para>SSL CA certificate in PEM format.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>TrustedCertificateFile=</varname></term>
<listitem><para>SSL CA certificate.</para></listitem>
<listitem><para>SSL CA certificate.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@@ -82,7 +90,9 @@
not reachable over the network for the configured time, <command>systemd-journal-upload</command>
exits. Takes a value in seconds (or in other time units if suffixed with "ms", "min", "h", etc).
For details, see <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
</variablelist>

8
man/journalctl.xml
View File

@@ -434,7 +434,9 @@
<term><option>--truncate-newline</option></term>
<listitem><para>Truncate each log message at the first newline character on output, so that only the
first line of each message is displayed.</para></listitem>
first line of each message is displayed.</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>
<varlistentry>
@@ -453,7 +455,9 @@
<term><option>short-delta</option></term>
<listitem><para>as for <option>short-monotonic</option> but includes the time difference
to the previous entry.
Maybe unreliable time differences are marked by a <literal>*</literal>.</para></listitem>
Maybe unreliable time differences are marked by a <literal>*</literal>.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>

36
man/journald.conf.xml
View File

@@ -98,6 +98,8 @@
<para>Note that per-user journal files are not supported unless persistent storage is enabled, thus
making <command>journalctl --user</command> unavailable.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -125,7 +127,9 @@
url="https://eprint.iacr.org/2013/397">Seekable Sequential Key
Generators</ulink> by G. A. Marson and B. Poettering
(doi:10.1007/978-3-642-40203-6_7) and may be used to protect
journal files from unnoticed alteration.</para></listitem>
journal files from unnoticed alteration.</para>
<xi:include href="version-info.xml" xpointer="v189"/></listitem>
</varlistentry>
<varlistentry>
@@ -142,7 +146,9 @@
instead stored in the single system journal. In this mode unprivileged users generally do not have access to
their own log data. Note that splitting up journal files by user is only available for journals stored
persistently. If journals are stored on volatile storage (see <varname>Storage=</varname> above), only a single
journal file is used. Defaults to <literal>uid</literal>.</para></listitem>
journal file is used. Defaults to <literal>uid</literal>.</para>
<xi:include href="version-info.xml" xpointer="v190"/></listitem>
</varlistentry>
<varlistentry>
@@ -314,7 +320,9 @@
<literal>month</literal>, <literal>week</literal>,
<literal>day</literal>, <literal>h</literal> or
<literal>m</literal> to override the default time unit of
seconds.</para></listitem>
seconds.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -334,7 +342,9 @@
<literal>month</literal>, <literal>week</literal>,
<literal>day</literal>, <literal>h</literal> or <literal>
m</literal> to override the default time unit of
seconds.</para></listitem>
seconds.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -346,7 +356,9 @@
immediately after a log message of priority CRIT, ALERT or
EMERG has been logged. This setting hence applies only to
messages of the levels ERR, WARNING, NOTICE, INFO, DEBUG. The
default timeout is 5 minutes. </para></listitem>
default timeout is 5 minutes. </para>
<xi:include href="version-info.xml" xpointer="v199"/></listitem>
</varlistentry>
<varlistentry>
@@ -420,7 +432,9 @@
<listitem><para>Takes a boolean value. If enabled <command>systemd-journal</command> processes
<filename>/dev/kmsg</filename> messages generated by the kernel. In the default journal namespace
this option is enabled by default, it is disabled in all others.</para></listitem>
this option is enabled by default, it is disabled in all others.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
@@ -437,6 +451,8 @@
to prevent <command>systemd-journald</command> from collecting the generated messages, the socket
unit <literal>systemd-journald-audit.socket</literal> can be disabled and in this case this setting
is without effect.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
@@ -445,7 +461,9 @@
<listitem><para>Change the console TTY to use if
<varname>ForwardToConsole=yes</varname> is used. Defaults to
<filename>/dev/console</filename>.</para></listitem>
<filename>/dev/console</filename>.</para>
<xi:include href="version-info.xml" xpointer="v185"/></listitem>
</varlistentry>
<varlistentry>
@@ -463,7 +481,9 @@
bytes. If the value is suffixed with K, M, G or T, the specified size is parsed as Kilobytes, Megabytes,
Gigabytes, or Terabytes (with the base 1024), respectively. Defaults to 48K, which is relatively large but
still small enough so that log records likely fit into network datagrams along with extra room for
metadata. Note that values below 79 are not accepted and will be bumped to 79.</para></listitem>
metadata. Note that values below 79 are not accepted and will be bumped to 79.</para>
<xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
</variablelist>

80
man/kernel-command-line.xml
View File

@@ -103,6 +103,8 @@
<para>Additional parameters understood by
<citerefentry><refentrytitle>systemd-run-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>, to
run a command line specified on the kernel command line as system service after booting up.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@@ -113,6 +115,8 @@
takes over. This parameter allows specifying an absolute path where core dump files should be stored until
a handler is installed. The path should be absolute and may contain specifiers, see
<citerefentry project='man-pages'><refentrytitle>core</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
@@ -126,6 +130,8 @@
and
<citerefentry><refentrytitle>systemd-rfkill.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
<xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
@@ -151,6 +157,8 @@
<citerefentry><refentrytitle>systemd-volatile-root.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
@@ -161,6 +169,8 @@
and service manager to control console log verbosity. For
details, see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -171,6 +181,8 @@
and service manager to control console log verbosity. For
details, see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v205"/>
</listitem>
</varlistentry>
@@ -215,6 +227,8 @@
manager to control locale and language settings. For
details, see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -236,6 +250,8 @@
<para>Parameter understood by the file quota checker
service. For details, see
<citerefentry><refentrytitle>systemd-quotacheck.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -295,6 +311,8 @@
<para>May be used to disable the Plymouth boot splash. For
details, see
<citerefentry project='die-net'><refentrytitle>plymouth</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -327,6 +345,8 @@
<para>Configures the <filename>/etc/fstab</filename> logic
at boot. For details, see
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -360,6 +380,8 @@
<para>Configures the /usr file system (if required) and
its file system type and mount options. For details, see
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@@ -390,6 +412,8 @@
<para>Configures whether the <filename>serial-getty@.service</filename> will run.
For details, see
<citerefentry><refentrytitle>systemd-getty-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
@@ -400,6 +424,8 @@
<listitem>
<para>Configures whether GPT-based partition auto-discovery shall be attempted. For details, see
<citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@@ -411,7 +437,9 @@
policy string to apply, as per
<citerefentry><refentrytitle>systemd.image-policy</refentrytitle><manvolnum>7</manvolnum></citerefentry>. For
details see
<citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para></listitem>
<citerefentry><refentrytitle>systemd-gpt-auto-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>
<varlistentry>
@@ -421,6 +449,8 @@
<para>Overrides the default start job timeout <varname>DefaultTimeoutStartSec=</varname> at
boot. For details, see
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
@@ -431,6 +461,8 @@
<para>Overrides the default device timeout <varname>DefaultDeviceTimeoutSec=</varname> at boot. For
details, see
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
@@ -440,6 +472,8 @@
<listitem>
<para>Overrides the watchdog device path <varname>WatchdogDevice=</varname>. For details, see
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v236"/>
</listitem>
</varlistentry>
@@ -453,6 +487,8 @@
implicitly assumed time unit) or the special strings <literal>off</literal> or
<literal>default</literal>. For details, see
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
@@ -465,6 +501,8 @@
implicitly assumed time unit) or the special strings <literal>off</literal> or
<literal>default</literal>. For details, see
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
@@ -475,6 +513,8 @@
<para>Overrides the watchdog pre-timeout settings otherwise configured with
<varname>RuntimeWatchdogPreGovernor=</varname>. Takes a string value. For details, see
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
@@ -486,6 +526,8 @@
processes it forks. This takes precedence over <varname>CPUAffinity=</varname>, see
<citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
@@ -497,6 +539,8 @@
<para>Load a specific kernel module early at boot. For
details, see
<citerefentry><refentrytitle>systemd-modules-load.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
@@ -506,7 +550,9 @@
<listitem><para>Configures DNS server information and search domains, see
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
@@ -531,7 +577,9 @@
the relevant settings are not initialized yet. Not to be confused with
<varname>systemd.condition-first-boot=</varname> (see below), which overrides the result of the
<varname>ConditionFirstBoot=</varname> unit file condition, and thus controls more than just
<filename>systemd-firstboot.service</filename> behaviour.</para></listitem>
<filename>systemd-firstboot.service</filename> behaviour.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -540,7 +588,9 @@
<listitem><para>Takes a boolean argument. If specified, overrides the result of
<varname>ConditionNeedsUpdate=</varname> unit condition checks. See
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
details.</para></listitem>
details.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -551,7 +601,9 @@
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
details. Not to be confused with <varname>systemd.firstboot=</varname> which only controls behaviour
of the <filename>systemd-firstboot.service</filename> system service but has no effect on the
condition check (see above).</para></listitem>
condition check (see above).</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -559,7 +611,9 @@
<listitem><para>Takes a decimal, numeric timestamp in μs since January 1st 1970, 00:00am, to set the
system clock to. The system time is set to the specified timestamp early during boot. It is not
propagated to the hardware clock (RTC).</para></listitem>
propagated to the hardware clock (RTC).</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -583,6 +637,8 @@
<para>Again: do not use this option outside of testing environments, it's a security risk elsewhere,
as secret key material derived from the entropy pool can possibly be reconstructed by unprivileged
programs.</para>
<xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
@@ -591,7 +647,9 @@
<listitem><para>Accepts a hostname to set during early boot. If specified takes precedence over what
is set in <filename>/etc/hostname</filename>. Note that this does not bar later runtime changes to
the hostname, it simply controls the initial hostname set during early boot.</para></listitem>
the hostname, it simply controls the initial hostname set during early boot.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -605,7 +663,9 @@
configure the <varname>$TERM</varname> value used by <command>systemd</command> if not set explicitly
using <varname>TERM</varname> on the kernel command line. The tty name should be specified without
the <filename>/dev/</filename> prefix (e.g. <literal>systemd.tty.rows.ttyS0=80</literal>).
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v254"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -618,7 +678,9 @@
<term>systemd 252</term>
<listitem><para>Kernel command-line arguments <varname>systemd.unified_cgroup_hierarchy</varname>
and <varname>systemd.legacy_systemd_cgroup_controller</varname> were deprecated. Please switch to
the unified cgroup hierarchy.</para></listitem>
the unified cgroup hierarchy.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
</variablelist>
</refsect1>

32
man/kernel-install.xml
View File

@@ -129,6 +129,8 @@
<para>If <varname>$KERNEL_INSTALL_LAYOUT</varname> is not "uki", this plugin does nothing.</para></listitem>
</itemizedlist>
<xi:include href="version-info.xml" xpointer="v241"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -156,6 +158,8 @@
<listitem><para><filename>90-uki-copy.install</filename> removes the file
<filename>$BOOT/EFI/Linux/<replaceable>ENTRY-TOKEN</replaceable>-<replaceable>KERNEL-VERSION</replaceable>.efi</filename>.</para></listitem>
</itemizedlist>
<xi:include href="version-info.xml" xpointer="v203"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -164,6 +168,8 @@
<para>Shows the various paths and parameters configured or auto-detected. In particular shows the
values of the various <varname>$KERNEL_INSTALL_*</varname> environment variables listed
below.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
@@ -199,6 +205,8 @@
the entry token, and is placed immediately below the boot root directory. When
<literal>auto</literal>, the directory is created or removed only when the install layout is
<literal>bls</literal>. Defaults to <literal>auto</literal>.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
@@ -241,6 +249,8 @@
installations of the same OS would try to use the same entry name. To support parallel
installations, the installer must use a different entry token when adding a second installation.
</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
@@ -249,6 +259,8 @@
<term><option>--verbose</option></term>
<listitem>
<para>Output additional information about operations being performed.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@@ -324,6 +336,8 @@
unified kernel images under <filename>$BOOT/EFI/Linux</filename> as
<filename>$BOOT/EFI/Linux/<replaceable>ENTRY-TOKEN</replaceable>-<replaceable>KERNEL-VERSION</replaceable>[+<replaceable>TRIES</replaceable>].efi</filename>.</para>
<para>Implemented by <filename>90-uki-copy.install</filename>.</para>
<xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -341,6 +355,8 @@
<filename>$BOOT/<replaceable>ENTRY-TOKEN</replaceable></filename> exists, or
<option>other</option> otherwise.</para>
<para>Leaving layout blank has the same effect. This is the default.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
</variablelist>
@@ -395,6 +411,8 @@
</term>
<listitem>
<para>Drop-in files which are executed by kernel-install.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -409,6 +427,8 @@
does not exist, <filename>/usr/lib/kernel/cmdline</filename> is used. If that also does not
exist, <filename>/proc/cmdline</filename> is used. <varname>$KERNEL_INSTALL_CONF_ROOT</varname>
may be used to override the path.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -426,6 +446,8 @@
<citerefentry><refentrytitle>systemd-boot</refentrytitle><manvolnum>7</manvolnum></citerefentry>
which implement boot attempt counting with a counter embedded in the entry file name.
<varname>$KERNEL_INSTALL_CONF_ROOT</varname> may be used to override the path.</para>
<xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -437,6 +459,8 @@
naming Boot Loader Specification entries, see <varname>$KERNEL_INSTALL_ENTRY_TOKEN</varname>
above for details. <varname>$KERNEL_INSTALL_CONF_ROOT</varname> may be used to override the
path.</para>
<xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -446,6 +470,8 @@
<listitem>
<para>The content of this file specifies the machine identification
<replaceable>MACHINE-ID</replaceable>.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -457,6 +483,8 @@
<para>Read by <filename>90-loaderentry.install</filename>.
If available, <varname>PRETTY_NAME=</varname> is read from these files and used as the title of the boot menu entry.
Otherwise, <literal>Linux <replaceable>KERNEL-VERSION</replaceable></literal> will be used.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -481,6 +509,8 @@
<varname>initrd_generator=</varname>,
<varname>uki_generator=</varname>.
See the Environment variables section above for details.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -491,6 +521,8 @@
<para>Ini-style configuration file for <citerefentry><refentrytitle>ukify</refentrytitle><manvolnum>1</manvolnum></citerefentry> which is only effective when <varname>$KERNEL_INSTALL_LAYOUT</varname> or <varname>layout=</varname> in <filename>install.conf</filename> is set to <option>uki</option> and <varname>$KERNEL_INSTALL_UKI_GENERATOR</varname> or <varname>uki_generator=</varname> in <filename>install.conf</filename> is set to <option>ukify</option>.
<varname>$KERNEL_INSTALL_CONF_ROOT</varname> may be used to override the path.
</para>
<xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
</variablelist>

60
man/loader.conf.xml
View File

@@ -117,7 +117,9 @@
<citerefentry project='man-pages'><refentrytitle>glob</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
but do not support all features. In particular, set negation and named character classes are not
supported. The matching is done case-insensitively on the entry ID (as shown by <command>bootctl
list</command>).</para></listitem>
list</command>).</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -132,6 +134,8 @@
is shown and the default entry will be booted immediately. The menu can be shown
by pressing and holding a key before systemd-boot is launched. Setting this to
<literal>menu-force</literal> disables the timeout while always showing the menu.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -147,6 +151,8 @@
<term>0</term>
<listitem>
<para>Standard UEFI 80x25 mode</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -154,6 +160,8 @@
<term>1</term>
<listitem>
<para>80x50 mode, not supported by all devices</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -162,6 +170,8 @@
<listitem>
<para>the first non-standard mode provided by the device
firmware, if any</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -169,6 +179,8 @@
<term>auto</term>
<listitem>
<para>Pick a suitable mode automatically using heuristics</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -176,6 +188,8 @@
<term>max</term>
<listitem>
<para>Pick the highest-numbered available mode</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -183,10 +197,14 @@
<term>keep</term>
<listitem>
<para>Keep the mode selected by firmware (the default)</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
</variablelist>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -195,7 +213,9 @@
<listitem><para>Takes a boolean argument. Enable (the default) or disable the
editor. The editor should be disabled if the machine can be accessed by
unauthorized persons.</para></listitem>
unauthorized persons.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -204,7 +224,9 @@
<listitem><para>Takes a boolean argument. Enable (the default) or disable
entries for other boot entries found on the boot partition. In particular,
this may be useful when loader entries are created to show replacement
descriptions for those entries.</para></listitem>
descriptions for those entries.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -212,14 +234,18 @@
<listitem><para>A boolean controlling the presence of the "Reboot into firmware" entry
(enabled by default). If this is disabled, the firmware interface may still be reached
by using the <keycap>f</keycap> key.</para></listitem>
by using the <keycap>f</keycap> key.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term>beep</term>
<listitem><para>Takes a boolean argument. If timeout enabled beep every second, otherwise beep n times when n-th entry in boot menu is selected (default disabled).
Currently, only x86 is supported, where it uses the PC speaker.</para></listitem>
Currently, only x86 is supported, where it uses the PC speaker.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
<varlistentry>
@@ -231,26 +257,34 @@
<variablelist>
<varlistentry>
<term><option>off</option></term>
<listitem><para>No action is taken.</para></listitem>
<listitem><para>No action is taken.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
<term><option>manual</option></term>
<listitem><para>Boot entries for found secure boot keys are created that allow manual
enrollment.</para></listitem>
enrollment.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
<term><option>if-safe</option></term>
<listitem><para>Same behavior as <option>manual</option>, but will try to automatically
enroll the key <literal>auto</literal> if it is considered to be safe. Currently, this is only
the case if the system is running inside a virtual machine.</para></listitem>
the case if the system is running inside a virtual machine.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
<varlistentry>
<term><option>force</option></term>
<listitem><para>Always enroll the <literal>auto</literal> key if found. Note that a warning
message with a timeout will still be shown if this operation is unknown to be safe.</para></listitem>
message with a timeout will still be shown if this operation is unknown to be safe.</para>
<xi:include href="version-info.xml" xpointer="v253"/></listitem>
</varlistentry>
</variablelist>
</para>
@@ -307,7 +341,9 @@ sbvarsign --attr ${attr} --key KEK.key --cert KEK.crt --output db.auth db db.esl
keys being loaded, some files necessary for the system to function properly still won't be. This
is especially the case with Option ROMs (e.g. for storage controllers or graphics cards). See
<ulink url="https://github.com/Foxboron/sbctl/wiki/FAQ#option-rom">Secure Boot and Option ROMs</ulink>
for more details.</para></listitem>
for more details.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -332,7 +368,9 @@ sbvarsign --attr ${attr} --key KEK.key --cert KEK.crt --output db.auth db db.esl
When Secure Boot is enabled, changing this to PCRs <literal>0,2,7,11</literal> should be safe.
The TPM key protector needs to be removed and then added back for the PCRs on an already
encrypted drive to change. If PCR 4 is not measured, this setting can be disabled to speed
up booting into Windows.</para></listitem>
up booting into Windows.</para>
<xi:include href="version-info.xml" xpointer="v251"/></listitem>
</varlistentry>
</variablelist>
</refsect1>

12
man/localectl.xml
View File

@@ -84,7 +84,9 @@
<citerefentry project='man-pages'><refentrytitle>locale</refentrytitle><manvolnum>7</manvolnum></citerefentry>
for details on the available settings and their meanings. Use
<command>list-locales</command> for a list of available
locales (see below). </para></listitem>
locales (see below). </para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -158,7 +160,9 @@
<term><option>--no-ask-password</option></term>
<listitem><para>Do not query the user for authentication for
privileged operations.</para></listitem>
privileged operations.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -168,7 +172,9 @@
<command>set-x11-keymap</command> is invoked and this option
is passed, then the keymap will not be converted from the
console to X11, or X11 to console,
respectively.</para></listitem>
respectively.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<xi:include href="user-system-options.xml" xpointer="host" />

74
man/loginctl.xml
View File

@@ -63,7 +63,9 @@
the caller's session is shown. This function is intended to
generate human-readable output. If you are looking for
computer-parsable output, use <command>show-session</command>
instead.</para></listitem>
instead.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -78,7 +80,9 @@
<option>--property=</option>. This command is intended to be
used whenever computer-parsable output is required. Use
<command>session-status</command> if you are looking for
formatted human-readable output.</para></listitem>
formatted human-readable output.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -88,7 +92,9 @@
the foreground if another session is currently in the
foreground on the respective seat. Takes a session identifier
as argument. If no argument is specified, the session of the
caller is put into foreground.</para></listitem>
caller is put into foreground.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -99,7 +105,9 @@
or more sessions, if the session supports it. Takes one or
more session identifiers as arguments. If no argument is
specified, the session of the caller is locked/unlocked.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -115,7 +123,9 @@
<listitem><para>Terminates a session. This kills all processes of the session and deallocates all
resources attached to the session. If the argument is specified as empty string the session invoking
the command is terminated.</para></listitem>
the command is terminated.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -124,7 +134,9 @@
<listitem><para>Send a signal to one or more processes of the session. Use
<option>--kill-whom=</option> to select which process to kill. Use <option>--signal=</option> to
select the signal to send. If the argument is specified as empty string the signal is sent to the
session invoking the command.</para></listitem>
session invoking the command.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
</variablelist></refsect2>
@@ -146,7 +158,9 @@
is shown for the user of the session of the caller. This
function is intended to generate human-readable output. If you
are looking for computer-parsable output, use
<command>show-user</command> instead.</para></listitem>
<command>show-user</command> instead.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -161,7 +175,9 @@
<option>--property=</option>. This command is intended to be
used whenever computer-parsable output is required. Use
<command>user-status</command> if you are looking for
formatted human-readable output.</para></listitem>
formatted human-readable output.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -178,7 +194,9 @@
<para>See also <varname>KillUserProcesses=</varname> setting in
<citerefentry><refentrytitle>logind.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -186,7 +204,9 @@
<listitem><para>Terminates all sessions of a user. This kills all processes of all sessions of the
user and deallocates all runtime resources attached to the user. If the argument is specified as
empty string the sessions of the user invoking the command are terminated.</para></listitem>
empty string the sessions of the user invoking the command are terminated.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -194,7 +214,9 @@
<listitem><para>Send a signal to all processes of a user. Use <option>--signal=</option> to select
the signal to send. If the argument is specified as empty string the signal is sent to the sessions
of the user invoking the command.</para></listitem>
of the user invoking the command.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
</variablelist></refsect2>
@@ -215,7 +237,9 @@
session's seat is shown. This function is intended to generate
human-readable output. If you are looking for
computer-parsable output, use <command>show-seat</command>
instead.</para></listitem>
instead.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -230,7 +254,9 @@
<option>--property=</option>. This command is intended to be
used whenever computer-parsable output is required. Use
<command>seat-status</command> if you are looking for
formatted human-readable output.</para></listitem>
formatted human-readable output.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -245,7 +271,9 @@
prefixed with <literal>seat</literal>. To drop assignment of a
device to a specific seat, just reassign it to a different
seat, or use <command>flush-devices</command>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
<varlistentry>
@@ -262,7 +290,9 @@
<listitem><para>Terminates all sessions on a seat. This kills
all processes of all sessions on the seat and deallocates all
runtime resources attached to them.</para></listitem>
runtime resources attached to them.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
</varlistentry>
</variablelist></refsect2>
@@ -299,7 +329,9 @@
<listitem><para>When showing session/user/seat properties,
only print the value, and skip the property name and
<literal>=</literal>.</para></listitem>
<literal>=</literal>.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@@ -327,7 +359,9 @@
kill. Must be one of <option>leader</option>, or
<option>all</option> to select whether to kill only the leader
process of the session or all processes of the session. If
omitted, defaults to <option>all</option>.</para></listitem>
omitted, defaults to <option>all</option>.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
</varlistentry>
<varlistentry>
@@ -352,6 +386,8 @@
and <command>session-status</command>, controls the number of
journal lines to show, counting from the most recent ones.
Takes a positive integer argument. Defaults to 10.</para>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@@ -364,7 +400,9 @@
of the journal entries that are shown. For the available
choices, see
<citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Defaults to <literal>short</literal>.</para></listitem>
Defaults to <literal>short</literal>.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<xi:include href="user-system-options.xml" xpointer="host" />

Some files were not shown because too many files have changed in this diff Show More