Re: seekable pipes

On Tue, Jun 21, 2005 at 10:47:22AM -0700, Bryan Henderson wrote:
> When you first described the concept, I was thinking of named pipes, which 
> someone would separately create.  It's still good for that.  For 
> shell-made pipes
> (| and <>()), though, I agree -- the shell has to change.  I don't see any 
> other reasonable way.

OK, that you agree is a good sign. Maybe I shouldn't have mentioned
"|", though. I think it's pretty obvious that the great majority of
commands that expect seekable input take it in the form of a file name
argument and not stdin, so probably only <>() is needed. And once
kernel support for seekable pipes is available it shouldn't be very
hard to extend the shells. That syntax is a parse error in both bash
and zsh, by the way, so I think it could be backward compatible...

Frederik

-- 
http://ofb.net/~frederik/
-
To unsubscribe from this list: send the line "unsubscribe linux-userfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html