[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.00.0907030347210.24650@fbirervta.pbzchgretzou.qr>
Date: Fri, 3 Jul 2009 03:50:29 +0200 (CEST)
From: Jan Engelhardt <jengelh@...ozas.de>
To: tridge@...ba.org
cc: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
Theodore Tso <tytso@....edu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Rusty Russell <rusty@...tcorp.com.au>,
Pavel Machek <pavel@....cz>, john.lanza@...ux.com,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel@...r.kernel.org,
Dave Kleikamp <shaggy@...ux.vnet.ibm.com>, corbet@....net,
jcm@...masters.org
Subject: Re: CONFIG_VFAT_FS_DUALNAMES regressions
On Friday 2009-07-03 03:11, tridge@...ba.org wrote:
>
> 1) do what I did in the May patch, which is to force
> VFAT_SFN_CREATE_WINNT when the patch code triggers.
>
> 2) force VFAT_SFN_CREATE_WINNT, but also if the name is mixed case
> within either prefix or extension (such as "Mixed.TXT") then force
> that part of the name to all lowercase. So "Mixed.TXT" would become
> "mixed.TXT" on disk.
>
>The 2nd choice maximises compatibility with devices that don't
>understand long filenames (such as Jan's camera). The first option
>keeps case preservation for devices that do understand long filenames.
The cam does not have a problem with long filenames — as said, it works
on any to-date vanilla/distro Linux kernel, which, if I understood
mount(8) right, always create a long filename due to me using a
lowercase filename in conjunction with the default shortname=mixed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists