From mboxrd@z Thu Jan 1 00:00:00 1970 References: In-Reply-To: Mime-Version: 1.0 (1.0) Content-Type: text/plain; charset=us-ascii Message-Id: Content-Transfer-Encoding: quoted-printable From: Bakul Shah Date: Wed, 27 Mar 2013 08:44:13 -0700 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] FAT32 question Topicbox-Message-UUID: 37bde788-ead8-11e9-9d60-3106f5b1d025 On Mar 27, 2013, at 5:24 AM, Comeau At9Fans wrote:= > I'm mounting a FAT32 flashdrive on a RPi. However, it seems that some > sort of legacy 8.3 filename situation is existing. For instance, if I > have a directory containing x.c and a23456789.c that the former is > taken as X.C and the latter is taken as shown. Therefore, to compile > x.c is not possible. So for instance, echo *.c produces a different > result than echo *.C. I tried mv'ing the problem files and then back > but same results. >=20 > 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. mv failed to cure it of its uppercase probably because the X.C slot in the p= atent dir. was reused when you renamed it back. Copy everything to a brand n= ew directory using lowercase names and see if that works. The broader lesson= is to *not* use FAT fs with tools that expect case sensitive file systems.=20=