From: Vitaly Fertman <vitaly@namesys.com>
To: "David Masover" <ninja@slaphack.com>, "Markus Törnqvist" <mjt@nysv.org>
Cc: David Dabbs <david@dabbs.net>, reiserfs-list@namesys.com
Subject: Re: Fibration questions
Date: Thu, 22 Jul 2004 14:10:25 +0400 [thread overview]
Message-ID: <200407221410.25043.vitaly@namesys.com> (raw)
In-Reply-To: <40FF3DAD.6020100@slaphack.com>
> First question: Can I manually enable/disable a particular plugin for a
> particular directory? (like how cryptocompress is supposed to be...)
you can change a plugin for a file if it does not destroy its structure.
Thus for an empty directory you can :
# cat somedir/metas/plugin/hash ; echo
1 r5 r5 hash
# echo -e "tea\0" > somedir/metas/plugin/hash
# cat somedir/metas/plugin/hash ; echo
2 tea tea hash
> Second question: Would such a setting be recursive? Can I tell it
> whether to recurse or not?
plugins are inherited at the creation time from the parent of the object
being created. Thus in the above example all subdirs would have the
hash r5 before changing the 'somedir' hash to 'tea' and will have the
'tea' hash after.
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2004-07-22 10:10 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 [this message]
2004-07-23 2:43 ` David Masover
2004-07-23 9:09 ` Vitaly Fertman
2004-07-26 6:28 ` Hans Reiser
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=200407221410.25043.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=david@dabbs.net \
--cc=mjt@nysv.org \
--cc=ninja@slaphack.com \
--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.