From owner-freebsd-questions Mon Jul 14 04:57:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA16078 for questions-outgoing; Mon, 14 Jul 1997 04:57:57 -0700 (PDT) Received: from pompano.pcola.gulf.net (root@pompano.pcola.gulf.net [198.69.72.14]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA16070 for ; Mon, 14 Jul 1997 04:57:53 -0700 (PDT) Received: from localhost (spatula@localhost.gulf.net [127.0.0.1]) by pompano.pcola.gulf.net (8.8.6/8.7.3) with SMTP id GAA07897; Mon, 14 Jul 1997 06:57:48 -0500 (CDT) Date: Mon, 14 Jul 1997 06:57:48 -0500 (CDT) From: Nick Johnson X-Sender: spatula@pompano.pcola.gulf.net To: Wes Peters - Softweyr LLC cc: questions@FreeBSD.ORG Subject: Re: A few solutions In-Reply-To: <199707140404.WAA07219@xmission.xmission.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 13 Jul 1997, Wes Peters - Softweyr LLC wrote: > Parity RAM won't prevent errors from happening, it will just tell you > when they do. The system will respond by rebooting, which really > doesn't get you much. You probably just ended up with better (or faster) > RAM than what you had before. I guess my point really was that replacing the RAM did the trick. I used parity RAM so that if anything runs amok again, I'll know for sure if it is the RAM or not (or I can at least make a better guess than I could before) Nick -- "Oh yeah? Well, you're ugly." - Me, to Steve Boursy of news.admin.censorship Nick Johnson, version 1.0 http://www.pcola.gulf.net/~spatula/