Udev/fr

udev est le gestionnaire de périphérique pour le noyau de Linux. En premier lieu, il gère les nœuds de périphérique dans et prend en charge toutes les actions dans l'espace utilisateur lors de l'ajout ou de la suppression de périphériques. Consultez aussi eudev, une dérivation de udev.

Le répertoire /dev
Lorsque les utilisateurs de Linux parlent du matériel sur leur système à des gens qui pensent que Linux est une sorte de virus ou de marque de café, l'utilisation de "slash dev slash foo" provoquera à coup sûr une sorte d'étonnement. Mais, pour l'utilisateur heureux (comme vous) utiliser  est une façon rapide d'expliquer que nous parlons de la première partition du premier disque maître SATA ?

Nous savons tous ce qu'est un fichier de périphérique. Certains savent même pourquoi les fichiers de périphériques possèdent des numéros spéciaux quand ils les regardent de près après avoir exécuté une commande  dans le dossier. Mais ce que nous tenons toujours comme garanti, c'est que le premier disque SATA est référencé comme. Vous pouvez le voir autrement mais cela est un défaut de conception.

Pensez à des périphériques connectables à chaud, comme les périphériques USB et IEE1394, ou les périphériques PCI commutables à chaud, ... Quel est le premier périphérique ? Et pour combien de temps ? Comment les autres périphériques seront-ils nommés quand le premier disparaitra ? Cela sera-t-il amusant si votre tâche d'impression est tout à coup déplacée de votre toute nouvelle imprimante laser vers votre quasi-moribonde imprimante à matrice parce que votre gamin aura tiré sur le cordon d'alimentation de l'imprimante laser qui justement était la première imprimante ?

Enter udev. The goals of the udev project are both interesting and needed:


 * Runs in userspace
 * Dynamically creates/removes device files
 * Provides consistent naming
 * Provides a user-space API

Every time a change happens within the device structure, the kernel emits a uevent which gets picked up by udev. udev then follows the rules as declared in the, and  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 can be creating or deleting device files, but can also trigger the loading of particular firmware files into the kernel memory.

Kernel
You need to activate the following kernel options:

Software
Portage knows the global USE flag udev for enabling support for udev in other packages. Enabling this USE flag (default in all linux profiles) will pull in automatically:

The USE flags of udev are:

After setting this you want to update your system so the changes take effect:

Service
To start udev at boot time, add it your sysinit runlevel:

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 set-up and configure the device.

The rule definitions are stored in (installed by packages) and  (for end-user specified rules). In these directories, multiple rule files (with suffix ) 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
 * commands need to be executed

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

Persistent device names
The kernel detects devices asynchronous, udev mirrors the kernel's sysfs filesystem and so the device are named and numbered in order of detection. So by default udev provides no persistent device names. However there are mechanismen 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 directory. So instead of using e.g. the device file  use the file.


 * The same for input devices in the directory.


 * Using custom rules you can create your own device files.

Usage
Some useful commands are:


 * Show all messages about a given device file:


 * Monitor udev activities:

See the udevadm man page for more information.

Log monitor messages
Log all message you see, when you run udevadm monitor:

It will create the new log file.

Debug mode
Enable debug mode to get more log messages:

It will create the new log file.

Missing device files and
Some udev versions need these files and can't create them on their own. So you have to create them:

NIC assigned eth0, but is moved to eth1
Those having dual network cards on their motherboards may run into a situation where ifconfig may show no eth0 or eth1. Dmesg may show their NIC detected as eth0, and later moved to eth1. Performing a "ifconfig -a" will also show the NIC as eth1. This is caused by using the kernel assigned names in the first place. You should write your own rules like to use free names like lan0 or wireless0 or use the predictable interface names which are enabled by the default since version 197.

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