From: Oliver Wegner <oliver@wilmskamp.dyndns.org>
To: root@chaos.analogic.com, linux-kernel@vger.kernel.org
Subject: Re: Load kernel module automatically
Date: Thu, 6 Jun 2002 00:33:16 +0200 [thread overview]
Message-ID: <200206060033.16700.oliver@wilmskamp.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1020605172819.12226A-100000@chaos.analogic.com>
Am Mittwoch, 5. Juni 2002 23:37 schrieb Richard B. Johnson:
> On Wed, 5 Jun 2002, Oliver Wegner wrote:
> > Am Mittwoch, 5. Juni 2002 21:08 schrieb Eric Kristopher Sandall:
> > > On Wed, 5 Jun 2002, John Tyner wrote:
> > > > > Just put the module name in /etc/modules
> > > >
> > > > This is distribution dependent isn't it?
> > >
> > > afaik, it is not distro dependent. I've used /etc/modules in
> > > RedHat, Debian, Sorcery, Source Mage, and Mandrake, all to the same
> > > effect.
> >
> > well, i havent found that file /etc/modules in SuSE. am not aware
> > right now how they handle loading modules during boot process... ;)
> >
> > Oliver
> [...] You need to know that Linux uses a strange command
> interpreter that, unlike windows, does not know how to read one's
> mind.
i never asked linux to read my mind and i know about the differences
between windows and linux. i appreciate that linux doesnt try to do
everything automatically. thats one reason why i use linux ;)
> This means that, should you enter, for instance, `ls
> /etc/modules`, it isn't going to find it because it doesn't exist. You
> need to either type its full name or use wild-cards which I won't
> explain here.
i am aware of all that of course, i think everybody who reads this
mailinglist knows how to handle shell commands and wildcards so i wonder
why you mention it here though. maybe you should consider writing a book
for linux beginners ;)
Oliver
next prev parent reply other threads:[~2002-06-05 22:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 19:38 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
2002-06-05 22:33 ` Oliver Wegner [this message]
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=200206060033.16700.oliver@wilmskamp.dyndns.org \
--to=oliver@wilmskamp.dyndns.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®