From: Adam Sampson <azz@us-lot.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Encrypted Filesystem
Date: Tue, 27 Jan 2004 00:43:21 +0000 [thread overview]
Message-ID: <y2ar7xmkyqe.fsf@cartman.at.fivegeeks.net> (raw)
In-Reply-To: <OFA97B290B.67DE842E-ON87256E27.0061728C-86256E27.0061BB0E@us.ibm.com> (Michael A. Halcrow's message of "Mon, 26 Jan 2004 11:46:29 -0600")
Michael A Halcrow <mahalcro@us.ibm.com> writes:
> - Userland filesystem-based (EncFS+FUSE, CryptoFS+LUFS)
Going off on a tangent...
There are all sorts of potentially-interesting things that could be
done if Linux had a userspace filesystem mechanism included in the
standard kernel -- as well as encryption, there's also network
filesystems, various sorts of specialised caching (such as Zero
Install), automounter-like systems, prototyping and so on.
Is there a technical reason that none of the userspace filesystem
layers have been included in the stock kernel, or is it just that
nobody's submitted any of them for inclusion yet?
--
Adam Sampson <azz@us-lot.org> <http://offog.org/>
next prev parent reply other threads:[~2004-01-27 0:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 17:46 Michael A Halcrow
2004-01-26 19:06 ` Mark Borgerding
2004-01-26 21:04 ` Felipe Alfaro Solana
2004-01-30 17:01 ` Pavel Machek
2004-01-27 0:06 ` jw schultz
2004-01-27 0:43 ` Adam Sampson [this message]
2004-01-27 1:42 ` Andy Isaacson
2004-01-27 22:01 ` Jan Harkes
2004-01-27 22:16 ` Jean-Luc Cooke
2004-01-28 13:50 ` Userspace filesystems (WAS: Encrypted Filesystem) Miklos Szeredi
2004-01-30 17:06 ` Pavel Machek
2004-02-02 9:42 ` Miklos Szeredi
2004-02-02 15:19 ` Pavel Machek
2004-02-02 15:36 ` Nikita Danilov
[not found] <16405.24299.945548.174085@laputa.namesys.com>
2004-01-26 19:02 ` Encrypted Filesystem Hans Reiser
2004-01-27 18:56 ` Edward Shishkin
2004-01-27 21:25 ` Michael Halcrow
2004-01-27 21:51 ` Hans Reiser
[not found] <OFA97B290B.67DE842E-ON87256E27.0061728C-86256E27.0061BB0E@us.ibm.com.suse.lists.linux.kernel>
2004-01-27 16:13 ` Andi Kleen
2004-01-27 18:17 ` Jari Ruusu
2004-01-27 18:44 ` Andi Kleen
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=y2ar7xmkyqe.fsf@cartman.at.fivegeeks.net \
--to=azz@us-lot.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®