Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753897AbZGFSz4 (ORCPT ); Mon, 6 Jul 2009 14:55:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752854AbZGFSzq (ORCPT ); Mon, 6 Jul 2009 14:55:46 -0400 Received: from sovereign.computergmbh.de ([85.214.69.204]:54739 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752194AbZGFSzq (ORCPT ); Mon, 6 Jul 2009 14:55:46 -0400 Date: Mon, 6 Jul 2009 20:55:48 +0200 (CEST) From: Jan Engelhardt To: tridge@samba.org cc: OGAWA Hirofumi , 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 Subject: Re: CONFIG_VFAT_FS_DUALNAMES regressions In-Reply-To: <19025.63119.656216.431469@samba.org> Message-ID: 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> <19021.23231.213863.726785@samba.org> <19021.26102.80885.330380@samba.org> <19021.31291.642416.956966@samba.org> <19021.63615.450348.192109@samba.org> <19025.63119.656216.431469@samba.org> User-Agent: Alpine 2.00 (LSU 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1643 Lines: 45 On Monday 2009-07-06 15:05, tridge@samba.org wrote: > > > With this extra patch: > > > > * "cp dscf4160.jpg dscf3010.jpg" works > > * "cp dscf4160.jpg dscF3011.jpg" does not work - i.e. cam ignores the > > file without error. > > Reason for that is that dscF3011 has an illegal 8.3 name > >It is probably not unreasonable to say that you should not be using >mixed case names when you are putting files onto a device that doesn't >understand mixed case. The reason it worked before my patch is that >the kernel forced the case of the 8.3 name, and only retained the >mixed case for the long name. > >How did things go with your mp3 players? Not too different from previously[1]. Entirely-lowercase fits-8-3-names work as usual, but of course are displayed with an uppercase filename in the OSD (technically correct, but still ick!). Whenever a long name is created and an 8.3 name is omitted (or rather, an invalid one is generated), files are displayed in the browser but fail to enqueue/play. As it stands, my two devices always want a valid 8.3 name. That in stark conflict to your patch. And I am not going to do without long filenames. [1] http://osdir.com/ml/linux-kernel/2009-07/msg01314.html Random statistic of the day about audio file's name length, as output by R: Min. 1st Qu. Median Mean 3rd Qu. Max. 6.00 18.00 25.00 26.62 33.00 77.00 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/