X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fudev.xml;h=7ec7a3fed00cd1cef242bbc4c255987fa0e91986;hb=772c552f763a125d17d814c4e5a35bbba49fc27a;hp=417fb11ebcda9f6b4476e5f9140a8d278a7dbd23;hpb=b45f770f0049fbdf3f6c9db0ab11deeff4ccd86d;p=elogind.git
diff --git a/man/udev.xml b/man/udev.xml
index 417fb11eb..7ec7a3fed 100644
--- a/man/udev.xml
+++ b/man/udev.xml
@@ -41,7 +41,7 @@
names provide a way to reliably identify devices based on their properties or
current configuration.
- The udev daemon, udevd
+ The udev daemon, systemd-udevd.service8, receives device uevents directly from
the kernel whenever a device is added or removed from the system, or it changes its
state. When udev receives a device event, it matches its configured set of rules
@@ -64,14 +64,6 @@
It consists of a set of variables allowing the user to override default udev values.
The following variables can be set:
-
-
-
- Specifies where to place the device nodes in the filesystem.
- The default value is /dev.
-
-
-
@@ -102,7 +94,7 @@
extensions are ignored.Every line in the rules file contains at least one key-value pair.
- There are two kind of keys: match and assignment.
+ There are two kinds of keys: match and assignment.
If all match keys are matching against its value, the rule gets applied and the
assignment keys get the specified value assigned.
@@ -335,7 +327,7 @@
The name to use for a network interface. The name of a device node
- can not be changed by udev, only additional symlinks can be created.
+ cannot be changed by udev, only additional symlinks can be created.
@@ -343,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.
@@ -520,7 +517,7 @@
Apply the permissions specified in this rule to the static device node with
the specified name. Static device node creation can be requested by kernel modules.
- These nodes might not have a corresponding kernel device at the time udevd is
+ These nodes might not have a corresponding kernel device at the time systemd-udevd is
started; they can trigger automatic kernel module loading.
@@ -699,7 +696,7 @@
See Also
- udevd8
+ systemd-udevd.service8,
udevadm8