From owner-freebsd-hackers Tue Jun 18 19:40:07 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA19171 for hackers-outgoing; Tue, 18 Jun 1996 19:40:07 -0700 (PDT) Received: from kitsune.swcp.com (swcp.com [198.59.115.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA19149 for ; Tue, 18 Jun 1996 19:40:02 -0700 (PDT) Received: from localhost.swcp.com (lundin.abq.nm.us [198.59.115.228]) by kitsune.swcp.com (8.6.9/8.6.9) with ESMTP id UAA11577 for ; Tue, 18 Jun 1996 20:40:00 -0600 Received: (from aflundi@localhost) by localhost (8.6.12/8.6.12) id UAA03501 for hackers@freebsd.org; Tue, 18 Jun 1996 20:09:24 -0600 Date: Tue, 18 Jun 1996 20:09:24 -0600 From: Alan Lundin Message-Id: <199606190209.UAA03501@localhost> In-Reply-To: "Karl Denninger, MCSNet" "Re: BSDI 2.0 vs. FreeBSD 2.x" (Jun 17, 11:22am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: hackers@freebsd.org Subject: Re: BSDI 2.0 vs. FreeBSD 2.x Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Jun 17, 11:22am, "Karl Denninger, MCSNet" wrote: > Subject: Re: BSDI 2.0 vs. FreeBSD 2.x > [ ... ] > 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. Why not, instead, purchase a cool NFS file server like the Network Appliance "toaster"? (Check out http://www.netapp.com/.) It'll give you features and performance that you'll be hard pressed to find on a Unix (or any general purpose OS, for that matter) machine, and shouldn't cost that much. --alan