From owner-freebsd-current  Tue Sep 17 21:14:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA29935
          for current-outgoing; Tue, 17 Sep 1996 21:14:08 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA29906
          for <current@FreeBSD.org>; Tue, 17 Sep 1996 21:14:04 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id VAA09862; Tue, 17 Sep 1996 21:14:01 -0700 (PDT)
Date: Tue, 17 Sep 1996 21:14:01 -0700 (PDT)
Message-Id: <199609180414.VAA09862@silvia.HIP.Berkeley.EDU>
To: rgrimes@GndRsh.aac.dev.com, current@FreeBSD.org
In-reply-to: <199609180354.UAA09793@silvia.HIP.Berkeley.EDU> (asami@FreeBSD.org)
Subject: Re: RAM parity error
From: asami@FreeBSD.org (Satoshi Asami)
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

 * From: asami@FreeBSD.org (Satoshi Asami)

 * I've done this many times on this machine, both with and without ccd.
 * Also, it's been compiling most of packages-current recently, and it
 * can run like 4 simultaneous compilations without even flinching.

Well, I guess I spoke a litte too soon.  I just started two
compilations (xemacs and wine) and it crashed.  I'm not sure why it
worked before, maybe it's the particular combination of processes
(patch on one, tar on the other) or the disk (it's using a Quantum 4GB 
Atlas now, it was using an array of 4GB Seagates before).

Satoshi