1 udev - userspace device management
3 For more information see the files in the docs/ directory.
6 Integrating udev in the system has complex dependencies and differs from distro
7 to distro. All major distros depend on udev these days and the system may not
8 work without a properly installed version. The upstream udev project does not
9 recommend to replace a distro's udev installation with the upstream version.
12 - Version 2.6.25 of the Linux kernel with sysfs, procfs, signalfd, inotify,
13 unix domain sockets, networking and hotplug enabled.
15 - For reliable operation, the kernel must not use the CONFIG_SYSFS_DEPRECATED*
18 - Unix domain sockets (CONFIG_UNIX) as a loadable kernel module is not
21 - The proc filesystem must be mounted on /proc/, the sysfs filesystem must
22 be mounted at /sys/. No other locations are supported by udev.
24 - The system must have the following group names resolvable at udev startup:
25 disk, cdrom, floppy, tape, audio, video, lp, tty, dialout, kmem.
26 Especially in LDAP setups, it is required, that getgrnam() is able to resolve
27 these group names with only the rootfs mounted, and while no network is
31 Udev creates and removes device nodes in /dev/, based on events the kernel
32 sends out on device discovery or removal.
34 - Early in the boot process, the /dev/ directory should get a 'tmpfs'
35 filesystem mounted, which is maintained by udev. Created nodes or changed
36 permissions will not survive a reboot, which is intentional.
38 - The content of /lib/udev/devices/ directory which contains the nodes,
39 symlinks and directories, which are always expected to be in /dev, should
40 be copied over to the tmpfs mounted /dev, to provide the required nodes
41 to initialize udev and continue booting.
43 - The old hotplug helper /sbin/hotplug should be disabled in the kernel
44 configuration, it is not needed, and may render the system unusable
45 because of a fork-bombing behavior.
47 - All kernel events are matched against a set of specified rules in
48 /lib/udev/rules.d/ which make it possible to hook into the event
49 processing to load required kernel modules and setup devices. For all
50 devices the kernel exports a major/minor number, udev will create a
51 device node with the default kernel name, or the one specified by a
54 Please direct any comment/question/concern to the linux-hotplug mailing list at:
55 linux-hotplug@vger.kernel.org