Date: Thu, 14 Sep 2000 11:43:49 -0700 (PDT) From: John Baldwin <jhb@pike.osd.bsdi.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Peter Pentchev <roam@orbitel.bg>, Julian Elischer <julian@elischer.org>, Chris Costello <chris@calldei.com>, hackers@FreeBSD.ORG, current@FreeBSD.ORGG Subject: Re: Fdescfs updates--coming to a devfs near you! Message-ID: <200009141843.LAA83370@pike.osd.bsdi.com> In-Reply-To: <56076.968924938@critter> from Poul-Henning Kamp at "Sep 14, 2000 11:48:58 am"
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@bsdi.com> -- 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-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200009141843.LAA83370>