From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] [TUHS} communication files: interprocess IO before pipes
Date: Sun, 05 Mar 2017 22:50:22 -0500 [thread overview]
Message-ID: <201703060350.v263oM7u024080@coolidge.cs.Dartmouth.EDU> (raw)
It's not really Unix history, but Dartmouth's "communication files"
have so often been cited as pipes before Unix, that you may like
to know what this fascinating facility actually was. See
http://www.cs.dartmouth.edu/~doug/DTSS/commfiles.pdf
next reply other threads:[~2017-03-06 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 3:50 Doug McIlroy [this message]
2017-03-06 8:05 ` arnold
2017-03-06 15:34 ` 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=201703060350.v263oM7u024080@coolidge.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
/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).