From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Vanilla Plan 9 or one of the flavors?
Date: Mon, 6 Jan 2014 08:29:10 -0500 [thread overview]
Message-ID: <c83ace87ba402a813d8c156d30d47f6c@brasstown.quanstro.net> (raw)
In-Reply-To: <E339D97B-4174-4DDB-BB1E-17D68CB0DF8C@gmail.com>
> Not to derail the discussion that this has now turned into, but it
> seems that the Ethernet card in the aforementioned server is too old,
> too esoteric, or simply hasn't had anyone around to bother writing a
> driver for it, and so wasn't recognized by the Bell Labs distribution
> or 9atom (both images downloaded today/yesterday - 1/5/14 - depending
> on your timezone). Do I have any other options, besides replacing the
> card with something known to work? I've been considering going with
> 9front, to see if that helps, but I'd rather stick with something as
> close to the Bell Labs distribution as I can get, e.g. I'd really
> rather use Fossil+Venti, rather than whatever 9front has. (I'd write
> a driver myself, but I am neither competent enough with C nor Plan 9
> nor hardware interfaces to do so.) Unfortunately, I'm at my dad's
> house, and the affected server is at my mom's house, so I can't give
> more information on the specific card. But I can give details, run
> commands, etc. after I get home from school tomorrow. I have a full
> installation on the affected box, so I can run Plan 9 tools; I just
> can't connect to the network. Thanks.
the output of "pci | grep net" should be enough.
- erik
next prev parent reply other threads:[~2014-01-06 13:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 2:02 Alex Jordan
2013-12-31 2:07 ` Alex Jordan
2013-12-31 4:33 ` erik quanstrom
2014-01-05 23:54 ` Alex Jordan
2014-01-06 0:03 ` Patryk Laurent
2014-01-06 4:03 ` Steven Stallion
2014-01-06 4:36 ` Lyndon Nerenberg
2014-01-06 4:41 ` Steven Stallion
2014-01-06 4:53 ` Lyndon Nerenberg
2014-01-06 5:01 ` Steven Stallion
2014-01-06 5:09 ` Lyndon Nerenberg
2014-01-06 5:13 ` andrey mirtchovski
2014-01-06 5:16 ` Steven Stallion
2014-01-06 5:28 ` Patryk Laurent
2014-01-06 5:12 ` Bruce Ellis
2014-01-06 15:35 ` a
2014-01-06 16:40 ` Aram Hăvărneanu
2014-01-06 16:54 ` Anthony Sorace
2014-01-06 17:21 ` lucio
2014-01-06 17:09 ` tlaronde
2014-01-06 17:25 ` lucio
2014-01-06 20:13 ` Kurt H Maier
2014-01-06 4:42 ` balaji
2014-01-06 20:05 ` Kurt H Maier
2014-01-06 7:08 ` Alex Jordan
2014-01-06 7:39 ` cinap_lenrek
2014-01-06 7:49 ` Alex Jordan
2014-01-06 10:48 ` Paul Clark
2014-01-06 17:29 ` Dave Eckhardt
2014-01-06 12:20 ` Richard Miller
2014-01-06 13:29 ` erik quanstrom [this message]
2014-01-07 6:58 ` Alex Jordan
2014-01-07 8:32 ` Andrés Domínguez
2014-01-07 14:00 ` erik quanstrom
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=c83ace87ba402a813d8c156d30d47f6c@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).