The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] A Talk on Early Unix
Date: Thu, 30 Jun 2016 20:48:39 -0700	[thread overview]
Message-ID: <5F0770EE-B494-445D-B78B-55EEF32A4702@orthanc.ca> (raw)
In-Reply-To: <728E6849-FAE3-43C2-9950-16BA591CE9B4@ronnatalie.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]


> On Jun 30, 2016, at 5:53 AM, Ronald Natalie <ron at ronnatalie.com> wrote:
> 
> Ah yes, the 3B’s.   Running the state university computer department (in NJ) we got a lot of 3B’s (3B2, 3B5, 3B20).

We had the misfortune of being donated a 3B4000.  

> The 3B20 was definitely a piece of telephone equipment.

The 3B4000 had a 3B20 inside that acted as the bootstrap controller (ala the micro-pdp inside the larger Vaxen doing similar duty).  Most impressively, said 3B20, with the CPU and IO power of a match stick, was also the Ethernet portal for the entire 3B4000.  It couldn't even come close to keeping up with its 10 mbit/s NIC.

AT&T flogged this abomination to us as the core of our "distributed network environment."  Actually, they flogged it to us as a "1 million dollar donation in kind" because they knew nobody would buy that piece of shit, but this way they got the tax write off, and our beloved University president got to grin madly at a press conference.

When they replaced it with a half-dozen 3B2-xxx servers (about a year later) we at least got a marginal improvement in network throughput.  But they cancelled that out with RFS.

Basically, the 3B2s (and the 3B4K by extension) were designed to hang off the side of the 4ESS and collect toll call records for billing purposes.  Anyone remember Tuxedo?

> The 3B5 was an interesting machine.   We found out how rugged it was when a drain pipe broke over the top of it (the Rutgers main computer center was underground under a court yard between the twin towers of the Hill Center).   The thing survived a deluge of water being dumped into it.

I don't think we ever landed one of those in the shop.  It seemed like an intriguing bit of gear back when I looked at it.  Decades ago, now.

--lyndon



  reply	other threads:[~2016-07-01  3:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-30 12:41 Doug McIlroy
2016-06-30 12:53 ` Ronald Natalie
2016-07-01  3:48   ` Lyndon Nerenberg [this message]
2016-07-02  1:57     ` Steve Simon
2016-07-03  1:17     ` Brad Spencer
2016-06-30 13:02 ` Dan Cross
  -- strict thread matches above, loose matches on Subject: below --
2016-06-30 16:34 Doug McIlroy
2016-06-30  6:56 Warren Toomey
2016-06-30  7:10 ` arnold
2016-06-30 10:30   ` Andrew Warkentin
2016-06-30 10:39     ` Andrew Warkentin
2016-06-30 11:03       ` Steve Nickolas
2016-06-30 22:22       ` Dave Horsfall
2016-06-30 14:11     ` Nemo

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=5F0770EE-B494-445D-B78B-55EEF32A4702@orthanc.ca \
    --to=lyndon@orthanc.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 NNTP newsgroup(s).