.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
and receives uevents directly from the kernel if a device is added or removed form the system.
.PP
If udev receives a device event, it matches its configured rules against the available device attributes provided in sysfs to identify the device. Rules that match, may provide additional device information or specify a device node name and multiple symlink names and instruct udev to run additional programs as part of the device event handling.
.SH "CONFIGURATION"
.PP
and receives uevents directly from the kernel if a device is added or removed form the system.
.PP
If udev receives a device event, it matches its configured rules against the available device attributes provided in sysfs to identify the device. Rules that match, may provide additional device information or specify a device node name and multiple symlink names and instruct udev to run additional programs as part of the device event handling.
.SH "CONFIGURATION"
.PP
-The name of the udev rules file or directory to look for files with the suffix
-\fI.rules\fR. Multiple rule files are read in lexical order. The default value is
+The name of the udev rules file or directory to look for files with the suffix
+\fI.rules\fR. Multiple rule files are read in lexical order. The default value is
directory or at the location specified value in the configuraton file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignement keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. A matching rule may specify the name of the device node, add a symlink pointing to the node, or run a specified program as part of the event handling. If no matching rule is found, the default device node name is used.
.PP
A rule may consists of a list of one or more key value pairs separated by a comma. Each key has a distinct operation, depending on the used operator. Valid operators are:
directory or at the location specified value in the configuraton file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignement keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. A matching rule may specify the name of the device node, add a symlink pointing to the node, or run a specified program as part of the event handling. If no matching rule is found, the default device node name is used.
.PP
A rule may consists of a list of one or more key value pairs separated by a comma. Each key has a distinct operation, depending on the used operator. Valid operators are:
keys can be specified per rule. All attributes must match on the same device. Trailing whitespace in the attribute values is ignored, if the specified match value does not contain trailing whitespace itself.
.TP
\fBENV{\fR\fB\fIkey\fR\fR\fB}\fR
keys can be specified per rule. All attributes must match on the same device. Trailing whitespace in the attribute values is ignored, if the specified match value does not contain trailing whitespace itself.
.TP
\fBENV{\fR\fB\fIkey\fR\fR\fB}\fR
-Import the printed result or the value of a file in environment key format into the event environment.
-\fBprogram\fR
-will execute an external program and read its output.
-\fBfile\fR
+Import the printed result or the value of a file in environment key format into the event environment.
+\fBprogram\fR
+will execute an external program and read its output.
+\fBfile\fR
will inport a text file. If no option is given, udev will determine it from the executable bit of of the file permissions.
.TP
\fBWAIT_FOR_SYSFS\fR
Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues.
.TP
\fBOPTIONS\fR
will inport a text file. If no option is given, udev will determine it from the executable bit of of the file permissions.
.TP
\fBWAIT_FOR_SYSFS\fR
Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues.
.TP
\fBOPTIONS\fR
-\fBlast_rule\fR
-stops further rules application. No later rules will have any effect.
-\fBignore_device\fR
-will ignore this event completely.
-\fBignore_remove\fR
-will ignore any later remove event for this device. This may be useful as a workaround for broken device drivers.
-\fBall_partitions\fR
+\fBlast_rule\fR
+stops further rules application. No later rules will have any effect.
+\fBignore_device\fR
+will ignore this event completely.
+\fBignore_remove\fR
+will ignore any later remove event for this device. This may be useful as a workaround for broken device drivers.
+\fBall_partitions\fR
-The string returned by the external program requested with PROGRAM. A single part of the string, separated by a space character may be selected by specifying the part number as an attribute:
-\fB%c{N}\fR. If the number is followed by the '+' char this part plus all remaining parts of the result string are substituted:
+The string returned by the external program requested with PROGRAM. A single part of the string, separated by a space character may be selected by specifying the part number as an attribute:
+\fB%c{N}\fR. If the number is followed by the '+' char this part plus all remaining parts of the result string are substituted: