From: jqb@netcom.com (Jim Balter) Subject: Re: bash problem b17.1 under Windows NT 4/NTFS 18 Mar 1997 17:59:49 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <332E5F44.2AFB.cygnus.gnu-win32@netcom.com> References: <1.5.4.32.19970314200047.008e63c4@sunspot.tiac.net> <332A1C78.3E51@netcom.com> <332DF1E7.3466@itg-sepg.logicon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.0b2 (WinNT; I) Original-To: shochat@itg-sepg.logicon.com Original-CC: gnu-win32@cygnus.com X-Priority: 3 (Normal) Original-Sender: owner-gnu-win32@cygnus.com David Shochat wrote: > > Jim Balter wrote: > > > > 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 < > > > 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 > > > Although this is certainly a question which is asked and answered > frequently, I just went looking for it in the FAQ and can't find it > there. Maybe it's hiding in the answer to some other question? Yr right; the FAQ only mentions /tmp under byacc. I guess Cygnus is too busy trying to woo potential licensees for their POSIX product-to-be away from Softway's OpenNT to update the FAQ. -- - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".