It's very good to use inotify, because it's a standard Linux tool
(don't know for other nixes), not yet-another-interface. This way DEs
shouldn't have any concern implementing it.
This means you will provide support for inotify in vdevfs? AFAIK
there isn't in every filesystem, eg sysfs.
Didier
Le 17/03/2015 09:48, Jude Nelson a écrit :
> > 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@???
> <mailto:reisenweber@web.de>> 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@??? <mailto:Dng@lists.dyne.org>
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>
>
>
>
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
::
Re: [Dng] vdev status updates
