X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Message-ID: <250B3114DA16D511B82C00E0094005F8055AC802@MSGWAW11>
From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= <wojciech DOT galazka AT polkomtel DOT com DOT pl>
To: "'djgpp-workers AT delorie DOT com'" <djgpp-workers AT delorie DOT com>,
   DJ Delorie <dj AT delorie DOT com>
Subject: RE: lfn from scratch...
Date: Thu, 27 Dec 2001 21:22:55 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-2"
Reply-To: djgpp-workers AT delorie DOT com


> 
> > From: DJ Delorie <dj AT delorie DOT com>
> > 
> > What's the best way to tell djgpp programs that *one* drive supports
> > LFNs and the others don't?
> 
> DJGPP doesn't cope well with this situation.
> 
> First, _use_lfn was at one point written to cache the last drive for
> which the filesystem was queried about LFN support, but what
> eventually went into v2.03 effectively disables that feature.  So the
> current code reuses the last result (eithe LFN or non-LFN) as long as
> the environment variables didn't change.  Depending on which drive
> did the first _use_lfn call happen, you have a 50-50 chance of doing

hm... not good
BTW which filesystems DOS, DOS emulator, dosemu know of do not support LFN
API
(I can write 'long-named' file to a floppy with FAT16)
> TRT ot TWT...
> 


We have an env. variable LFN
set lfn=y 	check to see if LFN API is supported on a filesystem and if
so use always, if no don't use anywhere
set lfn=n 	don't use LFN API at all

How about adding yet again possible value
set lfn=a 	always use LFN API, even if the filesystem doesn't support
it, the LFN API callee has to handle possible faults
on its own

This of course would require some, though minor, changes in libc