Like you know, with 2.6 kernels the module-init-tools doesn't use anymore /etc/modules.conf but the better /etc/modprobe.conf. Another IMPORTANT thing is that now the modules exports automatically all their symbols, so all the entries in /etc/modules.d aren't needed anymore. The problem is that If I want to manage a PURE 2.6 system getting rid of this entries I can't do this because /etc/init.d/modules calls modules-updates that calls a script named generate-modprobe.conf, this script call the old modprobe.old with the -c option, but modprobe.old use a list of its included aliases (in the file modutils-2.4.X/util/alias.h), but this aliases are different from the aliases exported from the modules themself (that you can find in /lib/modules/`uname -r`/modules.alias): for example the bluetooth module changed his name from bluez to bluetooth so the alias is broken. This script (generate-modprobe.conf) convert the old format of modules.conf in the new and create a modprobe.conf file. I think that all these things aren't useful, and like a test I've removed the script and my modprobe.conf is EMPTY. All works because the modules themself exports their symbols. A user will need an entry in modprobe.conf only for adding "options" to a module. So I think that a better solution is to create a dir like /etc/modules.d, for example "/etc/modprobe.d" and then use something like modules-update to create a modprobe.conf file: it'll be a simple script that will cat the files in modprobe.d and create a modprobe.conf file. Of course the /etc/init.d/modules script will check for the kernel version and then call the right script. If anyone thinks that this can be a good idea I'll do some patches for doing this and mantain the backcompatibility with the old kernels. Let me know! Bye! Reproducible: Always Steps to Reproduce: 1. 2. 3.
A debian developer (Marco d'Itri) saied to me that Debian already uses modprobe.d and a script to generate modprobe.conf (like now is done with modules.conf), so why gentoo doesn't uses it? Bye!
gentoo has been generating modprobe.conf for a while now, that has nothing to do with this bug
Actully modprobe allready scans /etc/modprobe.d so there is no need to generate modprobe.conf
sure there is ... what if a package provides a modules.d config file but not a modprobe.d config file
baselayout-1.12.0_pre19 and better should handle this graciously
