From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Iversen Subject: Re: reiser4 for windows Date: Wed, 2 Feb 2005 09:02:21 +0100 Message-ID: <200502020902.21492.chrivers@iversen-net.dk> References: <20041204211059.41930.qmail@web50908.mail.yahoo.com> <200502011059.37435.chrivers@iversen-net.dk> <42002A7F.3020305@slaphack.com> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <42002A7F.3020305@slaphack.com> Content-Disposition: inline List-Id: Content-Type: text/plain; charset="iso-8859-1" To: reiserfs-list@namesys.com On Wednesday 02 February 2005 02:18, David Masover wrote: > Christian Iversen wrote: > | On Tuesday 01 February 2005 09:52, Markus T=F6rnqvist wrote: > |>On Tue, Jan 18, 2005 at 08:37:13AM -0800, Hans Reiser wrote: > |>>>Could reiser4 support case-crushing, so it would be more > |>>>"windows-native"? > |>> > |>>It could, as a plugin. > |> > |>Reiser4 has a sys interface already, why not add echo 1 > case_crush or > |>somesuch? Shouldn't take a long time to code, but it shouldn't be a > |>priority and no one would really want it, I guess... > | > | I support your idea, but keep in mind that, to make matters worse, > > windows > > | uses case-insentivity, not case-crushing. This means that the original > > case > > | has to be saved, but the crushed case has to be searched. > | > | I don't know if that's easy with a hash function, but it seems mightly > > slow to > > | me. > > Who said anything about messing with the hash? Why not just add > original case as metadata and feed pre-crushed case to the existing > hash? Don't think overhead is huge if you're already creating a file. Well, thinking about it, you seem to be right. I was thinking about somethi= ng=20 else :) =2D-=20 Regards, Christian Iversen