[PATCH] Makefile tweaks for the DBUS build.

[elogind.git] / udev.8

diff --git a/udev.8 b/udev.8
index c6a92962554a4e201cdb832752661d74e2f9c05e..0c461967d2444f6bfc9093f6c804d2c10b5ecaad 100644 (file)
--- a/udev.8
+++ b/udev.8
@@ -27,7 +27,9 @@ On device removal,
 .B udev
 queries the internal database for the name of the device file to be deleted.
 .SH "CONFIGURATION"
 .B udev
 queries the internal database for the name of the device file to be deleted.
 .SH "CONFIGURATION"

-All udev configuration files consist of a set of lines of text.  All empty
+All
+.B udev
+configuration files consist of a set of lines of text.  All empty

 lines, and lines beginning with a '#' will be ignored.
 .P
 
 lines, and lines beginning with a '#' will be ignored.
 .P
 


@@ -61,7 +63,7 @@ permissions file.  The default value for this is
 .I 0666
 .br
 .P
 .I 0666
 .br
 .P

-A sample \fIudev.conf\fP might look like this:
+.RI "A sample " udev.conf " might look like this:

 .sp
 .nf
 # udev_root - where in the filesystem to place the device nodes
 .sp
 .nf
 # udev_root - where in the filesystem to place the device nodes


@@ -83,7 +85,7 @@ default_mode="0666"
 .P
 The rules for udev to use when naming devices may specified at
 .I /etc/udev/udev.rules
 .P
 The rules for udev to use when naming devices may specified at
 .I /etc/udev/udev.rules

-or specified by the 
+or specified by the

 .I udev_rules
 value in the 
 .I /etc/udev/udev.conf
 .I udev_rules
 value in the 
 .I /etc/udev/udev.conf


@@ -92,85 +94,73 @@ 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
 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. If no matching configuration is found, the default kernel device name
+device. Optional the name for a symlink targeting the node may specified.
+.br
+If no matching configuration is found, the default kernel device name

 is used.
 .P
 The line format is:
 is used.
 .P
 The line format is:

-.RS

 .sp
 .sp

-.I method, key,[key,...] name
+.I method, key,[key,...] name [, symlink]

 .sp
 .sp

-.RE

 where valid methods with corresponding keys are:
 .TP
 .B CALLOUT
 calling external program, that returns a string to match
 .br
 where valid methods with corresponding keys are:
 .TP
 .B CALLOUT
 calling external program, that returns a string to match
 .br

-keys: \fBBUS\fP, \fBPROGRAM\fP, \fBID\fP
+.RB "keys: " BUS ", " PROGRAM ", " ID

 .TP
 .B LABEL
 device label or serial number, like USB serial number, SCSI UUID or
 file system label
 .br
 .TP
 .B LABEL
 device label or serial number, like USB serial number, SCSI UUID or
 file system label
 .br

-keys: \fBBUS\fP, \fIsysfs_attribute\fP
+.RB "keys: " BUS ", "
+.I sysfs_attribute

 .TP
 .B NUMBER
 device number on the bus, like PCI bus id
 .br
 .TP
 .B NUMBER
 device number on the bus, like PCI bus id
 .br

-keys: \fBBUS\fP, \fBID\fP
+.RB "keys: " BUS ", " ID

 .TP
 .B TOPOLOGY
 device position on bus, like physical port of USB device
 .br
 .TP
 .B TOPOLOGY
 device position on bus, like physical port of USB device
 .br

-keys: \fBBUS\fP, \fBPLACE\fP
+.RB "keys: " BUS ", " PLACE

 .TP
 .B REPLACE
 string replacement of the kernel device name
 .br
 .TP
 .B REPLACE
 string replacement of the kernel device name
 .br

-key: \fBKERNEL_NAME\fP
+.RB "key: " KERNEL_NAME

 .P
 The methods are applied in the following order:
 .P
 The methods are applied in the following order:

-.B CALLOUT
-,
-.B LABEL
-,
-.B NUMBER
-,
-.B TOPOLOGY
-,
-.B REPLACE
+.BR CALLOUT ", " LABEL ", " NUMBER ", " TOPOLOGY ", " REPLACE "."

 .P
 .P

-The 
-.B NAME 
-and 
-.B PROGRAM 
-fields support simple printf-like string subtitution:
-.RS
+.RB "The " NAME " ," SYMLINK " and " PROGRAM
+fields support simple printf-like string substitution:

 .TP
 .B %n
 .TP
 .B %n

-the "kernel number" of the device
+The "kernel number" of the device.

 for example, 'sda3' has a "kernel number" of '3'
 .TP
 .B %M
 for example, 'sda3' has a "kernel number" of '3'
 .TP
 .B %M

-the kernel major number for the device
+The kernel major number for the device.

 .TP
 .B %m
 .TP
 .B %m

-the kernel minor number for the device
+The kernel minor number for the device.

 .TP
 .B %b
 .TP
 .B %b

