Hallo Bernd! >>> I don't think that mdev supports an mdev.conf.d/ sort of paradigm ... >> ... but we can implement that /etc/mdev.d feature ... it is not too >> difficult to do. >> >> With an /etc/mdev.d system it would be easy for other packages to add >> mdev rules to the system. That way we do not mangle with /etc/mdev.conf >> in every package and scripting would be a lot easier. > Supporting the same features in quite similar way make me fear that it > will be similarly slow.
No, it is not to implement every feature in the same way. There is just one difference which would make mdev more usable for package management: Currently mdev reads it's configuration from a single file /etc/mdev.conf ... my idea is to allow reading the same type of entries as are contained in /etc/mdev.conf from a directory /etc/mdev.d. That is: Scan that directory to read the configurations split out in separate files. May be in addition to reading /etc/mdev.conf. That way it will not make any differences to current Busybox mdev users but give additional flexibility to distro package managers (put single file per package in /etc/mdev.d -- if package needs to extend mdev.conf). Beside this I wouldn't like to add in every udev feature in mdev. I like the simplicity of mdev and won't change that ... but I also see the problems of distro package management and automatic updating of configuration files during package installation. -- Harald _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
