From owner-freebsd-questions Mon Nov 24 08:41:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA14216 for questions-outgoing; Mon, 24 Nov 1997 08:41:57 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from cerberus.partsnow.com (gatekeeper.partsnow.com [207.155.26.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA14204 for ; Mon, 24 Nov 1997 08:41:53 -0800 (PST) (envelope-from don@PartsNow.com) Received: (from bin@localhost) by cerberus.partsnow.com (8.8.5/8.6.9) id IAA29522; Mon, 24 Nov 1997 08:40:10 -0800 (PST) X-Authentication-Warning: cerberus.partsnow.com: bin set sender to using -f Received: from nouvelle(192.168.100.9) by cerberus.partsnow.com via smap (V2.0) id xma029519; Mon, 24 Nov 97 08:40:06 -0800 Message-ID: <3479ADC9.3B24@PartsNow.com> Date: Mon, 24 Nov 1997 08:39:37 -0800 From: Don Wilde Reply-To: don@PartsNow.com Organization: Soligen, Incorporated X-Mailer: Mozilla 3.0C-E-KIT (Win16; I) MIME-Version: 1.0 To: techweb@cmp.com CC: questions@freebsd.org Subject: Sean Fulton's OS holy wars article Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Please repeat this article with a little 'fine tuning' added. Kernel rebuilding is a minor task in FreeBSD and is part of its installation and no more difficult than any other part. It takes only a few minutes to configure the kernel build config file to recognize your memory, and less than an hour (on a P150 w/64 mb, not your steroid machines) to recompile and install. I think that's a lot less programmer time than NT'ds menus take, let alone their config files. That done, my P150 could blow any of your PPro180's off the block as a webserver. I should add that I am not a UNIX guru, have only been using FreeBSD for less than 2 years as a small portion of my job. That said, the article was reasonably unbiased and well written. I enjoyed its insightful comparisons, and learned perhaps a little of what I'm missing by not buying BSDi or SCO, although I'd be missing a whole lot of cash, too. I think that fairness would dictate that you do a follow-up that allows each server to be tweaked by its OS experts for 6 hours (by hand... no super turn-it-inside-out scripts) after being installed out-of-the-box, and then re-run your tests. You also should stipulate that there be no asynchronous disk writes unless everybody is allowed to do so. Linux uses async mounting, and it gives them a catch-up but it is dangerous on a real-world server, no matter how good your UPS. Again, thanks for the mention of FreeBSD! -- oooOOO O O O o * * * * * * o ___ _________ _________ ________ _________ _________ ___==_ V_=_=_DW ===--- Don Wilde [don@PartsNow.com] [http://www.PartsNow.com ] /oo0000oo-oo--oo-ooo---ooo-ooo---ooo-ooo--ooo-ooo---ooo-ooo---ooo-oo--oo