Udev

This page is a translated version of the page Udev and the translation is 16% complete.

Outdated translations are marked like this.

Other languages:

Resources

Nicht zu verwechseln mit eudev.

udev (user /dev) ist systemd's Gerätemanager für den Linux-Kernel. Er verwaltet Geräteknoten in /dev und wickelt alle User-Space-Aktionen beim Hinzufügen und Entfernen von Geräten ab.

udev aus dem Paket sys-apps/systemd-utils wird als Standard-Gerätemanager für Gentoo-Systeme verwendet, die das OpenRC-Init-System verwenden, unabhängig von systemd.

Was ist udev?

The /dev directory

Most Linux users understand that /dev/sda1 is just a fast way of referring to the first partition on the first disk that the kernel found. That's pretty easy, right?

But consider hotpluggable devices like USB, IEEE 1394, hot-swappable PCI, etc. What is the first device for each of these? And for how long? What will the other devices be named when the first one disappears? How will that affect ongoing transactions? Wouldn't it be fun if a printing job were suddenly moved from a high-end laser printer to an almost-dead matrix printer just because someone decided to pull the plug on the laser printer (which just happened to be the first printer)?

Enter the device manager. A modern device manager must:

Run in userspace.
Dynamically create and remove device files.
Provide consistent device naming.
Provide a userspace application program interface (API).

Every time a change happens within the device structure, the kernel emits a uevent which gets picked up by the device manager. The device manager then follows the rules declared in the /etc/udev/rules.d, /run/udev/rules.d and /lib/udev/rules.d directories. Based on the information contained within the uevent, it finds the rule or rules it needs to trigger and performs the required actions. These actions may involve the creation or deletion of device files, and may also trigger the loading of particular firmware files into kernel memory.

Installation

Wichtig
When updating udev, check the udev upgrade guide for information that can prevent unbootable systems.

Kernel

udev requires the following kernel options:

KERNEL

General setup  --->
    [*] Configure standard kernel features (expert users)  --->
        [ ] Enable deprecated sysfs features to support old userspace tools
        [*] Enable signalfd() system call
Enable the block layer  --->
    [*] Block layer SG support v4
Networking support  --->
    Networking options  --->
        <*> Unix domain sockets
Device Drivers  --->
    Generic Driver Options  --->
        ()  path to uevent helper
        [*] Maintain a devtmpfs filesystem to mount at /dev
    < > ATA/ATAPI/MFM/RLL support (DEPRECATED)  --->
File systems  --->
    [*] Inotify support for userspace
    Pseudo filesystems --->
        [*] /proc file system support
        [*] sysfs file system support

USE-Flags

Portage knows the udev USE flag for enabling support for udev in other packages. Adding this USE flag value to the USE flag list (default in all Linux profiles) will pull in the virtual/udev package automatically:

DATEI /etc/portage/make.conf

USE="udev"

USE flags for sys-apps/systemd-utils Utilities split out from systemd for OpenRC users

`+acl`	Add support for Access Control Lists
`+kmod`	Enable kernel module loading via sys-apps/kmod
`+tmpfiles`	Enable systemd-tmpfiles
`+udev`	Enable systemd-udev (userspace device manager)
`boot`	Enable systemd-boot (UEFI boot manager)
`kernel-install`	Enable kernel-install
`secureboot`	Automatically sign efi executables using user specified key
`selinux`	!!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur
`split-usr`	Enable behavior to support maintaining /bin, /lib, /sbin and /usr/sbin separately from /usr/bin and /usr/lib
`sysusers`	Enable systemd-sysusers
`test`	Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
`ukify`	Enable systemd-ukify

Data provided by the Gentoo Package Database · Last update: 2024-10-30 15:00 More information about USE flags

Emerge

After setting USE flags update the system so the changes take effect:

root #emerge --ask --changed-use --deep @world

Konfiguration

Service

To start udev at boot time, add it to the sysinit runlevel. This can be done by issuing the following command with root privileges:

root #rc-update add udev sysinit

Erweiterte Konfiguration

Rules

udev provides a set of rules that match against exported values of uevents (events sent by the kernel) and properties of the discovered device. A matching rule will possibly name and create a device node and run configured programs to setup and configure the device.

The rule definitions are stored in two locations:

/lib/udev/rules.d/ - Rules in this directory are installed by certain packages, they generally should not be changed by users;
/etc/udev/rules.d/ - This folder is for end-user specified rules. Any new rules should be added in this directory;

In these directories, multiple rule files (with suffix .rules) are traversed in alphanumerical order. Inside the rules files, udev will find expressions that might match a uevent together with the state to match (is the uevent because a device is added or removed) and the command to execute.

The event matching is based on information such as:

The SUBSYSTEM of the uevent (for which type of device is the uevent fired);
The ACTION that is taken (add, change, or remove);
One or more attributes (through ATTR or ATTRS), such as the device class, vendor or other device information;
The kernel-provided name (through KERNEL), such as sd* (for SCSI/SATA disks) or input* (for input devices such as mice and keyboards);
One or more environment settings (through ENV), used to send information between multiple rules.

Based on this information, the rule can then state if:

