Ralph Ronnquist wrote on 09/10/16 10:54:
> I've now uploaded a first beta, vdevd_2.0, that includes the mechanism
> for dealing with (hand) compiled udev rules, and also includes the
> scanner rules and modem mode switching rules....

Working version is vdevd_2.0.2 ... for the moment

Now, in order for VDEV to be of use to us mere mortals, there needs to
be better documentation. Although I like reading documentation, and know
how to enjoy well-documented functionality, I'm not especially good at
writing it. So this is a call for a technical writer, or anyone with
comparable skills, to step forward and volunteer for the VDEV
documentation page(s).

Presently there are a "man vdevd" page and a "man vdevd-actions" page.
Neither is more than adequate, at best. Given the central function VDEV
is supposed to take on, I think it needs to be quite well documented.
Especially since any other function that wishes to include hotplugging
aspects will need to integrate with it, and thus the developer(s) of
that function will want straight-forward, to-the-point and accurate
documentation.

In real life, I suppose they or we will want the push-button "my Udev
rules" to "my Vdev rules" compiler, but that won't be available very
immediately. Good documentation is the next best thing.

Also, though of lesser priority (in my mind), there's some drive towards
end-user oriented documentation, since some end-user(s) may want to tie
in their personal hotplug actions.

Ralph.