From: "Jeffrey H. Johnson" <trnsz@pobox.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Public access multics
Date: Mon, 3 Sep 2018 22:47:46 -0400 [thread overview]
Message-ID: <AC815801-DD2A-4933-8C24-3081CFA21156@pobox.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1809040937410.28912@aneurin.horsfall.org>
[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]
Yes, correct - I don't want to bring the list too off-topic, but Unisys (UNIVAC + Burroughs) still maintains those two platforms (OS 2000 from the UNIVAC line and MCP from Burroughs), and they have a hobbyist program for both systems.
https://www.unisys.com/offerings/clearpath-forward/clearpath-forward-products/clearpath-os-2200-software/clearpath-os-2200-express
and
https://www.unisys.com/offerings/clearpath-forward/clearpath-forward-products/clearpath-mcp-software/clearpath-mcp-express
Unisys has also released older versions of MCP (1970s) as well with less restrictive licensing, and the community has built an emulator capable of running them on an emulated B5500 system - http://www.phkimpel.us/B5500/
The Burroughs MCP name supposedly inspired the MCP villain in TRON as well.
I've never used Burroughs Algol nor Honeywell Algol, but I am aware you can use Honeywell Algol on Multics via gcos_tss (the GCOS Time Sharing Simulator).
-- Jeff
> On Sep 3, 2018, at 7:41 PM, Dave Horsfall <dave@horsfall.org> wrote:
>
> On Mon, 3 Sep 2018, Doug McIlroy wrote:
>
>>> Was Algol 60 any kind of viable alternative at the time?
>>
>> The operating system for the Burroughs B5000 had been written in Burroughs Algol. That punctured the widespread belief that OS's were so particular to the hardware that they had to be written in machine language. I don't recall how far Burroughs Algol went beyond Algol 60, nor why Multics did not want to follow that lead. ("Viable" is a slippery concept when choosing among Turing-complete alternatives.)
>
> Call me memory-challenged (which I am these days), but wasn't Burroughs' OS known as Master Control Program (MCP - Male Chauvinist Pig)?
>
> -- Dave, who has fond memories of the B1500...
[-- Attachment #2: Type: text/html, Size: 2777 bytes --]
next prev parent reply other threads:[~2018-09-04 2:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 13:29 Doug McIlroy
2018-09-03 23:41 ` Dave Horsfall
2018-09-04 2:47 ` Jeffrey H. Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-02 21:47 Doug McIlroy
2018-09-03 6:18 ` arnold
[not found] <5B48F6A3-374A-4579-AE8F-35BD328D07F9@reagan.com>
2018-09-02 3:17 ` Jeffrey H. Johnson
2018-09-01 23:33 Noel Chiappa
2018-09-01 23:44 ` jcs
2018-09-01 23:25 [TUHS] Fwd: " Noel Chiappa
2018-09-02 4:05 ` Will Senn
2018-09-02 4:25 ` [TUHS] " Jeffrey H. Johnson
2018-09-02 22:30 ` Will Senn
2018-09-01 20:31 Will Senn
2018-09-01 21:27 ` jcs
2018-09-01 23:24 ` John P. Linderman
2018-09-02 13:06 ` Dave Horsfall
2018-09-02 16:23 ` Charles Anthony
2018-09-02 18:18 ` Paul Winalski
2018-09-02 19:09 ` Paul Winalski
2018-09-02 0:57 ` Dan Cross
2018-09-02 2:06 ` Grant Taylor via TUHS
2018-09-02 2:32 ` Charles Anthony
2018-09-02 2:52 ` Larry McVoy
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=AC815801-DD2A-4933-8C24-3081CFA21156@pobox.com \
--to=trnsz@pobox.com \
--cc=dave@horsfall.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).