1 .TH UDEV 8 "October 2003" "" "Linux Administrator's Manual"
3 udev \- Linux configurable dynamic device naming support
8 creates or removes device node files usually located in the /dev directory.
13 is exectuted if a kernel device is added or removed from the system.
17 reads the sysfs directory of the given device, to collect device attributes
18 like label, serial number or bus device number.
19 These attributes are passed as a key to the namedev subsystem
20 to receive a unique name for device file creation.
21 namedev maintains a database for devices present on the system.
25 queries the namedev database for the name of the device file to delete.
27 namedev expects its configuration at
28 .I /etc/udev/namedev.config.
29 The file consists of a set of lines. All empty lines and
30 lines beginning with a '#' will be ignored.
32 Every line defines the mapping between device attributes and the name of
33 the device file. It starts with a keyword defining the method for
34 overriding the default kernel naming scheme, followed by a list
35 of keys and ends with the definition of the filename for the device.
38 device label or serial number, like USB serial number, SCSI UUID or
42 device number on the bus, like PCI bus id
45 device position on bus, like physical port of USB device
48 string replacement of the kernel device name
50 If no matching configuration is found, the default kernel device name is used.
53 # USB printer to be called lp_color
54 LABEL, BUS="usb", serial="W09090207101241330", NAME="lp_color"
56 # sound card with PCI bus id 00:0b.0 to be called dsp
57 NUMBER, BUS="pci", id="00:0b.0", NAME="dsp"
59 # USB mouse at third port of the second hub to be called mouse1
60 TOPOLOGY, BUS="usb", place="2.3", NAME="mouse1"
62 # ttyUSB1 should always be called pda
63 REPLACE, KERNEL="ttyUSB1", NAME="pda"
69 /sbin/udev udev program
70 /etc/udev/* udev config and database files
71 /etc/hotplug.d/default/udev.hotplug hotplug symlink to udev program
78 .I http://linux-hotplug.sourceforge.net/
81 udev was developed by Greg Kroah-Hartman <greg@kroah.com> with much help from
82 Dan Stekloff <dsteklof@us.ibm.com> and many others.