Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!cit-vax!news
From: news@cit-vax.Caltech.Edu (Usenet netnews)
Newsgroups: comp.sys.amiga
Subject: Re: PIPES (was Shell scripts on AmigaDOS & Unix)
Message-ID: <1550@cit-vax.Caltech.Edu>
Date: Wed, 21-Jan-87 15:07:17 EST
Article-I.D.: cit-vax.1550
Posted: Wed Jan 21 15:07:17 1987
Date-Received: Thu, 22-Jan-87 00:34:47 EST
References: <2228@jade.BERKELEY.EDU> <1987Jan19.022653.20521@utcs.uucp> <2259@jade.BERKELEY.EDU> <2023@tekgvs.UUCP>
Reply-To: tim@tomcat.caltech.edu (Tim Kay)
Organization: California Institute of Technology
Lines: 28

Organization : California Institute of Technology
Keywords: 
From: tim@tomcat.Caltech.Edu (Tim Kay)
Path: tomcat!tim

In article <2023@tekgvs.UUCP> keithe@tekgvs.UUCP (Keith Ericson) writes:
>Guess what.  You can use "pipes" on the Amiga to pipe the output of one
>process to the input of another.
>
>4) All of this will work faster if you run it out of RAM:.
>     7	  execute PIPE "{c1} > RAM:PIPE$$$" ...
>    18	      execute PIPE "{c1}" "{c3} < RAM:PIPE$$$" ...
>    54	  delete RAM:PIPE$$$

Even MS-DOS gives you this much.  Under Unix, a pipe is different.  The
source program is automatically blocked when the pipe buffer is full,
and the destination program is allowed to run.  When the pipe buffer is
empty, the destination program is blocked, and the source program is
resumed.  The advantage is that you only need enough memory for the
buffer, not for the entire source program's output.

Somebody made mention of a pipe device.  Does it do effectively what Unix
does?  Or does it just save all the source's output as above?

Timothy L. Kay				tim@csvax.caltech.edu
Department of Computer Science
Caltech, 256-80
Pasadena, CA  91125