public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Austin Gonyou <austin@digitalroadkill.net>
Cc: Jan Hudec <bulb@ucw.cz>,
	kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Load kernel module automatically
Date: Tue, 04 Jun 2002 19:27:10 -0400	[thread overview]
Message-ID: <3CFD4CCE.9DB9BF52@cfl.rr.com> (raw)
In-Reply-To: <20020604193806.58478.qmail@web14905.mail.yahoo.com> <20020604222743.GA15714@artax.karlin.mff.cuni.cz> <1023231270.9282.23.camel@UberGeek>

Austin Gonyou wrote:
> 
> On Tue, 2002-06-04 at 17:27, Jan Hudec wrote:
> > On Tue, Jun 04, 2002 at 03:38:06PM -0400, Michael Zhu wrote:
> > > Hi, I built a kernel module. I can load it into the
> > > kernle using insmod command. But each time when I
> > > reboot my computer I couldn't find it any more. I mean
> > > I need to use the insmod to load the module each time
> > > I reboot the computer. How can I modify the
> > > configuration so that the Linux OS can load my module
> > > automatically during reboot? I need to copy my module
> > > to the following directory?
> > >   /lib/modules/2.4.7-10/
> >
> > Kernel does not seek for modules to load in any way. Actually, in usual
> > installation there are tons of modules compiled an mostly unused. You
> > must put the insmod command (or better modprobe command) somewhere in
> > the init scripts. Since I expect your installation is RedHat (the kernel
> > version looks like a RedHat one), there should already be one a it
> > should be loading all modules listed in /etc/modules.conf (not sure abou
> > the exact name - I don't have RedHat).
> 
> Isn't that what modules.conf (conf.modules on some) is for though? To
> have lists of available devices and load modules if their services are
> used?(i.e. ifup eth0, but eth0 doesn't exist at boot time, so ifup calls
> a utility that loads the module, then ifup continues to run)
> 
The utility is built into the kernel, it's called kmod and uses /etc/modules.conf
as it's config file....


Mark

  reply	other threads:[~2002-06-04 23:26 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
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 [this message]
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=3CFD4CCE.9DB9BF52@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=austin@digitalroadkill.net \
    --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