From: "Thomas Ward" <slingshooter@valkyrie.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Linux rules, Windows sucks!
Date: Sun, 15 Sep 2002 01:32:13 -0400 [thread overview]
Message-ID: <000e01c25c79$3f94a6a0$0100a8c0@stargate> (raw)
In-Reply-To: <20020915041601.16293.1924.Mailman@speech.braille.uwo.ca>
Hi, I had a similar experience using the linksys cards. Over all they are
great cards. In my case I dropped it in, and Red Hat found it, and kudzu was
nice enough to configure it for me. All I needed then was to go ahead and
configure the network to my liking.
next parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020915041601.16293.1924.Mailman@speech.braille.uwo.ca>
` Thomas Ward [this message]
Adam Myrow
` Jason Symes
` MaTt
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='000e01c25c79$3f94a6a0$0100a8c0@stargate' \
--to=slingshooter@valkyrie.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).