X-Spam-Check-By: sourceware.org
Date: Wed, 12 Apr 2006 12:27:59 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: XP embedded
Message-ID: <20060412162759.GE13171@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <d62889820604111122u698c48fbk89881ee70082f434 AT mail DOT gmail DOT com> <20060412095556 DOT GC10758 AT calimero DOT vinschen DOT de> <d62889820604120443o64146155ud3cca1f868d50311 AT mail DOT gmail DOT com> <20060412154903 DOT GC13171 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT GSO DOT 4 DOT 63 DOT 0604121158590 DOT 21356 AT access1 DOT cims DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.63.0604121158590.21356@access1.cims.nyu.edu>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Wed, Apr 12, 2006 at 12:05:04PM -0400, Igor Peshansky wrote:
>On Wed, 12 Apr 2006, Christopher Faylor wrote:
>>On Wed, Apr 12, 2006 at 07:43:33AM -0400, Jeff Lange wrote:
>>>/dev/zero does work properly.  I changed line 68 in /etc/profile to use
>>>/dev/zero instead of /dev/null and I no longer get the bash error on
>>>start up.
>
>FWIW, /dev/zero is not always the proper substitution for /dev/null
>(i.e., on input redirection, it will work differently).
>
>>>Perhaps the cygwin libraries should be modified so that if the windows
>>>NUL device doesn't exist, it should use a different method.
>>
>>Sorry, no.  We already have enough special cases in the code.  We're
>>not going to start adding more for XP Embedded.
>
>What I'm wondering is whether we need the Windows NUL device at all for
>implementing /dev/null...  It's rather trivial[*] to implement one
>without resorting to a Windows device.  Would there be any way of
>distinguishing an emulation from the real NUL device?

Wasn't that the point that the OP was making and to which I responded?
I really do understand this stuff, Igor.

When possible we always try to use the underlying device.  There are
obvious benefits to doing things this way and there is no reason to
abandon this policy for XP Embedded.

cgf

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