Path: utzoo!utgpu!watmath!clyde!att!rutgers!bellcore!texbell!uhnix1!sugar!peter
From: peter@sugar.uu.net (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Devices in general
Message-ID: <3061@sugar.uu.net>
Date: 6 Dec 88 12:26:58 GMT
References: <5816@louie.udel.EDU>
Organization: Sugar Land Unix - Houston, TX
Lines: 31

In article <5816@louie.udel.EDU>, gay%elde.epfl.ch@cunyvm.cuny.edu (David Gay) writes:
> In article <3046@sugar.uu.net>, peter@sugar.uu.net (Peter da Silva) writes:
> >In article <1086@teorix.liu.se>, dat01@teorix.liu.se (Dat) writes:
> >> What I would like to do is use the devices as some kind of pipes.

> >Better would be some real pipes and better tools...

> >I want a good korn shell for the Amiga. csh is a crummy programming language.

> >>    saveas CRYPT:ZOO:MSDOS:file

> >crypt file | zoo create MSDOS:file.zoo input "file"

> Yes, but you can't do this from your favourite editor(or whatever) ...

Then what you want is another device I dreamed up, "CLI:". The theory
here would be "CLI:command" would open a pipe to command and pass back the
file handle... sort of the equivalent of the UNIX 'popen'.

[ I lamented the unfortunate state of the AmigaDOS PIPE: devices ]

> You can always use WShell (for the pipes).

Unfortunately too many commands (zoo, for example) are written by pc-brain
bozos who don't understand the concept of a 'filter'. The WShell pipe
device won't help with Zoo because it's got no name.
-- 
		    Peter da Silva  `-_-'  peter@sugar.uu.net
		     Have you hugged  U  your wolf today?

	          Disclaimer: My typos are my own damn busines#!rne