X-Spam-Check-By: sourceware.org Date: Wed, 12 Apr 2006 18:19:37 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: XP embedded Message-ID: <20060412161937.GG9135@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20060412095556 DOT GC10758 AT calimero DOT vinschen DOT de> <20060412154903 DOT GC13171 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Apr 12 12:05, 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). Mon dieu! > 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? > Igor Since /dev/null is a really existing native device, it also works for stdio redirection when executing a native Windows process. Off the top of my head I don't know a case for which that really matters, but it's guaranteed that somebody on the list will find a case really soon after this change. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/