From: Kay Sievers Date: Tue, 20 Apr 2010 05:29:51 +0000 (+0200) Subject: doc: add section about how *not* to rename device nodes X-Git-Tag: 174~535 X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=85f22036fc0e7667188c0ace5082236b1cbeff94;p=systemd doc: add section about how *not* to rename device nodes Thanks to Mario 'BitKoenig' Holbe . --- diff --git a/udev/udev.xml b/udev/udev.xml index d3fa76a9..192a6f12 100644 --- a/udev/udev.xml +++ b/udev/udev.xml @@ -297,8 +297,13 @@ - The name of the node to be created, or the name the network interface - should be renamed to. + The name, a network interface should be renamed to, or the name + a device node should be named. Usually the kernel provides the defined + node name, or even creates and removes the node before udev receives + any event. Changing the node name from the kernel's default may result + in unexpected behavior and is not supported. Udev is only expected to + handle device node permissions and to create additional symlinks, which + do not conflict with the kernel device node names. @@ -306,9 +311,16 @@ The name of a symlink targeting the node. Every matching rule will add - this value to the list of symlinks to be created along with the device node. + this value to the list of symlinks to be created along with the device node. Multiple symlinks may be specified by separating the names by the space - character. + character. In case multiple devices claim the same name, the link will + always point to the device with the highest link_priority. If the current device + goes away, the links will be re-evaluated and the device with the next highest + link_priority will own the link. If no link_priority is specified, the order + of the devices, and which of them will own the link, is undefined. Claiming + the same name for a node and links may result in unexpected behavior and is + not supported. +