From: Comeau At9Fans <comeauat9fans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] FAT32 question
Date: Wed, 27 Mar 2013 08:24:57 -0400 [thread overview]
Message-ID: <CAE9W7-gYJmOavr2RGGam=QVA8U6d3xELRNvLG_jqMtSG70nRQQ@mail.gmail.com> (raw)
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.
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.
--
Greg Comeau / 4.3.10.1 with C++0xisms now in beta!
Comeau C/C++ ONLINE ==> http://www.comeaucomputing.com/tryitout
World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90.
Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
next reply other threads:[~2013-03-27 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:24 Comeau At9Fans [this message]
2013-03-27 12:33 ` erik quanstrom
2013-03-27 14:18 ` Comeau At9Fans
2013-03-27 16:02 ` Nicolas Bercher
2013-03-27 16:16 ` Comeau At9Fans
2013-03-27 12:36 ` tlaronde
2013-03-27 12:39 ` dexen deVries
2013-03-27 13:07 ` Stuart Morrow
2013-03-27 15:44 ` Bakul Shah
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE9W7-gYJmOavr2RGGam=QVA8U6d3xELRNvLG_jqMtSG70nRQQ@mail.gmail.com' \
--to=comeauat9fans@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).