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: update version information

Browse Source 
As I noticed a lot of missing information when trying to implement checking
for missing info. I reimplemented the version information script to be more
robust, and here is the result.

Follow up to ec07c3c80b
This commit is contained in:
Abderrahim Kitouni
2023-09-18 16:03:38 +01:00
committed by Luca Boccassi
parent 6b66407080
commit aefdc1124f
69 changed files with 1577 additions and 447 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
man/bootctl.xml
View File

@@ -52,6 +52,8 @@
specified, this is the implied default.</para>
<para>See the example below for details of the output.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -94,6 +96,8 @@
JSON output may be requested with <option>--json=</option>.</para>
<para>See the example below for details of the output.</para>
<xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
@@ -159,7 +163,9 @@
<command>systemctl reboot --boot-loader-menu=<replaceable>timeout</replaceable></command>
to reboot into the boot loader menu once. See
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
<varlistentry>
@@ -174,7 +180,9 @@
<para>If this is set to <option>menu-hidden</option> or <option>0</option> no menu is shown and
the default entry will be booted immediately, while setting this to <option>menu-force</option>
disables the timeout while always showing the menu. When an empty string ("") is specified the
bootloader will revert to its default menu timeout.</para></listitem>
bootloader will revert to its default menu timeout.</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -192,7 +200,9 @@
<listitem><para>Installs <command>systemd-boot</command> into the EFI system partition. A copy of
<command>systemd-boot</command> will be stored as the EFI default/fallback loader at
<filename><replaceable>ESP</replaceable>/EFI/BOOT/BOOT*.EFI</filename>. The boot loader is then added
to the top of the firmware's boot loader list.</para></listitem>
to the top of the firmware's boot loader list.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -202,14 +212,18 @@
<citerefentry><refentrytitle>systemd-boot</refentrytitle><manvolnum>7</manvolnum></citerefentry>, if the
available version is newer than the version installed in the EFI system partition. This also includes the EFI
default/fallback loader at <filename><replaceable>ESP</replaceable>/EFI/BOOT/BOOT*.EFI</filename>. The boot
loader is then added to end of the firmware's boot loader list if missing.</para></listitem>
loader is then added to end of the firmware's boot loader list if missing.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
<term><option>remove</option></term>
<listitem><para>Removes all installed versions of <command>systemd-boot</command> from the EFI system partition
and the firmware's boot loader list.</para></listitem>
and the firmware's boot loader list.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -218,7 +232,9 @@
<listitem><para>Checks whether <command>systemd-boot</command> is installed in the ESP. Note that a
single ESP might host multiple boot loaders; this hence checks whether
<command>systemd-boot</command> is one (of possibly many) installed boot loaders — and neither
whether it is the default nor whether it is registered in any EFI variables.</para></listitem>
whether it is the default nor whether it is registered in any EFI variables.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@@ -235,7 +251,9 @@
<citerefentry><refentrytitle>systemd-boot-random-seed.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<para>See <ulink url="https://systemd.io/RANDOM_SEEDS">Random Seeds</ulink> for further
information.</para></listitem>
information.</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
</variablelist>
@@ -316,7 +334,9 @@
<term><option>-p</option></term>
<term><option>--print-esp-path</option></term>
<listitem><para>This option modifies the behaviour of <command>status</command>. Only prints the path
to the EFI System Partition (ESP) to standard output and exits.</para></listitem>
to the EFI System Partition (ESP) to standard output and exits.</para>
<xi:include href="version-info.xml" xpointer="v236"/></listitem>
</varlistentry>
<varlistentry>
@@ -335,7 +355,9 @@
<para>Note that this option (similarly to the <option>--print-boot-path</option> option mentioned
above), is available independently from the boot loader used, i.e. also without
<command>systemd-boot</command> being installed.</para></listitem>
<command>systemd-boot</command> being installed.</para>
<xi:include href="version-info.xml" xpointer="v242"/></listitem>
</varlistentry>
<varlistentry>

8
man/busctl.xml
View File

@@ -64,7 +64,7 @@
the owner of the bus (if no parameter is
specified).</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -77,7 +77,7 @@
<keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo>
to terminate the dump.</para>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -116,7 +116,7 @@
output is limited to members of the specified
interface.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
<xi:include href="version-info.xml" xpointer="v218"/></listitem>
</varlistentry>
<varlistentry>
@@ -285,6 +285,8 @@
if this option is specified, errors returned will still be
printed and the tool will indicate success or failure with
the process exit code.</para>
<xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>

