From owner-freebsd-hackers Tue Jun 18 08:09:54 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA02312 for hackers-outgoing; Tue, 18 Jun 1996 08:09:54 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA02268 for ; Tue, 18 Jun 1996 08:09:13 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id LAA03349 for ; Tue, 18 Jun 1996 11:15:38 -0400 Date: Tue, 18 Jun 1996 11:15:38 -0400 Message-Id: <199606181515.LAA03349@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: hackers@freebsd.org From: dennis@etinc.com (Dennis) Subject: Re: BSDI 2.0 vs. FreeBSD 2.x Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Karl, knowing you from the days of ISC I'm surprised you would >> give BSDI that much slack. I hardly think that an OS lacking >> a 'lockd' qualifies as an NFS server. Try juggling a network >> of BSDI NFS realestate in a network of machines that can >> actually do file locking... not fun. > >NOBODY does NFS file locking properly. NOBODY. > >Trust me on this -- 10+ years of experience with this beast has convinced me >that absolutely no one has implemented NFS locking in a manner that I would >trust for anything mission critical. So I don't. > >> I too was stunned by my recent BSDI pricing... only a matter of time. another point for Novell! Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX