X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=udev%2Fudev.xml;h=192a6f1238d806c642322c774d65e469e7f6ad7e;hb=901e80dc593967c5d5e810390722461760177ff8;hp=ccc1f45e4cf92b16bd9f2a9783696667f933a774;hpb=aeb53ca3d60057dfbb948b222046dcecfcc11ed9;p=elogind.git diff --git a/udev/udev.xml b/udev/udev.xml index ccc1f45e4..192a6f123 100644 --- a/udev/udev.xml +++ b/udev/udev.xml @@ -8,14 +8,12 @@ udev - August 2005 udev udev 7 - @@ -90,7 +88,7 @@ pointing to the node, or run a specified program as part of the event handling. If no matching rule is found, the default device node name is used. - A rule may consist of a list of one or more key value pairs separated by + A rule consists of a list of one or more key value pairs separated by a comma. Each key has a distinct operation, depending on the used operator. Valid operators are: @@ -104,7 +102,7 @@ - Compare for non-equality. + Compare for inequality. @@ -168,6 +166,16 @@ + + + + Match the name of a symlink targeting the node. It can + be used once a SYMLINK key has been set in one of the preceding + rules. There may be multiple symlinks; only one needs to match. + + + + @@ -289,19 +297,30 @@ - The name of the node to be created, or the name the network interface - should be renamed to. Only one rule can set the node name, all later rules with - a NAME key will be ignored. + 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. - The name of a symlink targeting the node. Every matching rule can add - this value to the list of symlinks to be created along with the device node. + 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. 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. + @@ -324,7 +343,8 @@ - Set a device property value. + Set a device property value. Property names with a leading '.' + are not stored in the database or exported to external tool or events. @@ -335,13 +355,22 @@ device. This can only be used for very short running tasks. Running an event process for a long period of time may block all further events for this or a dependent device. Long running tasks need to be immediately - detached from the event process itself. - If the specifiefd string starts with + detached from the event process itself. If the option + 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. @@ -369,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 . @@ -379,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. + + @@ -399,7 +438,8 @@ - Wait for a file to become available. + Wait for a file to become available or until a 10 + seconds timeout expires. @@ -408,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. - - @@ -435,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. - - @@ -458,6 +470,13 @@ with this option. + + + + Watch the device node with inotify, when closed after being opened for + writing, a change uevent will be synthesised. + + @@ -614,9 +633,6 @@ - The count of characters to be substituted may be limited by specifying - the format length value. For example, '%3s{file}' will only - insert the first three characters of the sysfs attribute