18
man/coredumpctl.xml
View File

@@ -121,7 +121,9 @@
<citerefentry><refentrytitle>systemd-coredump</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
Thus it may very well happen that a particular core dump is still listed
in the journal while its corresponding core dump file has already been
removed.</para></listitem>
removed.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -129,7 +131,9 @@
<listitem><para>Show detailed information about the last core dump
or core dumps matching specified characteristics
captured in the journal.</para></listitem>
captured in the journal.</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -138,7 +142,9 @@
<listitem><para>Extract the last core dump matching specified
characteristics. The core dump will be written on standard
output, unless an output file is specified with
<option>--output=</option>. </para></listitem>
<option>--output=</option>. </para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -226,7 +232,7 @@
field takes in matching core dump entries of the
journal.</para>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -234,7 +240,9 @@
<term><option>--output=</option><replaceable>FILE</replaceable></term>
<listitem><para>Write the core to <option>FILE</option>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>

132
man/crypttab.xml
View File

@@ -148,6 +148,8 @@
for possible values and the default value of this option. A cipher with unpredictable IV values, such
as <literal>aes-cbc-essiv:sha256</literal>, is recommended. Embedded commas in the cipher
specification need to be escaped by preceding them with a backslash, see example below.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -156,7 +158,9 @@
<listitem><para>Allow discard requests to be passed through the encrypted block
device. This improves performance on SSD storage but has security implications.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v207"/></listitem>
</varlistentry>
<varlistentry>
@@ -166,7 +170,9 @@
hashing. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -181,7 +187,9 @@
<para>Optionally, the path may be followed by <literal>:</literal> and an
<filename>/etc/fstab</filename> device specification (e.g. starting with <literal>UUID=</literal> or
similar); in which case, the path is relative to the device file system root. The device gets mounted
automatically for LUKS device activation duration only.</para></listitem>
automatically for LUKS device activation duration only.</para>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -191,7 +199,9 @@
start of the key file. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v187"/></listitem>
</varlistentry>
<varlistentry>
@@ -202,7 +212,9 @@
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this option. This
option is ignored in plain encryption mode, as the key file
size is then given by the key size.</para></listitem>
size is then given by the key size.</para>
<xi:include href="version-info.xml" xpointer="v188"/></listitem>
</varlistentry>
<varlistentry>
@@ -211,7 +223,9 @@
<listitem><para>If enabled, the specified key file is erased after the volume is activated or when
activation fails. This is in particular useful when the key file is only acquired transiently before
activation (e.g. via a file in <filename>/run/</filename>, generated by a service running before
activation), and shall be removed after use. Defaults to off.</para></listitem>
activation), and shall be removed after use. Defaults to off.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -224,7 +238,9 @@
<option>luks</option>. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values. The default is to try all key slots in
sequential order.</para></listitem>
sequential order.</para>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -235,7 +251,9 @@
and falls back to a password if it could not be accessed. See
<citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for key files on external devices.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@@ -245,14 +263,18 @@
following options are ignored since they are provided by the
LUKS header on the device: <option>cipher=</option>,
<option>hash=</option>,
<option>size=</option>.</para></listitem>
<option>size=</option>.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
<term><option>bitlk</option></term>
<listitem><para>Decrypt BitLocker drive. Encryption parameters
are deduced by cryptsetup from BitLocker header.</para></listitem>
are deduced by cryptsetup from BitLocker header.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -274,6 +296,8 @@
will be pulled in by <filename>local-fs.target</filename>, while the
service to configure the network is usually only started <emphasis>after</emphasis>
the local file system has been mounted.</para>
<xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
@@ -284,7 +308,9 @@
This means that it will not be automatically unlocked on boot, unless something else pulls
it in. In particular, if the device is used for a mount point, it'll be unlocked
automatically during boot, unless the mount point itself is also disabled with
<option>noauto</option>.</para></listitem>
<option>noauto</option>.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -296,27 +322,35 @@
unsuccessful. Note that other units that depend on the unlocked device may still fail. In
particular, if the device is used for a mount point, the mount point itself also needs to
have the <option>nofail</option> option, or the boot will fail if the device is not unlocked
successfully.</para></listitem>
successfully.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
<term><option>offset=</option></term>
<listitem><para>Start offset in the backend device, in 512-byte sectors. This
option is only relevant for plain devices.</para></listitem>
option is only relevant for plain devices.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
<term><option>plain</option></term>
<listitem><para>Force plain encryption mode.</para></listitem>
<listitem><para>Force plain encryption mode.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
<term><option>read-only</option></term><term><option>readonly</option></term>
<listitem><para>Set up the encrypted block device in read-only
mode.</para></listitem>
mode.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -326,6 +360,8 @@
an unbound workqueue so that encryption work is automatically balanced between available CPUs.</para>
<para>This requires kernel 4.0 or newer.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@@ -338,6 +374,8 @@
benefits the CFQ scheduler to have writes submitted using the same context.</para>
<para>This requires kernel 4.0 or newer.</para>
<xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
@@ -378,6 +416,8 @@
with its number for IV generation being <replaceable>n</replaceable>.</para>
<para>This option is only relevant for plain devices.</para>
<xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
@@ -387,7 +427,9 @@
<listitem><para>Specifies the key size in bits. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -396,7 +438,9 @@
<listitem><para>Specifies the sector size in bytes. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for possible values and the default value of this
option.</para></listitem>
option.</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
<varlistentry>
@@ -411,7 +455,9 @@
<para>WARNING: Using the <option>swap</option> option will
destroy the contents of the named partition during every boot,
so make sure the underlying block device is specified
correctly.</para></listitem>
correctly.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -438,7 +484,9 @@
to all key files. When using an empty passphrase in
combination with one or more key files, use
<literal>/dev/null</literal> as the password file in the third
field.</para></listitem>
field.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -452,7 +500,9 @@
no protection for the hidden volume if the outer volume is
mounted instead. See
<citerefentry project='die-net'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for more information on this limitation.</para></listitem>
for more information on this limitation.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -465,14 +515,18 @@
<para>See the entry for <option>tcrypt</option> on the
behavior of the passphrase and key files when using TrueCrypt
encryption mode.</para></listitem>
encryption mode.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
<term><option>tcrypt-system</option></term>
<listitem><para>Use TrueCrypt in system encryption mode. This
option implies <option>tcrypt</option>.</para></listitem>
option implies <option>tcrypt</option>.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -483,7 +537,9 @@
derivation algorithms that cannot be detected without this flag.
Enabling this option could substantially slow down unlocking, because
VeraCrypt's key derivation takes much longer than TrueCrypt's. This
option implies <option>tcrypt</option>.</para></listitem>
option implies <option>tcrypt</option>.</para>
<xi:include href="version-info.xml" xpointer="v232"/></listitem>
</varlistentry>
<varlistentry>
@@ -513,7 +569,9 @@
<listitem><para>Specifies the timeout for querying for a
password. If no unit is specified, seconds is used. Supported
units are s, ms, us, min, h, d. A timeout of 0 waits
indefinitely (which is the default).</para></listitem>
indefinitely (which is the default).</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -527,7 +585,9 @@
option implies <option>plain</option>.</para>
<para>WARNING: Using the <option>tmp</option> option will destroy the contents of the named partition
during every boot, so make sure the underlying block device is specified correctly.</para></listitem>
during every boot, so make sure the underlying block device is specified correctly.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -535,7 +595,9 @@
<listitem><para>Specifies the maximum number of times the user
is queried for a password. The default is 3. If set to 0, the
user is queried for a password indefinitely.</para></listitem>
user is queried for a password indefinitely.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -551,7 +613,9 @@
<term><option>verify</option></term>
<listitem><para>If the encryption password is read from console, it has to be entered twice to
prevent typos.</para></listitem>
prevent typos.</para>
<xi:include href="version-info.xml" xpointer="v186"/></listitem>
</varlistentry>
<varlistentry>
@@ -604,7 +668,9 @@
implement the newer and simpler FIDO2 standard. Consider using <option>fido2-device=</option>
(described below) to enroll it via FIDO2 instead. Note that a security token enrolled via PKCS#11
cannot be used to unlock the volume via FIDO2, unless also enrolled via FIDO2, and vice
versa.</para></listitem>
versa.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@@ -788,7 +854,9 @@
<listitem><para>Takes a boolean argument. If enabled, right before asking the user for a password it
is first attempted to unlock the volume with an empty password. This is useful for systems that are
initialized with an encrypted volume with only an empty password set, which shall be replaced with a
suitable password during first boot, but after activation.</para></listitem>
suitable password during first boot, but after activation.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -797,7 +865,9 @@
<listitem><para>Specifies how long systemd should wait for a block device to show up before
giving up on the entry. The argument is a time in seconds or explicitly specified units of
<literal>s</literal>, <literal>min</literal>, <literal>h</literal>, <literal>ms</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v216"/></listitem>
</varlistentry>
<varlistentry>
@@ -816,6 +886,8 @@
<para>All other encrypted block devices that contain file systems mounted in the initrd should use
this option.</para>
<xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>

