EcryptFS development
 help / color / mirror / Atom feed
From: Lance Reed <reed.r.lance@gmail.com>
To: ecryptfs@vger.kernel.org
Subject: Re: Can anyone confirm or deny if ecryptfs will work with a glusterfs backend?
Date: Wed, 26 Feb 2014 18:35:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140226T193240-335@post.gmane.org> (raw)
In-Reply-To: 20140226180044.GA5056@boyd

Tyler,

Thanks for the response!
Red Hat Enterprise Linux Server release 6.4 (Santiago) (and Centos 6.4)
2.6.32-358.14.1.el6.x86_64

I am actually planning to use this in a cloud setup.  Mostly for an internal
shared NFS like but HA space.
I had thought HekaFS had gone a bit dormant...(not a lot of talk since May
2013...)
I will look at it again.  Thanks for the tip and taking a look.
Any thought would be greatly appreciated.

Cheers,

Lance


If this is a double post, I apologize.. oddness on email vs web interface:





  reply	other threads:[~2014-02-26 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 16:06 Can anyone confirm or deny if ecryptfs will work with a glusterfs backend? Lance Reed
2014-02-26 18:00 ` Tyler Hicks
2014-02-26 18:35   ` Lance Reed [this message]
2014-02-26 19:56     ` Tyler Hicks

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=loom.20140226T193240-335@post.gmane.org \
    --to=reed.r.lance@gmail.com \
    --cc=ecryptfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox