All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xuân Baldauf" <xuan--2004.03.29--linux-kernel--vger.kernel.org@baldauf.org>
To: hirofumi@mail.parknet.co.jp
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: vfat: why is shortname=lower the default?
Date: Tue, 29 Mar 2005 22:32:28 +0200	[thread overview]
Message-ID: <4249BB5C.5000102@baldauf.org> (raw)

Hi Hirofumi,

Why is shortname=lower the default mount option for vfat filesystems? 
Because, with "shortname=lower", copying one FAT32 filesystem tree to 
another FAT32 filesystem tree using Liux results in semantically 
different filesystems. (E.g.: Filenames which were once "all uppercase" 
are now "all lowercase").

With "shortname=mixed", such semantic changes would not occur. That's 
why I'd consider "shortname=lower" as default mount option as a bug. I'd 
propose "shortname=mixed" as default as a fix for this bug.

What do you think?

ciao,
Xuân.


P.S.: "man mount" says:

       shortname=[lower|win95|winnt|mixed]

              Defines the behaviour for creation and display of 
filenames which fit into 8.3 characters. If a long name for a file 
exists, it will always be preferred display. There are four modes:

              lower  Force the short name to lower case upon display; 
store a long name when the short name is not all upper case.

              win95  Force the short name to upper case upon display; 
store a long name when the short name is not all upper case.

              winnt  Display the shortname as is; store a long name when 
the short name is not all lower case or all upper case.

              mixed  Display the short name as is; store a long name 
when the short name is not all upper case.

       The default is "lower".


             reply	other threads:[~2005-03-29 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 20:32 Xuân Baldauf [this message]
2005-03-30 13:12 ` vfat: why is shortname=lower the default? OGAWA Hirofumi
2005-03-30 13:26   ` Xuân Baldauf
2005-03-30 14:38     ` OGAWA Hirofumi

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=4249BB5C.5000102@baldauf.org \
    --to=xuan--2004.03.29--linux-kernel--vger.kernel.org@baldauf.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.