78
man/file-hierarchy.xml
View File

@@ -68,7 +68,7 @@
systems that run on physical or emulated hardware that
requires boot loaders.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -92,7 +92,7 @@
back to defaults if configuration is
missing.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -111,7 +111,7 @@
environment variable, or via the home directory field of the
user database.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -122,7 +122,7 @@
may log in even without <filename>/home/</filename> being
available and mounted.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -134,7 +134,7 @@
available or writable only very late during
boot.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -158,7 +158,7 @@
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"/>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@@ -175,7 +175,7 @@
socket files, and similar. This directory is flushed on boot, and generally writable for privileged
programs only. Always writable.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -185,7 +185,7 @@
when <filename>/var/log/</filename> might not be accessible
yet.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -200,7 +200,7 @@
url="https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html">XDG
Base Directory Specification</ulink>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
@@ -218,7 +218,7 @@
by the administrator, except when installing or removing
vendor-supplied packages.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -230,7 +230,7 @@
binaries); these should be placed in a subdirectory of
<filename>/usr/lib/</filename> instead.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -238,7 +238,7 @@
<listitem><para>C and C++ API header files of system
libraries.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -252,7 +252,7 @@
directory, use <varname>$libdir</varname> (see below),
instead.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -271,7 +271,7 @@
system, invoke:
<programlisting># systemd-path system-library-arch</programlisting></para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
@@ -283,7 +283,7 @@
of files stored below this directory is subject to
specifications that ensure interoperability.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -291,7 +291,7 @@
<listitem><para>Documentation for the operating system or
system packages.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -304,7 +304,7 @@
defaults and to populate the local configuration with
defaults.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -315,7 +315,7 @@
versions of files in the variable, persistent data directory
<filename>/var/</filename>.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>
@@ -335,7 +335,7 @@
late during boot. Components that are required to operate during early boot hence shall not
unconditionally rely on this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -346,7 +346,7 @@
programs, except for increased runtimes necessary to rebuild
these caches.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -354,7 +354,7 @@
<listitem><para>Persistent system data. System components may
place private data in this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -367,7 +367,7 @@
<citerefentry><refentrytitle>sd_journal_print</refentrytitle><manvolnum>3</manvolnum></citerefentry>
calls.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -375,7 +375,7 @@
<listitem><para>Persistent system spool data, such as printer
or mail queues.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -398,7 +398,7 @@
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"/>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@@ -421,7 +421,7 @@
special purpose virtual file systems might be mounted below
this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -441,7 +441,7 @@
directories are not world-writable and hence not vulnerable to
security-sensitive name clashes.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -454,7 +454,7 @@
A number of special purpose virtual file systems might be
mounted below this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -466,7 +466,7 @@
files. In sandboxed/containerized setups, this directory is
generally mounted read-only.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -479,7 +479,7 @@
of special purpose virtual file systems might be mounted below
this directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -520,7 +520,7 @@
binaries referencing these legacy paths correctly find their
binaries.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -531,7 +531,7 @@
referencing this legacy path correctly find their
resources.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -544,7 +544,7 @@
whose ABI places the dynamic loader in this
path.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -555,7 +555,7 @@
this legacy path correctly find their runtime
data.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
</variablelist>
@@ -583,7 +583,7 @@
<varname>$XDG_CACHE_HOME</varname> set, it should use the directory specified in it instead of this
directory.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -594,7 +594,7 @@
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>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -607,7 +607,7 @@
problematic if the home directory is shared between multiple hosts with different
architectures.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -616,7 +616,7 @@
<listitem><para>Static, private vendor data that is compatible with all
architectures.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -626,7 +626,7 @@
defined on <ulink url="https://wiki.debian.org/Multiarch/Tuples">Multiarch Architecture Specifiers
(Tuples)</ulink> list.</para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>
@@ -637,7 +637,7 @@
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>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v215"/></listitem>
</varlistentry>
<varlistentry>

