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: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: vfat: why is shortname=lower the default?
Date: Wed, 30 Mar 2005 15:26:00 +0200	[thread overview]
Message-ID: <424AA8E8.1020008@baldauf.org> (raw)
In-Reply-To: <871x9xs2fy.fsf@devron.myhome.or.jp>

OGAWA Hirofumi wrote:

>Xuân Baldauf <xuan--2004.03.29--linux-kernel--vger.kernel.org@baldauf.org> writes:
>
>  
>
>>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").
>>    
>>
>
>The reason is only it's very long-standing behavior.  When this
>behavior was changed before, it seems an one user was confused at
>least.
>
>    http://marc.theaimsgroup.com/?t=97041869500002&r=1&w=2
>
>Personally I agree that "winnt" or "mixed" is proper.
>
>However, if we want to change the default behavior, it would need to
>be tested for some months, and if anyone has no objection it can
>change I think.
>  
>
One could make a slow transition, starting now with a warning like 
"vfat: warning: You are using "shortname=lower" as default. This may not 
be what you want. This default will change to "shortname=mixed" after 
2005-07-01." if the shortname behaviour is not explicitly selected.

>Thanks.
>  
>
ciao,
Xuân. :-)

P.S.: I'm now trying to recover about 4M files from "lost case"...


  reply	other threads:[~2005-03-30 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 20:32 vfat: why is shortname=lower the default? Xuân Baldauf
2005-03-30 13:12 ` OGAWA Hirofumi
2005-03-30 13:26   ` Xuân Baldauf [this message]
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=424AA8E8.1020008@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.