From owner-freebsd-hackers Fri Mar 17 10:33:11 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA05470 for hackers-outgoing; Fri, 17 Mar 1995 10:33:11 -0800 Received: from goof.com (root@goof.com [198.82.204.15]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA05460 for ; Fri, 17 Mar 1995 10:33:09 -0800 Received: (from mmead@localhost) by goof.com (8.6.11/8.6.9) id NAA08414 for hackers@freebsd.org; Fri, 17 Mar 1995 13:32:53 -0500 From: "matthew c. mead" Message-Id: <199503171832.NAA08414@goof.com> Subject: Non Parity Ram To: hackers@FreeBSD.org Date: Fri, 17 Mar 1995 13:32:52 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 490 Sender: hackers-owner@FreeBSD.org Precedence: bulk What will FreeBSD do with Non Parity ram? I have some of this. I haven't been getting parity errors or anything, but I'm kind of curious if it's going to cause problems... -matt -- Matthew C. Mead -> Virginia Tech Center for Transportation Research - -> Multiple Platform System and Network Administration Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other ---- ------- WWW -> http://www.goof.com/~mmead --- -----