public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Cc: Jan Hudec <bulb@ucw.cz>
Subject: Re: Load kernel module automatically
Date: Thu, 06 Jun 2002 05:16:48 -0400	[thread overview]
Message-ID: <3CFF2880.8D697F90@cfl.rr.com> (raw)
In-Reply-To: <3CFD19D1.5768FCF8@compro.net> <20020605194716.4290.qmail@web14906.mail.yahoo.com> <20020606085907.GA28704@artax.karlin.mff.cuni.cz>

Jan Hudec wrote:
> 
> On Wed, Jun 05, 2002 at 03:47:16PM -0400, Michael Zhu wrote:
> > Hi, I've read the man page of modules.conf. But I
> > still couldn't figure out how to solve my problem. I
> > mean how to change the modules.conf file. Can I edit
> > this file directly? Can anyone give me an example?
> 
> You say you read the page. ... Hey, wait a moment!
> There are TWO files. /etc/modules.conf, that defines how to load modules
> when they are requested (default parameters), which modules to load on
> kernel request (autoloading) etc. And then there is another file -
> /etc/modules, that is simply processed like
> for each line do modprobe <the line>
> during boot process.
> 
> So depending on what kind of module you have. If it's a module for some
> device, you can make the alias in modules.conf and kernel will ask for
> it when it's needed. It also works for some special cases (like iptables
> - they don't even need an alias). For other things, especially network
> device drivers you need to load them from /etc/modules
> 
That isn't the case.  There is no /etc/modules file on any Linux box I've
ever used. My network driver modules are loaded automatically by the kernel's
internal module loader "kmod" because the are set up correctly in /etc/modules.conf.

"alias eth0 3c905"

ALL device driver modules can be set up to load automatacally by "kmod".

Mark

  reply	other threads:[~2002-06-06  9:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 19:38 Load kernel module automatically Michael Zhu
2002-06-04 19:46 ` Richard B. Johnson
2002-06-04 19:49 ` Mark Hounschell
2002-06-05 19:47   ` Michael Zhu
2002-06-05 20:07     ` Måns Rullgård
2002-06-06  0:00     ` Keith Owens
2002-06-06  8:59     ` Jan Hudec
2002-06-06  9:16       ` Mark Hounschell [this message]
2002-06-06 11:22         ` Jan Hudec
2002-06-06 13:24           ` Mark Hounschell
2002-06-07  3:42         ` Andrew Rodland
2002-06-04 22:27 ` Jan Hudec
2002-06-04 22:54   ` Austin Gonyou
2002-06-04 23:27     ` Mark Hounschell
2002-06-05  0:11       ` Austin Gonyou
2002-06-05 18:56 ` Eric Kristopher Sandall
2002-06-05 19:03   ` John Tyner
2002-06-05 19:08     ` Eric Kristopher Sandall
2002-06-05 19:41       ` Michael Zhu
2002-06-05 20:25         ` Eric Kristopher Sandall
2002-06-06 13:27           ` Thunder from the hill
2002-06-05 20:57       ` Oliver Wegner
2002-06-05 21:37         ` Richard B. Johnson
2002-06-05 22:23           ` Oliver Wegner
2002-06-05 23:45             ` Alan Cox
2002-06-05 23:12               ` J.A. Magallon
2002-06-05 22:33           ` Oliver Wegner
  -- strict thread matches above, loose matches on Subject: below --
2002-06-06 13:29 Thunder from the hill

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3CFF2880.8D697F90@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=bulb@ucw.cz \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox