Date: Mon, 17 Jun 1996 14:41:35 -0400 From: dennis@etinc.com (Dennis) To: "Karl Denninger, MCSNet" <karl@mcs.com> Cc: hackers@freebsd.org Subject: Re: BSDI 2.0 vs. FreeBSD 2.x Message-ID: <199606171841.OAA01559@etinc.com>
next in thread | raw e-mail | index | archive | help
>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. True, however BSD is marketing themselves as an internet gateway, where NFS is not as important. And now that FreeBSD has a Netware compatible server available....the option to dump NFS (which I really dont want to use on my Windows workstations anyways) is more than viable. The Netware stuff (although not free) is a lot nicer (and faster) than NFS. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606171841.OAA01559>