On Wed, Mar 27, 2013 at 08:24:57AM -0400, Comeau At9Fans wrote:
>
> I do believe that historically there was some sort of interpretations
> such as this in the evolution from FAT to FAT32, but not sure it
> should be so in current version, or, at least, other operating systems
> don't take this interpretation. Is there an option or something I'm
> missing? How do I get to process x.c as x.c and not X.C.
>
For "other operating systems", in one office where I happen to do work
from time to time, there is a fileserver and various versions of
Windows and an Unix I have put.
I have been unable to understand how the capitalized letters
are taken or dropped in filenames. You can create a file on a Windows,
and the name appearing when mounting the fileserver with NFS is
different from what you typed, and may be different from what a Windows
chows.
Just to mention that this may not be a 9 idiosynchracy but
something to do with curious "rules" in the FAT32 and 8.3 transition.
(Even if in my example, there is no FAT32 left, there are NTFS on NTs
and whatever by default on Windows XP or Windows 7.)
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
