From owner-freebsd-hardware Mon Aug 7 23: 2:41 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id C854837B946 for ; Mon, 7 Aug 2000 23:02:36 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id DD1412B295; Tue, 8 Aug 2000 01:02:35 -0500 (CDT) Date: Mon, 7 Aug 2000 23:02:35 -0700 From: Paul Saab To: Simon Cc: "freebsd-hardware@FreeBSD.ORG" Subject: Re: What happened? Message-ID: <20000807230235.A96603@elvis.mu.org> References: <20000807224818.B96386@elvis.mu.org> <200008081323.HAA51096@mail.fpsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200008081323.HAA51096@mail.fpsn.net>; from simon@optinet.com on Tue, Aug 08, 2000 at 01:56:55AM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Simon (simon@optinet.com) wrote: > Hmmm... you are not allowed to use a dos boot up disk to boot > and upgrade? strange. Uhm, doesn't write cache speed things up, > though? I'm not using softupdates to avoid data loss during crashes > (if any should occur). Bad RAM caused so much problems in the past for > us. Took a while to figure out it was RAM. If I could get freebsd box > to not crash under heavy load for 6+ months, I would be the happiest > man. Maybe I'm getting there, don't know yet. Umm, we build so many machines in a day, it would take a lot of time to boot into dos and upgrade the firmware. We've also made sure we get the correct firmware when we order drives, so this solution is to fix machines already out in production and on drives we dont have corrected firmwares. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message