Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265608AbUA0Anb (ORCPT ); Mon, 26 Jan 2004 19:43:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265611AbUA0Anb (ORCPT ); Mon, 26 Jan 2004 19:43:31 -0500 Received: from greendale.ukc.ac.uk ([129.12.21.13]:9667 "EHLO greendale.ukc.ac.uk") by vger.kernel.org with ESMTP id S265608AbUA0Ana (ORCPT ); Mon, 26 Jan 2004 19:43:30 -0500 To: linux-kernel@vger.kernel.org Subject: Re: Encrypted Filesystem References: From: Adam Sampson Organization: Things I did not know at first I learned by doing twice. Date: Tue, 27 Jan 2004 00:43:21 +0000 In-Reply-To: (Michael A. Halcrow's message of "Mon, 26 Jan 2004 11:46:29 -0600") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-UKC-Mail-System: No virus detected Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 962 Lines: 23 Michael A Halcrow 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/