[systemd-devel] [PATCH 3/5] man: udev - document kernel commandline options

[Zbigniew Jędrzejewski-Szmek]

On Mon, Mar 18, 2013 at 02:17:26PM +0100, Tom Gundersen wrote:
> ---
>  man/udev.xml | 43 ++++++++++++++++++++++++++++++++++++-------
>  1 file changed, 36 insertions(+), 7 deletions(-)
> 
> diff --git a/man/udev.xml b/man/udev.xml
> index 34b1e6f..fed8a5e 100644
> --- a/man/udev.xml
> +++ b/man/udev.xml
> @@ -55,14 +55,12 @@
>    </refsect1>
>  
>    <refsect1><title>Configuration</title>
> -    <para>udev configuration files are placed in <filename>/etc/udev</filename>
> -    and <filename>/usr/lib/udev</filename>. All empty lines or lines beginning with
> -    '#' are ignored.</para>
>  
>      <refsect2><title>Configuration file</title>
>        <para>udev expects its main configuration file at <filename>/etc/udev/udev.conf</filename>.
>        It consists of a set of variables allowing the user to override default udev values.
> -      The following variables can be set:</para>
> +      All empty lines or lines beginning with '#' are ignored. The following variables can be
s/or/and/
> +      set:</para>
>        <variablelist>
>          <varlistentry>
>            <term><varname>udev_log</varname></term>
> @@ -75,6 +73,36 @@
>        </variablelist>
>      </refsect2>
>  
> +    <refsect2><title>Kernel command line</title>
> +      <para>The default settings and the udev configuration file can be overridden by specifying
> +      options on the kernel command line. Variables prefixed with <varname>rd.</varname> only apply
> +      in the initrd. The following variables can be set:</para>
> +      <variablelist>
Please use  <variablelist class='kernel-commandline-options'> so that
it'll be indexed properly.

> +        <varlistentry>
> +          <term><varname>udev.log-priority</varname></term>
> +          <listitem>
> +            <para>The logging priority. Valid values are the numerical syslog priorities
> +            or their textual representations: <option>err</option>, <option>info</option>
> +            and <option>debug</option>.</para>
> +          </listitem>
> +        </varlistentry>
> +        <varlistentry>
> +          <term><varname>udev.children-max</varname></term>
> +          <listitem>
> +            <para>The maximal number of workers udev will spawn. If not specified, or set to 0,
> +            a default value is used based on the ammount of available RAM.</para>
> +          </listitem>
> +        </varlistentry>
> +        <varlistentry>
> +          <term><varname>udev.exec-delay</varname></term>
> +          <listitem>
> +            <para>The time in seconds to sleep between applying an udev rule and executing its
> +            external helper program.</para>
> +          </listitem>
> +        </varlistentry>
> +      </variablelist>
> +    </refsect2>
> +
>      <refsect2><title>Rules files</title>
>        <para>The udev rules are read from the files located in the
>        system rules directory <filename>/usr/lib/udev/rules.d</filename>,
> @@ -94,9 +122,10 @@
>        extensions are ignored.</para>
>  
>        <para>Every line in the rules file contains at least one key-value pair.
> -      There are two kinds of keys: match and assignment.
> -      If all match keys are matching against its value, the rule gets applied and the
> -      assignment keys get the specified value assigned.</para>
> +      All empty lines or lines beginning with '#' are ignored. There are two
> +      kinds of keys: match and assignment. If all match keys are matching against
> +      its value, the rule gets applied and the assignment keys get the specified
s/its value/their value/       

s/the assignment key get ... assigned/the specified values are assigned to their keys/
(or something like that, neither your version nor mine sound too good.)

Zbyszek

> +      value assigned.</para>
>  
>        <para>A matching rule may rename a network interface, add symlinks
>        pointing to the device node, or run a specified program as part of