From owner-freebsd-isp Fri Mar 23 16:57:46 2001 Delivered-To: freebsd-isp@freebsd.org Received: from luke.cpl.net (luke.cpl.net [63.169.72.3]) by hub.freebsd.org (Postfix) with ESMTP id D407437B719 for ; Fri, 23 Mar 2001 16:57:44 -0800 (PST) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.9.3/8.9.3) id QAA34901; Fri, 23 Mar 2001 16:57:43 -0800 (PST) Date: Fri, 23 Mar 2001 16:57:43 -0800 From: Shawn Ramsey To: Jim King Cc: Ed Henderson , freebsd-isp@FreeBSD.ORG, "'Bob Martin'" Subject: Re: Good server motherboard? Message-ID: <20010323165743.B57362@cpl.net> References: <001c01c0b3ea$df109920$0464a8c0@pnt004> <001501c0b3f5$f40b8910$04e48486@marble> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001501c0b3f5$f40b8910$04e48486@marble>; from jim@jimking.net on Fri, Mar 23, 2001 at 06:04:09PM -0600 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Mar 23, 2001 at 06:04:09PM -0600, Jim King wrote: > "Ed Henderson" wrote: > >I plan to use AMD Athlon chips, tower case, IDE drives/peripherals, > >at least 256MB RAM. Budget is limited since we are just beginning: > >approx. $1300 per server (not including tape drive which is seperate > >see #3 below). Servers will host typical ISP apps: DNS, RADIUS, > >mail, Apache, etc. > > When I looked a couple months ago none of the Athlon motherboards supported > ECC memory. Considering the amount of potential grief you'll avoid by using > ECC memory I'd say that Athlon shouldn't be considered. :-( > > Jim Perhaps that was true then, certainly not now. Besides, I have never seen a problem caused by using non-ECC memory. Thats not to say that ECC memory shouldn't be used, but from what I have seen it is an unneccesary expense. Though I do believe the most RAM you can currently get on an Athlon MB is 2GB, so if you need more than that your out of luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message