> How would that "watching" work?

vdevd-user would have an inotify(2)-based back-end (hopefully via
libkqueue, so it would be portable). The back-end would set up inotify
watches on /dev and its descendant directories, and translate creat(2) and
unlink(2) events from inotify into a vdev-specific device event with the
relevant information (e.g. by querying the device metadata that the
system's vdevd puts into /dev/vdev/...).

-Jude

On Tue, Mar 17, 2015 at 1:30 AM, Joerg Reisenweber <reisenweber@???>
wrote:

> On Tue 17 March 2015 01:20:43 Jude Nelson wrote:
> > What I'm considering doing is creating vdevd-user, a build of
> > vdevd with a backend for watching the contents of /dev, instead of
> > listening to the kernel for device events.
>
> How would that "watching" work?
>
> /jOERG
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>
>