public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Oliver Wegner <oliver@wilmskamp.dyndns.org>,
	root@chaos.analogic.com, linux-kernel@vger.kernel.org
Subject: Re: Load kernel module automatically
Date: Thu, 6 Jun 2002 01:12:45 +0200	[thread overview]
Message-ID: <20020605231245.GA1804@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.3.95.1020605172819.12226A-100000@chaos.analogic.com> <200206060023.42180.oliver@wilmskamp.dyndns.org> <1023320742.2443.31.camel@irongate.swansea.linux.org.uk>


On 2002.06.06 Alan Cox wrote:
>On Wed, 2002-06-05 at 23:23, Oliver Wegner wrote:
>> all i wanted to point out was that it doesnt seem to be distribution 
>> independent as someone had stated before because that file /etc/modules 
>> for example doesnt exist under SuSE. i wasnt asking anything about it 
>> myself.
>> 
>> anyway i will be able to find out that information if i need to sometime. 
>> thanks.
>
>modules.conf is the standard name for it. A long time ago it was
>sometimes called conf.modules. 
>

Usually there is an rc script called /etc/rc.d/rc.modules. It
can load modules directly (perhaps this is the case on SuSE and RH),
or it reads the list of modules to load from an independent file
(/etc/modules in Mandrake, for example). In the first case you add
the 'modprobe xxxx' directly in the rc script, and in the second you
just add 'xxxx' in /etc/modules, so you do not modify a system file
and rpm is happy about .rpmnew files.

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.3 (Cooker) for i586
Linux werewolf 2.4.19-pre10-jam1 #3 SMP jue jun 6 00:00:33 CEST 2002 i686

  reply	other threads:[~2002-06-05 23:14 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
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 [this message]
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=20020605231245.GA1804@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@wilmskamp.dyndns.org \
    --cc=root@chaos.analogic.com \
    /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