For example /usr/lib64/modules-load.d/virtualbox.conf from virtualbox(-modules) will now automatically load vbox's modules, starkly contrasting all the years past I can remember when one had to manually load such things. I have long considered things not magically loading just because you installed them to be a significant (and desirous) difference between Gentoo and other distributions. This should be opt-in, not opt-out. (And to be clear, unlike bug 594012, I am not suggesting merely a way to opt-out should be present, but that it should be opt-in in the first place [as it has been already as long as I can remember until now]). Thanks!
Modules-load is an automatic service by design, similar to how udev/eudev works. If you want to block modules from loading because a package installs a /usr/lib/modules-load.d/*.conf file, you can do one of the following: - blacklist the modules in /etc/modprobe.d (see man 5 modprobe.d). - symlink a file in /etc/modules-load.d with the same name as the file installed by the package to /dev/null. I just learned about a way to opt out globally, whwich I will add to 0.23.3. This method involves adding modules-load=0 to the kernel command line.
I have researched this further, and modules-load= is not a way to opt out. Instead, it is a way to add extra modules to load from the kernel command line. Not supporting this is a separate issue which will be fixed in 0.24. The two methods of opting out are given in my previous comment. The blacklist method would insure that the modules will not be loaded by either the modules-load or modules services. The file method would only affect the modules-load service.
So 0.24 will have something additional addressing this issue? Again, these types of services have been opt-in for the entire history of Gentoo until now, and should based even on that alone remain opt-in.
