Eudev

Resources

Project

GitHub

Not to be confused with udev.

eudev is Gentoo's maintained fork of udev, systemd's device file manager for the Linux kernel. It manages device nodes in /dev and handles all user space actions when adding or removing devices.

The goal of eudev is to obtain better compatibility with existing software such as OpenRC, Upstart, older kernels, various toolchains, and anything else required by (but not well supported through) udev. Configurations utilizing systemd should not use it.

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 (including udev and eudev) 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

USE flags

Some packages know the udev USE flag for enabling virtual/udev integration.

Cannot load package information. Is the atom sys-fs/eudev correct?

Emerge

To avoid registration in the world set, the oneshot option should be used.

root #emerge --ask --oneshot sys-fs/eudev

Configuration

RC service

The RC name is udev, not eudev. It needs to be registered in the sysinit runlevel.

root #rc-update add udev sysinit

 * rc-update: udev already installed in runlevel `sysinit'; skipping

From sys-fs/udev-init-scripts version 29 onward, udev-trigger should also be added to the sysinit runlevel.

Migrating from udev to eudev

Migrating from udev 216 to eudev 1.10-r2 (March 2015) is straight forward:

root #emerge --ask --oneshot sys-fs/eudev

In case the system uses multilib and, for example, has the abi_x86_32 USE flag active against the older udev package, then don't forget to change it too:

FILE /etc/portage/package.useSwitching udev to eudev in package.use

# sys-fs/udev abi_x86_32
sys-fs/eudev abi_x86_32

Keep classic 'eth0' naming

Network device names eth0, wlan0, etc. as provided by the kernel could be changed on boot (see dmesg) by the /lib/udev/rules.d/80-net-name-slot.rules udev rule.

To keep the classic naming this rule can be overwritten with an equally named empty file in the /etc/udev/rules.d directory:

root #touch /etc/udev/rules.d/80-net-name-slot.rules

Alternatively add net.ifnames=0 to the kernel command line, change the default policy or create a custom one.

An interesting resource related to the network naming is I don't like this, how do I disable this on the Freedesktop wiki.

Use new 'predictable' naming

The new network interface naming convention is not the same so interfaces 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 ifconfig command:

user $ifconfig

Create symbolic links for the existing interfaces in the /etc/init.d/ and /etc/conf.d/ directories:

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

root #ln -s /etc/conf.d/net.lo /etc/conf.d/net.<interface_name>

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

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

Troubleshooting

Using udevadm

Start udevadm monitor and see what happens:

user $udevadm monitor

Get device info using udevadm info followed by the device path:

user $udevadm info -p /devices/pci0000:00/0000:00:1d.7

Get the device path using its name:

user $udevadm info -q path -n input/mouse1

/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3.4/1-3.4:1.0/0003:046D:C404.0006/input/input24/mouse1

Test an event run using udevadm test followed by the device path for which an event is to be tested:

user $udevadm test /devices/pci0000:00/0000:00:1d.7

To get a list of all udevadm commands:

user $udevadm -h

Migrating older releases

udev 171-r10 to eudev 1.2-r1

See this post on the Gentoo forums.

Broken system switching from udev to eudev

See this post on the Gentoo forums.

See also

• udev —
• Gentoo eudev Project - The official Gentoo project fork of udev.
• Allow only known usb devices
• Google Summer of Code/2016/Ideas/Eudev

External resources

• Moving from udev (171-r10) to eudev (1.2-r1) on the Gentoo Forums