1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
|
.TH UDEV 8 "October 2003" "" "Linux Administrator's Manual"
.SH NAME
udev \- Linux configurable dynamic device naming support
.SH SYNOPSIS
.BI udev " hotplug-subsystem"
.SH "DESCRIPTION"
.B udev
creates or removes device node files usually located in the /dev directory.
Its goal is to provide a dynamic device directory that contains only the files
for devices that are actually present.
.P
As part of the
.B hotplug
subsystem,
.B udev
is executed if a kernel device is added or removed from the system.
On device creation,
.B udev
reads the sysfs directory of the given device to collect device attributes
like label, serial number or bus device number.
These attributes are treated as a key
to determine a unique name for device file creation.
.B udev
maintains a database for devices present on the system.
.br
On device removal,
.B udev
queries the internal database for the name of the device file to be deleted.
.SH "CONFIGURATION"
.B udev
expects its configuration at
.I /etc/udev/udev.config.
The file consists of a set of lines. All empty lines and
lines beginning with a '#' will be ignored.
.br
Every line defines 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 is used.
.P
The line format is:
.RS
.sp
.I method, key,[key,...] name
.sp
.RE
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
.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
.TP
.B NUMBER
device number on the bus, like PCI bus id
.br
keys: \fBBUS\fP, \fBID\fP
.TP
.B TOPOLOGY
device position on bus, like physical port of USB device
.br
keys: \fBBUS\fP, \fBPLACE\fP
.TP
.B REPLACE
string replacement of the kernel device name
.br
key: \fBKERNEL_NAME\fP
.P
The methods are applied in the following order:
.B CALLOUT
,
.B LABEL
,
.B NUMBER
,
.B TOPOLOGY
,
.B REPLACE
.P
The
.B NAME
and
.B PROGRAM
fields support simple printf-like string subtitution:
.RS
.TP
.B %n
the "kernel number" of the device
for example, 'sda3' has a "kernel number" of '3'
.TP
.B %M
the kernel major number for the device
.TP
.B %m
the kernel minor number for the device
.TP
.B %b
the bus id for the device
.TP
.B %c
the CALLOUT program return value (this does not work within the PROGRAM field for the obvious reason.)
.RE
.P
A sample \fIudev.conf\fP might look like this:
.sp
.nf
# if /sbin/scsi_id returns "OEM 0815" device will be called disk1
CALLOUT, BUS="scsi", PROGRAM="/sbin/scsi_id", ID="OEM 0815", NAME="disk1"
# USB printer to be called lp_color
LABEL, BUS="usb", serial="W09090207101241330", NAME="lp_color"
# sound card with PCI bus id 00:0b.0 to be called dsp
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"
# USB webcams to be called webcam0, webcam1, ...
LABEL, BUS="usb", model="WebCam Version 3", NAME="webcam%n"
.fi
.P
Permissions and ownership for the created device files may specified at
.I /etc/udev/udev.permissions.
The file consists of a set of lines. All empty lines and
lines beginning with a '#' will be ignored.
.br
Every line lists a device name followed by numeric owner, group and permission
mode. All values are separated by colons. The name field may end with a
wildcard to apply the values to a whole class of devices.
.br
If udev was built using glibc, string owner and group names may be used.
.sp
A sample \fIudev.permissions\fP might look like this:
.sp
.nf
#name:user:group:mode
ttyUSB1:0:8:0660
video*:500:500:0660
dsp1:::0666
.fi
.P
If
.B
udev
was built using glibc, string owner and group names may be used.
.SH "FILES"
.nf
.ft B
.ft
/sbin/udev udev program
/etc/udev/* udev config and database files
/etc/hotplug.d/default/udev.hotplug hotplug symlink to udev program
.fi
.LP
.SH "SEE ALSO"
.BR hotplug (8)
.PP
The
.I http://linux-hotplug.sourceforge.net/
web site.
.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.
|
