with the current device. If all keys are matching, the rule will be applied
and the name is used for the device node.
.br
If no matching rule is found, the default kernel device name is used.
.P
with the current device. If all keys are matching, the rule will be applied
and the name is used for the device node.
.br
If no matching rule is found, the default kernel device name is used.
.P
.sp
.IR "key " ,[ "key " ,...] " name " [, " symlink" ]
.sp
.sp
.IR "key " ,[ "key " ,...] " name " [, " symlink" ]
.sp
This makes it possible to specify additional symlinks in a possibly
separate rules file, while the device nodes are maintained by the
distribution provided rules file.
This makes it possible to specify additional symlinks in a possibly
separate rules file, while the device nodes are maintained by the
distribution provided rules file.
.P
.RB "The " NAME " ," SYMLINK " and " PROGRAM
fields support simple printf-like string substitution:
.P
.RB "The " NAME " ," SYMLINK " and " PROGRAM
fields support simple printf-like string substitution:
field for the obvious reason.)
.br
A single part of the string, separated by a space character
field for the obvious reason.)
.br
A single part of the string, separated by a space character
-may be selected by specifying the part number as a attribute:
-.BI %c{ part }
+may be selected by specifying the part number as an attribute:
+.BI %c{ N }
+If the number is followed by the + char this part plus
+all remaining parts of the result string are substituted:
+.BI %c{ N+ }