The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: <ron@ronnatalie.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] ATT Hardware
Date: Fri, 29 Jun 2018 14:48:17 -0400	[thread overview]
Message-ID: <20180629144817.18f76be7@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <00f101d40fab$5af29aa0$10d7cfe0$@ronnatalie.com>

On Fri, 29 Jun 2018 09:16:12 -0400 <ron@ronnatalie.com> wrote:
> The recent reference to the Dennis's comments on ATT chip
> production had me feeling nostalgic to the 3B line of computers.
> In the late 80's I was in charge of all the UNIX systems (among
> other things) at the state university system in New Jersey.   As a
> result we got a lot of this hardware gifted to us.    The 3B5 and
> 3B2s were pretty doggy compared with the stuff on the market
> then.   The best thing I could say about the 3B5 is that it stood
> up well to having many gallons of water dumped on it (that's
> another story, Rutgers had the computer center under a seven story
> building and it still had a leaky roof).

We had huge numbers of 3B2s at Columbia that were gifted to us by
AT&T. They didn't know what to do with the things, so the undergrads
were subjected to using them for their labs for a few classes like
computer graphics. The blits attached to them were neat, though. If
only the same could have been said for the overall system.

> The 3B20 was another
> thing.   It was a work of telephone company art.    You knew this
> when it came to power it down where you turned a knob inside the
> rack and held a button down until it clicked off.

We had one of those donated, too. It was put into an extra machine
room and not used for very much, I think because the version of the
OS it came with didn't really do networking at a point where
everything else at the Columbia CS department did.

At one point we considered reusing its disk pack drives for some of
the Vaxes but unfortunately the cabling was incompatible. 

Perry
-- 
Perry E. Metzger		perry@piermont.com

  parent reply	other threads:[~2018-06-29 18:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29 13:16 ron
2018-06-29 14:55 ` John P. Linderman
2018-06-29 15:07   ` Clem Cole
2018-06-29 16:31   ` ron
2018-06-29 17:51     ` Seth J. Morabito
2018-06-29 15:26 ` Seth J. Morabito
2018-06-29 16:29   ` ron
2018-06-29 18:48 ` Perry E. Metzger [this message]
2018-06-30 11:15 Norman Wilson
2018-07-01  2:17 ` Greg 'groggy' Lehey
2018-07-01 20:14   ` John P. Linderman
2018-07-02  0:20     ` William Corcoran
2018-07-02  0:55       ` John P. Linderman
2018-07-02  3:59         ` William Corcoran
2018-07-02 10:13       ` Kevin Bowling
2018-07-03  1:02     ` Dave Horsfall

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=20180629144817.18f76be7@jabberwock.cb.piermont.com \
    --to=perry@piermont.com \
    --cc=ron@ronnatalie.com \
    --cc=tuhs@minnie.tuhs.org \
    /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).