The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Norman Wilson <norman@oclsc.org>
To: tuhs@tuhs.org
Subject: [TUHS]  Research UNIX on the AT&T 3B2?
Date: Sun, 26 Aug 2018 09:09:42 -0400	[thread overview]
Message-ID: <1535288985.3793.for-standards-violators@oclsc.org> (raw)

Seth Morabito:

  After the past several years of focusing on 3B2 preservation and
  emulation, I've begun to wonder whether 3B2 hardware was used very much
  inside of Bell Labs. Has anyone ever heard whether Research UNIX was
  ever ported to the WE32100? I've certainly never seen anything that
  would suggest it was, but I'd love to be proven wrong.

=====

I never heard of anyone doing such a thing.  Had they ported
the kernel I would almost certainly have heard about it, because
they'd have asked me a question or two.  Much VAX-specific
structure inside there that I'd love to have had the time and
energy to clean up.

It's possible that someone did a semi-port, moving a lot of
the user-mode tools like the shell and the Jerq software.
Dave Kapilow did something like that for early SunOS, including
a mux-like X11 terminal program called sux, built atop a
library that did a simple mapping from Jerq graphics-library
calls to X11.

Certainly nobody inside 1127 ever did either of those things.
A few of us played with 3B1 or 3B2 systems (I remember Tom
Duff had a 3B1 at home at one point), but never very seriously.

Norman Wilson
Toronto ON

             reply	other threads:[~2018-08-26 13:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-26 13:09 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-08-24 15:13 Seth Morabito
2018-08-24 15:23 ` William Cheswick
2018-08-24 16:06 ` Clem Cole
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  1:06                 ` Dave Horsfall
2018-08-29  3:23                   ` Theodore Y. Ts'o
2018-08-29  5:06                     ` 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

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=1535288985.3793.for-standards-violators@oclsc.org \
    --to=norman@oclsc.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).