From: David Masover <ninja@slaphack.com>
To: Christian Iversen <chrivers@iversen-net.dk>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 for windows
Date: Tue, 01 Feb 2005 19:18:55 -0600 [thread overview]
Message-ID: <42002A7F.3020305@slaphack.com> (raw)
In-Reply-To: <200502011059.37435.chrivers@iversen-net.dk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Iversen wrote:
| On Tuesday 01 February 2005 09:52, Markus Törnqvist 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQgAqfngHNmZLgCUhAQJXSA/8C+sgMtMZXjZBEjB0yYG/9Ccrp86vtchG
64pbwiS81p/Jy0iBGNYkYxzLav25Y7geXSaUNTjjHDyVbom4xkHdjAO6ayDzQDTw
kfiVkUVBw5Vrd99svRTHagXjm/KgijWsQD+8SUB2xy0D5qQsC49vse0u2vXHxmhU
D/XsyYp4n0f/BKcMeOtg2n+jq22m41SPbluU7DKVN3aE3bvseqCiKupWgsyLrgUy
Iyo0IB2b5cY9N2s8MhbFYgoB1HytLyw6PIOZb4gzv60Rhh4CAanScgvkACrRSRRa
uDMWgJwmnoWmcmuBlKGz8dqTpO3fwNrBdKJbhL8BWyPvgdEdlqQd+L2x2ST/YGRH
Eazd7QHBmU300jAbNMJZlViT1S2VCocnLX6K6fN/PRs1UvypNTDdEf4hoIKOGNoG
VL3c65qI02oWoRzusU11M0pfwkTrUW1aAqYUlLAuMNL4xl2+orV8OuWERdIPxm+V
widPGgfoaSBSy6orF6ywbtbwd/4PzOUF3CKYjG4mJpX9bGUtCpcBxxFGxTW3zakz
SHlaotf4G4szwxpYUSjg+iQ2yo4q/XaPVdXgRR2CaFHb0u5v2LksPltgRE/xfpYg
JCK2KBcKdkL5aF6Gkzboir+Pe6KbAjlOrgTsu9c3UvQJU2A77eEvqPDTM7rpx7XS
FvTfsqvOvG4=
=4YQD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-02-02 1:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 21:10 reiser4 for windows Job Bob
2004-12-05 1:57 ` Hans Reiser
2004-12-05 4:00 ` Hans Reiser
2004-12-05 4:54 ` David Masover
2004-12-07 8:28 ` Redeeman
2004-12-08 0:51 ` Philip Miller
2005-01-26 19:27 ` Marcus Furlong
2005-01-16 2:39 ` Hans Reiser
2005-01-16 6:07 ` David Masover
2005-01-17 16:46 ` Hans Reiser
2005-01-17 17:12 ` Christian Iversen
2005-01-18 16:37 ` Hans Reiser
2005-02-01 8:52 ` mjt
2005-02-01 9:59 ` Christian Iversen
2005-02-02 1:18 ` David Masover [this message]
2005-02-02 8:02 ` Christian Iversen
2005-01-18 5:08 ` David Masover
2005-01-18 17:03 ` Hans Reiser
2004-12-05 8:14 ` Dr. Giovanni A. Orlando
2004-12-05 7:37 ` David Masover
2004-12-06 2:31 ` Jonathan Briggs
2004-12-06 4:17 ` Tierra
2004-12-06 14:55 ` Dr. Giovanni A. Orlando
-- strict thread matches above, loose matches on Subject: below --
2004-12-07 6:07 Jiri Klouda
2004-12-07 8:29 ` Redeeman
2004-12-08 1:40 ` Spam
2004-12-08 4:38 ` David Masover
2004-12-08 7:50 ` Radovan Garabik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42002A7F.3020305@slaphack.com \
--to=ninja@slaphack.com \
--cc=chrivers@iversen-net.dk \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.