xfs
[Top] [All Lists]

Re: Tomorrow

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Tomorrow
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Sat, 24 May 2003 02:04:41 -0800
In-reply-to: <20030524093103.GA12181@wotan.suse.de>
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
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> <20030524093103.GA12181@wotan.suse.de>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Sat, May 24, 2003 at 11:31:03AM +0200, Andi Kleen wrote:
> > 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.

all the more reason to leave it in userspace.  

all for a legacy OS...

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

Attachment: pgp5K2xoPcX9e.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>