14
man/homectl.xml
View File

@@ -139,7 +139,9 @@
<literal>short</literal> all superfluous whitespace is suppressed. If <literal>off</literal> (the
default) the user information is not shown in JSON format but in a friendly human readable formatting
instead. The <option>-j</option> option picks <literal>pretty</literal> when run interactively and
<literal>short</literal> otherwise.</para></listitem>
<literal>short</literal> otherwise.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@@ -338,7 +340,7 @@
user, including <option>--email=</option>, <option>--timezone=</option> and
<option>--language=</option>.</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@@ -808,7 +810,9 @@
<para>Note that <command>homectl</command> uses bytes for key size, like
<filename>/proc/crypto</filename>, but <citerefentry
project='man-pages'><refentrytitle>cryptsetup</refentrytitle><manvolnum>8</manvolnum></citerefentry>
uses bits.</para></listitem>
uses bits.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>
@@ -881,7 +885,9 @@
directory of the share. The <option>--cifs-extra-mount-options=</option> setting allows specifying
additional mount options when mounting the share, see <citerefentry
project='man-pages'><refentrytitle>mount.cifs</refentrytitle><manvolnum>8</manvolnum></citerefentry>
for details.</para></listitem>
for details.</para>
<xi:include href="version-info.xml" xpointer="v245"/></listitem>
</varlistentry>
<varlistentry>

