From owner-freebsd-questions@FreeBSD.ORG Wed Mar 1 07:48:10 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1CDE16A420 for ; Wed, 1 Mar 2006 07:48:10 +0000 (GMT) (envelope-from corwin@aeternal.net) Received: from amber.aeternal.net (amber.in.markiza.sk [62.168.76.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 110E943D45 for ; Wed, 1 Mar 2006 07:48:09 +0000 (GMT) (envelope-from corwin@aeternal.net) Received: from localhost (localhost.aeternal.net [127.0.0.1]) by amber.aeternal.net (Postfix) with ESMTP id B0E9BB91B for ; Wed, 1 Mar 2006 08:48:07 +0100 (CET) Received: from amber.aeternal.net ([127.0.0.1]) by localhost (amber.aeternal.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04607-02 for ; Wed, 1 Mar 2006 08:48:07 +0100 (CET) Received: from [192.168.0.30] (pleiades.aeternal.net [192.168.0.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by amber.aeternal.net (Postfix) with ESMTP id 36267B917 for ; Wed, 1 Mar 2006 08:48:07 +0100 (CET) Message-ID: <440551B7.3070400@aeternal.net> Date: Wed, 01 Mar 2006 08:48:07 +0100 From: Martin Hudec User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <058101c63ca5$585d0780$0300020a@mickey> In-Reply-To: <058101c63ca5$585d0780$0300020a@mickey> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at aeternal.net Subject: Re: System Burn In X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: corwin@aeternal.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 07:48:10 -0000 Hello, Don O'Neil wrote: > What is the best way to 'burn in' or 'stress test' a new system w/ FreeBSD? > I'd like to stress test the CPU, Memory, Disk, etc.. To make sure the > hardware is 100% good before putting it in production. You want to test hardware, not OS, so I would recommend you to use: http://www.ultimatebootcd.com/ Martin