X-Spam-Check-By: sourceware.org
Message-ID: <455B18D9.30504@byu.net>
Date: Wed, 15 Nov 2006 06:40:41 -0700
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: request for /dev/stdin and friends
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFWxjY84KuGfSFAYARAnAaAJ92M8GtHVvVSIhphmP+1205uvWMgACfZ+0b
E3HBCaw16fLVF+ubE5qq2f4=
=98ie
-----END PGP SIGNATURE-----

--
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/