4
man/hostnamectl.xml
View File

@@ -64,7 +64,9 @@
<term><command>status</command></term>
<listitem><para>Show system hostname and related information. If no command is specified,
this is the implied default.</para></listitem>
this is the implied default.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>

252
man/journalctl.xml
View File

File diff suppressed because it is too large Load Diff

2
man/journald.conf.xml
View File

@@ -424,6 +424,8 @@
<literal>systemd.journald.max_level_kmsg=</literal>,
<literal>systemd.journald.max_level_console=</literal>,
<literal>systemd.journald.max_level_wall=</literal>.</para>
<xi:include href="version-info.xml" xpointer="v185"/>
</listitem>
</varlistentry>

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

@@ -80,6 +80,8 @@
<para>Parameters understood by the system and service
manager to control system behavior. For details, see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -92,6 +94,8 @@
<citerefentry><refentrytitle>systemd-debug-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
to mask or start specific units at boot, or invoke a debug
shell on tty9.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@@ -204,6 +208,8 @@
<para>Parameters understood by the system and service
manager, as compatibility and convenience options. For details, see
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -240,6 +246,8 @@
<para>Parameters understood by the file system checker
services. For details, see
<citerefentry><refentrytitle>systemd-fsck@.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -265,6 +273,8 @@
<para>Parameters understood by the journal service. For
details, see
<citerefentry><refentrytitle>systemd-journald.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -278,6 +288,8 @@
<listitem>
<para>Parameters understood by the virtual console setup logic. For details, see
<citerefentry><refentrytitle>vconsole.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -301,6 +313,8 @@
<para>Parameters understood by the device event managing
daemon. For details, see
<citerefentry><refentrytitle>systemd-udevd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -334,6 +348,8 @@
<para>Configures the LUKS full-disk encryption logic at
boot. For details, see
<citerefentry><refentrytitle>systemd-cryptsetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v186"/>
</listitem>
</varlistentry>
@@ -368,6 +384,8 @@
will be in effect. In this case <varname>rootfstype=</varname>, <varname>rootflags=</varname>,
<varname>ro</varname>, <varname>rw</varname> will be interpreted by
<command>systemd-gpt-auto-generator</command>.</para>
<xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
@@ -402,6 +420,8 @@
<para>Configures the integrity protection root hash for the root and <filename>/usr</filename> file systems, and other related
parameters. For details, see
<citerefentry><refentrytitle>systemd-veritysetup-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
@@ -540,7 +560,7 @@
details, see
<citerefentry><refentrytitle>systemd-modules-load.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v233"/>
<xi:include href="version-info.xml" xpointer="v187"/>
</listitem>
</varlistentry>
@@ -565,6 +585,8 @@
<citerefentry project='man-pages'><refentrytitle>fstab</refentrytitle><manvolnum>5</manvolnum></citerefentry>-like
paths are supported. For details, see
<citerefentry><refentrytitle>systemd-hibernate-resume-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>.</para>
<xi:include href="version-info.xml" xpointer="v217"/>
</listitem>
</varlistentry>

