Re: [announce] mdevd-0.0.1.0 - a mdev-compatible uevent manager

2018-01-08 Thread Olivier Brunel
Hey there :) So I've been using this (instead of your old uevent handler & busybox's mdev) for a little while now, works great; Thanks! I do have a few questions though. Originally what I had done was to start mdevd, run mdevd-coldplug (referred to as coldplug thereafter), and then start mdevd-ne

Re: [announce] mdevd-0.0.1.0 - a mdev-compatible uevent manager

2018-01-08 Thread Laurent Bercot
However, somewhat recently I believe I heard (read) you say on IRC that the recommended way was actually the other way around, so I switched to start netlinkd first, and then run coldplug. Well, it's really up to you. The thing is, if you coldplug first then listen to the netlink, you have a wi

Re: [announce] mdevd-0.0.1.0 - a mdev-compatible uevent manager

2018-01-08 Thread Colin Booth
On Mon, Jan 08, 2018 at 07:31:17PM +, Laurent Bercot wrote: > > #!/usr/bin/execlineb -P > > pipeline { find /sys -type f -name uevent -print0 } > > forstdin -0 -p f importas -u f f redirfd -w 1 $f echo add > The problem with your script is that it's getting a lot of > duplicates, since multipl

Re: [announce] mdevd-0.0.1.0 - a mdev-compatible uevent manager

2018-01-08 Thread Olivier Brunel
On Mon, 08 Jan 2018 19:31:17 + "Laurent Bercot" wrote: > >But, it seems to me that when you're talking about this you expect > >one to have two different instances of mdevd, one for netlinkd & > >another one > >for coldplug. That's not how I made things however: mdevd is a > >longrun and I si