man: split systemd.network(5) and related into various sections for better readability

This commit is contained in:
Lennart Poettering 2014-06-27 20:42:36 +02:00
parent fed515f0a8
commit 102bd40e1e
3 changed files with 50 additions and 0 deletions

View File

@ -76,6 +76,10 @@
<literal>[Link]</literal> section specifying how the device should be
configured. The first (in lexical order) of the link files that matches
a given device is applied.</para>
</refsect1>
<refsect1>
<title>[Match] Section Options</title>
<para>A link file is said to match a device if each of the entries in the
<literal>[Match]</literal> section matches, or if the section is empty.
@ -156,6 +160,11 @@
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[Link] Section Options</title>
<para>The <literal>[Link]</literal> section accepts the following
keys:</para>

View File

@ -78,6 +78,11 @@
<filename>/usr/lib</filename>, pointing to <filename>/dev/null</filename>,
disables the configuration file entirely.</para>
</refsect1>
<refsect1>
<title>[Match] Section Options</title>
<para>A virtual network device is only created if the
<literal>[Match]</literal> section matches the current
environment, or if the section is empty. The following keys are accepted:</para>
@ -127,6 +132,11 @@
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[NetDev] Section Options</title>
<para>The <literal>[NetDev]</literal> section accepts the following
keys:</para>
@ -149,6 +159,11 @@
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[VLAN] Section Options</title>
<para>The <literal>[VLAN]</literal> section only applies for netdevs of kind <literal>vlan</literal>,
and accepts the following key:</para>
@ -162,6 +177,11 @@
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[MACVLAN] Section Options</title>
<para>The <literal>[MACVLAN]</literal> section only applies for netdevs of kind
<literal>macvlan</literal>, and accepts the following key:</para>

View File

@ -78,6 +78,11 @@
<filename>/usr/lib</filename>, pointing to <filename>/dev/null</filename>,
disables the configuration file entirely.</para>
</refsect1>
<refsect1>
<title>[Match] Section Options</title>
<para>The network file contains a <literal>[Match]</literal> section,
which determines if a given network file may be applied to a given device;
and a <literal>[Network]</literal> section specifying how the device should
@ -172,6 +177,11 @@
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[Network] Section Options</title>
<para>The <literal>[Network]</literal> section accepts the following keys:</para>
<variablelist class='network-directives'>
@ -294,6 +304,11 @@
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[Address] Section Options</title>
<para>An <literal>[Address]</literal> section accepts the following keys.
Specify several <literal>[Address]</literal> sections to configure several
addresses.</para>
@ -321,7 +336,10 @@
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[Route] Section Options</title>
<para>The <literal>[Route]</literal> section accepts the following keys. Specify
several <literal>[Route]</literal> sections to configure several routes.</para>
@ -340,7 +358,10 @@
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>[DHCPv4] Section Options</title>
<para>The <literal>[DHCPv4]</literal> section accepts the following keys:</para>
<variablelist class='network-directives'>