summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorpeter <peter@FreeBSD.org>1996-04-03 04:57:27 +0000
committerpeter <peter@FreeBSD.org>1996-04-03 04:57:27 +0000
commit14009d1ae054998506dbe2ac7d4b3b8d471e0df0 (patch)
treedfdf961943491da65bf265a28e3e66768afe74ff
parentd0c71521cd29101e1d4196e03b1161d0cd34c096 (diff)
downloadFreeBSD-src-14009d1ae054998506dbe2ac7d4b3b8d471e0df0.zip
FreeBSD-src-14009d1ae054998506dbe2ac7d4b3b8d471e0df0.tar.gz
Remove outdated (and never quite correct anyway) reference to the
"fact" that pipes were implemented as calls to socketpair().
-rw-r--r--lib/libc/sys/pipe.24
1 files changed, 0 insertions, 4 deletions
diff --git a/lib/libc/sys/pipe.2 b/lib/libc/sys/pipe.2
index b05eeb2..763cc2f 100644
--- a/lib/libc/sys/pipe.2
+++ b/lib/libc/sys/pipe.2
@@ -80,10 +80,6 @@ Widowing a pipe is the only way to deliver end-of-file to a reader:
after the reader consumes any buffered data, reading a widowed pipe
returns a zero count.
.Pp
-Pipes are really a special case of the
-.Xr socketpair 2
-call and, in fact, are implemented as such in the system.
-.Pp
The bidirectional nature of this implementation of pipes is not
portable to older systems, so it is recommended to use the convention
for using the endpoints in the traditional manner when using a
OpenPOWER on IntegriCloud