From: Edward Shishkin <edward@namesys.com>
To: Ben Martin <monkeyiq@users.sourceforge.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Selecting unixfile plugin
Date: Mon, 05 Jun 2006 13:21:21 +0400 [thread overview]
Message-ID: <4483F791.7020608@namesys.com> (raw)
In-Reply-To: <1149491181.3926.59.camel@sam>
Ben Martin wrote:
>Hi,
>
>
Hello
> After much digging around as to how to use the reiser4 compression
>plugin I have found this message.
>http://marc.theaimsgroup.com/?l=reiserfs&m=113190018626958&w=2
>
>I'm using 2.6.15 + resier4 + metas patches.
>
>I'm trying to set the default plugin to cryptcompress for a directory in
>a r4 filesystem.
>
>It seems that the plugins/regular is thought to be a directory when I
>echo "cryptcompress\0" >|plugins/regular
>
>Trying various combinations of things inside regular/ like echoing into
>label etc don't seem to have an effect when read back again.
>
>It seems from the below link and grepping the 2.6.15 reiser4 patch that
>echoing "cryptcompress" >| mydir/..../plugins/regular/label
>should make new files in mydir use the cryptcompress plugin by defualt.
>http://www.namesys.com/cryptcompress-related_plugins.html
>
>The info like http://www.namesys.com/cryptcompress_design.html seems to
>be targetted toward developers rather than users. Are there any
>references or logs of command line interactions to enable and tweak
>compression/crypto aimed at end user consumption?
>
>
>
Yes, it is. Although this stuff should be qualified as experimental.
If you have spare disk space and another box with serial connection,
then we will send you the setup..
Edward.
>Also from what I've seem a
>sed s/metas/..../g
>might be in order for
>http://www.namesys.com/v4/pseudo.html
>
>
>
>
next prev parent reply other threads:[~2006-06-05 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 7:06 Selecting unixfile plugin Ben Martin
2006-06-05 9:21 ` Edward Shishkin [this message]
2006-06-05 9:35 ` Ben Martin
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=4483F791.7020608@namesys.com \
--to=edward@namesys.com \
--cc=monkeyiq@users.sourceforge.net \
--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.