From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: "David Masover" <ninja@slaphack.com>,
"Markus Törnqvist" <mjt@nysv.org>,
"David Dabbs" <david@dabbs.net>,
reiserfs-list@namesys.com
Subject: Re: Fibration questions
Date: Sun, 25 Jul 2004 23:28:24 -0700 [thread overview]
Message-ID: <4104A488.2060103@namesys.com> (raw)
In-Reply-To: <200407231309.55295.vitaly@namesys.com>
Vitaly Fertman wrote:
>>wait -- what does this do:
>>echo -e "tea\0" > somedir/metas/plugin/hash
>>
>>
>
>will set the hash tea in 'somedir' if it is empty.
>if it has 'subdir' already, nothing happens.
>
>
>
>>echo -e "something_differenet\0" > somedir/subdir/metas/plugins/hash
>>
>>
>
>will set the hash 'something_differenet' if any of [r5 | tea | fnv1 |
>rupasov | degenerate hash | all future hash plugins] in 'somedir/subdir'
>if 'subdir' is empty.
>
>
is something_different constrained to
[r5 | tea | fnv1 | rupasov | degenerate hash | some future hash plugin existing at time of command]
?
(I hope so.)
>
>
>>echo -e "r5\0" > somedir/metas/plugins/hash
>>
>>
>
>nothing happens as 'subdir' exists.
>
>
>
>>What is the hash of "subdir" now?
>>
>>
>
>'somthing_different'
>
>
>
>>What about new subdirs? What hash will they get?
>>
>>
>
>new subobjects inherit all plugins from the object they are created
>in at the creation time. future changes of plugins of the object will
>not be applied to already created subobjects, only to new subobjects.
>
>Note: if a plugin is used for rendering the object content then its
>changing needs a convertion method. Thus if you create a file in
>the dir then the hash plugin gets used, and you need to convert the
>dir to change the hash successfully. As there is no such convertion
>methods yet, you cannot change the hash of not empty dir.
>
>
>
next prev parent reply other threads:[~2004-07-26 6:28 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 10:35 Fibration questions David Dabbs
2004-07-16 11:04 ` Nikita Danilov
2004-07-16 17:45 ` David Dabbs
2004-07-18 7:11 ` Hans Reiser
2004-07-18 7:47 ` David Dabbs
2004-07-19 4:23 ` David Masover
2004-07-19 7:21 ` David Dabbs
2004-07-19 21:34 ` David Masover
2004-07-19 22:06 ` Valdis.Kletnieks
2004-07-19 22:32 ` David Dabbs
2004-07-20 6:03 ` Hans Reiser
2004-07-20 7:03 ` David Masover
2004-07-20 5:30 ` Hans Reiser
2004-07-20 7:07 ` David Masover
2004-07-20 8:31 ` David Dabbs
2004-07-21 5:13 ` David Masover
2004-07-21 5:44 ` David Dabbs
2004-07-21 6:20 ` David Masover
2004-07-21 6:36 ` David Dabbs
2004-07-21 8:32 ` mjt
2004-07-22 4:08 ` David Masover
2004-07-22 10:06 ` mjt
2004-07-22 18:14 ` Hans Reiser
2004-07-23 2:45 ` David Masover
2004-07-23 9:42 ` mjt
2004-07-23 18:21 ` David Masover
2004-07-22 10:10 ` Vitaly Fertman
2004-07-23 2:43 ` David Masover
2004-07-23 9:09 ` Vitaly Fertman
2004-07-26 6:28 ` Hans Reiser [this message]
2004-07-26 10:11 ` Vitaly Fertman
2004-07-23 9:59 ` Christian Mayrhuber
2004-07-23 9:59 ` mjt
2004-07-23 18:13 ` David Masover
2004-07-23 10:05 ` mjt
2004-07-22 8:03 ` Hans Reiser
2004-07-22 12:16 ` Nikita Danilov
2004-07-22 14:39 ` mjt
2004-07-22 18:17 ` Hans Reiser
2004-07-22 18:26 ` mjt
2004-07-22 19:57 ` Valdis.Kletnieks
2004-07-22 21:05 ` mjt
2004-07-22 21:36 ` Valdis.Kletnieks
2004-07-23 9:28 ` mjt
2004-07-23 22:42 ` Valdis.Kletnieks
2004-07-23 2:40 ` David Masover
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=4104A488.2060103@namesys.com \
--to=reiser@namesys.com \
--cc=david@dabbs.net \
--cc=mjt@nysv.org \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.