From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] First appearance of named pipes
Date: Fri, 6 Mar 2020 21:41:57 +0100 [thread overview]
Message-ID: <8A3F3334-D8C0-4075-B21B-FEAD709C086D@planet.nl> (raw)
The Luderer paper on distributed Unix has the following paragraph:
"A new special UNIX interprocess communication mechanism is the fifo, which provides communication between unrelated processes by associating a new special file type with a file name. Since remote fifos are legal, they can be used for interprocessor communication between S-UNIX machines or between an S-UNIX machine and an F-UNIX machine.”
The paper is from late 1981. Maybe I’m especially mud-eyed today, but I cannot see FIFO’s implemented in V7..V8 or 4.1xBSD. When did FIFO’s become a standard Unix feature?
Paul
next reply other threads:[~2020-03-06 20:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 20:41 Paul Ruizendaal [this message]
2020-03-06 21:06 ` Clem Cole
2020-03-06 21:10 ` Clem Cole
2020-03-07 5:08 ` Heinz Lycklama
2020-03-06 22:44 Noel Chiappa
2020-03-07 12:17 ` Paul Ruizendaal
2020-03-07 13:29 ` Clem Cole
2020-03-07 16:39 ` Derek Fawcus
2020-03-08 2:36 ` Rob Pike
2020-03-08 2:47 ` Larry McVoy
2020-03-08 13:07 ` Ralph Corderoy
2020-03-08 13:25 ` arnold
2020-03-08 3:06 ` Dave Horsfall
2020-03-08 7:16 ` arnold
2020-03-09 23:22 ` Grant Taylor via TUHS
2020-03-10 7:29 ` arnold
2020-03-11 2:47 ` Grant Taylor via TUHS
2020-03-11 7:02 ` arnold
2020-03-10 13:49 ` Chet Ramey
2020-03-10 20:26 ` Dave Horsfall
2020-03-10 20:37 ` Chet Ramey
2020-03-11 2:51 ` Grant Taylor via TUHS
2020-03-08 21:42 Paul Ruizendaal
2020-03-08 22:04 ` 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=8A3F3334-D8C0-4075-B21B-FEAD709C086D@planet.nl \
--to=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).