From: Bennett Todd <bet@rahul.net>
To: Yury Umanets <umka@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: user-space cmd/lib to compute hash filename ordering?
Date: Thu, 11 Sep 2003 09:16:40 -0400 [thread overview]
Message-ID: <20030911131640.GA556@rahul.net> (raw)
In-Reply-To: <1063264669.29645.4.camel@haron.namesys.com>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
2003-09-11T03:17:49 Yury Umanets:
> If you are interested, I will find out details.
Thanks anyway, I get the message that a stock, standard distro of
ReiserFS doesn't have a single, consistent way to lay hands on the
available hashes for purposes like this, so if I do ever do it, I'll
be making my tool dependent on the ReiserFS dev tooling.
If someone wanted to enhance ReiserFS to make this job easier for
people, I've got a recommendation: include a reiserfs_hashsort
filter, reads a list of full pathnames from stdin, takes a hash name
as a cmdline arg, and prints the files sorted according to that
hash; slap that between the find that generates filenames and the
cpio that packs 'em, and you get a ReiserFS-tuned archive order.
I may pursue doing that eventually, but it's somewhere pretty far
down on my priority list at the moment. In other words, if it had
been there, I'd have used it, but it'll take me a while to get
around to coding it up myself.
Thanks again for the very helpful answer --- "no, what you want
isn't there, here's how you'd go about constructing it" is every bit
as valuable as "yes, here's where to find it". Maybe even more so,
negative answers are harder to research.
-Bennett
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-09-11 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 14:04 user-space cmd/lib to compute hash filename ordering? Bennett Todd
2003-09-11 7:17 ` Yury Umanets
2003-09-11 13:16 ` Bennett Todd [this message]
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=20030911131640.GA556@rahul.net \
--to=bet@rahul.net \
--cc=reiserfs-list@namesys.com \
--cc=umka@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.