Re: mdevd / udevd issues, and the issue of "reverse" dependencies

2020-02-10 Thread Laurent Bercot
This has obvious benefits, at least for now. udevd does not have a readiness notification mechanism (polling for the existence of /run/udev/control surely does not count) There is no fundamental reason why it doesn't. inotify works on tmpfs; you don't need to poll for the existence of

Re: mdevd / udevd issues, and the issue of "reverse" dependencies

2020-02-10 Thread Casper Ti. Vector
On Mon, Feb 10, 2020 at 08:02:44PM +, Laurent Bercot wrote: > There is no fundamental reason why it doesn't. inotify works on tmpfs; > you don't need to poll for the existence of /run/udev/control, you can > inotifywait for its appearance. Thanks. I just did not take inotify into

mdevd / udevd issues, and the issue of "reverse" dependencies

2020-02-10 Thread Casper Ti. Vector
I recently added service definitions for mdevd into slew, during which I switched from a `devd' longrun (which has a dedicated logger, and so requires a R/W filesystem) that depends on a `devices' oneshot (starting a temporary devd process to coldplug basic devices) plus a `devd' longrun to a