<para>Usually udev runs as <citerefentry><refentrytitle>udevd</refentrytitle>
<manvolnum>8</manvolnum></citerefentry> and receives uevents directly from the
- kernel if a device is added or removed form the system. The program
- <command>udev</command> itself may be used as an event handler in situations,
- where running the daemon is not appropriate, like in initramfs.</para>
+ kernel if a device is added or removed form the system.</para>
<para>If udev receives a device event, it matches its configured rules
against the available device attributes provided in sysfs to identify the device.
<refsect1><title>CONFIGURATION</title>
<para>All udev configuration files are placed in <filename>/etc/udev/*</filename>.
- Every file consist of a set of lines of text. All empty lines or lines beginning
+ Every file consists of a set of lines of text. All empty lines or lines beginning
with '#' will be ignored.</para>
<refsect2><title>Configuration file</title>
</listitem>
</varlistentry>
- <varlistentry>
- <term><option>udev_db</option></term>
- <listitem>
- <para>The name and location of the udev database. The default value is
- <filename>/dev/.udevdb</filename>.</para>
- </listitem>
- </varlistentry>
-
<varlistentry>
<term><option>udev_rules</option></term>
<listitem>
<varlistentry>
<term><option>BUS</option></term>
<listitem>
- <para>Match the typ of bus the device is connected to.</para>
+ <para>Match the type of bus the device is connected to.</para>
</listitem>
</varlistentry>
<term><option>ENV{<replaceable>key</replaceable>}</option></term>
<listitem>
<para>Match against the value of an environment key. Depending on
- the specified operation, this key is also used as a assignment.</para>
+ the specified operation, this key is also used as an assignment.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>NAME</option></term>
<listitem>
- <para>The name of the node to be created, or the name, the network interface
- should be renamed to. Only one rule can set the a name, all later rules with
+ <para>The name of the node to be created, or the name the network interface
+ should be renamed to. Only one rule can set the node name, all later rules with
a NAME key will be ignored.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>OWNER, GROUP, MODE</option></term>
<listitem>
- <para>The permissions for the device node. Every specified value over writes
+ <para>The permissions for the device node. Every specified value overwrites
the compiled-in default value.</para>
</listitem>
</varlistentry>
</varlistentry>
<varlistentry>
- <term><option>%e{<replaceable>key</replaceable>}</option>, <option>$env{<replaceable>key</replaceable>}</option></term>
+ <term><option>%E{<replaceable>key</replaceable>}</option>, <option>$env{<replaceable>key</replaceable>}</option></term>
<listitem>
<para>The value of an environment variable.</para>
</listitem>
</listitem>
</varlistentry>
- <varlistentry>
- <term><option>%e</option>, <option>$enum</option></term>
- <listitem>
- <para>If a device node already exists with the name, the smallest next free
- number is used. This can be used to create compatibility symlinks and enumerate
- devices of the same type originating from different kernel subsystems.</para>
- <para>Note: The use of the enumeration facility is unreliable for events that
- request a number at the same time. The use of enumerations in todays setups
- where devices can come and go at any time is not recommended.</para>
- </listitem>
- </varlistentry>
-
<varlistentry>
<term><option>%P</option>, <option>$parent</option></term>
<listitem>