From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option Date: Fri, 1 May 2009 13:47:57 -0400 Message-ID: <20090501174757.GC8104@infradead.org> References: <1241199689.13073.6.camel@norville.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ogawa Hirofumi , Andrew Tridgell , Steve French , Mingming Cao , Paul McKenney , LKML , linux-fsdevel To: Dave Kleikamp Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:48814 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750940AbZEARr7 (ORCPT ); Fri, 1 May 2009 13:47:59 -0400 Content-Disposition: inline In-Reply-To: <1241199689.13073.6.camel@norville.austin.ibm.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, May 01, 2009 at 12:41:29PM -0500, Dave Kleikamp wrote: > From: Andrew Tridgell > Subject: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option > > When this option is enabled the VFAT filesystem will refuse to create > new files with long names. Accessing existing files with long names > will continue to work. > > File names to be created must conform to the 8.3 format. Mixed case is > not allowed in either the prefix or the suffix. This doesn't make any sense as a compile time option. Might make sense as a mount option, but I'd like to hear a rationale for it first.