From: Keith Owens <kaos@ocs.com.au>
To: Ken Moffat <ken@kenmoffat.uklinux.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is tulip in its own directory (at least to 2.4.8) ?
Date: Sat, 01 Sep 2001 18:16:49 +1000 [thread overview]
Message-ID: <19669.999332209@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Fri, 31 Aug 2001 20:37:07 +0100." <Pine.LNX.4.21.0108312031320.711-100000@pppg_penguin.linux.bogus>
On Fri, 31 Aug 2001 20:37:07 +0100 (BST),
Ken Moffat <ken@kenmoffat.uklinux.net> wrote:
>I've just changed the NIC on my main box from a natsemi to a tulip. The
>natsemi module was in /lib/modules/`uname -r`/kernel/drivers/net along
>with the ppp modules, but the tulip module is in a tulip subdirectory.
The module install directory tree follows the source tree structure.
All the module tools know about this directory structure. Do not hard
code pathnames in insmod, just "insmod tulip" and let the tools do
their job.
next prev parent reply other threads:[~2001-09-01 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 19:37 Ken Moffat
2001-09-01 8:16 ` Keith Owens [this message]
2001-09-01 20:33 ` Jeff Garzik
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=19669.999332209@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=ken@kenmoffat.uklinux.net \
--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
all inboxes | Powered by JetHome®