From: Hans Reiser <reiser@namesys.com>
To: Mathieu Segaud <matt@minas-morgul.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Crypto(compress) plugin stability
Date: Thu, 12 Aug 2004 11:46:40 -0700 [thread overview]
Message-ID: <411BBB10.5020308@namesys.com> (raw)
In-Reply-To: <87isbogqfs.fsf@barad-dur.crans.org>
Mathieu Segaud wrote:
>Hi !
>
>I've got a question about Reiser4 encryption ? Is it stable enough to run
>other things than test run or benchmarks ? :)
>
>
No.
>I'm curently running my desktop box with several partitions encrypted thru
>dm-crypt. I know pros of Reiser4, which are: encryption at flush time,
>selection of files to be encrypted, speed of Reiser4 :)
>But are there problems with this plugin ? Is it stable enough to be trustworthy ?
>(I'm used to living on the bleeding edge, with my linux boxes)
>
>
Wait a few, ok?
>I'm willing to switch but do I risk serious damages to my system :))) ?
>(I know I do, but I do not stress it a lot)
>
>Regards
>
>
>
next prev parent reply other threads:[~2004-08-12 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 18:29 Crypto(compress) plugin stability Mathieu Segaud
2004-08-12 18:46 ` Hans Reiser [this message]
2004-08-13 6:02 ` Edward Shishkin
2004-08-12 19:30 ` Mathieu Segaud
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=411BBB10.5020308@namesys.com \
--to=reiser@namesys.com \
--cc=matt@minas-morgul.org \
--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.