From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /rc/bin/boota:
Date: Wed, 1 May 2002 14:13:28 -0400 [thread overview]
Message-ID: <a6bf9fceb74b93fd94b537e12c2e4713@plan9.bell-labs.com> (raw)
On Sun Apr 28 14:23:17 EDT 2002, boyd@strakt.com wrote:
> Russ Cox wrote:
> ...
> > Not sure about your PCMCIA card. If it's a relabeled
> > 3Com 589 then you could add an ID string to the driver,
> > but I suspect this is not the case.
>
> I'm pretty sure it's a 3c589 replacement :( aka:
>
> 3CCFE574BT
>
> 10/100 Mbit.
Last September we tried to help you with this (look in the 9fans
archives). In your last message on the subject you said
that sounds right. thanks. i'll let you know how i get on.
But you didn't.
next reply other threads:[~2002-05-01 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 18:13 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-28 17:58 Russ Cox
2002-04-28 18:21 ` Boyd Roberts
2002-04-28 18:51 ` Latchesar Ionkov
2002-04-28 17:30 Boyd Roberts
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=a6bf9fceb74b93fd94b537e12c2e4713@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).