summaryrefslogtreecommitdiff
path: root/udev.8
diff options
context:
space:
mode:
authorkay.sievers@vrfy.org <kay.sievers@vrfy.org>2003-12-10 15:40:08 -0800
committerGreg KH <gregkh@suse.de>2005-04-26 21:13:07 -0700
commit26004fcc665d14220c5b15a15ee4b2dd5d4af314 (patch)
treed89d5f8f3f63180e5108ae260c77d2361c85d0b7 /udev.8
parentbabad3ff2ce7769b65474b29d97517e816f89bbd (diff)
[PATCH] man-page mention multiple symlinks
As usual, when the stuff gets in the tree - here is a small man page update and a TODO line removal. mention multiple symlinks update example with silly symlink rule :) shorten example line to have less than 80 chars remove "want symlink support" from TODO
Diffstat (limited to 'udev.8')
-rw-r--r--udev.810
1 files changed, 5 insertions, 5 deletions
diff --git a/udev.8 b/udev.8
index 0c461967d2..7b4e17b5c4 100644
--- a/udev.8
+++ b/udev.8
@@ -94,7 +94,7 @@ file.
Every line in the rules file define the mapping between device attributes and
the device file name. It starts with a keyword defining the method used to
match, followed by one ore more keys to compare and the filename for the
-device. Optional the name for a symlink targeting the node may specified.
+device. One ore more optional symlinks targeting the node may be specified.
.br
If no matching configuration is found, the default kernel device name
is used.
@@ -175,11 +175,11 @@ NUMBER, BUS="pci", ID="00:0b.0", NAME="dsp"
# USB mouse at third port of the second hub to be called mouse1
TOPOLOGY, BUS="usb", PLACE="2.3", NAME="mouse1"
-# ttyUSB1 should always be called pda
-REPLACE, KERNEL="ttyUSB1", NAME="pda"
+# ttyUSB1 should always be called pda with two additional symlinks
+REPLACE, KERNEL="ttyUSB1", NAME="pda", SYMLINK="palmtop handheld"
-# USB webcams with symlinks to be called webcam0, webcam1, ...
-LABEL, BUS="usb", model="WebCam Version 3", NAME="video%n", SYMLINK="webcam%n"
+# multiple USB webcams with symlinks to be called webcam0, webcam1, ...
+LABEL, BUS="usb", model="WebCam V3", NAME="video%n", SYMLINK="webcam%n"
.fi
.P
Permissions and ownership for the created device files may specified at