<command>enable</command>, depending
how the unit is listed in the preset
files. For more information on preset
- policy see
- <citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
+ policy format see
+ <citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>. For
+ more information on the concept of
+ presets please consult the <ulink
+ url="http://freedesktop.org/wiki/Software/systemd/Preset">Preset</ulink>
+ document.</para>
</listitem>
</varlistentry>
two containers is complete and the containers will
share very few runtime objects except for the
underlying file system.</para>
+
+ <para><command>systemd-nspawn</command> implements the
+ <ulink
+ url="http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">Container
+ Interface</ulink> specification.</para>
</refsect1>
<refsect1>
set of units to be enabled/disabled even before
installing the actual package.</para>
+ <para>For more information on the preset logic please
+ have a look at the <ulink
+ url="http://freedesktop.org/wiki/Software/systemd/Preset">Presets</ulink>
+ document.</para>
+
<para>It is not recommended to ship preset files
within the respective software packages implementing
the units, but rather centralize them in a
<filename>.service</filename> suffix removed) and
dynamically creates a service unit from that
script. This is useful for compatibility with
- SysV.</para>
+ SysV. Note that this compatibility is quite
+ comprehensive but not 100%. For details about the
+ incomptibilities see the <ulink
+ url="http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities">Incompatibilities
+ with SysV</ulink> document.
+ </para>
</refsect1>
<refsect1>
<filename>suspend.target</filename>,
<filename>swap.target</filename>,
<filename>sysinit.target</filename>,
- <filename>syslog.service</filename>,
<filename>syslog.socket</filename>,
<filename>syslog.target</filename>,
<filename>system-update.target</filename>,
or b.</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><filename>syslog.service</filename></term>
- <listitem>
- <para>The syslog service if
- any. Implementations should
- create a symlink from the
- actual syslog implementation
- to this generic name for
- activating it.</para>
- </listitem>
- </varlistentry>
<varlistentry>
<term><filename>syslog.socket</filename></term>
<listitem>
syslog implementations should
listen on. All userspace log
messages will be made
- available on this
- socket.</para>
+ available on this socket. For
+ more information about syslog
+ integration, please consult
+ the <ulink
+ url="http://www.freedesktop.org/wiki/Software/systemd/syslog">Syslog
+ Interface</ulink>
+ document.</para>
</listitem>
</varlistentry>
<varlistentry>
command line. For details see the <ulink
url="http://www.freedesktop.org/wiki/Software/systemd/Generators">Generators
Specification</ulink>.</para>
+
+ <para>Systems which invoke systemd in a container
+ resp. initrd environment should implement the
+ <ulink
+ url="http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface">Container
+ Interface</ulink> resp. <ulink
+ url="http://www.freedesktop.org/wiki/Software/systemd/InitrdInterface">initrd
+ Interface</ulink> specifications.</para>
</refsect1>
<refsect1>