From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] datakit
Date: Fri, 20 Aug 2004 16:24:05 +0200 [thread overview]
Message-ID: <00a601c486c1$5bfffe10$7dec7d50@SOMA> (raw)
In-Reply-To: <Pine.LNX.4.44.0408192114450.13910-100000@maxroach.lanl.gov>
> - what errors? We're not seeing them
> (oh, wait, we're not LOOKING for them, oops -- yes, this really
> happens!)
sure does. took me a year to find a flakey switch to
switch cable. this was ethernet and this cable was
special so you could stack them.
every few months one chunk of [thin] coax would go
bad to one office (the other 7 were fine).
once found, the standard protocol, when dealing with
broken h/w, was employed:
if it's broken, break it
this avoids some other poor sap from re-using it.
satisfying too!
next prev parent reply other threads:[~2004-08-20 14:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 15:11 Steve Simon
2004-08-20 1:35 ` geoff
2004-08-20 1:52 ` George Michaelson
2004-08-20 2:43 ` geoff
2004-08-20 3:09 ` George Michaelson
2004-08-20 5:46 ` geoff
2004-08-21 0:33 ` ron minnich
2004-08-21 4:51 ` boyd, rounin
2004-08-21 14:22 ` Brantley Coile
2004-08-22 9:50 ` Tim Newsham
2004-08-23 2:50 ` ron minnich
2004-08-20 14:13 ` boyd, rounin
2004-08-20 9:45 ` C H Forsyth
2004-08-20 12:55 ` Long Political Rant. Was: [Re: [9fans] datakit] Dave Lukes
2004-08-20 16:45 ` Jack Johnson
2004-08-20 16:59 ` rog
2004-08-20 13:06 ` [9fans] datakit Wes Kussmaul
2004-08-20 16:51 ` Skip Tavakkolian
2004-08-20 17:07 ` rog
2004-08-22 19:06 ` Jack Johnson
2004-08-20 18:41 ` boyd, rounin
2004-08-21 16:37 ` Boris Maryshev
2004-08-21 17:19 ` Boris Maryshev
2004-08-20 3:30 ` ron minnich
2004-08-20 14:24 ` boyd, rounin [this message]
2004-08-23 15:04 ` andrey mirtchovski
2004-08-23 15:27 ` ron minnich
2004-08-20 13:48 ` boyd, rounin
2004-08-20 5:05 dmr
2004-08-20 5:35 ` George Michaelson
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='00a601c486c1$5bfffe10$7dec7d50@SOMA' \
--to=boyd@insultant.net \
--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).