From b1239c3fb3d19ff7273a8e5ead5c42f055d10b92 Mon Sep 17 00:00:00 2001 From: Kay Sievers Date: Mon, 2 Jul 2012 03:37:28 +0200 Subject: [PATCH 1/1] udev: man - clarify escaping and replacing for SYMLINK+= --- man/udev.xml | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/man/udev.xml b/man/udev.xml index b5c7cd4be..0746618d0 100644 --- a/man/udev.xml +++ b/man/udev.xml @@ -335,15 +335,20 @@ The name of a symlink targeting the node. Every matching rule adds - this value to the list of symlinks to be created. Multiple symlinks may be - specified by separating the names by the space character. In case multiple - 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. Also, symlink names must - never conflict with the kernel's default device node names, as that would - result in unpredictable behavior. + this value to the list of symlinks to be created. + The set of characters to name a symlink is limited. Allowed + characters are [0-9A-Za-z#+-.:=@_/], valid utf8 character sequences, + and "\x00" hex encoding. All other characters are replaced by + a '_' character. + Multiple symlinks may be specified by separating the names by the + space character. In case multiple 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. + Symlink names must never conflict with the kernel's default device + node names, as that would result in unpredictable behavior. -- 2.30.2