14
man/kernel-install.xml
View File

@@ -139,7 +139,7 @@
<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"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -172,7 +172,7 @@
</para></listitem>
</itemizedlist>
<xi:include href="version-info.xml" xpointer="v203"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -182,7 +182,7 @@
values of the various <varname>$KERNEL_INSTALL_*</varname> environment variables listed
below.</para>
<xi:include href="version-info.xml" xpointer="v254"/>
<xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
@@ -337,6 +337,8 @@
kernel and initrds under
<filename>$BOOT/<replaceable>ENTRY-TOKEN</replaceable>/<replaceable>KERNEL-VERSION</replaceable>/</filename></para>
<para>Implemented by <filename>90-loaderentry.install</filename>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -357,6 +359,8 @@
<term>other</term>
<listitem>
<para>Some other layout not understood natively by <command>kernel-install</command>.</para>
<xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -441,7 +445,7 @@
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"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>
@@ -497,7 +501,7 @@
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"/>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<varlistentry>

26
man/localectl.xml
View File

@@ -71,7 +71,9 @@
<term><command>status</command></term>
<listitem><para>Show current settings of the system locale and keyboard mapping.
If no command is specified, this is the implied default.</para></listitem>
If no command is specified, this is the implied default.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -86,7 +88,7 @@
<command>list-locales</command> for a list of available
locales (see below). </para>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -94,7 +96,9 @@
<listitem><para>List available locales useful for
configuration with
<command>set-locale</command>.</para></listitem>
<command>set-locale</command>.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -108,7 +112,9 @@
keyboard mapping of X11, after converting it to the closest
matching X11 keyboard mapping. Use
<command>list-keymaps</command> for a list of available
keyboard mappings (see below).</para></listitem>
keyboard mappings (see below).</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -116,7 +122,9 @@
<listitem><para>List available keyboard mappings for the
console, useful for configuration with
<command>set-keymap</command>.</para></listitem>
<command>set-keymap</command>.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -130,7 +138,9 @@
for details. Unless <option>--no-convert</option> is passed,
the selected setting is also applied as the system console
keyboard mapping, after converting it to the closest matching
console keyboard mapping.</para></listitem>
console keyboard mapping.</para>
<xi:include href="version-info.xml" xpointer="v195"/></listitem>
</varlistentry>
<varlistentry>
@@ -144,7 +154,9 @@
<command>set-keymap</command>. The command
<command>list-x11-keymap-variants</command> optionally takes a
layout parameter to limit the output to the variants suitable
for the specific layout.</para></listitem>
for the specific layout.</para>
<xi:include href="version-info.xml" xpointer="v201"/></listitem>
</varlistentry>
</variablelist>

6
man/loginctl.xml
View File

@@ -115,7 +115,9 @@
<term><command>unlock-sessions</command></term>
<listitem><para>Activates/deactivates the screen lock on all
current sessions supporting it. </para></listitem>
current sessions supporting it. </para>
<xi:include href="version-info.xml" xpointer="v188"/></listitem>
</varlistentry>
<varlistentry>
@@ -348,6 +350,8 @@
<term><option>--full</option></term>
<listitem><para>Do not ellipsize process tree entries.</para>
<xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>

8
man/logind.conf.xml
View File

@@ -251,7 +251,9 @@
to take over suspend and hibernation handling, and to use their own configuration
mechanisms. If a low-level inhibitor lock is taken, logind will not take any
action when that key or switch is triggered and the <varname>Handle*=</varname>
settings are irrelevant.</para></listitem>
settings are irrelevant.</para>
<xi:include href="version-info.xml" xpointer="v184"/></listitem>
</varlistentry>
<varlistentry>
@@ -280,7 +282,9 @@
This means that when <command>systemd-logind</command> is handling events by
itself (no low level inhibitor locks are taken by another application), the lid
switch does not respect suspend blockers by default, but the power and sleep keys
do.</para></listitem>
do.</para>
<xi:include href="version-info.xml" xpointer="v190"/></listitem>
</varlistentry>
<varlistentry>

40
man/machinectl.xml
View File

