AuxXxilium/eudev
1
0
Fork 0
mirror of https://github.com/AuxXxilium/eudev.git synced 2024-12-16 19:47:24 +07:00
Code Issues Actions Packages Projects Releases Wiki Activity

[PATCH] udev - man page update

Browse Source 
Here is a small change to the udev man page:

  - clarify the use of the NAME{all_partitions} syntax
    and add a example to udev.rules.example
  - mention the empty NAME field to ignore the device
  - prepare a SYMLINK field for the addition of Andrey's
    "multiple symlinks" documentation :)
This commit is contained in:
kay.sievers@vrfy.org 2004-03-01 22:38:44 -08:00 committed by Greg KH
parent 92c5ddee38
commit 311e9ae681
2 changed files with 18 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
etc/udev/udev.rules.examples
View File

@ -51,6 +51,10 @@ KERNEL="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", NAME="%k", SYMLINK="%c"
# DRI devices always go into a subdirectory (as per the LSB spec) # DRI devices always go into a subdirectory (as per the LSB spec)
KERNEL="card*", NAME="dri/card%n" KERNEL="card*", NAME="dri/card%n"
# create all 15 partitions of a USB flash card reader
# note the trailing spaces in the attribute, use udevinfo(8) to examine your device
BUS="scsi", SYSFS{model}="CF/MD ", NAME{all_partitions}="compactflash"
# alsa devices # alsa devices
KERNEL="controlC[0-9]*", NAME="snd/%k" KERNEL="controlC[0-9]*", NAME="snd/%k"
KERNEL="hw[CD0-9]*", NAME="snd/%k" KERNEL="hw[CD0-9]*", NAME="snd/%k"

23
udev.8
View File

@ -151,16 +151,15 @@ file.
Every line in the rules file defines the mapping between device attributes Every line in the rules file defines the mapping between device attributes
and the device file name. One ore more keys are specified to match a rule and the device file name. One ore more keys are specified to match a rule
with the current device. If all keys are matching, the rule will be applied with the current device. If all keys are matching, the rule will be applied
and the name is used for the device node. One or more optional symlinks and the name is used for the device node.
targeting the node may be specified.
.br .br
If no matching rule is found, the default kernel device name is used. If no matching rule is found, the default kernel device name is used.
.P .P
The line format is: Every rule consists of a list a comma separated fields:
.sp .sp
.I key,[key,...] name [, symlink] .IR "key " ,[ "key " ,...] " name " [, " symlink" ]
.sp .sp
where keys are: where possible fields are:
.TP .TP
.B BUS .B BUS
Match the bus type of the device. Match the bus type of the device.
@ -196,13 +195,19 @@ Match the returned string of the last
call. This key may used in any following rule after a call. This key may used in any following rule after a
.B PROGRAM .B PROGRAM
call. call.
.P .TP
The
.B NAME .B NAME
field given with the attribute 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.
.br
If given with the attribute
.BR NAME{ all_partitions } .BR NAME{ all_partitions }
will create all 15 partitions of a blockdevice. it will create all 15 partitions of a blockdevice.
This may be useful for removable media devices. This may be useful for removable media devices.
.TP
.B SYMLINK
The name of a symlink targeting the node. Multiple symlinks may be
specified by separating the names by the space character.
.P .P
.RB "The " NAME " ," SYMLINK " and " PROGRAM .RB "The " NAME " ," SYMLINK " and " PROGRAM
fields support simple printf-like string substitution: fields support simple printf-like string substitution: