summaryrefslogtreecommitdiff
path: root/udev
diff options
context:
space:
mode:
authorMichael Witten <mfwitten@gmail.com>2011-04-08 23:17:39 +0000
committerMichael Witten <mfwitten@gmail.com>2011-04-11 05:49:37 +0000
commitac1ba8e487b12e15c12e64ac78023b9dfbc0a30e (patch)
tree8d28076635db30cf826de3013d2cdbbc335f478f /udev
parent2c47027b31f7af9b7b25348f2baba77bba586b61 (diff)
Docs: udev.xml: Clean up description of NAME assignment key
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'udev')
-rw-r--r--udev/udev.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/udev/udev.xml b/udev/udev.xml
index 77053b7700..225ad5ce3f 100644
--- a/udev/udev.xml
+++ b/udev/udev.xml
@@ -308,17 +308,17 @@
<varlistentry>
<term><option>NAME</option></term>
<listitem>
- <para>The name, a network interface should be renamed to. Or as
- a temporary workaround, the name a device node should be named.
- Usually the kernel provides the defined node name, or even creates
+ <para>What a network interface should be named.</para>
+ <para>Also, as a temporary workaround, this is what a device node
+ should be named; usually the kernel provides the defined node name or creates
and removes the node before udev even receives any event. Changing
the node name from the kernel's default creates inconsistencies
and is not supported. If the kernel and NAME specify different names,
- an error is logged. Udev is only expected to handle device node
+ an error is logged. udev is only expected to handle device node
permissions and to create additional symlinks, not to change
kernel-provided device node names. Instead of renaming a device node,
- SYMLINK should be used. Symlink names must never conflict with
- device node names, it results in unpredictable behavior.</para>
+ SYMLINK should be used. However, symlink names must never conflict with
+ device node names, as that would result in unpredictable behavior.</para>
</listitem>
</varlistentry>