@@ -97,7 +97,9 @@
be started, use <command>list-images</command> (see
below). Note that this command hides the special
<literal>.host</literal> machine by default. Use the
<option>--all</option> switch to show it.</para></listitem>
<option>--all</option> switch to show it.</para>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -113,7 +115,7 @@
console output of the machine, but not necessarily journal
contents of the machine itself.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -127,7 +129,7 @@
required, and does not print the control group tree or journal entries. Use <command>status</command> if you
are looking for formatted human-readable output.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -161,7 +163,7 @@
<command>systemd-nspawn</command> directly. To stop a running
container use <command>machinectl poweroff</command>.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -188,7 +190,7 @@
a single command, either interactively or in the
background.</para>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -233,7 +235,7 @@
preferable for scripting purposes. However, note that <command>systemd-run</command> might require
higher privileges than <command>machinectl shell</command>.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v225"/></listitem>
</varlistentry>
<varlistentry>
@@ -250,7 +252,7 @@
Note that this command does not implicitly start or power off the containers that are being operated on.
If this is desired, combine the command with the <option>--now</option> switch.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -267,7 +269,7 @@
terminate a container or VM, without cleanly shutting it
down.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v212"/></listitem>
</varlistentry>
<varlistentry>
@@ -279,7 +281,7 @@
on a non-containerized system, and is compatible with
containers running any system manager.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v209"/></listitem>
</varlistentry>
<varlistentry>
@@ -292,7 +294,7 @@
<command>poweroff</command> to issue a clean shutdown
request.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -305,7 +307,7 @@
process to kill. Use <option>--signal=</option> to select the
signal to send.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<varlistentry>
@@ -338,7 +340,7 @@
group ID is preserved for the copy, otherwise all files and directories in the copy will be owned by the root
user and group (UID/GID 0).</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -354,7 +356,7 @@
group ID is preserved for the copy, otherwise all files and directories in the copy will be owned by the root
user and group (UID/GID 0).</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
</variablelist></refsect2>
@@ -387,7 +389,7 @@
<command>show-image</command> (see below) to generate
computer-parsable output instead.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -405,7 +407,7 @@
<command>image-status</command> if you are looking for
formatted human-readable output.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -477,7 +479,7 @@
the host's own directory tree, may not be
removed.</para>
<xi:include href="version-info.xml" xpointer="v233"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
<varlistentry>
@@ -705,7 +707,7 @@
transfers and their IDs, use
<command>list-transfers</command>. </para>
<xi:include href="version-info.xml" xpointer="v237"/></listitem>
<xi:include href="version-info.xml" xpointer="v219"/></listitem>
</varlistentry>
</variablelist></refsect2>
@@ -780,7 +782,7 @@
processes of the machine. If omitted, defaults to
<option>all</option>.</para>
<xi:include href="version-info.xml" xpointer="v252"/></listitem>
<xi:include href="version-info.xml" xpointer="v206"/></listitem>
</varlistentry>
<xi:include href="standard-options.xml" xpointer="signal" />
@@ -809,7 +811,7 @@
<para>Note that this option is not supported for the <command>login</command> command.
</para>
<xi:include href="version-info.xml" xpointer="v250"/></listitem>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>

18
man/networkctl.xml
View File

@@ -209,7 +209,7 @@
</variablelist>
</para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@@ -278,7 +278,7 @@
</variablelist>
</para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@@ -308,7 +308,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
1 neighbors listed.</programlisting></para>
<xi:include href="version-info.xml" xpointer="v242"/>
<xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
@@ -347,7 +347,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
</term>
<listitem><para>Deletes virtual netdevs. Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v243"/></listitem>
</varlistentry>
<varlistentry>
@@ -357,7 +357,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
</term>
<listitem><para>Bring devices up. Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -367,7 +367,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
</term>
<listitem><para>Bring devices down. Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -378,7 +378,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
<listitem><para>Renew dynamic configurations e.g. addresses received from DHCP server.
Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
<varlistentry>
@@ -389,7 +389,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
<listitem><para>Send a FORCERENEW message to all connected clients, triggering DHCP reconfiguration.
Takes interface name or index number.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
@@ -402,7 +402,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR)
corresponding to the specified interface. So, if you edit config files, it is necessary to call
<command>networkctl reload</command> first to apply new settings.</para>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
<varlistentry>

18
man/networkd.conf.xml
View File

