[gentoo-user] openrc and /etc/modprobe.d/*

[gentoo-user] openrc and /etc/modprobe.d/*

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 805 bytes --]

As I was booting an old laptop I noticed a message coming up telling me that 
the /etc/modprobe.d/irda file will be done away with in future versions.

Are these files now deprecated?  Are we meant to fit everything in 
/etc/conf.d/modules as per the OpenRC migration page?

http://www.gentoo.org/doc/en/openrc-migration.xml

Most of the /etc/modprobe.d/* files were created at the time I installed 
packages and include aliases for character device drivers and what not - of 
course I have a couple which I set up myself.  Not all of the info has been 
transferred over to /etc/conf.d/modules;  e.g.

	alias char-major-161 ircomm-tty

Am I supposed to copy such stuff over to /etc/conf.d/modules myself, or am I 
going to mess up the new way of configuring modules?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: openrc and /etc/modprobe.d/*

[Nikos Chantziaras]

On 05/26/2011 10:36 PM, Mick wrote:
> As I was booting an old laptop I noticed a message coming up telling me that
> the /etc/modprobe.d/irda file will be done away with in future versions.
>
> Are these files now deprecated?  Are we meant to fit everything in
> /etc/conf.d/modules as per the OpenRC migration page?
>[...]

AFAIK, this is only for module auto-loading.  Stuff like configuration 
options of modules, blacklisting, etc, still go in /etc/modprobe.d/. 
But all files placed there, need to have a ".conf" suffix.  And packages 
still place files there.  It's not deprecated.  For example, run this:

   equery belongs /etc/modprobe.d/*

and you'll get a list of packages that actually placed files there.  If 
you have modules you wish to get loaded automatically on boot, only then 
put entries for them in /etc/conf.d/modules.

[gentoo-user] Re: openrc and /etc/modprobe.d/*

[Harry Putnam]

Nikos Chantziaras <realnc@arcor.de> writes:

> If you have modules you wish to get loaded automatically on boot,
> only then put entries for them in /etc/conf.d/modules.

Sorry to butt in and change the subject slightly:

Do you happen to know the exact syntax for that kind of rule or
whatever it's called.

I've been trying to auto load the `fuse' module using this:

  modules=fuse

Which appears to be the proper syntax judging from the comments in
the stub file provided (/etc/conf.d/modules).

But `fuse' never gets auto loaded.  There must be something more or
different it needs.

Re: [gentoo-user] Re: openrc and /etc/modprobe.d/*

[Alan McKinnon]

Apparently, though unproven, at 00:38 on Monday 30 May 2011, Harry Putnam did 
opine thusly:

> Nikos Chantziaras <realnc@arcor.de> writes:
> > If you have modules you wish to get loaded automatically on boot,
> > only then put entries for them in /etc/conf.d/modules.
> 
> Sorry to butt in and change the subject slightly:
> 
> Do you happen to know the exact syntax for that kind of rule or
> whatever it's called.
> 
> I've been trying to auto load the `fuse' module using this:
> 
>   modules=fuse
> 
> Which appears to be the proper syntax judging from the comments in
> the stub file provided (/etc/conf.d/modules).
> 
> But `fuse' never gets auto loaded.  There must be something more or
> different it needs.


Your syntax is correct. I suspect a module loading issue (not a config issue). 
The answer is likely in your dmesg or messages log 

:-)

can you successfully "modprobe fuse" after first login?


-- 
alan dot mckinnon at gmail dot com

[gentoo-user] Re: openrc and /etc/modprobe.d/*

[Harry Putnam]

Alan McKinnon <alan.mckinnon@gmail.com> writes:

>>   modules=fuse
>> 
>> Which appears to be the proper syntax judging from the comments in
>> the stub file provided (/etc/conf.d/modules).
>> 
>> But `fuse' never gets auto loaded.  There must be something more or
>> different it needs.
>
>
> Your syntax is correct. I suspect a module loading issue (not a
> config issue).  The answer is likely in your dmesg or messages log
>
> :-)
>
> can you successfully "modprobe fuse" after first login?

Yes.  No problems there at all

The only mention of fuse in dmesg looks like:

  # dmesg|grep fuse
  [   19.364168] fuse init (API version 7.13)

Re: [gentoo-user] Re: openrc and /etc/modprobe.d/*

[Alan McKinnon]

Apparently, though unproven, at 00:33 on Tuesday 31 May 2011, Harry Putnam did 
opine thusly:

> Alan McKinnon <alan.mckinnon@gmail.com> writes:
> >>   modules=fuse
> >> 
> >> Which appears to be the proper syntax judging from the comments in
> >> the stub file provided (/etc/conf.d/modules).
> >> 
> >> But `fuse' never gets auto loaded.  There must be something more or
> >> different it needs.
> > 
> > Your syntax is correct. I suspect a module loading issue (not a
> > config issue).  The answer is likely in your dmesg or messages log
> > 
> > :-)
> > 
> > can you successfully "modprobe fuse" after first login?
> 
> Yes.  No problems there at all
> 
> The only mention of fuse in dmesg looks like:
> 
>   # dmesg|grep fuse
>   [   19.364168] fuse init (API version 7.13)

Is fuse blacklisted?


-- 
alan dot mckinnon at gmail dot com