From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: A tail of two NICs - help needed
Date: Wed, 1 Aug 2001 08:50:01 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0108010846480.1886-100000@ignatious> (raw)
In-Reply-To: <Pine.LNX.4.32.0108011558320.493-100000@data.home>
Geoff,
If you have the (financial) resources I would recomend you look into
getting a couple low cost pci nics. I have seen these as low as $15 a
piece and they often even come with linux drivers (or use the ones already
there). It is then as simple as putting the first one in and getting it to
work, then adding an alias to have the second ome up. The only caveate is
that the order may not be as orginially thought. (The first one you place
in may be the second one enumerated and thus eth1 instead of eth0.) This
is a minor detail easily corrected with the cables though.
=======
Kirk Wood
Cpt.Kirk@1tree.net
The mind is like a parachute; it works much better when open.
If you're too open minded, your brains will fall out.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Geoff Shang
` Brad Thomson
` Kirk Wood [this message]
` Gregory Nowak
` Kirk Wood
` Gregory Nowak
` Kirk Wood
` Raul A. Gallegos
` Terry D. Cudney
` jwantz
` Gregory Nowak
` Raul A. Gallegos
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=Pine.LNX.4.21.0108010846480.1886-100000@ignatious \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).