From owner-freebsd-questions Sat Feb 10 10:57:19 2001 Delivered-To: freebsd-questions@freebsd.org Received: from crunch.shivakaul.com (unknown [166.84.151.100]) by hub.freebsd.org (Postfix) with SMTP id 5F37537B69F for ; Sat, 10 Feb 2001 10:56:45 -0800 (PST) Received: (qmail 91651 invoked by uid 0); 10 Feb 2001 00:02:23 -0000 Received: from unknown (HELO taco) (192.168.0.2) by 166.84.151.100 with SMTP; 10 Feb 2001 00:02:23 -0000 Message-ID: <001401c09394$205a3700$0200a8c0@taco> From: "shivak" To: "freebsd-questions" Subject: NFS and SFS - alternatives? Date: Sat, 10 Feb 2001 14:03:17 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soon, I will be implementing a network where network-exported filesystems are a crucial component of functionality. Naturally, I looked to NFS as a solution, but I have heard of many people having problems with it (i'm basically worried about performance and security). Somebody told me about SFS (http://www.fs.net), and i thought, "hey, self certifying cryptographic network file system? cool!" But I'm not sure about the actual protocol. Taken from the SFS manual: "The SFS read-write server software requires each SFS server to run an NFS server." Is this SFS thing just an addon to NFS? huh? In the end, I'm quite confused. I'm just a guy looking for a good network exportable file system. I'm not that worried about cryptography, I'm more concerned with inherent problems in the protocols themselves. I'm sure that some of you have had some experience with this. What do you suggest? Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message