Date:	Mon, 12 Feb 2001 09:28:32 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Mark E." <snowball3 AT bigfoot DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Bash problem with SFN
In-Reply-To:	<3A86B90D.15400.11A13E4@localhost>
Message-ID:	<Pine.SUN.3.91.1010212092757.12969F-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 11 Feb 2001, Mark E. wrote:

> Hmm, I can get this fail without using Bash with LFN=N. Below is an excerpt 
> of the program I used on my own machine to trigger the problem.
> 
> ...
> 
>   mkdir("longlonglong", S_IWUSR);
>   chdir("/dev/d/djgpp/projects/sfn/longlonglong");
>   mkdir("dir", S_IWUSR);
>   chdir("/dev/d/djgpp/projects/sfn/longlonglong/dir");
> 
>   fd = open("file", O_WRONLY | O_TEXT | O_CREAT | O_TRUNC, S_IWUSR);
> 
> [fd will be -1 when LFN=N.]

On DOS or on Windows?

> I've uploaded a new version of Bash 2.04 to 
> http://members.nbci.com/snowball3/djgpp/ that avoids this error.

How does it avoid this?  Did you succeed to understand why does this
problem happen?  If so, perhaps you could explain what causes it.

- Raw text -