From mboxrd@z Thu Jan 1 00:00:00 1970 From: tridge@samba.org Subject: Re: CONFIG_VFAT_FS_DUALNAMES regressions Date: Fri, 3 Jul 2009 11:11:27 +1000 Message-ID: <19021.23231.213863.726785@samba.org> References: <19013.8005.541836.436991@samba.org> <20090630063102.GB1351@ucw.cz> <200907012019.53932.rusty@rustcorp.com.au> <20090701122558.3a7c80d3@lxorguk.ukuu.org.uk> <20090701140503.GA21185@mit.edu> <19021.19842.663727.146474@samba.org> <87hbxu60qm.fsf@devron.myhome.or.jp> Reply-To: tridge@samba.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Jan Engelhardt , Theodore Tso , Alan Cox , Rusty Russell , Pavel Machek , john.lanza@linux.com, Linux Kernel Mailing List , linux-fsdevel@vger.kernel.org, Dave Kleikamp , corbet@lwn.net, jcm@jonmasters.org To: OGAWA Hirofumi Return-path: Received: from mail.samba.org ([66.70.73.150]:50014 "EHLO lists.samba.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753806AbZGCBLl (ORCPT ); Thu, 2 Jul 2009 21:11:41 -0400 In-Reply-To: <87hbxu60qm.fsf@devron.myhome.or.jp> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > I have no objection to improve. And in this case, for this option, to > force the shortname= sounds reasonable. Great! Which varient of this would you prefer I implement? I think the two obvious choices are: 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. What do you think? Cheers, Tridge