Where to put modules configuration options in Karmic?

David Curtis dcurtis at uniserve.com
Thu Oct 8 02:56:12 UTC 2009


On Wed, 7 Oct 2009 17:24:20 -0300
"Marcelo Magno T. Sales" <mmtsales at gmail.com> wrote:

> Em Terça-feira 06 Outubro 2009, David Curtis escreveu:
> > On Tue, 6 Oct 2009 21:52:55 -0300
> >
> > "Marcelo Magno T. Sales" <mmtsales at gmail.com> wrote:
> > > Hello,
> > >
> > > Until Jaunty, we would put modules configuration options in
> > > /etc/modprobe.conf. It seems this file no longer exists in Karmic.
> > > Where to put such options now?
> >
> > You just have to create a <module_name>.conf file with the options
> > line in it in /etc/modprobe.d. I believe all files in that directory
> > are read at boot so the name of the file may not even matter.
> >
> > Dave
> 
> Thanks, I'll try that. Should I use the same line I would put in 
> /etc/modprobe.conf in Jaunty 

Yes. 

> or only the module parameters? If it is
> the last, it will assume the module name is the file name?
 
I believe you can name it whatever you wish, I would pick something
that makes sense like /etc/modprobe.d/<module_name>.conf. Though I do
think that you will (just)get a warning if the filename does not end
in .conf.

It is in the line that you write that specifies which module the params
or options are for. Nothing has changed as far as how the lines are
read, it's just that modprobe.conf is broken up into individual files.
In fact I think you could name a file /etc/modprobe.d/modprobe.conf and
it would be read, but why not follow the preferred naming method?
Pretty sure this is just a cosmetic change.

Dave





More information about the ubuntu-users mailing list