From owner-freebsd-hackers Mon Jun 24 06:23:15 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA20529 for hackers-outgoing; Mon, 24 Jun 1996 06:23:15 -0700 (PDT) Received: from seagull.rtd.com (root@seagull.rtd.com [198.102.68.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA20524 for ; Mon, 24 Jun 1996 06:23:13 -0700 (PDT) Received: (from dgy@localhost) by seagull.rtd.com (8.7.5/1.2) id GAA29600; Mon, 24 Jun 1996 06:23:01 -0700 (MST) From: Don Yuniskis Message-Id: <199606241323.GAA29600@seagull.rtd.com> Subject: Re: Memory tests ... To: jsigmon@www.hsc.wvu.edu (Jeremy Sigmon) Date: Mon, 24 Jun 1996 06:23:01 -0700 (MST) Cc: hua@XENON.chromatic.com, hackers@freebsd.org In-Reply-To: from "Jeremy Sigmon" at Jun 24, 96 08:17:53 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings! > According to the systems people around here, the best way to test memory is > to put it into a Novell server. If the memory is flakey it will let > you know fast. (ABEND???) > I thinks someone around here has a 4.1 2 user box setup just for that > purpose. Are people looking for *exhaustive* tests, "quick and dirty" tests, diagnostic tests, or what? There are different solutions for each of these. But I think just the "make world" style tests add very little value (tho' prehaps, they are probably easiest to invoke...) --don