diff options
| author | Michael Witten <mfwitten@gmail.com> | 2011-04-08 23:21:51 +0000 |
|---|---|---|
| committer | Michael Witten <mfwitten@gmail.com> | 2011-04-11 05:49:37 +0000 |
| commit | 9f38b806d273e19c4fcb71fdcbaa9c61839b2a51 (patch) | |
| tree | 554d3fa3259036fb1d55e49c5cc6468dee445fa9 /udev | |
| parent | ac1ba8e487b12e15c12e64ac78023b9dfbc0a30e (diff) | |
Docs: udev.xml: Clean up description of SYMLINK assignment key
Signed-off-by: Michael Witten <mfwitten@gmail.com>
Diffstat (limited to 'udev')
| -rw-r--r-- | udev/udev.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/udev/udev.xml b/udev/udev.xml index 225ad5ce3f..dc277c8918 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> |