The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Seth Morabito <web@loomcom.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Research UNIX on the AT&T 3B2?
Date: Fri, 24 Aug 2018 12:06:22 -0400	[thread overview]
Message-ID: <CAC20D2MoDL7C3WSWn2Gmzo4qgA2Pe4+LTnchDq_VQdvKykubEA@mail.gmail.com> (raw)
In-Reply-To: <1535123616.1824656.1485063544.08BED1A8@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 2583 bytes --]

On Fri, Aug 24, 2018 at 11:13 AM Seth Morabito <web@loomcom.com> wrote:

> ...
> I've begun to wonder whether 3B2 hardware was used very much inside of
> Bell Labs.
>
I'd be curious to hear of people that actually used it.  AT&T forced you to
buy one with SVR3 as the porting base (I'd have never had bought the one we
had a Stellar otherwise).
The only time I ever knew anyone run one, was to check to see the behavior
of some code/validation testing of RFS *etc*...

The HW as pretty slow/inflexible compared to 68020/68030 which came out
around the same time, so it was just not interesting - *i.e.* 'JAWS' - Just
another work station' and it did not have a display.  IIRC, it was a server
and pretty inflexible in the I/O subsystem for that use.
Sun would quickly produce the first Sparcs, which as Larry has pointed out,
kicked butt
and were cheaper
.   The MIPS chip would emerge
with lots of designs,
and for that matter the 040 and the 386 would appear soon their after
, too.

I've always felt that the 3Bx series was an example of fighting the
previous war; other than 3B4000 (which had high reliability but other
issues in practice to use it), there was never anything that made them
special - compared to everyone else.

The only 'successful' product
that I
can
remember that used the WE32100
was the
second version (*a.k.a.* product version) of the Blit (Bart's first version
was 68000 IIRC).  Does anyone know of another product?  I think I was told
the 5ESS
changed
 the SLICs
design
from the original 68000 design to WE32100 but I was no
longer associated with anyone working on it by then, so I don't know.

Dennis once remarked to a couple of us that the WE32100 was an example of
AT&T wanting to make sure it had its own recipe to make processors, but it
was not clear it was worth it.   BTW: around the same time both AT&T and HP
were making their own DRAM too.  It was common thinking in management at
tech companies - telling folks that they needed to be 'vertically
integrated.'  But in the case of both HP and AT&T there internally produced
DRAM chips cost 2-3 times what the merchant market cost; so besides the
investment in the fab (which was huge) it was a pretty expensive insurance
policy.

That said, this was also the end times for the idea of the 'second
source.'   Chip manufacturers would be required to license their designs to
some one else (for instance AMD was originally Intel's second source).   I
think HP was using a second source license for their memory, but IIRC AT&T
had developed its own because they had higher reliability standards.

[-- Attachment #2: Type: text/html, Size: 6115 bytes --]

  parent reply	other threads:[~2018-08-24 16:07 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 15:13 Seth Morabito
2018-08-24 15:23 ` William Cheswick
2018-08-24 16:06 ` Clem Cole [this message]
2018-08-24 16:46   ` Larry McVoy
2018-08-24 17:54     ` Jon Forrest
2018-08-26  2:22       ` Larry McVoy
2018-08-27 15:54   ` Mary Ann Horton
2018-08-27 17:06     ` Seth Morabito
2018-08-27 17:33     ` Clem Cole
2018-08-27 19:59       ` John P. Linderman
2018-08-27 20:27         ` Brad Spencer
2018-08-28  0:24       ` Dave Horsfall
2018-08-28  0:30         ` Larry McVoy
2018-08-28  6:01           ` arnold
2018-08-28  6:11             ` George Michaelson
2018-08-28  6:42               ` arnold
2018-08-28 13:13                 ` Arthur Krewat
2018-08-28 22:39                 ` Dave Horsfall
2018-08-29  5:25                   ` arnold
2018-08-28 22:33             ` Dave Horsfall
2018-08-29  0:36               ` Harald Arnesen
2018-08-29  0:46                 ` Larry McVoy
2018-08-29  5:29                   ` [TUHS] SunOS code? arnold
2018-08-29 14:40                     ` Larry McVoy
2018-08-29 14:41                       ` Dan Cross
2018-08-29 14:44                         ` William Pechter
2018-08-29 14:46                           ` Warner Losh
2018-08-29 14:45                         ` Clem Cole
2018-08-29 14:43                     ` Warner Losh
2018-08-29 14:45                       ` Warner Losh
2018-08-29 14:53                       ` Larry McVoy
2018-09-01 11:43                         ` Steve Mynott
2018-09-01 13:50                           ` Andy Kosela
2018-09-01 14:32                             ` Warner Losh
2018-09-04  9:39                               ` Andy Kosela
2018-09-01 15:01                           ` Larry McVoy
2018-09-01 15:20                             ` Warner Losh
2018-09-01 18:24                               ` Steve Mynott
2018-09-01 18:38                                 ` Larry McVoy
2018-08-29 23:09                       ` David Arnold
2018-08-29  1:06                 ` [TUHS] Research UNIX on the AT&T 3B2? Dave Horsfall
2018-08-29  3:23                   ` Theodore Y. Ts'o
2018-08-29  4:36                     ` [TUHS] Cryptic Unix Commands Warren Toomey
2018-08-29 16:13                       ` Jeremy C. Reed
2018-08-29 22:03                       ` Dave Horsfall
2018-08-29 22:09                         ` Grant Taylor via TUHS
2018-08-29 22:21                           ` William Pechter
2018-08-29 23:04                             ` Grant Taylor via TUHS
2018-08-29 23:38                               ` Larry McVoy
2018-08-30  3:59                               ` William Pechter
2018-08-29 22:31                         ` Dan Mick
2018-08-29 23:00                           ` Grant Taylor via TUHS
2018-08-30  8:28                             ` Dave Horsfall
2018-08-30 11:06                         ` ron
2018-08-30 11:35                           ` John P. Linderman
2018-08-30 13:24                           ` Clem Cole
2018-08-30 14:31                             ` William Pechter
2018-08-30 15:01                               ` Clem Cole
2018-08-30 15:22                                 ` Warner Losh
2018-08-30 16:11                                   ` William Pechter
2018-08-29  5:06                     ` [TUHS] Research UNIX on the AT&T 3B2? Greg 'groggy' Lehey
2018-08-29 14:25                       ` Theodore Y. Ts'o
2018-08-29 14:41                         ` Dan Cross
2018-08-29 14:50                           ` Chet Ramey
2018-08-29 14:59                             ` Larry McVoy
2018-08-29 15:08                               ` Chet Ramey
2018-08-29 17:14                           ` Arno Griffioen
2018-08-29 23:23                             ` Eric Wayte
2018-08-30  3:03                               ` Gregg Levine
2018-08-29 17:28                           ` Theodore Y. Ts'o
2018-08-30  5:58                         ` Greg 'groggy' Lehey
2018-08-30 13:14                           ` Warner Losh
2018-08-29  8:43                     ` Dave Horsfall
2018-08-29  7:03                   ` Arrigo Triulzi
2018-08-28  1:14         ` Warren Toomey
2018-08-28 17:47         ` Paul Winalski
2018-08-26  8:48 ` arnold
2018-08-26 13:09 Norman Wilson

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=CAC20D2MoDL7C3WSWn2Gmzo4qgA2Pe4+LTnchDq_VQdvKykubEA@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=web@loomcom.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).