Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!news.cs.indiana.edu!news.nd.edu!mentor.cc.purdue.edu!purdue!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.m68k
Subject: Re: Need 68030 SYSV Box
Message-ID: <1991Feb9.203813.11394@ni.umd.edu>
Date: 9 Feb 91 20:38:13 GMT
References: <1991Feb6.182148.14806@demott.com> <1646@peritek.UUCP> <1991Feb8.153145.22870@letni.lonestar.org>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 15

>>Actually, all UNIX systems that I have ever dealt with (from Version 6 through
>>SVR3 and 4.3BSD) have put pipes on disk, usually in the root filesystem.  This
>>is a standard UNIXism.  If this is not acceptable for your environment, you can
>>(a) buy SVR4 source and rewrite the pipe code,


>Bzzzzzt BING!   In SVR4 Pipes are stream based. Also a couple of SVR3's
>implmented pipes via streams as well.

Bzzzzt BING! (again).  Certainly in 4.3BSD, and probably in 4.2BSD pipes 
were implemented in the kernel using the socket abstraction with in-memory
socket buffers.  In fact, it was very similar to socketpair() in the
underlying implementation.

louie