diff options
| author | Kay Sievers <kay@vrfy.org> | 2012-07-02 03:37:28 +0200 |
|---|---|---|
| committer | Kay Sievers <kay@vrfy.org> | 2012-07-02 03:37:28 +0200 |
| commit | b1239c3fb3d19ff7273a8e5ead5c42f055d10b92 (patch) | |
| tree | 3d3a9de6d5e5df99235cdfa0d2c8a9f481b7ab8b /man/udev.xml | |
| parent | ddbe6850b2ae490ab359a050b190cf96e1559cd7 (diff) | |
udev: man - clarify escaping and replacing for SYMLINK+=
Diffstat (limited to 'man/udev.xml')
| -rw-r--r-- | man/udev.xml | 23 |
1 files 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 @@ <term><option>SYMLINK</option></term> <listitem> <para>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.</para> + <para>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.</para> + <para>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.</para> + <para>Symlink names must never conflict with the kernel's default device + node names, as that would result in unpredictable behavior. </para> </listitem> </varlistentry> |