From: "Matthew W. Lowe" <swds.mlowe@home.com>
To: linux-kernel@vger.kernel.org
Subject: 2.3.4 Module Problems UPDATED
Date: Mon, 16 Apr 2001 09:57:49 -0600 [thread overview]
Message-ID: <3ADB167D.3872BB38@home.com> (raw)
Ok, I've gotten both NICs to work thanks to the help from you guys.
Basically, what you have to do is disable all the packet filtering stuff
with exception to the minimal requirements to select ipchains. And also
I disabled modular install and built in install for every nic card but
the ones I had. (aka, clicking a bunch of options, rebooting and linux
loading.)
Note: Just in case anyone else comes around asking about 2000 smbfs
mounting, it works with 2.4.3. Before (or in version 2.2.16 and
earlier... Not sure when it was fixed) there use to be this bug with
mounting 2000 shares. Changes to the drive and files wouldn't be
updated, just reloaded from the cache.
Thanks for the help,
Matt
reply other threads:[~2001-04-15 21:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ADB167D.3872BB38@home.com \
--to=swds.mlowe@home.com \
--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