xfs
[Top] [All Lists]

Re: Tomorrow

To: linux-xfs@xxxxxxxxxxx
Subject: Re: Tomorrow
From: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Sat, 24 May 2003 01:15:16 -0800
In-reply-to: <20030524095245.A24074@xxxxxxxxxxxxx>
Mail-copies-to: nobody
Mail-followup-to: linux-xfs@xxxxxxxxxxx
References: <1053694002.2887.1.camel@xxxxxxxxxxxxxxxxxxxxx> <1053697162.21472.51.camel@xxxxxxxxxxxxxxxxxxxx> <20030523134438.GC30288@xxxxxxxxxxxxx> <20030523150530.A31022@xxxxxxxxxxxxx> <20030524071709.GK27626@xxxxxxxxxxxxxxx> <20030524095245.A24074@xxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
On Sat, May 24, 2003 at 09:52:45AM +0100, Christoph Hellwig wrote:
> On Fri, May 23, 2003 at 11:17:10PM -0800, Ethan Benson wrote:
> > > The current plan is to have a v3 directory format for case sensitive
> > > filesystems.
> > 
> > eh?  XFS is already case sensitive.
> 
> Umm, caseInsensitive, of course :)  Sorry for the stupid typo.
> 
> > or do you mean a (i hope optional and non-default) v3 which is
> > brokenly case INsensitive?
> 
> yes.

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 still take the stance that this kind of thing belongs in userspace
(eg samba).

> > seems like a sad thing to put such cruft into a decent filesystem just
> > to support a broken legacy OS.
> 
> I will make sure it'll be a config option.

compile time i presume.  good.

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

Attachment: pgpLCl04T6hSi.pgp
Description: PGP signature

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