From: jqb AT netcom DOT com (Jim Balter)
Subject: Re: bash problem b17.1 under Windows NT 4/NTFS
14 Mar 1997 20:44:32 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <332A1C78.3E51.cygnus.gnu-win32@netcom.com>
References: <1 DOT 5 DOT 4 DOT 32 DOT 19970314200047 DOT 008e63c4 AT sunspot DOT tiac DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (WinNT; I)
Original-To: Mark Levine <dynasens AT tiac DOT net>
Original-CC: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Mark Levine wrote:
> 
> I am running b17.1 under Windows NT 4.0.
> 
> The following command sequence when run under bash fails when running on an
> NTFS file system:
> 
>         % cat >foo <<EOF
>         > aaa
>         > bbb
>         > EOF
>         bash.exe: 49069028: No such file or directory
> 
> The file foo is created but it is empty, the number in the error messages
> sometimes is different, last few digits change.
> 
> The above works fine on a FAT file system partition.
> 
> As a result of this problem I can not build any of the GNU software from
> source because the configure script will fail because of this problem.

The FAQ! The FAQ!  I haven't read the FAQ!  No time to waste, I must
make haste, no time to read the FAQ!


In other words, mkdir /tmp

--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".