Lines Matching full:para
37 <para>udev supplies the system software with device events, manages permissions
42 current configuration.</para>
44 <para>The udev daemon, <citerefentry><refentrytitle>udevd</refentrytitle>
50 to be used to create meaningful symlink names.</para>
52 <para>All device information udev processes is stored in the udev database and
54 sources is provided by the library libudev.</para>
58 <para>The udev rules are read from the files located in the
71 <filename>.rules</filename>; other extensions are ignored.</para>
73 <para>Every line in the rules file contains at least one key-value pair.
77 assignment keys get the specified values assigned.</para>
79 <para>A matching rule may rename a network interface, add symlinks
81 the event handling.</para>
83 <para>A rule consists of a comma-separated list of one or more key-value pairs.
85 operators are:</para>
90 <para>Compare for equality.</para>
97 <para>Compare for inequality.</para>
104 <para>Assign a value to a key. Keys that represent a list are reset
105 and only this single value is assigned.</para>
112 <para>Add the value to a key that holds a list of entries.</para>
119 <para>Remove the value from a key that holds a list of entries.</para>
126 <para>Assign a value to a key finally; disallow any later changes.</para>
131 <para>The following key names can be used to match against device properties.
135 one and the same parent device.</para>
140 <para>Match the name of the event action.</para>
147 <para>Match the devpath of the event device.</para>
154 <para>Match the name of the event device.</para>
161 <para>Match the name of a network interface. It can be used once the
162 NAME key has been set in one of the preceding rules.</para>
169 <para>Match the name of a symlink targeting the node. It can
172 </para>
179 <para>Match the subsystem of the event device.</para>
185 <para>Match the driver name of the event device. Only set this key for devices
186 which are bound to a driver at the time the event is generated.</para>
192 <para>Match sysfs attribute values of the event device. Trailing
195 </para>
199 <para>Match a kernel parameter value.
200 </para>
207 <para>Search the devpath upwards for a matching device name.</para>
214 <para>Search the devpath upwards for a matching device subsystem name.</para>
221 <para>Search the devpath upwards for a matching device driver name.</para>
228 <para>Search the devpath upwards for a device with matching sysfs attribute values.
231 unless the specified match value itself contains trailing whitespace.</para>
238 <para>Search the devpath upwards for a device with matching tag.</para>
245 <para>Match against a device property value.</para>
252 <para>Match against a device tag.</para>
259 <para>Test the existence of a file. An octal mode mask can be specified
260 if needed.</para>
267 <para>Execute a program to determine whether there
271 is available in the <varname>RESULT</varname> key.</para>
272 <para>This can only be used for very short-running foreground tasks. For details,
273 see <varname>RUN</varname>.</para>
280 <para>Match the returned string of the last <varname>PROGRAM</varname> call.
282 <varname>PROGRAM</varname> call.</para>
287 <para>Most of the fields support shell glob pattern matching and
288 alternate patterns. The following special characters are supported:</para>
293 <para>Matches zero or more characters.</para>
299 <para>Matches any single character.</para>
305 <para>Matches any single character specified within the brackets. For
312 any characters not enclosed are matched.</para>
318 <para>Separates alternative patterns. For example, the pattern string
320 or <literal>x*</literal>.</para>
325 <para>The following keys can get values assigned:</para>
330 <para>The name to use for a network interface. The name of a device node
331 cannot be changed by udev, only additional symlinks can be created.</para>
338 <para>The name of a symlink targeting the node. Every matching rule adds
339 this value to the list of symlinks to be created.</para>
340 <para>The set of characters to name a symlink is limited. Allowed
343 characters are replaced by a <literal>_</literal> character.</para>
344 <para>Multiple symlinks may be specified by separating the names by the
350 them owns the link) is undefined.</para>
351 <para>Symlink names must never conflict with the kernel's default device
353 </para>
360 <para>The permissions for the device node. Every specified value overrides
361 the compiled-in default value.</para>
368 <para>Applies the specified Linux Security Module label to the device node.</para>
375 <para>The value that should be written to a sysfs attribute of the
376 event device.</para>
383 <para>The value that should be written to kernel parameter.</para>
390 <para>Set a device property value. Property names with a leading <literal>.</literal>
393 match key).</para>
400 <para>Attach a tag to a device. This is used to filter events for users
406 handling.</para>
413 <para>Add a program to the list of programs to be executed after
415 <literal>type</literal>:</para>
420 <para>Execute an external program specified as the assigned
423 absolute path must be specified.</para>
424 <para>This is the default if no <replaceable>type</replaceable>
425 is specified.</para>
431 <para>As <varname>program</varname>, but use one of the
432 built-in programs rather than an external one.</para>
436 <para>The program name and following arguments are separated by spaces.
437 Single quotes can be used to specify arguments with spaces.</para>
438 <para>This can only be used for very short-running foreground tasks. Running an
440 this or a dependent device.</para>
441 <para>Starting daemons or other long-running processes is not appropriate
443 killed after the event handling has finished.</para>
450 <para>A named label to which a <varname>GOTO</varname> may jump.</para>
457 <para>Jumps to the next <varname>LABEL</varname> with a matching name.</para>
464 <para>Import a set of variables as device properties,
465 depending on <literal>type</literal>:</para>
470 <para>Execute an external program specified as the assigned value and
473 and quoting work like in <varname>RUN</varname>.</para>
479 <para>Similar to <literal>program</literal>, but use one of the
480 built-in programs rather than an external one.</para>
486 <para>Import a text file specified as the assigned value, the content
487 of which must be in environment key format.</para>
493 <para>Import a single property specified as the assigned value from the
495 by an earlier event.</para>
501 <para>Import a single property from the kernel command line. For simple flags
502 the value of the property is set to <literal>1</literal>.</para>
508 <para>Import the stored keys from the parent device by reading
512 comparisons).</para>
516 <para>This can only be used for very short-running foreground tasks. For details
517 see <option>RUN</option>.</para>
524 <para>Wait for a file to become available or until a timeout of
526 if no path is specified, this waits for an attribute to appear.</para>
533 <para>Rule and device options:</para>
538 <para>Specify the priority of the created symlinks. Devices with higher
539 priorities overwrite existing symlinks of other devices. The default is 0.</para>
545 <para>Usually control and other possibly unsafe characters are replaced
547 with this option.</para>
553 <para>Apply the permissions specified in this rule to the
557 they can trigger automatic kernel module loading.</para>
563 <para>Watch the device node with inotify; when the node is
565 synthesized.</para>
571 <para>Disable the watching of a device node with inotify.</para>
579 <para>The <varname>NAME</varname>, <varname>SYMLINK</varname>,
587 processed. The available substitutions are:</para>
592 <para>The kernel name for this device.</para>
599 <para>The kernel number for this device. For example,
601 </para>
608 <para>The devpath of the device.</para>
615 <para>The name of the device matched while searching the devpath
618 </para>
625 <para>The driver name of the device matched while searching the
629 </para>
636 <para>The value of a sysfs attribute found at the device where
642 </para>
643 <para>If the attribute is a symlink, the last element of the
645 </para>
652 <para>A device property value.</para>
659 <para>The kernel major number for the device.</para>
666 <para>The kernel minor number for the device.</para>
673 <para>The string returned by the external program requested with
678 of the result string are substituted: <literal>%c{N+}</literal>.</para>
685 <para>The node name of the parent device.</para>
692 <para>The current name of the device. If not changed by a rule, it is the
693 name of the kernel device.</para>
700 <para>A space-separated list of the current symlinks. The value is
701 only set during a remove event or if an earlier rule assigned a value.</para>
708 <para>The sysfs mount point.</para>
715 <para>The name of the device node.</para>
722 <para>The <literal>%</literal> character itself.</para>
729 <para>The <literal>$</literal> character itself.</para>
736 <para>The hwdb files are read from the files located in the
749 <filename>.hwdb</filename>; other extensions are ignored.</para>
751 <para>The hwdb file contains data records consisting of matches and
757 the line.</para>
759 <para>The match lines are followed by one or more key-value pair lines, which
762 of a record. Lines beginning with <literal>#</literal> are ignored.</para>
764 <para>The content of all hwdb files is read by
769 During runtime only the binary database is used.</para>
774 <para>
780 </citerefentry></para>