Файловая система udev ("юдев") появилась в ядрах версии 2.6 kernel заместо DevFS ("дев фс")

В отличие от devfs, которая работает в пространстве ядра, udev работает в пространстве пользователя. Она динамически обновляет содержимое директори /dev , как и его предшественница sysfs ("сисфс"). Sysfs рассматривалась как полезный инструмент для разработки и существовала только в ядрах Линукс версии 2.5, и была замещена udev в ядре 2.6.

udev позволяет назначать постоянные имена для устройств. Например, можно создать правило для монтирования жесткого диска производителем которого является "iRiver" с кодом устройства "ABC", как устройство /dev/iriver. Постоянность в названии устройств гарантирует, что все скрипты, зависящие от присутствия в системе определённых устройст, будут работать правильно.


udev состоит из нескольких сервисов ядра и демона (процесса) udevd. Ядро сообщает демону udevd о наступлении определенного события. Сам демон udevd реагирует на наступившее событие через actions ("действия"). Информация о событии поступает от ядра. Все действия происходят в пользовательском окружении. Можно ли сделать так, чтобы от ядра передавалась только определенная информация о событии ? Можно настраивать действия на наступившее событие через "rules" ("правила").

The udevd daemon, like other daemons, starts on boot because of an init script: /etc/rcS.d/udev. Its config file is in /etc/udev/udev.conf. The rules files (which amount to more configuration for udevd) are taken from /etc/udev/rules.d. Files in there are parsed in alpha order, as long as the name ends with ".rules". When the config file or rules files are changed, then the udevd daemon should be restarted (or, as mentioned further down this page, you can use the udevtest program).

Many of the files in /etc/udev/rules.d are links to files elsewhere. I'm guessing that's so that when the rules files are edited, the editor backups aren't left lying around where they might be used in the next restart of the udevd daemon. Also, since the links can have different names from the original files, then they can be ordered without having to worry about what names they have (as with the init scripts).

udev was created to respond to hotplug type of events. Much documentation refers to creating devices in response to new devices that have appeared. But, udev is more general; it can run arbitrary userspace commands in response to a new device appearing - or to whatever events it receives from the kernel.

The times when udevd is active are:

  1. at startup, it parses all the config files and rule files and builds a rules database in memory.
  2. When an event happens, it checks its rule database and performs the appropriate actions.


Rules for rules:

  1. rules are all on one line (lines can be broken with \ just before newline)
  2. rules consist of "matches" and "actions"
  3. matches and actions are "key" "operator" "value" triplets
  4. matches have == or != for operator
  5. actions have = (assignment) for operator
  6. matches check one or more attributes of the event to see if the action will be applied
  7. actions specify what will happen
  8. example match: BUS=="usb"

  9. example action: NAME="mydev"

  10. example rule:

    KERNEL=="sd*[0-9]|dasd*[0-9]", ENV{ID_SERIAL}=="?*", \
  11. all matching rules will fire
  12. earlier rules have precedence over later rules - so put your customizations early in the rules.d file list
  13. actions like key="value" override
  14. actions like key+="value" add to the actions that are executed, eg SYMLINK+="foo" means "in addition to any other symlinks you were going to make for this event, also make one called foo"

Rule sets

Rules for rule sets:

  1. All the rules are in one big rule space, although they are divided into several files.
  2. The only organization in the rule space is the ability to set labels, and then to skip a bunch of rules during "match this event to rules" time by jumping forward with a GOTO action.

  3. there is one other rule type called a label: eg LABEL="persistent_storage_end" These are used by regular rules that have "GOTO" actions, eg:

    ACTION!="add", GOTO="persistent_storage_end"
    Note that in this rule, the term ACTION is an attribute of an event and is being used as a condition for deciding if the GOTO action will be triggered.
  4. It is polite to keep GOTOs to jump within a file (or you will have to worry about reordering the files)
  5. Don't jump backwards to a label (didn't try it, but imagine it might end in an infinite loop? Maybe the udev code checks for that - but if it's going to be ignored (at best) why bother?)
  6. You can set variables in ENV space in earlier rules and refer to them with later rules
  7. The facility for dynamic rule creation exists (example: see z45_persistent-net-generator.rules)



Persistent Device name

In this example, we want to make sure your 3G card get a persistent name.

1. Plug the "card" (or device) 2. run the following command, on the proper device :

3. Create a file in /etc/udev/rules.d, typically named z21_persistent-local.rules.

ATTRS{prod_id2}=="Merlin UMTS Modem", ATTRS{prod_id1}=="Novatel Wireless", SYMLINK+="MerlinUMTS"
## Alternatively we could use :
# ATTRS{card_id}=="0x1aaf", ATTRS{manf_id}=="0x00a4", SYMLINK+="MerlinUMTS"

4. Force re-running the scripts (or reboot ;)

udevtest  $(udevinfo -q path -n /dev/ttyS1) --force

a more detailed example by semu5 on comp.os.linux.questions. There is also a Writing udev rules.


CategorySystemAdministration | ?CategoryLocalResourcesManagement