From owner-freebsd-current Tue Apr 29 11:15:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00403 for current-outgoing; Tue, 29 Apr 1997 11:15:10 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00398 for ; Tue, 29 Apr 1997 11:15:06 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id TAA01591; Tue, 29 Apr 1997 19:14:34 +0100 (BST) Date: Tue, 29 Apr 1997 19:14:34 +0100 (BST) From: Doug Rabson To: "Louis A. Mamakos" cc: current@freebsd.org Subject: Re: latest -current upgrade and CFS In-Reply-To: <199704291540.LAA02695@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 29 Apr 1997, Louis A. Mamakos wrote: > > CFS is the crypto filesystem that Matt Blaze did. Essentially, you > talk to it via NFS and it decrypts/encrypts files on the fly which are > stored elsewhere in the UNIX filesystem. > > I just upgraded my system running an older -current to the version > checkout as of last night. My cfsd stopped working; it appears the > the NFSv3 default is the cause of this problem, and the > "auto-fallback" to NFSv2 mechansim doesn't work with cfs. I had to > add the '-2' option to the mount command to get things working; I > recompiled cfsd for good measure too. I will look into it soon. Where can I get a copy of CFS? > Note that this still requires the one-line fix to correctly parse > mount options with parameters, like the 'port=3049', in the file > /usr/src/sbin/mount/getmntopts.c. I submitted a PR on this on quite a > while ago: Can you remember the PR number? The fix looks good, so I will probably commit it tomorrow. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891