|:: [DNG] libudev-compat documentation …|
|This message is part of the following thread:|
|the complete thread tree sorted by date|
> As far as I understand, Vdev goes beyond being an alternative to > Systemd-Udev: it also aims at providing the possibility to give a > per-process view of the device special files - I personnaly haven't any > need of that. Its implementation differs strongly from Udev, which makes > it necessary to have a different library for applications (libudev-compat).
> For what regards complexity, I cannot tell which one is the most > complicated. The biggest problem for me is that none of these tools has > set an obvious standard on how to pass information from the hotplugger > to the applications invoking the library.