X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=udev%2Fudev.xml;h=dc277c891884c66669c4d90d66af5038667e5db0;hb=9f38b806d273e19c4fcb71fdcbaa9c61839b2a51;hp=225ad5ce3f099426bb6e225e62d07e88468ceffb;hpb=ac1ba8e487b12e15c12e64ac78023b9dfbc0a30e;p=elogind.git

diff --git a/udev/udev.xml b/udev/udev.xml
index 225ad5ce3..dc277c891 100644
--- a/udev/udev.xml
+++ b/udev/udev.xml
@@ -331,10 +331,10 @@
             devices claim the same name, the link always points to the device with
             the highest link_priority. If the current device goes away, the links are
             re-evaluated and the device with the next highest link_priority becomes the owner of
-            the link. If no link_priority is specified, the order of the devices, and
-            which one of them owns the link, is undefined. Claiming the same name for
-            a symlink, which is or might be used for a device node, may result in
-            unexpected behavior and is not supported.
+            the link. If no link_priority is specified, the order of the devices (and
+            which one of them owns the link) is undefined. Also, symlink names must
+            never conflict with the kernel's default device node names, as that would
+            result in unpredictable behavior.
             </para>
           </listitem>
         </varlistentry>