xfs
[Top] [All Lists]

Re: Tomorrow

To: Steve Lord <lord@xxxxxxx>
Subject: Re: Tomorrow
From: Andi Kleen <ak@xxxxxxx>
Date: Tue, 27 May 2003 11:16:00 +0200
Cc: Ethan Benson <erbenson@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <1054004533.1170.6.camel@laptop.americas.sgi.com>
References: <20030524071709.GK27626@plato.local.lan> <20030524095245.A24074@infradead.org> <20030524091516.GM27626@plato.local.lan> <20030524093103.GA12181@wotan.suse.de> <20030524100441.GN27626@plato.local.lan> <1053814283.4056.25.camel@holly> <20030524223508.GO27626@plato.local.lan> <1054003505.1174.1.camel@laptop.americas.sgi.com> <20030527025545.GE32642@plato.local.lan> <1054004533.1170.6.camel@laptop.americas.sgi.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
On Mon, May 26, 2003 at 10:02:12PM -0500, Steve Lord wrote:
> On Mon, 2003-05-26 at 21:55, Ethan Benson wrote:
> 
> > 
> > well price you pay for using crud like windows..
> > 
> > anyway they should just use a broken case insensitive filesystem like
> > NTFS, or HFS+ for the smb export, rather then insist we cripple (or
> > cruftify) decent filesystems like XFS.
> > 
> 
> This stuff will not get in the way of normal operation, and there is
> a market for being an SMB server - and XFS runs on more than one
> operating system. Actually it is really not that much code.

Also Linux already has the required I18N code for it. I would be still
curious if you chose UTF-8 or 8bit code pages for it.

-Andi


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