The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jon Steinhart <jon@fourwinds.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Interesting commentary on Unix from Multicians.
Date: Fri, 08 Apr 2022 08:45:28 -0700	[thread overview]
Message-ID: <202204081545.238FjSGv3781664@darkstar.fourwinds.com> (raw)
In-Reply-To: <CAEoi9W5DCi=FZsMCqm9tZdtFvRBfcT7SZbFWukfTJ8p8dkc=CQ@mail.gmail.com>

Dan Cross writes:
> Bell Labs dropping out of Multics in 1969 was, of course, before Unix. This
> raises the question, what did Bell Labs use instead? I imagine 360s and
> either traditional batch processing or TSS or something?

Someone who was older than me at the time like Heinz probably knows more
than I do.  My recollection is that many departments had their own random
systems as minicomputers took over.  We used 516-TSS on a Honeywell DDP-516/
I have no idea what Max Matthews ran on his DDP-224 but would guess that it
was all custom stuff.  I believe that the behemoth GE-635 aka Honeywell 6070
in the computer center ran GECOS.  I don't know if that machine was originally
there for the MULTICS project.

  parent reply	other threads:[~2022-04-08 15:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 16:32 Dan Cross
2022-04-08  5:30 ` Lars Brinkhoff
2022-04-08 13:34   ` Clem Cole
2022-04-08 14:14     ` Dan Cross
2022-04-08 13:59   ` Dan Cross
2022-04-08 15:28     ` Larry McVoy
2022-04-08 15:35       ` Dan Cross
2022-04-08 19:36       ` Rich Morin
2022-04-08 21:02       ` Greg A. Woods
2022-04-08 23:34         ` Andrew Warkentin
2022-04-09 19:28           ` Greg A. Woods
2022-04-09  3:33         ` Adam Thornton
2022-04-09 12:10         ` tytso
2022-04-09 13:09           ` Dan Cross
2022-04-09 19:14           ` Greg A. Woods
2022-04-08 15:45     ` Jon Steinhart [this message]
2022-04-08 16:07 Noel Chiappa
2022-04-10 17:14 Noel Chiappa
2022-04-10 17:31 ` Larry McVoy
2022-04-10 20:41 ` John Cowan

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=202204081545.238FjSGv3781664@darkstar.fourwinds.com \
    --to=jon@fourwinds.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).