The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: alan@alanlee.org
To: tuhs@tuhs.org
Subject: [TUHS] Re: Reaction to the 3B2 at Bell Labs
Date: Tue, 29 Nov 2022 06:33:19 -0500	[thread overview]
Message-ID: <b8bdbf58b789a49b3084918515b223f1@alanlee.org> (raw)
In-Reply-To: <8f278bf8-de57-4e77-a3b8-d007d7c3a446@app.fastmail.com>

It would be nice to get more technical information on the 3B2s.  As late 
as 2016, I had reached out to Ed Eckart the archivist at Alcatel-Lucent 
and Seth had contacted William Caughlin at AT&T archives for more 
information.  Both seemed to indicate the systems were still in use at 
some customer sites and thus detailed technical info (eg. schematics, 
theory of operation docs, etc) could not be shared with the public.  But 
that sort of information was preserved and safe.

If anyone has contacts into either organization, a gentile nudge would 
be appreciated! :)

-Alan

On 2022-11-26 13:46, Seth Morabito wrote:
> Hello all,
> 
> I'm giving a presentation on the AT&T 3B2 at a local makerspace next
> month, and while I've been preparing the talk I became curious about
> an aspect that I don't know has been discussed elsewhere.
> 
> I'm well aware that the 3B2 was something of a market failure with not
> much penetration into the wider commercial UNIX space, but I'm very
> curious to know more about what the reaction was at Bell Labs. When
> AT&T entered the computer hardware market after the 1984 breakup, I
> get the impression that there wasn't very much interest in any of it
> at Bell Labs, is that true?
> 
> Can anyone recall what the general mood was regarding the 3B2 (and the
> 7300 and the 6300, I suppose!)
> 
> -Seth

  parent reply	other threads:[~2022-11-29 11:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 18:46 [TUHS] " Seth Morabito
2022-11-26 19:18 ` [TUHS] " Larry McVoy
2022-11-26 20:04   ` Seth Morabito
2022-11-26 20:42     ` Rob Pike
2022-11-26 21:46       ` Clem Cole
2022-11-26 23:00         ` Marc Donner
2022-11-26 23:23           ` Larry McVoy
2022-11-26 23:47             ` Dan Cross
2022-11-27  0:17               ` Larry McVoy
2022-11-27  4:43                 ` Phil Budne
2022-11-27 14:51                   ` John P. Linderman
2022-11-27 15:29                     ` arnold
2022-11-27 16:11                     ` Ron Natalie
2022-11-27 16:59                       ` Warner Losh
2022-11-27 18:59                       ` arnold
2022-11-27 20:45                         ` Rob Pike
2022-11-28 18:53                     ` William Corcoran
2022-11-28 20:59                       ` Kenneth Goodwin
2022-11-28 22:33                         ` ron minnich
2022-11-28 22:43                           ` Marc Donner
2022-11-29  1:49                             ` Alan Glasser
2022-12-01  6:10                               ` Kevin Bowling
2022-12-01  8:30                                 ` Andrew Hume
2022-12-01  8:53                                   ` arnold
2022-12-01  9:19                                     ` Skip Tavakkolian
2022-12-01 12:25                                       ` Brad Spencer
2022-12-01 10:00                                     ` Andrew Hume
2022-12-01 10:17                                       ` arnold
2022-11-27 14:53                   ` Larry McVoy
2022-11-26 19:21 ` Douglas McIlroy
2022-11-29 11:33 ` alan [this message]
2022-11-30  2:50 ` Mary Ann Horton

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=b8bdbf58b789a49b3084918515b223f1@alanlee.org \
    --to=alan@alanlee.org \
    --cc=tuhs@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).