From: Rich Morin <rdm@cfcl.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Cc: Paul Ruizendaal <pnr@planet.nl>
Subject: [TUHS] CSRG report TR/3 (IPC Architecture)
Date: Sun, 19 Jan 2020 09:40:35 -0800 [thread overview]
Message-ID: <E0AB8AEB-7418-45CB-8202-236409E1FA00@cfcl.com> (raw)
In-Reply-To: <DFC407A8-397F-4074-AFF5-D7DC053B5AC7@planet.nl>
I think the following may have been missed, because folks thought it was more
discussion about the CSRG TR/4. Read on...
> On Jan 18, 2020, at 01:08, Paul Ruizendaal <pnr@planet.nl> wrote:
>
> At the bottom of page 6 TR/4 references TR/3:
>
> A more complete description of the motivation of the IPC architecture
> described here, measurements of a prototype implementation, comparisons
> with other work and a complete bibliography are given in CSRG TR/3: “An IPC
> Architecture for UNIX”.
This was also in the box: about 50 pages, including a four-page bibliography.
An Architecture for Interprocess Communication in UNIX*
-- DRAFT of June 22, 1981 --
William Joy and Robert Fabry
Paul sez:
> Before yesterday I did not know that TR/3 existed and in my (arguable) view
> it is even a bigger find than TR/4, as it gives great insight how design
> trade-offs were perceived back in 1981.
Again, I scanned the paper and then Paul aggregated the scans into a single PDF.
It should be available here:
http://cfcl.com/private/CSRG_TR_3.pdf
-r
prev parent reply other threads:[~2020-01-19 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 0:32 [TUHS] CSRG report TR/4 was in Jim Joyce papers Paul Ruizendaal
2020-01-18 0:36 ` Warner Losh
2020-01-18 0:50 ` Rich Morin
2020-01-18 1:14 ` Clem Cole
2020-01-18 9:01 ` Thomas Paulsen
2020-01-18 19:25 ` Rich Morin
2020-01-18 21:38 ` reed
2020-01-18 22:35 ` Warner Losh
2020-01-18 23:22 ` Rich Morin
2020-01-19 17:40 ` Rich Morin [this message]
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=E0AB8AEB-7418-45CB-8202-236409E1FA00@cfcl.com \
--to=rdm@cfcl.com \
--cc=pnr@planet.nl \
--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).