X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Fri, 28 Dec 2001 13:07:39 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: wojciech DOT galazka AT polkomtel DOT com DOT pl Message-Id: <6436-Fri28Dec2001130739+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: djgpp-workers AT delorie DOT com In-reply-to: <250B3114DA16D511B82C00E0094005F8055AC802@MSGWAW11> (message from =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= on Thu, 27 Dec 2001 21:22:55 +0100) Subject: Re: lfn from scratch... References: <250B3114DA16D511B82C00E0094005F8055AC802 AT MSGWAW11> 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 > From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= > Date: Thu, 27 Dec 2001 21:22:55 +0100 > > 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) Sorry, I don't understand the question. Given the right software, _any_ of the platforms DJGPP can run on could support the LFN API. But in practice, some of them don't have the necessary software. Plain DOS is one; DOSEmu is another; some old network redirectors and OS/2 are yet another example. > 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 This is not how _use_lfn works: you _can_ force it to query the filesystem again if you call _use_lfn with a non-NULL argument. > 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 In what situations would this option be useful? If the callee is expected to be able to cope with the LFN API calls, then why can't it just support function 71A0h and return the LFN supported flag when we call it?