shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-01-26 14:04:03 +03:00
Code

doc: add section about how *not* to rename device nodes

Browse Source 
Thanks to Mario 'BitKoenig' Holbe <Mario.Holbe@tu-ilmenau.de>.
This commit is contained in:
Kay Sievers 2010-04-20 07:29:51 +02:00
parent 4101ce14b3
commit 85f22036fc
1 changed files with 16 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
udev/udev.xml
View File

@ -297,8 +297,13 @@
<varlistentry>
<term><option>NAME</option></term>
<listitem>
<para>The name of the node to be created, or the name the network interface
should be renamed to.</para>
<para>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.</para>
</listitem>
</varlistentry>
@ -308,7 +313,14 @@
<para>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.
Multiple symlinks may be specified by separating the names by the space
character.</para>
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.
</para>
</listitem>
</varlistentry>