From: Frederik Eaton Subject: Re: seekable pipes Date: Thu, 23 Jun 2005 22:43:08 -0700 Message-ID: <20050624054308.GF27535@a5.repetae.net> References: <20050621050252.GC7874@a5.repetae.net> Reply-To: frederik@ofb.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: fsdevel , Linux-userfs , x Return-path: To: Bryan Henderson Content-Disposition: inline In-Reply-To: Sender: linux-userfs-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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/