The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ronald Natalie)
Subject: [TUHS] Was 5ESS built on UNIX?
Date: Sun, 12 Mar 2017 15:35:49 -0400	[thread overview]
Message-ID: <F885504C-782E-41EE-8FBB-154C468156B1@ronnatalie.com> (raw)
In-Reply-To: <20170312163529.0F31C18C09B@mercury.lcs.mit.edu>

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

Being just down the road, AT&T gave us a lot of their own branded compute equipment, a 3B20, a couple of 3B5’s, and countless 3B2’s.

The 3B2 was amusing as I tried to work the power switch and it told me I didn’t have sufficient permissions.

The 3B20 you powered down by turning the switch to standby and holding a button down (this is very akin to how you put the original arpanet 303 broadband modems into loopback).

The 3B5 was distinguished in that even though I was in the basement of a 7 story building, the roof leaked into our machine room.    One day in attempt to find the leak, we had the campus fire department pump water in various places in the building courtyard.    We finally found the leak was a broken drain pipe, but not before about a hundred gallons of water flowed into the machine room ceiling and directly on top of the 3B5.    The 3B5 took a licking, but like the timex, kept on ticking.



  reply	other threads:[~2017-03-12 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 16:35 Noel Chiappa
2017-03-12 19:35 ` Ronald Natalie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-01  4:20 Rudi Blom
2017-02-28 21:12 Doug McIlroy
2017-02-28 19:11 Nemo
2017-02-28 19:30 ` Corey Lindsly
2017-03-10  8:04   ` Erik E. Fair
2017-03-12 16:21     ` Nemo
2017-02-28 19:35 ` Nelson H. F. Beebe

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=F885504C-782E-41EE-8FBB-154C468156B1@ronnatalie.com \
    --to=ron@ronnatalie.com \
    /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).