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

[Axel Thimm]

On Fri, Apr 08, 2005 at 02:08:51PM +0200, Arjan van de Ven wrote:
> On Fri, 2005-04-08 at 13:36 +0200, Axel Thimm wrote:
> > On Thu, Apr 07, 2005 at 10:11:49PM -0700, Pete Zaitcev wrote:
> > > I'm sending you round to gather examples because while it's intuitively
> > > obvious that /etc/rc.modules is useful, it really has no reason to exist.
> > 
> > The capabilities modules were mentioned a couple times, e.g. any
> > module that has no detectable hardware or no hardware at all mapped
> > to.
> 
> but capabilities as a module is a big mistake and even a security
> hole ;)

No, it's not, if you want to replace it with something better.

> So please give another, more realistic example....

You are the kernel guru, never seen any non-hardware modules? ;)

Choosing netfilter/netscheduling modules also comes to mind ...
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20050408/d7bf61c8/attachment.sig>