Skip to contentSkip to conversation

put netdev handling and dev.d/ in manpages

PATCH Applied Kay Sievers 2 participants 2 messages Apr 1, 2004

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 put netdev handling and dev.d/ in manpages

Mention the recently added netdev handling and the dev.d/ directories in the man pages.

thanks,
Kay

===== udev.8 1.54 vs edited =====

udev.8 +45 -11
@@ -23,14 +23,25 @@
 .B UDEV_NO_SLEEP
 The default behavior of
 .B udev
-is to wait until all the sysfs files of the device chain are populated. If set
+is to wait until all the sysfs files of the device chain are populated. If set,
 .B udev
 will continue, regardless of the state of the device representation.
+.TP
+.B UDEV_NO_DEVD
+The default behavior of
+.B udev
+is to execute programs in the
+.I /etc/dev.d/
+directory after device handling. If set,
+.B udev
+will skip this step.
 .SH "DESCRIPTION"
 .B udev
-creates or removes device node files usually located in the /dev directory.
-It provides a dynamic device directory contaning only the files for
-actually present devices.
+provides a dynamic device directory containing only the files for actually
+present devices. It creates or removes device node files usually located in
+the /dev directory, or it renames network interfaces.
+.br
+
 .P
 As part of the
 .B hotplug
@@ -42,7 +53,7 @@
 reads the sysfs directory of the given device to collect device attributes
 like label, serial number or bus device number.
 These attributes may be used as keys to determine a
-unique name for device file creation.
+unique name for the device.
 .B udev
 maintains a database for devices present on the system.
 .br
@@ -88,8 +99,8 @@
 and all permission files are read in lexical order.
 .TP
 .B udev_log
-If you want udev to log some information to the syslog for every node created or
-removed. The default value is
+If you want udev to log some information to the syslog for every device handled.
+The default value is
 .IR yes .
 .TP
 .B default_mode
@@ -149,9 +160,9 @@
 file.
 .P
 Every line in the rules file defines the mapping between device attributes
-and the device file name. One or more keys are specified to match a rule
-with the current device. If all keys are matching, the rule will be applied
-and the name is used for the device node.
+and the device name. One or more keys are specified to match a rule with
+the current device. If all keys are matching, the rule will be applied and
+the name is used to name the device file or the network interface.
 .br
 If no matching rule is found, the default kernel device name is used.
 .P
@@ -200,7 +211,8 @@
 call.
 .TP
 .B NAME
-The name of the node to be created.
+The name of the node to be created, or the name, the network interface
+should be renamed to.
 .br
 If given with the attribute
 .BR NAME{ all_partitions }
@@ -341,11 +353,33 @@
 supported within this match with the '\-' character.  For example, to match on
 the range of all digits, the pattern [0\-9] would be used. If the first character
 following the '[' is a '!', any character not enclosed is matched.
+.P
+After device node creation, removal, or network device renaming,
+.B udev
+executes the programs in the directory tree under
+.IR /etc/dev.d/ .
+The name of a program must end with
+.I .dev
+suffix, to be recognized.
+.br
+In addition to the hotplug environment variables,
+.B DEVNAME
+is exported to make the name of the created node, or the name the network
+device is renamed to, available to the executed program. The programs in every
+directory are sorted in lexical order, while the directories are searched in
+the following order:
+.sp
+.nf
+/etc/dev.d/$(DEVNAME)/*.dev
+/etc/dev.d/$(SUBSYSTEM)/*.dev
+/etc/dev.d/default/*.dev
+.fi
 .SH "FILES"
 .nf
 /sbin/udev                           udev program
 /etc/udev/*                          udev config files
 /etc/hotplug.d/default/udev.hotplug  hotplug symlink to udev program
+/etc/dev.d/*                         programs invoked by udev
 .fi
 .LP
 .SH "SEE ALSO"

===== udevinfo.8 1.9 vs edited =====

udevinfo.8 +5 -4
@@ -24,7 +24,8 @@
 will be prepended.
 .TP
 .BI \-q " query_type"
-Query the database for specified value of a created device node.
+Query the database for specified value of a created device node or network
+interface.
 .RB Needs " \-p " or " \-n " specified.
 .br
 Valid types are:
@@ -34,9 +35,9 @@
 Specify the sysfs path of the device to query.
 .TP
 .BI \-n " name"
-Specify the name of the node or the symlink for the device to query.
-Partition names generated with the NAME{all_partitons} option can not be
-queried, the main device must be used instead.
+Specify the name of the node, the symlink or the network interface for the
+device to query. Partition names generated with the NAME{all_partitons} option
+can not be queried, the main device must be used instead.
 .TP
 .B \-a
 Print all

===== udevtest.8 1.1 vs edited =====

udevtest.8 +3 -2
@@ -7,8 +7,9 @@
 .B udevtest
 simulates a
 .B udev
-run for the given device, and prints out the node names
-for the given device, the real udev would have created.
+run for the given device, and prints out the name of the node
+the real udev would have created, or the name of the renamed network
+interface.
 .SH "SEE ALSO"
 .BR udev (8)
 .SH AUTHORS
Applied
#1 lore raw
Quoted 2 lines · Kay Sievers

Mention the recently added netdev handling and the dev.d/ directories in the man pages.

Applied, thanks.

greg k-h

-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel