| 1 |
On Fri, Jan 8, 2010 at 3:39 PM, <felix@×××××××.com> wrote: |
| 2 |
> On Fri, Jan 08, 2010 at 02:01:08PM -0600, Paul Hartman wrote: |
| 3 |
> |
| 4 |
>> I haven't noticed any difference with any of my vfat devices in |
| 5 |
>> 2.6.32. Filenames have mixed-case and seem usual. Where did you read |
| 6 |
>> about 2.6.32 changing long filename handling? I can't find any info |
| 7 |
>> about it. |
| 8 |
> |
| 9 |
> I have read it in several places, but the only one I (think I) |
| 10 |
> remember by name is lwn.net, and I couldn't give you any specific |
| 11 |
> article. |
| 12 |
|
| 13 |
In the 2.6.32 kernel ChangeLog this is the only thing that looks to |
| 14 |
address it, and if anything it sounds like it should be the opposite |
| 15 |
of your problem (fixing it instead of causing it)... weird. Maybe try |
| 16 |
to add shortname=mixed to your mount options in case something in your |
| 17 |
system has it set otherwise. |
| 18 |
|
| 19 |
commit 955234755ce4a2c33cfc558912aa8f2148cc1fc6 |
| 20 |
Author: Paul Wise <pabs3@×××××××××.net> |
| 21 |
Date: Sat Aug 1 21:30:31 2009 +0900 |
| 22 |
|
| 23 |
vfat: change the default from shortname=lower to shortname=mixed |
| 24 |
|
| 25 |
Because, with "shortname=lower", copying one FAT filesystem tree to |
| 26 |
another FAT filesystem tree using Linux results in semantically |
| 27 |
different filesystems. (E.g.: Filenames which were once "all |
| 28 |
uppercase" are now "all lowercase"). |
| 29 |
|
| 30 |
So, this changes the default of "shortname=lower" to "shortname=mixed". |
| 31 |
|
| 32 |
Signed-off-by: Paul Wise <pabs3@×××××××××.net> |
| 33 |
[change fat_show_options()] |
| 34 |
Signed-off-by: OGAWA Hirofumi <hirofumi@×××××××××××××××.jp> |
Archives