X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fudev.xml;h=415cf8e6a9d32eedf3ae48c8965beb6c4d8b4429;hb=1d98d9a62c16c8282d02942d80e025ceec962c9b;hp=417fb11ebcda9f6b4476e5f9140a8d278a7dbd23;hpb=b45f770f0049fbdf3f6c9db0ab11deeff4ccd86d;p=elogind.git
diff --git a/man/udev.xml b/man/udev.xml
index 417fb11eb..415cf8e6a 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
@@ -65,15 +65,7 @@
The following variables can be set:
-
-
- Specifies where to place the device nodes in the filesystem.
- The default value is /dev.
-
-
-
-
-
+ udev_logThe logging priority. Valid values are the numerical syslog priorities
or their textual representations: ,
@@ -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.
@@ -115,21 +107,21 @@
operators are:
-
+ ==Compare for equality.
-
+ !=Compare for inequality.
-
+ =Assign a value to a key. Keys that represent a list are reset
and only this single value is assigned.
@@ -137,14 +129,14 @@
-
+ +=Add the value to a key that holds a list of entries.
-
+ :=Assign a value to a key finally; disallow any later changes.
@@ -156,7 +148,7 @@
not only the device that has generated the event. If multiple keys that match
a parent device are specified in a single rule, all these keys must match at
one and the same parent device.
-
+
@@ -305,19 +297,19 @@
pattern characters are supported:
-
+ *Matches zero or more characters.
-
+ ?Matches any single character.
-
+ []Matches any single character specified within the brackets. For
example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'.
@@ -330,12 +322,12 @@
The following keys can get values assigned:
-
+ 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,21 +335,26 @@
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.
-
+ , , The permissions for the device node. Every specified value overrides
the compiled-in default value.
@@ -430,10 +427,10 @@
Import a set of variables as device properties,
- depending on type:
+ depending on type:
-
+ programExecute an external program specified as the assigned value and
import its output, which must be in environment key
@@ -442,14 +439,14 @@
-
+ fileImport a text file specified as the assigned value, the content
of which must be in environment key format.
-
+ dbImport a single property specified as the assigned value from the
current device database. This works only if the database is already populated
@@ -457,14 +454,14 @@
-
+ cmdlineImport a single property from the kernel command line. For simple flags
the value of the property is set to '1'.
-
+ parentImport the stored keys from the parent device by reading
the database entry of the parent device. The value assigned to
@@ -492,7 +489,7 @@
Rule and device options:
-
+
@@ -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.
@@ -549,7 +546,7 @@
is executed, allowing for the use of device properties set by earlier matching
rules. For all other fields, substitutions are performed while the individual rule is
being processed. The available substitutions are:
-
+ ,
@@ -680,14 +677,14 @@
-
+ %%The '%' character itself.
-
+ $$The '$' character itself.
@@ -699,7 +696,7 @@
See Also
- udevd8
+ systemd-udevd.service8,
udevadm8