Dave Kleikamp wrote:
On Fri, 2009-05-01 at 13:47 -0400, Christoph Hellwig wrote:
On Fri, May 01, 2009 at 12:41:29PM -0500, Dave Kleikamp wrote:
From: Andrew Tridgell <tridge@xxxxxxxxx>
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.
Some linux-based devices would be happy not to contain code to create
the long name at all.
Well, is that a rationale per se? Which devices they are and why?
But besides, why `msdos' filesystem is not sufficient?
It contains no code to create long file names and no code to
read such names either.
/mjt
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
