From: Tony Finch <dot@dotat.at>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] sockets (was Re: First appearance of named pipes)
Date: Mon, 9 Mar 2020 17:09:02 +0000 [thread overview]
Message-ID: <alpine.DEB.2.20.2003091627290.24181@grey.csi.cam.ac.uk> (raw)
In-Reply-To: <1583708946.8301.for-standards-violators@oclsc.org>
Norman Wilson <norman@oclsc.org> wrote:
>
> I wish POSIX and Linux and the BSDs would catch up; that
> was only 30 years ago.
After sockets were added to BSD, pipe() was implemented using them. But it
was a slightly different implementation than socketpair().
e.g.
https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_syscalls.c
and the amusing comment at the top of
https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/src/sys/sys/uipc_pipe.c
But the socket-backed pipes weren't bidirectional even though they could
have been - see this fix in FreeBSD
https://svnweb.freebsd.org/base/head/sys/kern/uipc_syscalls.c?r1=12843&r2=13146
Which did not last long because socket-backed pipe were soon replaced
with a new (bidirectional) implementation
https://svnweb.freebsd.org/base/head/sys/kern/sys_pipe.c?view=log&log_pagestart=200#rev13675
Tony.
--
f.anthony.n.finch <dot@dotat.at> http://dotat.at/
Ardnamurchan Point to Cape Wrath: South or southwest 4 or 5, increasing 6 to
gale 8, then veering west later. Rough or very rough, occasionally high in
west. Rain or drizzle, then showers. Moderate or good, occasionally poor at
first.
next prev parent reply other threads:[~2020-03-09 17:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 23:09 Norman Wilson
2020-03-09 17:09 ` Tony Finch [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-06 22:44 [TUHS] First appearance of named pipes Noel Chiappa
2020-03-07 12:17 ` Paul Ruizendaal
2020-03-07 16:39 ` Derek Fawcus
2020-03-08 2:36 ` Rob Pike
2020-03-08 15:13 ` [TUHS] sockets (was Re: First appearance of named pipes) Derek Fawcus
2020-03-09 23:22 ` Grant Taylor via TUHS
2020-03-09 23:44 ` Larry McVoy
2020-03-23 8:49 ` Peter Pentchev
2020-03-24 9:47 ` Derek Fawcus
2020-03-25 23:25 ` Grant Taylor via TUHS
2020-03-25 23:47 ` Richard Salz
2020-03-26 0:11 ` Grant Taylor via TUHS
2020-03-26 0:18 ` Richard Salz
2020-03-26 1:08 ` Grant Taylor via TUHS
2020-03-26 2:38 ` Dave Horsfall
2020-03-26 3:08 ` Rob Pike
2020-03-26 3:43 ` George Michaelson
2020-03-26 4:11 ` Grant Taylor via TUHS
2020-03-28 11:12 ` Peter Pentchev
2020-03-28 11:14 ` Peter Pentchev
2020-03-28 16:03 ` Steffen Nurpmeso
2020-03-26 1:20 ` Tony Finch
2020-03-27 10:51 ` Derek Fawcus
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=alpine.DEB.2.20.2003091627290.24181@grey.csi.cam.ac.uk \
--to=dot@dotat.at \
--cc=norman@oclsc.org \
--cc=tuhs@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).