From: "Seth J. Morabito" <web@loomcom.com>
To: tuhs@minnie.tuhs.org
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] AT&T 3b4000 (was Re: Old 386 Unix Versions)
Date: Fri, 26 Jul 2019 11:18:06 -0700 [thread overview]
Message-ID: <87muh0zmld.fsf@loomcom.com> (raw)
In-Reply-To: <CAC20D2MiW1aKHoNUaiabUfngbsB0C=9uNKmkcy_O7Ur0ULSrsQ@mail.gmail.com>
Clem Cole writes:
> Yes, it was a full Single System Image (SSI) system -- one of the 3B4000's
> SW architects was Tom Bishop, whom I'm still in contact (he's in the Austin
> these days). Those folk did a nice job. FWIW: When the 4000 project was
> canceled in Indiana Hill, Tom joined us @ LCC to work on TNC.
This is of course extremeley relevant to my interests as well. Since
I've gotten the 3B2/400 emulator pretty much finished up (MAU, NI, CTC,
and PORTS are all working now), I'm turning my attention to trying to
emulate other 3B2 models, starting with the /600 and /1000 WE32200
systems.
The 3B4000 is an entirely different beast, of course, but I've seen
precious little documentation about it. I'd love to hear more from Tom
Bishop's history at Indian Hill, if he's willing to share!
-Seth
--
Seth Morabito
Poulsbo, WA, USA
web@loomcom.com
next prev parent reply other threads:[~2019-07-26 18:24 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 14:53 [TUHS] PCC for the i386 Jason Stevens
2019-07-11 15:12 ` arnold
2019-07-11 15:37 ` Clem cole
2019-07-11 15:50 ` Jason Stevens
2019-07-11 16:30 ` Clem cole
2019-07-11 16:42 ` Richard Salz
2019-07-11 16:48 ` Warner Losh
2019-07-11 17:05 ` Clem Cole
2019-07-11 19:39 ` Charles H Sauer
2019-07-12 0:14 ` Clem Cole
2019-07-11 16:50 ` A. P. Garcia
2019-07-11 16:54 ` Clem Cole
2019-07-12 3:44 ` Michael Parson
2019-07-17 7:37 ` [TUHS] Old 386 Unix Versions, was: " emanuel stiebler
2019-07-17 8:10 ` arnold
2019-07-17 9:28 ` Arrigo Triulzi
2019-07-17 10:09 ` Jason Stevens
2019-07-17 10:42 ` emanuel stiebler
2019-07-17 15:40 ` Adam Thornton
2019-07-17 18:01 ` Clem Cole
2019-07-17 12:32 ` Ben Greenfield via TUHS
2019-07-17 12:50 ` Dagobert Michelsen
2019-07-17 13:38 ` Arrigo Triulzi
2019-07-17 14:41 ` Clem Cole
2019-07-17 15:08 ` Ben Greenfield via TUHS
2019-07-17 21:09 ` Dagobert Michelsen
2019-07-18 8:56 ` Arrigo Triulzi
2019-07-17 16:04 ` William Pechter
2019-07-17 14:34 ` Clem Cole
2019-07-17 23:22 ` Bakul Shah
2019-07-18 0:04 ` Clem cole
2019-07-17 22:48 ` Chris Hanson
2019-07-18 8:39 ` Wesley Parish
2019-07-17 14:15 ` Clem Cole
2019-07-17 15:11 ` Larry McVoy
2019-07-17 15:31 ` Warner Losh
2019-07-17 15:36 ` Jason Stevens
2019-07-17 16:56 ` Larry McVoy
2019-07-24 1:04 ` Lyndon Nerenberg
2019-07-24 1:30 ` Arthur Krewat
2019-07-24 21:53 ` Kevin Bowling
2019-07-25 19:16 ` Lyndon Nerenberg
2019-07-25 19:29 ` [TUHS] AT&T 3b4000 (was Re: Old 386 Unix Versions) Kevin Bowling
2019-07-25 20:47 ` Clem Cole
2019-07-26 18:18 ` Seth J. Morabito [this message]
2019-07-26 19:24 ` Clem Cole
2019-07-18 0:04 ` [TUHS] BSD/386 (was: Old 386 Unix Versions, was: Re: PCC for the i386) Greg 'groggy' Lehey
2019-07-18 0:16 ` Richard Salz
2019-07-18 1:08 ` Greg 'groggy' Lehey
2019-07-18 15:01 ` Chet Ramey
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=87muh0zmld.fsf@loomcom.com \
--to=web@loomcom.com \
--cc=tuhs@minnie.tuhs.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).