From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FAT32 question
Date: Wed, 27 Mar 2013 13:36:37 +0100 [thread overview]
Message-ID: <20130327123637.GA1278@polynum.com> (raw)
In-Reply-To: <CAE9W7-gYJmOavr2RGGam=QVA8U6d3xELRNvLG_jqMtSG70nRQQ@mail.gmail.com>
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
next prev parent reply other threads:[~2013-03-27 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 12:24 Comeau At9Fans
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 [this message]
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=20130327123637.GA1278@polynum.com \
--to=tlaronde@polynum.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).