Date: Wed, 7 Feb 2001 15:56:33 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Juan Manuel Guerrero <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Probably a bug in bash 2.04
In-Reply-To: <145AEC0032A@HRZ1.hrz.tu-darmstadt.de>
Message-ID: <Pine.SUN.3.91.1010207155537.4599b-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
Precedence: bulk


On Wed, 7 Feb 2001, Juan Manuel Guerrero wrote:

> I am using bash 2.04. TMPDIR points to an existing directory.
> I try to run the following script:
> #! /bin/sh
> ./bar.sub
> 
> The script ./bar.sub is a **valid** shell script.
> The above script works as it should work as long as
> LFN are ***enabled***.
> Once again: The above script works if LFN=y.
> As soon as LFN is set to n (LFN=n), the above
> script stops working. All this means that
> bash seems to lose the capability to indentify
> a shell script as soon as LFN support becomes disabled.

Mark, was this port built with the modified version of dosexec.c or with 
the stock version from djdev203.zip?