The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Interesting commentary on Unix from Multicians.
Date: Fri, 8 Apr 2022 10:14:05 -0400	[thread overview]
Message-ID: <CAEoi9W7hUrR-fmgbQMx7Gmjb0h=pkG8QuLvtdR4KSSfGCtCtUA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P3Jn9WOC3pkwm-RP8FN+=ZS9OdYrbC48pB2+S5SbuPiw@mail.gmail.com>

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

On Fri, Apr 8, 2022 at 9:34 AM Clem Cole <clemc@ccc.com> wrote:

> On Fri, Apr 8, 2022 at 1:33 AM Lars Brinkhoff <lars@nocrew.org> wrote:
>
>> Multics was started in 1964 and first went online in 1967, although it
>> seems likely it wasn't exactly at the top of its game yet.  Bell Labs
>> pulled out in 1969.  If that was the 75% point, 100% would be around
>> 1971.
>>
> Not to put too fine a point on it, It seems like it would be fair to say
> Multics was 'complete' by the time Organick published his book: *"**The
> Multics System: An Examination of Its Structure**.*" Amazon says the 3rd
> printing was April 72, so that means he must have published it earlier.  I
> don't know when it first appeared and can not seem to find it.  My copy
> is in storage but I bet I have the 3rd printing.   But I had >>thought<<
> that was still in the late 1960s.   Anyone have a first edition around
> with the publication date?ᐧ
>

I have a scanned copy of Organick from MIT that says Copyright 1972 (and
has a stamp from the Barker Engineering Library listing May 16, 1972 as the
acquisition date).  I can't see any indication that this is anything other
than the first printing. Corbato's forward is dated Dec 13, 1971.

However, Organick's book is often said to describe an earlier version of
the system, up to somewhere in the vicinity of 1968/1970 (
https://multicians.org/history.html, also message to the old Multicians
list at Yahoo! I'm not sure about the archives of that, so don't have a
link). I understand that Multics got much better after the move to the 6180
and DPS8/M; Organick's book describes GE 645 Multics only.

        - Dan C.

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

  reply	other threads:[~2022-04-08 14:17 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 [this message]
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
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='CAEoi9W7hUrR-fmgbQMx7Gmjb0h=pkG8QuLvtdR4KSSfGCtCtUA@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=clemc@ccc.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).