diff options
author | kay.sievers@vrfy.org <kay.sievers@vrfy.org> | 2004-03-09 19:50:22 -0800 |
---|---|---|
committer | Greg KH <gregkh@suse.de> | 2005-04-26 21:35:08 -0700 |
commit | 2bd07cf29b30b424d4b5a17882d0cab0b235153b (patch) | |
tree | 1adcdd217520c71b465ad678478390c46376a2f3 | |
parent | 17794d77b97fcb8af263bcecbe03dad5d0e9a89a (diff) |
[PATCH] put symlink only rules to the man page
Here we mention the "symlink only - add it to another rule" feature
to the man page. Andrey, does this describe what you have implemented :)
-rw-r--r-- | udev.8 | 13 |
1 files changed, 11 insertions, 2 deletions
@@ -200,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 } @@ -211,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: |