Date:	Tue, 3 Jun 1997 09:23:29 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	"Peter J. Farley III" <pjfarley AT dorsai DOT org>
cc:	djgpp AT delorie DOT com
Subject:	Re: /dev/null BASH bug?
In-Reply-To:	<33932f7d.19066230@news.dorsai.org>
Message-ID:	<Pine.SUN.3.91.970603092252.29063F-100000@is>
MIME-Version:	1.0

On Mon, 2 Jun 1997, Peter J. Farley III wrote:

> I think I have found a bug (difference?) in the way DJGPP libc treats
> /dev/null under COMMAND.COM and the way it treats it under BASH
[snip]
> bash.exe$ ./tdevnull
> ./tdevnull: /dev/null: No such file or directory (ENOENT)

You will have to investigate further, because your script works for me
exactly as you'd expect.  "/dev/null" is supported by the DJGPP
library on its lowest level, so the chance of the shell to have any
impact on that is extremely low.

A few things to check:

	1) Are you running on Windows 95?  If so, try booting into
plain DOS mode (no Windows at all).  I tested your script on DOS 6.2.

	2) Is the drive where you run it somehow unusual (e.g
networked)?  If so, copy everything to a local drive and try again.

	3) Remove any Bash-specific settings in your CONFIG.SYS,
AUTOEXEC.BAT and DJGPP.ENV and see if that changes anything.

Btw, when reporting information on program versions, it is best to
post the output of `dir' or `ls -l', so the size and the timestamps
are clearly visible.  Sometimes, updated ports are uploaded to DJGPP
archives with the same version (since the version is derived from the
official GNU release) which makes --version output ambiguous.  At
least for Bash, the time stamp you've posted says that you seem to
have the latest version, so the problem is most probably elsewhere.

- Raw text -