X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 15 Nov 2010 01:37:48 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Cygwin uninstall: Problem with /dev/nul Message-ID: <20101115063747.GB27322@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5590179202C1488BBE99F7A9A80D1566 AT SonyPC> <4CA581FD DOT 8030207 AT lysator DOT liu DOT se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 Mon, Nov 15, 2010 at 05:11:46AM +0000, TryingToHelp wrote: >This is a known DOS/Windows bug. I'm fairly sure that DOS used NUL as a null >device, and that Windows kept it around (not sure why, guess it's for >backward-compatibility). This thread is more than a month old. There is no reason to resurrect it. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple