X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=udev%2Fudev.xml;h=192a6f1238d806c642322c774d65e469e7f6ad7e;hb=901e80dc593967c5d5e810390722461760177ff8;hp=c34a106d208635f2ce24fc14582206456f04ffc2;hpb=5bdba42ddb9cda2858e042bac991f67ae36cc888;p=elogind.git
diff --git a/udev/udev.xml b/udev/udev.xml
index c34a106d2..192a6f123 100644
--- a/udev/udev.xml
+++ b/udev/udev.xml
@@ -297,8 +297,13 @@
- The name of the node to be created, or the name the network interface
- should be renamed to.
+ The name, a network interface should be renamed to, or the name
+ a device node should be named. Usually the kernel provides the defined
+ node name, or even creates and removes the node before udev receives
+ any event. Changing the node name from the kernel's default may result
+ in unexpected behavior and is not supported. Udev is only expected to
+ handle device node permissions and to create additional symlinks, which
+ do not conflict with the kernel device node names.
@@ -306,9 +311,16 @@
The name of a symlink targeting the node. Every matching rule will add
- this value to the list of symlinks to be created along with the device node.
+ this value to the list of symlinks to be created along with the device node.
Multiple symlinks may be specified by separating the names by the space
- character.
+ character. In case multiple devices claim the same name, the link will
+ always point to the device with the highest link_priority. If the current device
+ goes away, the links will be re-evaluated and the device with the next highest
+ link_priority will own the link. If no link_priority is specified, the order
+ of the devices, and which of them will own the link, is undefined. Claiming
+ the same name for a node and links may result in unexpected behavior and is
+ not supported.
+
@@ -347,12 +359,18 @@
is
specified, and the executed program returns non-zero, the event will be
marked as failed for a possible later handling.
+ If no path is given, the program must be in
+ /lib/udev, otherwise the full path must be
+ specified.If the specified string starts with
, all current event
values will be passed to the specified socket, as a message in the same
format the kernel sends an uevent. If the first character of the specified path
is an @ character, an abstract namespace socket is used, instead of an existing
socket file.
+ Program name and arguments are separated with spaces. To
+ include spaces in an argument, use single quotes. Please note
+ that this does not run through a shell.
@@ -380,7 +398,9 @@
Execute an external program specified as the assigned value and
- import its output, which must be in environment key format.
+ import its output, which must be in environment key
+ format. Path specification, command/argument separation,
+ and quoting work like in .
@@ -390,6 +410,14 @@
environment key format.
+
+
+
+ Import a single property specified as the assigned value from the
+ current device database. This works only if the database is already populated
+ by an earlier event.
+
+
@@ -410,7 +438,8 @@
- Wait for a file to become available.
+ Wait for a file to become available or until a 10
+ seconds timeout expires.
@@ -419,26 +448,6 @@
Rule and device options:
-
-
-
- Stops further rules application. No later rules will have
- any effect.
-
-
-
-
-
- Ignore this event completely.
-
-
-
-
-
- Do not remove the device node when the device goes away. This may be
- useful as a workaround for broken device drivers.
-
-
@@ -446,14 +455,6 @@
priorities overwrite existing symlinks of other devices. The default is 0.
-
-
-
- Create the device nodes for all available partitions of a block device.
- This may be useful for removable media devices where media changes are not
- detected.
-
-
@@ -473,7 +474,7 @@
Watch the device node with inotify, when closed after being opened for
- writing, a change uevent will be synthesised.
+ writing, a change uevent will be synthesised.