* Re: bash problem b17.1 under Windows NT 4/NTFS
@ 1997-03-15 7:09 Mark Levine
0 siblings, 0 replies; 6+ messages in thread
From: Mark Levine @ 1997-03-15 7:09 UTC (permalink / raw)
To: Jim Balter; +Cc: gnu-win32
At 19:50 97/03/14 -0800, you 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 <<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.
>
..snip
>
>
>In other words, mkdir /tmp
>
>
I did have a /tmp mounted to G:\TEMP, / is mounted to F:\Cygnus, /usr is
mounted to F:\Cygnus\H-i386-cygwin32. I also have a C partition (FAT), and
a D, E, F, G, T are all NTFS. I had the above problem on the G partition
where I was trying to build some source, in a subdirectory under /tmp.
After much experimentation I remounted /tmp on my T partition and the
problem went away. I am not sure why.
************************************************************************
* *
* Visit Our Web Page at: *
* http://www.tiac.net/users/dynasens *
* *
*----------------------------------------------------------------------*
* | *
* Mark Levine | EMAIL: dynasens@tiac.net *
* DynaSense Consulting Services | *
* Framingham, MA 01701 | *
* | *
************************************************************************
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bash problem b17.1 under Windows NT 4/NTFS
1997-03-17 21:44 ` David Shochat
@ 1997-03-18 9:38 ` Jim Balter
0 siblings, 0 replies; 6+ messages in thread
From: Jim Balter @ 1997-03-18 9:38 UTC (permalink / raw)
To: shochat; +Cc: gnu-win32
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 <<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
> >
> 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.
--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bash problem b17.1 under Windows NT 4/NTFS
1997-03-14 19:53 ` Jim Balter
@ 1997-03-17 21:44 ` David Shochat
1997-03-18 9:38 ` Jim Balter
0 siblings, 1 reply; 6+ messages in thread
From: David Shochat @ 1997-03-17 21:44 UTC (permalink / raw)
To: gnu-win32
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 <<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
>
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?
-- David
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bash problem b17.1 under Windows NT 4/NTFS
1997-03-14 16:28 Mark Levine
1997-03-14 19:53 ` Jim Balter
@ 1997-03-15 19:31 ` Rick Rankin
1 sibling, 0 replies; 6+ messages in thread
From: Rick Rankin @ 1997-03-15 19:31 UTC (permalink / raw)
To: Mark Levine, gnu-win32
You need to have a /tmp. You can either create one directly or mount one
from another drive.
Rick
At 03:00 PM 3/14/97 -0500, 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.
>
>
>
>************************************************************************
>* *
>* Visit Our Web Page at: *
>* http://www.tiac.net/users/dynasens *
>* *
>*----------------------------------------------------------------------*
>* | *
>* Mark Levine | EMAIL: dynasens@tiac.net *
>* DynaSense Consulting Services | *
>* Framingham, MA 01701 | *
>* | *
>************************************************************************
>
>-
>For help on using this list, send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>
>
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: bash problem b17.1 under Windows NT 4/NTFS
1997-03-14 16:28 Mark Levine
@ 1997-03-14 19:53 ` Jim Balter
1997-03-17 21:44 ` David Shochat
1997-03-15 19:31 ` Rick Rankin
1 sibling, 1 reply; 6+ messages in thread
From: Jim Balter @ 1997-03-14 19:53 UTC (permalink / raw)
To: Mark Levine; +Cc: gnu-win32
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@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 6+ messages in thread
* bash problem b17.1 under Windows NT 4/NTFS
@ 1997-03-14 16:28 Mark Levine
1997-03-14 19:53 ` Jim Balter
1997-03-15 19:31 ` Rick Rankin
0 siblings, 2 replies; 6+ messages in thread
From: Mark Levine @ 1997-03-14 16:28 UTC (permalink / raw)
To: gnu-win32
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.
************************************************************************
* *
* Visit Our Web Page at: *
* http://www.tiac.net/users/dynasens *
* *
*----------------------------------------------------------------------*
* | *
* Mark Levine | EMAIL: dynasens@tiac.net *
* DynaSense Consulting Services | *
* Framingham, MA 01701 | *
* | *
************************************************************************
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1997-03-18 9:38 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-03-15 7:09 bash problem b17.1 under Windows NT 4/NTFS Mark Levine
-- strict thread matches above, loose matches on Subject: below --
1997-03-14 16:28 Mark Levine
1997-03-14 19:53 ` Jim Balter
1997-03-17 21:44 ` David Shochat
1997-03-18 9:38 ` Jim Balter
1997-03-15 19:31 ` Rick Rankin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).