X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=udev%2Fudev.xml;h=7b31173b21870f6cc159e0331a7d342ec4f44b81;hb=12a362be5c1982f80dbfb75bda070208a2c99cdf;hp=ab82012cee8a92d2c12fa04db0397f86132f621b;hpb=c096407caaf1f3c03bb816e195eebb886662b03a;p=elogind.git diff --git a/udev/udev.xml b/udev/udev.xml index ab82012ce..7b31173b2 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,9 +71,9 @@ Rules files The udev rules are read from the files located in the - system rules directory /lib/udev/rules.d/, - the local administration directory /etc/udev/rules.d/ - and the volatile runtime directory /run/udev/rules.d/. + 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 @@ -398,7 +398,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. @@ -511,7 +511,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.