From: Richard Dawe Newsgroups: comp.os.msdos.djgpp Subject: Re: Rhide, NT and LFN - some news Date: Sun, 30 Jan 2000 00:38:25 +0000 Organization: Customer of Planet Online Lines: 50 Message-ID: <38938801.E304B4FA@tudor21.net> References: <38909F3F DOT CA060487 AT mailbox DOT swipnet DOT se> <3891618F DOT 90CC4B18 AT mdh DOT se> <389196AB DOT 75F4F711 AT inti DOT gov DOT ar> <3892A935 DOT 2DA80FFB AT is DOT elta DOT co DOT il> NNTP-Posting-Host: modem-248.hydrogen.dialup.pol.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news7.svr.pol.co.uk 949255018 16922 62.136.0.248 (30 Jan 2000 17:56:58 GMT) NNTP-Posting-Date: 30 Jan 2000 17:56:58 GMT X-Complaints-To: abuse AT theplanet DOT net X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586) X-Accept-Language: de,fr To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hello. This is a bit off-topic, but... Eli Zaretskii wrote: > > Damian Yerrick wrote: > > If an entire long filename is uppercase, lowercase it before returning > > it to the caller. That's what Linux vfat support does. Unfortunately the Linux VFAT support isn't entirely like that. I have experienced some weirdness with it. Here's how I think it happened (I may be mistaken): 1. Install Internet Explorer 4 (or maybe 5, I haven't tried it) onto Windows '95. 2. Wnable the option that allows you to type filenames actually as all capitals (e.g. README.TXT) - it's in the Folder Options somewhere. 3. Reboot into Linux. 4. Look at the file README.TXT, see that Linux thinks it's README.TXT. 5. Create a file called readme.txt. Now you have two files that technically have the same DOS/Windows filename. Confused? I think what happens is that Windows '95 stores a long filename, to get the correct capitalisation. I think Linux sees the short filename as being distinct from the long filename. This sort of thing has happened to me many times using Programmer's File Editor, which seems to insist on saving all 8+3 filenames in capitals, which causes the problem. It has been said previously that the VFAT support in Linux is a hack. I suffered quite bad FAT file system corruption with a stable kernel (2.2.4?), so beware. > Not only does the library already do so, it's even documented > Note that the library only does this for DOS 8+3 names; long file names > are left intact, because otherwise names like GETTING.GNU.SOFTWARE would > also be downcased. If Linux does that with long file names, Linux is > wrong. No, Linux leaves the long filenames as they are. Bye, -- Richard Dawe richdawe AT bigfoot DOT com ICQ 47595498 http://www.bigfoot.com/~richdawe/