From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] [TUHS} communication files: interprocess IO before pipes
Date: Mon, 6 Mar 2017 07:34:53 -0800 [thread overview]
Message-ID: <20170306153453.GL16343@mcvoy.com> (raw)
In-Reply-To: <201703060350.v263oM7u024080@coolidge.cs.Dartmouth.EDU>
On Sun, Mar 05, 2017 at 10:50:22PM -0500, Doug McIlroy wrote:
> 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
If I'm understanding correctly, an I/O on the slave side would cause
an event on the master side. So the master was almost like a debugger
with break points at open/read/write/lseek/close?
That would explain a lot of the complexity. And if the slave does a
read(comm, buf, 1<<20) I suspect that the master does multiple writes?
As in is there a PIPEBUF analogy?
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
prev parent reply other threads:[~2017-03-06 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 3:50 Doug McIlroy
2017-03-06 8:05 ` arnold
2017-03-06 15:34 ` Larry McVoy [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=20170306153453.GL16343@mcvoy.com \
--to=lm@mcvoy.com \
/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).