On Thu, 24 Mar 2016, George Dunlap wrote: > On Wed, Mar 23, 2016 at 12:14 PM, Roger Pau Monné wrote: > > On Wed, 23 Mar 2016, George Dunlap wrote: > >> On 22/03/16 12:52, Roger Pau Monné wrote: > >> > On Mon, 21 Mar 2016, George Dunlap wrote: > >> >> Signed-off-by: George Dunlap > >> >> --- > >> >> Changes since v1: > >> >> - Attempt to make a clear distinction between custom hotplug scripts > >> >> and the script called for raw physical devices and files > >> >> > >> >> CC: Ian Jackson > >> >> CC: Wei Liu > >> >> CC: Roger Pau Monne > >> >> --- > >> >> docs/misc/block-scripts.txt | 101 ++++++++++++++++++++++++++++++++++++++++++++ > >> >> 1 file changed, 101 insertions(+) > >> >> > >> >> diff --git a/docs/misc/block-scripts.txt b/docs/misc/block-scripts.txt > >> >> new file mode 100644 > >> >> index 0000000..6dd5d48 > >> >> --- /dev/null > >> >> +++ b/docs/misc/block-scripts.txt > >> >> @@ -0,0 +1,101 @@ > >> > [...] > >> >> +Inputs > >> >> +------ > >> >> + > >> >> +In all cases, the scripts are called with either "add" or "remove" as > >> >> +the command. For custom scripts, the command will be the first > >> >> +argument of the script (i.e. $1). > >> >> + > >> >> +The environment variable XENBUS_PATH will be set to the > >> >> +path for the block device to be created. > >> > > >> > This is true for Linux, but not for NetBSD. On NetBSD no env variables are > >> > needed, and everything is passed as arguments using the following format: > >> > > >> > ./