baselayout2 and modprobe

Message

v_andal · Post by **v_andal** » Mon May 09, 2011 8:06 am

Hi!

After reading the http://www.gentoo.org/doc/en/openrc-migration.xml I've discovered, that I don't have /etc/modules.autoload.d/kernel-2.6. Instead I have
/etc/modprobe.conf, /etc/modprobe.d, /etc/modules.conf and /etc/modules.d There's also update-modules utility from module-init-tools. I can't understand, how the /etc/conf.d/modules is involved here.

Ok. Most likely, I can get rid /etc/modules.conf and /etc/modules.d. Probably I should also get rid of /etc/modprobe.conf and keep things in /etc/modprobe.d
directory. Why would I want to use /etc/conf.d/modules and how it is used really?

krinn · Post by **krinn** » Mon May 09, 2011 9:32 am

cause /etc/conf.d/modules is for kernel module config and /etc/modprobe.d is for modules config

let's take alsa

if you want configure some alsa functions, it's done in /etc/modprobe.d/alsa.conf
and if you want to load the alsa module with some extra option, this time, it's in /etc/conf.d/modules, this is == to the command line parameter you could use when using modprobe on a module

Sysa · Post by **Sysa** » Mon May 09, 2011 9:58 am

Just do your migration and do not worry about.

v_andal · Post by **v_andal** » Tue May 10, 2011 7:14 am

krinn wrote:cause /etc/conf.d/modules is for kernel module config and /etc/modprobe.d is for modules config

let's take alsa

if you want configure some alsa functions, it's done in /etc/modprobe.d/alsa.conf
and if you want to load the alsa module with some extra option, this time, it's in /etc/conf.d/modules, this is == to the command line parameter you could use when using modprobe on a module

Hm. If I want to provide options to my alsa module, then I put them directly into alsa.conf. At least that's what I always do. Do you say that instead I can place those options into /etc/conf.d/modules and some script shall provide them to kernel when it loads the module? Hm. I'm curious how this is done. So far I was assuming that modules loading is done always by modprobe, so there's no sense in having any other configuration except for /etc/modprobe.d.

krinn · Post by **krinn** » Tue May 10, 2011 8:35 am

v_andal wrote:so there's no sense in having any other configuration except for /etc/modprobe.d.

there's no sense until you wish to provide an option to load your module when using kernel X and using some different ones when using kernel Y.
/etc/modprobe.d/*.conf will be load for all kernels, /etc/conf.d/modules can target kernel versions.

v_andal · Post by **v_andal** » Tue May 10, 2011 11:48 am

I guess, I've figured out why this exists. This is needed for loading those modules that are not loaded automatically by the kernel