X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=udev%2Fudev.xml;h=fca0dad7bff1956c8324e8dd75053ace61bb5d38;hp=9b40cbb03e88c7825c4246490dba8cd2a105e4f9;hb=220893b3cbdbf8932f95c44811b169a8f0d33939;hpb=d0878effb94b9375185e9f590e1708b3664b8ab3 diff --git a/udev/udev.xml b/udev/udev.xml index 9b40cbb03..fca0dad7b 100644 --- a/udev/udev.xml +++ b/udev/udev.xml @@ -41,8 +41,8 @@ Configuration - udev configuration files are placed in /etc/udev/ - and /lib/udev/. All empty lines or lines beginning with + udev configuration files are placed in /etc/udev + and /usr/lib/udev. All empty lines or lines beginning with '#' are ignored. Configuration file @@ -71,14 +71,18 @@ Rules files The udev rules are read from the files located in the - default rules directory /lib/udev/rules.d/, - the custom rules directory /etc/udev/rules.d/ - and the temporary rules directory /run/udev/rules.d/. - All rule files are collectively sorted and processed in lexical order, - regardless of the directories in which they live. However, files in - /etc/udev/rules.d/ take precedence over files with - the same name in /lib/udev/rules.d/; this can be - used to ignore a default rules file if needed. + system rules directory /usr/lib/udev/rules.d, + the local administration directory /etc/udev/rules.d + and the volatile runtime directory /run/udev/rules.d. + All rules files are collectively sorted and processed in lexical order, + regardless of the directories in which they live. However, files with + identical file names replace each other. Files in /run + have the highest priority, files in /etc take precedence + over files with the same name in /lib. This can be + used to overwrite a system rules file if needed; a symlink in + /etc with the same name as a rules file in + /lib, pointing to /dev/null, + disables the rules file entirely. Rule files must have the extension .rules; other extensions are ignored. @@ -163,9 +167,8 @@ - Match the name of the node or network interface. It can - be used once the NAME key has been set in one of the preceding - rules. + Match the name of a network interface. It can be used once the + NAME key has been set in one of the preceding rules. @@ -233,6 +236,13 @@ + + + + Search the devpath upwards for a device with matching tag. + + + @@ -308,17 +318,8 @@ - What a network interface should be named. - Also, as a temporary workaround, this is what a device node - should be named; usually the kernel provides the defined node name or creates - and removes the node before udev even receives any event. Changing - the node name from the kernel's default creates inconsistencies - and is not supported. If the kernel and NAME specify different names, - an error is logged. udev is only expected to handle device node - permissions and to create additional symlinks, not to change - kernel-provided device node names. Instead of renaming a device node, - SYMLINK should be used. However, symlink names must never conflict with - device node names, as that would result in unpredictable behavior. + The name to use for a network interface. The name of a device node + can not be changed by udev, only additional symlinks can be created. @@ -387,7 +388,7 @@ detached from the event process itself. If no absolute path is given, the program is expected to live in the directory provided at compile-time to configure via --libexecdir - (this is usually /lib/udev), otherwise the absolute + (this is usually /usr/lib/udev), otherwise the absolute path must be specified. The program name and following arguments are separated by spaces. Single quotes can be used to specify arguments with spaces. @@ -456,9 +457,6 @@ - If no option is given, udev chooses between - and based on the executable bit of the file - permissions. @@ -503,7 +501,7 @@ Apply the permissions specified in this rule to the static device node with the specified name. Static device nodes might be provided by kernel modules - or copied from /lib/udev/devices. These nodes might not have + or copied from /usr/lib/udev/devices. These nodes might not have a corresponding kernel device at the time udevd is started; they can trigger automatic kernel module loading. @@ -511,8 +509,8 @@ - Watch the device node with inotify; when closed after being opened for - writing, a change uevent is synthesised. + Watch the device node with inotify; when the node is closed after being opened for + writing, a change uevent is synthesized. @@ -629,7 +627,7 @@ - The current name of the device node. If not changed by a rule, it is the + The current name of the device. If not changed by a rule, it is the name of the kernel device. @@ -657,10 +655,9 @@ - , + , - The name of a temporary device node created to provide access to - the device from a external program before the real node is created. + The name of the device node.