X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 1 Jun 2006 12:29:22 -0400 From: "Lev Bishop" To: cygwin AT cygwin DOT com Subject: Re: bash: /dev/null: No such file or directory. Why is /dev/null implemented using the windows NUL device? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: 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 6/1/06, Robert McKay wrote: > Does anyone know what can go wrong with the windows NUL device? :-) > > Do you need any kind of special permissions to use NUL? You could download winobj from sysinternals.com. Check that \GLOBAL??\NUL is a symbolic link to \Device\Null Check that \Device\Null exists. Check the permissions for both (properties, security tab). HTH Lev -- 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/