udev

</tr> </table>

udev is the device manager for the Linux 2.6 kernel series. Primarily, it manages device nodes in /dev. It is the successor of devfs and hotplug, which means that it handles the /dev directory and all user space actions when adding/removing devices, including firmware load.

The latest versions of udev depend on the latest version of the uevent interface of the Linux kernel, which has been updated or introduced with Linux kernel 2.6.13. A system using a new version of udev will not boot with kernels older than 2.6.13 unless udev is disabled and a traditional /dev directory is used for device access.

[edit] Overview

Unlike traditional Unix systems, where the device nodes in the /dev directory have been a static set of files, the Linux udev device manager dynamically provides only the nodes for the devices actually present on a system. Although devfs used to provide similar functionality, advocates of udev cited a number of reasons^[1] for preferring its implementation over devfs:

• udev supports persistent device naming, which does not depend on, for example, the order in which the devices are plugged into the system. The default udev setup provides persistent names for storage devices. Any hard disk is recognized by its unique filesystem id, the name of the disk and the physical location on the hardware it is connected to.
• udev executes entirely in user space, as opposed to devfs' kernel space. One consequence is that udev moved the naming policy out of the kernel and can run arbitrary programs to compose a name for the device from the device's properties, before the node is created.

[edit] Operation

udev is a generic kernel device manager. It runs as a daemon on a Linux system and listens to uevents the kernel sends out (via netlink socket) if a new device is initialized or a device is removed from the system. The system provides a set of rules that match against exported values of the event and properties of the discovered device. A matching rule will possibly name and create a device node and run configured programs to set-up and configure the device.

udev rules can match on properties like the kernel subsystem, the kernel device name, the physical location of the device, or properties like the device's serial number. Rules can also request information from external programs to name a device or specify a custom name that will always be the same, regardless of the order devices are discovered by the system.

A common way to use udev on Linux systems is to let it send events through a socket to HAL or DeviceKit, which will perform further device-specific actions. For example, HAL/DeviceKit will notify other software running on the system that the new hardware has arrived by issuing a broadcast message on the D-Bus IPC system to all interested processes. In this way, desktops such as GNOME or KDE will be able to pop up a file browser on attached USB flash drives and SD cards, for example.^[2]

[edit] Architecture

The system is divided in three parts:

• The library libsysfs, that allows access to device information (dropped since version 080)
• The daemon udevd, in user space, that manages the virtual /dev
• The administrative command udevadm for diagnostics

The system gets calls from the kernel via netlink socket. Earlier versions used hotplug, adding a link to themselves in /etc/hotplug.d/default with this purpose.

[edit] Authors

udev was developed by Greg Kroah-Hartman and Kay Sievers, with much help from Dan Stekloff, among others.

[edit] References

[edit] External links

• udev home at kernel.org
• Kay Sievers on the recent state of udev
• Discussion of udev rules
• A simple introduction to writing rules for udev
• udev – A Userspace Implementation of devfs by Greg Kroah-Hartman
• PySDM (Storage Device Manager and udev rule writer)de:Udev