Merge pull request #3798 from keszybz/news-and-man-tweaks
News and man tweaks
This commit is contained in:
commit
26598be814
6
NEWS
6
NEWS
|
@ -201,9 +201,9 @@ CHANGES WITH 231:
|
||||||
decrease systemd footprint both in memory during runtime and on
|
decrease systemd footprint both in memory during runtime and on
|
||||||
disk. Note that the shared library is not for public use, and is
|
disk. Note that the shared library is not for public use, and is
|
||||||
neither API not ABI stable, but is likely to change with every new
|
neither API not ABI stable, but is likely to change with every new
|
||||||
released version. Packagers need to make sure that any package built
|
released update. Packagers need to make sure that binaries
|
||||||
from the systemd sources has a strict versioned dependency on the
|
linking to libsystemd-shared.so are updated in step with the
|
||||||
right package for this shared library.
|
library.
|
||||||
|
|
||||||
* Configuration for "mkosi" is now part of the systemd
|
* Configuration for "mkosi" is now part of the systemd
|
||||||
repository. mkosi is a tool to easily build legacy-free OS images,
|
repository. mkosi is a tool to easily build legacy-free OS images,
|
||||||
|
|
|
@ -996,12 +996,11 @@ kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
||||||
unit configuration diectory, however they point to the single template unit file they are instantiated
|
unit configuration diectory, however they point to the single template unit file they are instantiated
|
||||||
from.</para>
|
from.</para>
|
||||||
|
|
||||||
<para>This command expects either valid unit names (in which case appropriate unit files for these names
|
<para>This command expects either valid unit names (in which case various unit file directories are
|
||||||
are automatically searched in the various unit file directories), or absolute paths to unit files (in which
|
automatically searched for unit files with appropriate names), or absolute paths to unit files (in which
|
||||||
case these files are read directly). If a specified unit file is located outside of the unit file
|
case these files are read directly). If a specified unit file is located outside of the usual unit file
|
||||||
directories searched automatically, an additional symlink is created, linking it into the unit
|
directories, an additional symlink is created, linking it into the unit configuration path, thus ensuring
|
||||||
configuration path, thus ensuring it is automatically found when requested by commands such as
|
it is found when requested by commands such as <command>start</command>.</para>
|
||||||
<command>start</command>.</para>
|
|
||||||
|
|
||||||
<para>This command will print the file system operations executed. This output may be suppressed by passing
|
<para>This command will print the file system operations executed. This output may be suppressed by passing
|
||||||
<option>--quiet</option>.
|
<option>--quiet</option>.
|
||||||
|
|
|
@ -73,11 +73,9 @@
|
||||||
since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and
|
since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and
|
||||||
the host and domain name.</para>
|
the host and domain name.</para>
|
||||||
|
|
||||||
<para>Like <citerefentry
|
<para><command>systemd-nspawn</command> may be invoked on any directory tree containing an operating system tree,
|
||||||
project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry> the
|
|
||||||
<command>systemd-nspawn</command> command may be invoked on any directory tree containing an operating system tree,
|
|
||||||
using the <option>--directory=</option> command line option. By using the <option>--machine=</option> option an OS
|
using the <option>--directory=</option> command line option. By using the <option>--machine=</option> option an OS
|
||||||
tree is automatically searched in a couple of locations, most importantly in
|
tree is automatically searched for in a couple of locations, most importantly in
|
||||||
<filename>/var/lib/machines</filename>, the suggested directory to place container images installed on the
|
<filename>/var/lib/machines</filename>, the suggested directory to place container images installed on the
|
||||||
system.</para>
|
system.</para>
|
||||||
|
|
||||||
|
@ -935,8 +933,8 @@
|
||||||
<literal>tmpfs</literal> instance, and
|
<literal>tmpfs</literal> instance, and
|
||||||
<filename>/usr</filename> from the OS tree is mounted into it
|
<filename>/usr</filename> from the OS tree is mounted into it
|
||||||
in read-only mode (the system thus starts up with read-only OS
|
in read-only mode (the system thus starts up with read-only OS
|
||||||
resources, but pristine state and configuration, any changes
|
image, but pristine state and configuration, any changes
|
||||||
to the either are lost on shutdown). When the mode parameter
|
are lost on shutdown). When the mode parameter
|
||||||
is specified as <option>state</option>, the OS tree is
|
is specified as <option>state</option>, the OS tree is
|
||||||
mounted read-only, but <filename>/var</filename> is mounted as
|
mounted read-only, but <filename>/var</filename> is mounted as
|
||||||
a <literal>tmpfs</literal> instance into it (the system thus
|
a <literal>tmpfs</literal> instance into it (the system thus
|
||||||
|
|
Loading…
Reference in New Issue