The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Jeffrey H. Johnson" <trnsz@pobox.com>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Public access multics
Date: Sat, 1 Sep 2018 23:17:02 -0400	[thread overview]
Message-ID: <EE36B4F0-6DE1-4B26-B30F-527DCA69C823@pobox.com> (raw)
In-Reply-To: <5B48F6A3-374A-4579-AE8F-35BD328D07F9@reagan.com>

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

Greetings,

Multics, while not a 'massive' sales success in retrospect, was certainly not the failure commonly believed and wasn't treated as one in the press of the time - at least not until after the decision was made by Honeywell-Bull to phase out the the Multics (and CP-6) products to focus on GCOS - GCOS7/GCOS8 is still a major player today.

"Honeywell is having considerable — and surprising — success with the ultra-secure Multics operating system … Besides 3-5 systems within Honeywell, Multics has been installed or committed within Nippon Electric, Rome Air Development Center, USAF Data Services Center, and Ford." from mid-1970's industry press.

See also https://multicians.org/myths.html

We have about 120 members on BAN - including many original and new Multicians who make the project possible. We're always working on new things and projects - see "pmotd -a" when logged in for some of the most recent activity.

I'd be happy to answer any questions on BAN.AI if anyone has particular questions - or just ssh to dps8@m.trnsz.com - feel free to use the guest account. I don't want to take the list too off-topic. We have many exclusive features that I hope makes BAN.AI a 'special' (and loved) system, a lot more coming.


--
https://ban.ai/multics

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

       reply	other threads:[~2018-09-02  3:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5B48F6A3-374A-4579-AE8F-35BD328D07F9@reagan.com>
2018-09-02  3:17 ` Jeffrey H. Johnson [this message]
2018-09-03 13:29 Doug McIlroy
2018-09-03 23:41 ` Dave Horsfall
2018-09-04  2:47   ` Jeffrey H. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2018-09-02 21:47 Doug McIlroy
2018-09-03  6:18 ` arnold
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=EE36B4F0-6DE1-4B26-B30F-527DCA69C823@pobox.com \
    --to=trnsz@pobox.com \
    --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).