From owner-freebsd-hackers  Mon Jun 17 18:33:40 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA15020
          for hackers-outgoing; Mon, 17 Jun 1996 18:33:40 -0700 (PDT)
Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA15013
          for <hackers@freebsd.org>; Mon, 17 Jun 1996 18:33:35 -0700 (PDT)
Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id UAA06171; Mon, 17 Jun 1996 20:33:13 -0500 (CDT)
Message-Id: <199606180133.UAA06171@sierra.zyzzyva.com>
To: "Karl Denninger, MCSNet" <karl@mcs.com>
cc: dennis@etinc.com (Dennis), hackers@freebsd.org
Subject: Re: BSDI 2.0 vs. FreeBSD 2.x 
In-reply-to: karl's message of Mon, 17 Jun 1996 11:22:02 -0500.
         <m0uVh3y-000IDOC@venus.mcs.com> 
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 17 Jun 1996 20:33:08 -0500
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


> BSDI has priced themselves out of the game, and their support, of late at
> least, has IMHO stunk.
> 
> I was one of their original evangalizers many years ago when they first got
> going.  The primary reason wasn't the code; their code is ok, but nothing
> spectacular.  The primary reason was support.
> 
> Recently, in the past few months, that has evaporated.  There have also been
> price increases which make BSDI non-viable in many environments.
> 
> The sole area where they hold a stability advantage, IMHO, is in the area of
> NFS file service.  But certainly, if you have 10 licenses, you could use
> those for your NFS file servers and run the rest of your plant on FreeBSD.
> 
> That is basically the strategy we are taking here.  Within another few
> months the only places you're likely to see BSDI is in the NFS file service
> arena -- unless FreeBSD gets those problems resolved first, in which case
> we'll have a gecko-killing contest.

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.

I too was stunned by my recent BSDI pricing... only a matter of time.