Re: Proper way to autoload modules (/etc/rc.modules)?

[Pete Zaitcev]

On Mon, 4 Apr 2005 10:27:09 +0200 Axel Thimm <Axel.Thimm(a)ATrpms.net&gt; wrote:

>  > lm_sensors and lirc* modules
>  
>  Both projects take care of this with init.d scripts.
>  
>  But there are others like ivtv. The question is not which modules,
>  there will always be some that need extra handling and even such where
>  an autodetection is not possible (since they may not mirror any
>  hardware piece, but some other functionality). 
So, why do init.d scripts not work for ivtv?

-- Pete

Proper way to autoload modules (/etc/rc.modules)?

[Ignacio Vazquez-Abrams]

On Mon, 2005-04-04 at 23:33 -0700, Pete Zaitcev wrote:
>  On Mon, 4 Apr 2005 10:27:09 +0200 Axel Thimm
> <Axel.Thimm(a)ATrpms.net&gt; wrote:
>  
>  > > lm_sensors and lirc* modules
>  > 
>  > Both projects take care of this with init.d scripts.
>  > 
>  > But there are others like ivtv. The question is not which modules,
>  > there will always be some that need extra handling and even such where
>  > an autodetection is not possible (since they may not mirror any
>  > hardware piece, but some other functionality).
>  
>  So, why do init.d scripts not work for ivtv? 
It's not that they won't work, it's that there's none written.

-- 
Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net&gt;
http://fedora.ivazquez.net/

gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72

Proper way to autoload modules (/etc/rc.modules)?

[Axel Thimm]

On Tue, Apr 05, 2005 at 02:39:53AM -0400, Ignacio Vazquez-Abrams wrote:
>  On Mon, 2005-04-04 at 23:33 -0700, Pete Zaitcev wrote:
>  > On Mon, 4 Apr 2005 10:27:09 +0200 Axel Thimm <Axel.Thimm(a)ATrpms.net&gt; wrote:
>  > 
>  > > > lm_sensors and lirc* modules
>  > > 
>  > > Both projects take care of this with init.d scripts.
>  > > 
>  > > But there are others like ivtv. The question is not which modules,
>  > > there will always be some that need extra handling and even such where
>  > > an autodetection is not possible (since they may not mirror any
>  > > hardware piece, but some other functionality).
>  > 
>  > So, why do init.d scripts not work for ivtv?
>  
>  It's not that they won't work, it's that there's none written. 
For ivtv one could go init.d (if carefully done), but this is an
overshoot. lirc and lm_sesnors have sensible things to do in
userspace, so having an init.d is OK. Having an init.d only with a
modprobe is the wrong design.

And there are other modules that need to be before any init.d scripts,
like capabilities modules whose absence will break named etc.

I'm after a generic solution. :)
-- 
Axel.Thimm at ATrpms.net