From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Interesting commentary on Unix from Multicians.
Date: Fri, 8 Apr 2022 12:07:34 -0400 (EDT) [thread overview]
Message-ID: <20220408160734.380DB18C0A8@mercury.lcs.mit.edu> (raw)
> From: Clem Cole
> 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
This is a pretty ill-judged claim, IMO - but not for any particulars about
the Organick book, etc. The problem is more global.
When was UNIX 'complete' - when the first people were able to do real work on
the PDP-7? When non-programmer clerks from the patent group were able to use
the assembler UNIX on the PDP-11 to format parent documents? When it was
re-written in C for the 4th Edition (since the _portability_ of UNIX was IMO
perhaps the greatest factor in its eventual domination)? Etc, etc, etc.
The exact same problem applies to the question of 'when was Multics
'complete''.
> don't know when it first appeared and can not seem to find it. ... I
> bet I have the 3rd printing. ... Anyone have a first edition around
> with the publication date?
The third printing _is_ the first edition. Anyway, it doesn't matter - see
above. And of course even if the book _wriring_ was finished at time T, it
wouldn't have been printed until some unknown time later. So that's really
pretty useless as a temporal marker; we have much better ones availablw.
> From: Dan Cross
> I can't see any indication that this is anything other than the first
> printing.
My 3rd printing says 3rd was 1980, 2nd in 1976, and copyright 1972.
> Organick's book is often said to describe an earlier version of the
> system
Yes; I'm not sure if the version described in it was ever available for
general usege (which could be my definition of 'complete') - or even usage my
Multics system programmers. I don't remember all the details of the
differences (it's been way too long since I read it, and I don't know the
details of the 'first operational' Multics well enough), but for instance:
ISTR that it describes a version which had a linkage segment (holding
intermediate locations in outbound links - since segment >a>b>c might well
have different segment numbers assigned to it in the address spaces of
processes X and Y, so one copy of >a>b>c, shared between X and Y, couldn't
contain direct outbound links) _per segment_ (data or code) - but operational
Multics (I don't know if this is from 'first available to users', or 'first
available to Multics system programmers', or what) collapsed all the linkage
info into a 'combined linkage segment', in which the linkage info from all
the segments in a process' address space were combined (by copying) into a
single linkage segment.
Etc, etc, etc.
> I understand that Multics got much better after the move to the 6180
I'm not sure that the 6180 made that big a difference to the environment the
average use saw. My understanding (not having been there) was that the big
_architectural_ difference was that cross-ring inter-segment references were
done and monitored in hardware, so a host of security holes caused by
insufficient checking of cross-ring inter-segment pointers were caught
automatically. (The 6180 was also built out of SSI chips, unlike the 645 which
was individual transistors, like a KA10.)
Noel
next reply other threads:[~2022-04-08 16:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 16:07 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-10 17:14 Noel Chiappa
2022-04-10 17:31 ` Larry McVoy
2022-04-10 20:41 ` John Cowan
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
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=20220408160734.380DB18C0A8@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).