From owner-freebsd-isp Wed Jun 5 05:55:09 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA25441 for isp-outgoing; Wed, 5 Jun 1996 05:55:09 -0700 (PDT) Received: from ptavv.nsta.org (ptavv.gfoster.com [199.0.2.254]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA25432 for ; Wed, 5 Jun 1996 05:55:05 -0700 (PDT) Received: (from gfoster@localhost) by ptavv.nsta.org (8.7.5/8.6.12) id IAA00308; Wed, 5 Jun 1996 08:54:46 -0400 (EDT) Date: Wed, 5 Jun 1996 08:54:46 -0400 (EDT) From: Glen Foster Message-Id: <199606051254.IAA00308@ptavv.nsta.org> To: coventry@io.org CC: freebsd-isp@freebsd.org In-reply-to: <199606051141.HAA01264@io.org> (coventry@io.org) Subject: Re: feature list Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Caveat: My experience with Solaris has been mostly on Sparcs, not on Intel. I have about six years of experience with Sparcs (SunOs and Solaris) and aboiut four with Unix on Intel (SCO, UnixWare, Solaris, FreeBSD, BSD/OS, and others). I am not an ISP but I do Unix consulting for several ISPs in the Washington DC area and their customers. These ISPs typically use BSD/OS, Solaris, and FreeBSD in about that order of popularity. The ones who are using FreeBSD have the fewest recurring problems and spend the least amount of time fussing with their internal systems, Solaris is the worst of the three for reliability. WRT the specific applications you list below, both OS's run them fine and they all build "out of the box." However, Solaris is wedded to NIS. If you choose not to run NIS, once in a while a host lookup non-event will catch you by surprise (e.g. a `who` will not return a hostname but an IP address instead). Nothing fatal but it can be annoying. Also, Solaris is not as complete as FreeBSD (e.g. FreeBSD allows you to see what each sendmail process is doing when you run the ps(1) command, Solaris doesn't). FreeBSD is significantly less memory hungry and faster on the same hardware. This is especially noticeable in X windows. OTOH, there are lots of commercial apps for Solaris and very few for FreeBSD. One other factor that may be of importance, the FreeBSD core team has made it easy to have all upgrades and patches be applied to your system over the net (see the CTM and sup docs). This is in stark contrast to Sun whose OS patch system is painful. WRT installation, I have done both over-the-net and cdrom installs. Both work fine but I prefer the cdrom especially on a slow net connection. If I was installing on a system without a cdrom, I would use the net rather than install a cdrom drive, it is really easy and almost bullet-proof. Buy the cdrom, you will sleep better at nights knowing that you can reinstall part or all of your system without needing net resources. >Date: Wed, 5 Jun 1996 07:41:54 -0400 >From: coventry@io.org (graydon hoare) > >Hi y'all. I know there is an official FAQ feature list, but I am >attempting to gather information to present an accurate comparison >between FreeBSD and Solaris/x86 as ISP OSs'... > >Was wondering if anyone could confirm for sure the day-to-day operation of the >following services under FreeBSD and possibly comment on their ease-of-build >and reliability, either alone or in comparison to Solaris/x86 if you have >experience with it: > >BIND/NAMED >GATED/ROUTED >Usenet/INN/UUCP >Sendmail/SMTP >Apache/HTTPD >Ftp/TFTPD/FTPD > >Also: has anyone loaded their OS from the network or have you found the >CDROM from walnut creek to be a better route?