X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=udev.8;h=24ff4e28a964fca2ea698282ffaff7fe8ea1a4f9;hp=c0dc68b80360a2454a882ec319d2c255dde03a87;hb=2bd07cf29b30b424d4b5a17882d0cab0b235153b;hpb=a6f01502bd2a76d1f9d90abb7bbeebd8f6893ed9 diff --git a/udev.8 b/udev.8 index c0dc68b80..24ff4e28a 100644 --- a/udev.8 +++ b/udev.8 @@ -25,7 +25,7 @@ The default behavior of .B udev is to wait until all the sysfs files of the device chain are populated. If set .B udev -will will continue, regardless of the state of the device representation. +will continue, regardless of the state of the device representation. .SH "DESCRIPTION" .B udev creates or removes device node files usually located in the /dev directory. @@ -178,6 +178,9 @@ Match the topological position on bus, like physical port of USB device Match sysfs device attribute like label, vendor, USB serial number, SCSI UUID or file system label. Up to 5 different sysfs files can be checked, with all of the values being required in order to match the rule. +.br +Trailing whitespace characters in the sysfs attribute value are ignored, if +the key doesn't have any trailing whitespace characters by itself. .TP .B PROGRAM Call external program. This key is valid if the program returns successful. @@ -197,8 +200,7 @@ call. This key may used in any following rule after a call. .TP .B NAME -The name of the node to be created. If the name field is omitted or its -value is empty, the device will be ignored and no node will be created. +The name of the node to be created. .br If given with the attribute .BR NAME{ all_partitions } @@ -208,6 +210,16 @@ This may be useful for removable media devices. .B SYMLINK The name of a symlink targeting the node. Multiple symlinks may be specified by separating the names by the space character. +.br +If both the name and the symlink fields are omitted or its +values empty, the device will be ignored and no node will be created. +.br +If only the symlink field is given and the name field is omitted, +the rule will not be applied immediatly, but the symlink field is added +to the symlink list of the rule which will create the node. +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: