The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] First appearance of named pipes
Date: Fri, 6 Mar 2020 16:06:02 -0500	[thread overview]
Message-ID: <CAC20D2NRAdcG0OYUAibMohrMYvK5Td276ECy4SwMhw+don=oxA@mail.gmail.com> (raw)
In-Reply-To: <8A3F3334-D8C0-4075-B21B-FEAD709C086D@planet.nl>

[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]

The first version was from Rand (called "Rand Pipes").   They
certainly were available in the mid-70s on Sixth Edition, you have to ask
someone like Bruce Borden if they were on Fifth.  I think the code is on
one of the 'USENIX' tapes in Warren's archives.

At this point in time, someone would need to refresh my memory of the
details of Rand's implementation compared to what came in the USG systems
in the 1980s.   For instance, I believe the early versions used mknod(2) to
create the "named entity."   IIRC early USG did that too, and mkfifo(3)
came as part of the POSIX (I have memories of the discussion at a POSIX
meeting, but as I say, I've forgotten the details).

IIRC there were differences in buffering behavior, flushing, error path
between USG's later versions and the original Rand, but I'd have to stare
at the code again to remember.

On Fri, Mar 6, 2020 at 3:42 PM Paul Ruizendaal <pnr@planet.nl> wrote:

> 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
>
>

[-- Attachment #2: Type: text/html, Size: 2301 bytes --]

  reply	other threads:[~2020-03-06 21:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-06 20:41 Paul Ruizendaal
2020-03-06 21:06 ` Clem Cole [this message]
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='CAC20D2NRAdcG0OYUAibMohrMYvK5Td276ECy4SwMhw+don=oxA@mail.gmail.com' \
    --to=clemc@ccc.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).