@@ -147,7 +147,9 @@
<literal>43793</literal> as the vendor identifier (systemd) and hashed contents of
<citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
This is the default if <varname>DUIDType=</varname> is not specified.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@@ -158,7 +160,9 @@
<citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>
is used as a DUID value. About the application-specific machine ID, see
<citerefentry><refentrytitle>sd_id128_get_machine_app_specific</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@@ -168,13 +172,17 @@
then the MAC address of the interface is used as a DUID value. The value <literal>link-layer-time</literal>
can take additional time value after a colon, e.g. <literal>link-layer-time:2018-01-23 12:34:56 UTC</literal>.
The default time value is <literal>2000-01-01 00:00:00 UTC</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
</variablelist>
</para>
<para>In all cases, <varname>DUIDRawData=</varname> can be used to override the
actual DUID value that is used.</para></listitem>
actual DUID value that is used.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
@@ -203,6 +211,8 @@ DUIDRawData=00:00:ab:11:f9:2a:c2:77:29:f9:5c:00</programlisting>
43793 (<literal>00:00:ab:11</literal>), and identifier value <literal>f9:2a:c2:77:29:f9:5c:00</literal>.
</para>
</example>
<xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
</variablelist>

4
man/oomd.conf.xml
View File

@@ -58,7 +58,7 @@
<varname>ManagedOOMSwap=</varname>. Takes a value specified in percent (when suffixed with "%"),
permille ("‰") or permyriad ("‱"), between 0% and 100%, inclusive. Defaults to 90%.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
<varlistentry>
@@ -76,7 +76,7 @@
<varname>ManagedOOMMemoryPressure=</varname>. Takes a fraction specified in the same way as
<varname>SwapUsedLimit=</varname> above. Defaults to 60%.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
<xi:include href="version-info.xml" xpointer="v247"/></listitem>
</varlistentry>
<varlistentry>

28
man/os-release.xml
View File

@@ -215,7 +215,9 @@
Edition"</literal>.</para>
<para>Note: this field is for display purposes only. The <varname>VARIANT_ID</varname> field should
be used for making programmatic decisions.</para></listitem>
be used for making programmatic decisions.</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
<varlistentry>
@@ -227,7 +229,9 @@
may not be implemented on all systems.</para>
<para>Examples: <literal>VARIANT_ID=server</literal>, <literal>VARIANT_ID=embedded</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v220"/></listitem>
</varlistentry>
</variablelist>
</refsect2>
@@ -268,7 +272,9 @@
is optional and may not be implemented on all systems.</para>
<para>Examples: <literal>VERSION_CODENAME=buster</literal>,
<literal>VERSION_CODENAME=xenial</literal>.</para></listitem>
<literal>VERSION_CODENAME=xenial</literal>.</para>
<xi:include href="version-info.xml" xpointer="v231"/></listitem>
</varlistentry>
<varlistentry>
@@ -283,7 +289,9 @@
optional.</para>
<para>Examples: <literal>BUILD_ID="2013-03-20.3"</literal>, <literal>BUILD_ID=201303203</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v200"/></listitem>
</varlistentry>
<varlistentry>
@@ -384,7 +392,9 @@
systems.</para>
<para>Examples: <literal>LOGO=fedora-logo</literal>, <literal>LOGO=distributor-logo-opensuse</literal>
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
</varlistentry>
<varlistentry>
@@ -452,7 +462,9 @@
<para>See <citerefentry><refentrytitle>org.freedesktop.hostname1</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for a description of how
<citerefentry><refentrytitle>systemd-hostnamed.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
determines the fallback hostname.</para></listitem>
determines the fallback hostname.</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>
@@ -480,7 +492,9 @@
for more information.</para>
<para>Examples: <literal>SYSEXT_LEVEL=2</literal>, <literal>SYSEXT_LEVEL=15.14</literal>.
</para></listitem>
</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
</varlistentry>
<varlistentry>

10
man/pam_systemd.xml
View File

@@ -299,7 +299,7 @@
<listitem><para>Sets unit <varname>MemoryMax=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -307,7 +307,7 @@
<listitem><para>Sets unit <varname>TasksMax=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -315,7 +315,7 @@
<listitem><para>Sets unit <varname>CPUWeight=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -323,7 +323,7 @@
<listitem><para>Sets unit <varname>IOWeight=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v239"/></listitem>
</varlistentry>
<varlistentry>
@@ -331,7 +331,7 @@
<listitem><para>Sets unit <varname>RuntimeMaxSec=</varname>.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
</variablelist>

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