[comp.os.minix] Clam alias pipe glitch?

dfenyes@thesis1.hsch.utexas.edu (FENYES DAVID A) (09/27/90)

Hello,

This is addressed to Minixers with the Clam Shell--
I have patched the Shell on my own computer to run under the Coherent
operating system, and find it to be an excellent shell.  However, I
found one bug, and since the shell has been on Minix for a while, someone
may have a patch for it.  The bug is that Clam doesn't like to pipe a stream
through an alias.  Do you have it, too?  Try:

	% ls | cat			/* it works. */

Try:
	% echo cat > c
	% ls | c		  		/* it works, */

Try:
	% alias c cat
	% ls | c				/* it bombs */

Try:
	% ls | c | sort	/* it may work, but you get ENOTTY errors
	             		   from ioctl() in runalias */

I believe that runalias does something funky with the ioctl calls, since
the expanded code is not run the same way as a non-alias.  I don't believe
these calls should be getting made anyway, for piped io.  These are terminal
related calls.

I found that a Clam compiled under HPUX with -DATT with and without 
-DHASH -DSCRIPT behaves identically to my Coherent version of Clam.
Has anyone noticed and patched this?  I have emailed the author, but have
gotten no response.  The shell, by the way, is excellent to use, and I
found myself preferring it to /bin/sh even before I had the port debugged.
By the way, Coherent doesn't stink.  It's OK, really.  Minix and Coherent
users should keep a line of communication open, since were working with
similar resources. (Except we don't have the source code)

Thanks, folks --

David Fenyes 				dfenyes@thesis1.hsch.utexas.edu

wkt@csadfa.cs.adfa.oz.au (Warren Toomey,,,) (09/27/90)

From article <31654@nigel.ee.udel.edu>, by (FENYES DAVID A):

> This is addressed to Minixers with the Clam Shell--
> The bug is that Clam doesn't like to pipe a stream through an alias.
> 
> I found that a Clam compiled under HPUX with -DATT with and without 
> -DHASH -DSCRIPT behaves identically to my Coherent version of Clam.
> Has anyone noticed and patched this?

Yes, this is a very well-known bug (feature?) of Clam. However, if you
do
	% alias ls 'ls -l'
	% ls > file &
it works. The same goes for pipes (I think).

If anybody has any ideas on this bug, PLEASE PLEASE email me! I've been
trying to figure this out for nearly a year now, and have given up
twice.

*******
BTW, the author, Callum Gibson, currently does not have an email address.

I am the custodian of the source, and can be reached at
	wkt@csadfa.cs.adfa.oz.au
*******

Mind you, I can only help with the code - I didn't write it.

> Minix and Coherent users should keep a line of communication open,
> since were working with similar resources. (Except we don't have
> the source code)

Agreed!

> The shell, by the way, is excellent to use, and I
> found myself preferring it to /bin/sh even before I had the port debugged.

And I still can't believe the number of people out there still using sh!

P.S Now working on an Ansified version, pity the acc runs out of stack :-(

Cheers,
	Warren Toomey	wkt@csadfa.cs.adfa.oz.au

wkt@ccadfa.adfa.oz.au (Warren Toomey) (09/27/90)

		[sorry if this is a duplicate]

From article <31654@nigel.ee.udel.edu>, by (FENYES DAVID A):

> This is addressed to Minixers with the Clam Shell--
> The bug is that Clam doesn't like to pipe a stream through an alias.
> 
> I found that a Clam compiled under HPUX with -DATT with and without 
> -DHASH -DSCRIPT behaves identically to my Coherent version of Clam.
> Has anyone noticed and patched this?

Yes, this is a very well-known bug (feature?) of Clam. However, if you
do
        % alias ls 'ls -l'
        % ls > file &
it works. The same goes for pipes (I think).

If anybody has any ideas on this bug, PLEASE PLEASE email me! I've been
trying to figure this out for nearly a year now, and have given up
twice.

*******
BTW, the author, Callum Gibson, currently does not have an email address.

I am the custodian of the source, and can be reached at
        wkt@csadfa.cs.adfa.oz.au
*******

Mind you, I can only help with the code - I didn't write it.

> Minix and Coherent users should keep a line of communication open,
> since were working with similar resources. (Except we don't have
> the source code)

Agreed!

> The shell, by the way, is excellent to use, and I
> found myself preferring it to /bin/sh even before I had the port debugged.

And I still can't believe the number of people out there still using sh!

P.S Now working on an Ansified version, pity the acc runs out of stack :-(

Cheers,
        Warren Toomey   wkt@csadfa.cs.adfa.oz.au


-- 
     Warren Toomey VK2XWT, homing
Deep in the bowels of ADFA Comp Science.
 `At least I'm not a boiled artichoke'