the custom rules directory <filename>/etc/udev/rules.d/</filename>
and the temporary rules directory <filename>/dev/.udev/rules.d/</filename>.
All rule files are sorted and processed in lexical order, regardless
- in which of these directories they live.</para>
+ in which of these directories they live. Files in
+ <filename>/etc/udev/rules.d/</filename> have precedence over files with
+ the same name in <filename>/lib/udev/rules.d/</filename>. This can be
+ used to ignore a default rules file if needed.</para>
- <para>Rule files are required to have a unique name, duplicate file names
- are ignored. Files in <filename>/etc/udev/rules.d/</filename> have precedence
- over files with the same name in <filename>/lib/udev/rules.d/</filename>. This
- can be used to ignore a default rules file if needed.</para>
+ <para>Rule files must end in <filename>.rules</filename>, other extensions
+ are ignored.</para>
<para>Every line in the rules file contains at least one key value pair.
There are two kind of keys, match and assignment keys.
writing, a change uevent will be synthesised.</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><option>nowatch</option></term>
+ <listitem>
+ <para>Disable the watching of a device node with inotify.</para>
+ </listitem>
+ </varlistentry>
</variablelist>
</listitem>
</varlistentry>
<listitem>
<para>The value of a sysfs attribute found at the device, where
all keys of the rule have matched. If the matching device does not have
- such an attribute, follow the chain of parent devices and use the value
- of the first attribute that matches.
+ such an attribute, and a previous KERNELS, SUBSYSTEMS, DRIVERS, or
+ ATTRS test selected a parent device, use the attribute from that
+ parent device.
If the attribute is a symlink, the last element of the symlink target is
returned as the value.</para>
</listitem>