:: Re: [Dng] vdev update and design do…
Top Page
Delete this message
Reply to this message
Author: Jude Nelson
Date:  
To: Enrico Weigelt, metux IT consult
CC: dng@lists.dyne.org
Subject: Re: [Dng] vdev update and design document
Hi Enrico,

I think vdev can support this while keeping a consistent design. vdev
would have two Linux-specific back-ends--one that listens for netlink
packets and forwards them to the rest of vdev (the one slated for alpha
release), and one that simply exits once it all of the initial requests
generated from sysfs get processed. That way, adding support for this
scenario won't affect the core logic.

-Jude

On Sun, Jan 4, 2015 at 9:30 AM, Enrico Weigelt, metux IT consult <
enrico.weigelt@???> wrote:

> On 03.01.2015 23:07, Jude Nelson wrote:
> > Hi Aldemir,
> >
> > That sounds like a good idea--give the Linux port the option to exit
> > once it processes all devices from sysfs. If run again by root
> > manually, it will "patch" /dev by adding new nodes for new devices and
> > remove nodes for devices no longer present.
>
> So, not running as a daemon (not mount itself as fs), but just
> updating /dev ? Sounds like a good idea for that scenario.
>
> OTOH, isn't there already mdev for that ? Should we really duplicate
> that feature here ?
>
>
> cu
> --
> Enrico Weigelt,
> metux IT consulting
> +49-151-27565287
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>