Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!husc6!think!ames!ucbcad!ucbvax!jade!eris!mwm From: mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer) Newsgroups: comp.sys.amiga Subject: Re: MCC pipes Message-ID: <3872@jade.BERKELEY.EDU> Date: Fri, 5-Jun-87 20:03:41 EDT Article-I.D.: jade.3872 Posted: Fri Jun 5 20:03:41 1987 Date-Received: Wed, 10-Jun-87 03:34:46 EDT References: <1174@crash.CTS.COM> <279@louie.udel.EDU> Sender: usenet@jade.BERKELEY.EDU Reply-To: mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer) Organization: Missionaria Phonibalonica Lines: 27 Keywords: uw pipes interlace egad gaded In article <279@louie.udel.EDU> rminnich@udel.EDU (Ron Minnich) writes: <6. Do MCC pipes work as named pipes (a la sys V), or just the < equivalent of the unix '|'? Uh, MCC pipes (and also Matt's pipe device, which is PD) are more than the "|". They put pipes in the file system name space, where you can use the for magic. To wit: run edit from ram:input to pipe:edit-tmp with s:edit-script run edit from ram:control to pipe:control-tmp with s:edit-control edit from pipe:edit-tmp to ram:output with pipe:edit-control Pipe:file is a pipe. Such things run an order of magniude faster than going through ram:. I *think* that's what SysV pipes do, but the closest I can come to a SysV box is Unicos, which was based on SysV before there was a relase number, and has been severely hacked upon. Someone wanna tell me what named pipes really do? Thanx,