Date: Sat, 24 May 2003 11:31:03 +0200
From: Andi Kleen <ak@suse.de>
To: linux-xfs@oss.sgi.com
Subject: Re: Tomorrow
Message-ID: <20030524093103.GA12181@wotan.suse.de>
References: <1053694002.2887.1.camel@localhost.localdomain> <1053697162.21472.51.camel@jen.americas.sgi.com> <20030523134438.GC30288@wotan.suse.de> <20030523150530.A31022@infradead.org> <20030524071709.GK27626@plato.local.lan> <20030524095245.A24074@infradead.org> <20030524091516.GM27626@plato.local.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030524091516.GM27626@plato.local.lan>
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk
Content-Length: 807
Lines: 17

> i wouldn't call them v3 dirs either, that implies its an `upgrade' to
> v2, when in fact its a downgrade (non-broken -> broken).  maybe call
> them v0 (afaik xfs only has two dir formats v1 and v2). or call it
> something entirely different, like broken_dirs ;-)

I would not call them broken, but what is a bit worrying is that it can
be quite complicated to lower case letters.  In the American ASCII subset it's 
easy, but for other languages it usually needs huge lookup tables and worse
there are different character set.

You either only support UTF-8 Unicode (shifting the burden of conversion 
to user space) or you need to store a "codepage" per filesystem.  Linux seems
to go towards the UTF-8 route.  The kernel already has some code for this 
(JFS does it), but it will be not pretty.

-Andi