From 1021e6dfcc339728d83bfa5a3e8cd73bb37dbcef Mon Sep 17 00:00:00 2001 From: Kay Sievers Date: Tue, 22 Nov 2011 23:51:17 +0100 Subject: [PATCH] man: clarify 'config file stack' --- udev/udev.xml | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/udev/udev.xml b/udev/udev.xml index a7853485..ab82012c 100644 --- a/udev/udev.xml +++ b/udev/udev.xml @@ -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 /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. -- 2.39.5