Some information needs to be shared with later events (through environment variables)
Links need to be created in /dev
Commands need to be executed

Udev does this for every rule that matches (it does not stop after the first match) to allow a flexible device management approach.

Persistent device names

The kernel detects devices asynchronously, udev mirrors the kernel's sysfs filesystem and so the devices are named and numbered in order of detection. So by default udev provides no persistent device names. However there are mechanisms for some device classes to provide these:

Udev creates for storage devices additional symlinks based on the device's ID, label, UUID and path. See the /dev/disk/by-* directory. So instead of using e.g. the device file /dev/sda use the file /dev/disk/by-label/SOME_LABEL.

The same for input devices in the /dev/input directory.

Using custom rules enables users to create their own device files.

Predictable network interface naming

The new network interface naming convention is not the same. So the symlinks used by netifrc will need to be re-linked. Use /etc/init.d/net.lo as a link target for whatever interface names need to be added. Be sure to replace <interface_name> in the commands below with the Ethernet interface names present on the system. It is possible to discover which interfaces exist by running the ip link command:

user $ip link

Create a symbolic link for the existing interfaces in the /etc/init.d/ directory:

root #

ln -s /etc/init.d/net.lo /etc/init.d/net.<interface_name>

Edit /etc/conf.d/net with any necessary configuration for all interfaces.

Add the script(s) to the default runlevel to have the interface(s) start automatically:

root #rc-update add net.<interface_name> default

Optional: Disable or override predictable network interface naming

Network device names such as eth0 or wlan0 as provided by the kernel are normally changed on system boot (see dmesg) by the /lib/udev/rules.d/80-net-setup-link.rules udev rule and the NamePolicy in /lib/systemd/network/99-default.link.

This behavior may be disabled in several ways:

Symlink /etc/systemd/network/99-default.link to /dev/null: ln -s /dev/null /etc/systemd/network/99-default.link.
Create a lower-numbered .link file in /etc/systemd/network which assigns a different name to the interface.
Pass net.ifnames=0 on the kernel command line.

Reference: https://systemd.io/PREDICTABLE_INTERFACE_NAMES/

Usage

Some useful commands are:

Monitor all udev activities:

root #udevadm monitor

Show all messages about a given device file:

root #udevadm info --query=all --name=/dev/DEVICE_FILE

Show udev info about a given sys path device file (might be obtained via udevadm monitor):

root #udevadm info --attribute-walk --path=/devices/DEVICE_FILE

Udev rules file example - assign a persistent name to an Ethernet device:

DATEI /etc/udev/rules.d/50-ethernet.rules

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="01:23:45:67:89:ab", NAME="ethernet0"

After changing a rules file in /etc/udev/rules.d/, either reboot or make udev reload them with:

root #udevadm control --reload-rules

For already added devices (plugged USB, etc.), the reloaded rules take effect either after changing the device (replugging USB, etc.) or by making udev request kernel events again via udevadm trigger. Various event actions can be triggered. By default, the change event action is triggered:

root #udevadm trigger

See the udevadm(8) man page for more information.

Fehlersuche

Gentoo bugtracker: known bugs

Log monitor messages

To log all message when udevadm monitor is run, modify the following configuration file:

DATEI /etc/conf.d/udev

udev_monitor="YES"

It will create the new log file located at /run/udev/udevmonitor.log.

Debug-Modus

Enabling debug mode will output more log messages:

DATEI /etc/conf.d/udev

udev_debug="YES"

Set the logging priority:

DATEI /etc/udev/udev.conf

udev_log="debug"

The log file /run/udev/debug.log will be created but no messages will be logged to it. The most recent versions of udev will log all messages to dmesg.

Missing device files /dev/null and /dev/console

Some udev versions need the /dev/null and /dev/console files in order to work properly, but cannot create them on their own. To manually create these files for udev run the following commands with root privileges:

root #

mkdir test

root #

mount --bind / test

root #

cd test/dev

root #

mknod -m 660 console c 5 1

root #

mknod -m 660 null c 1 3

root #

cd ../..

root #

umount test

root #

rmdir test

NIC ist eth0 zugewiesen, wird aber auf eth1 verschoben

Those having dual network cards on their motherboards may run into a situation where ip link may show no eth0 or eth1. dmesg may show their NIC detected as eth0, and later moved to eth1. Performing a ip link will also show the NIC as eth1. This is caused by using the kernel assigned names in the first place. Users should write custom rules like /etc/udev/rules.d/70-my-network.rules to use free names like lan0 or wireless0 or use predictable interface names (which have been enabled by default since udev version 197).

Remember to also remove old files from old versions of udev:

root #

rm /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/80-net-setup-link.rules /etc/udev/rules.d/80-net-name-slot.rules /etc/systemd/network/99-default.link

Also make sure not to pass net.ifnames=0 on the kernel commandline. This setting would disable the predictable interface names feature of udev altogether.

Siehe auch

Eudev — a fork of udev, systemd's device file manager for the Linux kernel.

Externe Ressourcen

Bug 575718 - Request for council decision regarding virtual/udev default provider - Default virtual/udev provider changed to sys-fs/eudev