Reader Question: Why is there no /etc/modules.conf in Ubuntu?
July 10, 2006 by Jon
Filed under Reader Questions
OK, I’ll admit it - I’m the reader in this case.
I was reading the booting section of my fancy-dancy LPI certification book and it speaks about kernel parameters. It mentions that you can feed the kernel parameters at boot time (which will be the subject of an upcoming entry) and also states that you can feed kernel modules parameters as well. It says that kernel module parameters can be specified in either the /etc/modules.conf or the /etc/conf.modules file.
I’m running Kubuntu 6.06LTS and I have neither of these files. I have an /etc/modprobe.d/ directory that contains a bunch of files that kind of look like what I want, but I’m not familiar enough with this topic to figure it out. I did some preliminary Googling and came up with this post that states running a sudo update-modules will create the modules.conf file, but it doesn’t work.
Now, it’s quite obvious that I don’t need this file as my system runs fine, but in order to understand how to pass module parameters, I need to understand how the system works in Ubuntu. Anyone want to take a shot at explaining it for me?
I’m not really sure, but I’ve been starting to notice that folders ending with .d seem to be a place to put a load of individual files that together constitute a whole configuration file. Like init.d and (in Fedora) yum.repos.d. Kind of like they make your conf files modular.
So maybe you don’t need a modules.conf because Ubuntu splits all the files out into modules.d, to make it a bit easier to manage?
Methinks you’re right. I have an /etc/modules.conf on my Debian server and it has sections (like alias, for example) that look like individual files in my /etc/modules.d director on my Kubuntu box.
in 2.6 OS
the /etc/modules.conf was replaced by /etc/modprobe.conf
and since this is not in Ubuntu been replace by
/etc/modprobe.d (which contains the modules in scripts anyways)
I find that the modules.conf has been replaced by /etc/modeprobe.conf in the Fedora Core!
You could have a look at the folling two files:
/etc/module-init-tools
/etc/module
you may find something