From owner-freebsd-current Thu Sep 14 11:56: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id B837637B440 for ; Thu, 14 Sep 2000 11:55:59 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id LAA83998 for current@FreeBSD.org; Thu, 14 Sep 2000 11:55:49 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009141855.LAA83998@pike.osd.bsdi.com> Subject: Re: Fdescfs updates--coming to a devfs near you! To: current@FreeBSD.org Date: Thu, 14 Sep 2000 11:55:49 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <20000914123945.A32524@ringwraith.office1.bg>, Peter Pentchev writes > : > >On Thu, Sep 14, 2000 at 01:12:10AM -0700, Julian Elischer wrote: > >> I've never thought of a use for fdescfs... > > > >Well.. just a trivial example - imagine a program which takes a filename > >as an argument; imagine yourself trying to pipe something into it - > >passing /dev/fd/0 as a filename to process would do the trick. > > I must admit that I think in general that /dev/std{in,out,err} and /dev/fd > is bogus. It looks like something which happened "because we can" more > than something which has a legitimate need. How about the fact that the printing chapter in the Handbook uses /dev/fd/0 in its example of setting up a print filter using ghostscript since gs doesn't read from stdin by default or use '-' for that purpose. Hmmm?? > If anything I would propose we ditch it... Tools, not policy, as you are so fond of saying. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message