-the bus id for the device
+The bus id for the device.

 .TP
 .B %c
 .TP
 .B %c

-the CALLOUT program returned string
-(this does not work within the PROGRAM field for the obvious reason.)
+The CALLOUT program returned string.
+(This does not work within the PROGRAM field for the obvious reason.)

 .TP
 .B %D
 Use the devfs style disk name for this device.
 For partitions, this will result in 'part%n'
 .TP
 .B %D
 Use the devfs style disk name for this device.
 For partitions, this will result in 'part%n'

-If this is not a partition, it will result in 'disk'
-.RE
+If this is not a partition, it will result in 'disk'.

 .P
 .P

-A sample \fIudev.rules\fP might look like this:
+.RI "A sample " udev.rules " might look like this:"

 .sp
 .nf
 # if /sbin/scsi_id returns "OEM 0815" device will be called disk1
 .sp
 .nf
 # if /sbin/scsi_id returns "OEM 0815" device will be called disk1


@@ -188,29 +178,28 @@ 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
 REPLACE, KERNEL="ttyUSB1", NAME="pda"
 

-# USB webcams to be called webcam0, webcam1, ...
-LABEL, BUS="usb", model="WebCam Version 3", NAME="webcam%n"
+# USB webcams with symlinks to be called webcam0, webcam1, ...
+LABEL, BUS="usb", model="WebCam Version 3", NAME="video%n", SYMLINK="webcam%n"

 .fi
 .P
 Permissions and ownership for the created device files may specified at
 .I /etc/udev/udev.permissions
 .fi
 .P
 Permissions and ownership for the created device files may specified at
 .I /etc/udev/udev.permissions

-or specified by the 
+or specified by the

 .I udev_permission
 .I udev_permission

-value in the 
+value in the

 .I /etc/udev/udev.conf
 file.
 .br
 Every line lists a device name followed by owner, group and permission
 mode. All values are separated by colons. The name field may contain a
 .I /etc/udev/udev.conf
 file.
 .br
 Every line lists a device name followed by owner, group and permission
 mode. All values are separated by colons. The name field may contain a

-wildcard to apply the values to a whole class of devices.
+pattern to apply the values to a whole class of devices.

 .br
 If
 .B udev
 was built using klibc or is used before the user database is accessible (e.g.
 .br
 If
 .B udev
 was built using klibc or is used before the user database is accessible (e.g.

-.B initrd
-), only numeric owner and group values may be used.
+.BR initrd "(4)), only numeric owner and group values may be used."

 .sp
 .sp

-A sample \fIudev.permissions\fP might look like this:
+.RI "A sample " udev.permissions " might look like this:"

 .sp
 .nf
 #name:user:group:mode
 .sp
 .nf
 #name:user:group:mode


@@ -221,9 +210,7 @@ dsp1:::0666
 .fi
 .P
 A number of different fields in the above configuration files support a simple
 .fi
 .P
 A number of different fields in the above configuration files support a simple

-form of wildcard matching.  This form is based on the fnmatch(3) style, and
-supports the following fields:
-.RS
+form of shell style pattern matching. It supports the following pattern characters:

 .TP
 .B *
 Matches zero, one, or more characters.
 .TP
 .B *
 Matches zero, one, or more characters.


@@ -235,12 +222,10 @@ Matches any single character, but does not match zero characters.
 Matches any single character specified within the brackets. For example, the
 pattern string "tty[SR]" would match either "ttyS" or "ttyR".  Ranges are also
 supported within this match with the '-' character.  For example, to match on
 Matches any single character specified within the brackets. For example, the
 pattern string "tty[SR]" would match either "ttyS" or "ttyR".  Ranges are also
 supported within this match with the '-' character.  For example, to match on

-the range of all digits, the pattern [0-9] would be used.
-.RE
+the range of all digits, the pattern [0-9] would be used. If the first character
+following the '[' is a '!' then any character not enclosed is matched.

 .SH "FILES"
 .nf
 .SH "FILES"
 .nf

-.ft B
-.ft

 /sbin/udev                           udev program
 /etc/udev/*                          udev config files
 /etc/hotplug.d/default/udev.hotplug  hotplug symlink to udev program
 /sbin/udev                           udev program
 /etc/udev/*                          udev config files
 /etc/hotplug.d/default/udev.hotplug  hotplug symlink to udev program


@@ -255,4 +240,5 @@ web site.
 .SH AUTHORS
 .B udev
 was developed by Greg Kroah-Hartman <greg@kroah.com> with much help from
 .SH AUTHORS
 .B udev
 was developed by Greg Kroah-Hartman <greg@kroah.com> with much help from

-Dan Stekloff <dsteklof@us.ibm.com> and many others.
+Dan Stekloff <dsteklof@us.ibm.com>, Kay Sievers <kay.sievers@vrfy.org>, and
+many others.