From ac1ba8e487b12e15c12e64ac78023b9dfbc0a30e Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Fri, 8 Apr 2011 23:17:39 +0000 Subject: [PATCH] Docs: udev.xml: Clean up description of NAME assignment key Signed-off-by: Michael Witten --- udev/udev.xml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/udev/udev.xml b/udev/udev.xml index 77053b770..225ad5ce3 100644 --- a/udev/udev.xml +++ b/udev/udev.xml @@ -308,17 +308,17 @@ - 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 + What a network interface should be named. + 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. + SYMLINK should be used. However, symlink names must never conflict with + device node names, as that would result in unpredictable behavior. -- 2.30.2