> Well, from what I understand, mdev parses through the entire > /etc/mdev.conf file for every device it discovers (I think it does > this even when running `mdev -s' which scans all existing > devices). This makes mdev smaller and simpler, but probably less > efficient than a daemon which parses and caches the whole > configuration (like udevd). Adding a bunch of rules to mdev with more > hooks and having it parse multiple files in an mdev.conf.d definitely > would decrease the efficiency of a system with an mdev setup. But it > would still be a simpler and perhaps easier to understand setup than a > udevd one(?)
mdev could also be patched to be run as a "mdevd" daemon listening to the netlink. That would solve the speed problem related to /etc/mdev.conf parsing, and would still be orders of magnitude below the complexity of udevd. -- Laurent _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
