X-Spam-Check-By:	sourceware.org
Date:	Thu, 16 Nov 2006 09:27:15 -0500 (EST)
From:	Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: request for /dev/stdin and friends
In-Reply-To:	<20061116104538.GK11304@calimero.vinschen.de>
Message-ID:	<Pine.GSO.4.63.0611160924200.10673@access1.cims.nyu.edu>
References:	<455B18D9 DOT 30504 AT byu DOT net> <20061116104538 DOT GK11304 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Thu, 16 Nov 2006, Corinna Vinschen wrote:

> On Nov 15 06:40, Eric Blake wrote:
> >
> > I know it is possible to create /dev/std{in,out,err} myself, simply making
> > symlinks to /proc/self/fd/{0,1,2}, once I create an underlying physical
> > /dev directory.  But by doing so, I have made it so that the version of
> > bash that I compile detects their existence, and assumes it can use
> > /dev/stdin without problems, and then running that version of bash on
> > other machines fails because /dev/stdin is not standard in cygwin.  I
> > suppose I could try to make the bash postinstall script create a physical
> > /dev/ drive, and populate it with std{in,out,err}, but it seems like it
> > might be nicer if cygwin/devices.in were to provide them natively for all
> > users.
>
> Dunno about that.  On Linux, /dev/std{in,out,err} are just symbolic
> links to fd/{0,1,2} and fd is just a symlink to /proc/self/fd.
>
> So what we should do here IMO is to augment the base-files package
> to create a /dev directory and create a couple of standard symlinks
> in it, which are not covered automatically by the Cygwin DLL.
> For a start:
>
>   fd -> /proc/self/fd
>   stdin -> fd/0
>   stdout -> fd/1
>   stderr -> fd/2
>   dvd -> scd0
>   cdrom -> scd0
>   rmt0 -> st0
>   nrmt0 -> nst0
>   tape -> nst0

There already was some discussion, ending in
<http://cygwin.com/ml/cygwin-developers/2005-02/msg00010.html>, which
never got a reply...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -