From owner-freebsd-fs Wed Nov 1 21: 1:13 2000 Delivered-To: freebsd-fs@freebsd.org Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by hub.freebsd.org (Postfix) with ESMTP id DD07137B4C5 for ; Wed, 1 Nov 2000 21:01:11 -0800 (PST) Received: from shekel.mcl.cs.columbia.edu (shekel.mcl.cs.columbia.edu [128.59.18.15]) by cs.columbia.edu (8.9.3/8.9.3) with ESMTP id AAA11430; Thu, 2 Nov 2000 00:01:09 -0500 (EST) Received: (from ezk@localhost) by shekel.mcl.cs.columbia.edu (8.9.3/8.9.3) id AAA11555; Thu, 2 Nov 2000 00:01:09 -0500 (EST) Date: Thu, 2 Nov 2000 00:01:09 -0500 (EST) Message-Id: <200011020501.AAA11555@shekel.mcl.cs.columbia.edu> From: Erez Zadok To: Alex Povolotsky Cc: Erez Zadok , freebsd-fs@FreeBSD.ORG Subject: Re: crypto fs? In-reply-to: Your message of "Tue, 31 Oct 2000 18:44:07 +0300." <20001031184407.P81831@mail.over.ru> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20001031184407.P81831@mail.over.ru>, Alex Povolotsky writes: > On Fri, Sep 29, 2000 at 01:03:26PM -0400, Erez Zadok wrote: > > Mine in the only known (so far :-) working stackable compression f/s. My > > templates (Linux only) can do arbitrary size-changing f/s: I have a working > > gzipfs, uuencodefs, etc. See http://www.cs.columbia.edu/~ezk/research/fist/ > ... and what is with FreeBSD FiST? Does anyone working on it? > > Alex. It's been working as of 3.3, but with my stacking template that had to work around the VFS problems. Certainly cryptfs is working. I've not done a full port using the latest nullfs yet, which, I understand uses the fixed VFS. Erez. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message