[PATCH] hotplug - man page addition

[Kay Sievers <kay.sievers@vrfy.org>]

[-- Attachment #1: Type: text/plain, Size: 111 bytes --]

We should mention the DEVPATH in the hotplug man page too,
as someone missed it and got confused.

thanks,
Kay

[-- Attachment #2: hotplug.8.diff --]
[-- Type: text/plain, Size: 1294 bytes --]

--- hotplug.8	2002-08-13 23:59:30.000000000 +0200
+++ hotplug.8.0	2004-02-25 02:44:39.000000000 +0100
@@ -30,13 +30,14 @@
 parameter.  The name corresponds to a specific kernel subsystem whose
 events it processes (e.g. "usb", "pci", "net" etc.).
 .P
-Information about an event is usually passed to agents in the form of
-environment variables.  Most agents accept a "ACTION" variable that describes
-the type of the event.  It can be, for example, "add" or "remove" to signify
-that some device has just been connected to or disconnected from the system
-respectively.  In such requests, agents are also given variables
-describing at the device (and its location) so that they can choose
-the appropriate drivers to set up.
+Information about an event is passed in the form of environment variables.
+Most agents accept a "ACTION" variable that describes the type of the event.
+It is set to "add" or "remove" to signify that some device has just been
+connected to or disconnected from the system.
+.br
+The location of the device is provided in the variable "DEVPATH".
+With kernel version 2.5 and later it is set to the corresponding sysfs device
+path without the mountpoint but a leading slash.
 .P
 .B hotplug
 agents aren't necessarily called only by the kernel though.  While the OS