From owner-freebsd-stable@FreeBSD.ORG  Mon Jun 26 21:27:04 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@FreeBSD.ORG
Delivered-To: freebsd-stable@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D863216A401
	for <freebsd-stable@FreeBSD.ORG>; Mon, 26 Jun 2006 21:27:04 +0000 (UTC)
	(envelope-from wb@freebie.xs4all.nl)
Received: from smtp-vbr3.xs4all.nl (smtp-vbr3.xs4all.nl [194.109.24.23])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 442E743D8E
	for <freebsd-stable@FreeBSD.ORG>; Mon, 26 Jun 2006 21:27:04 +0000 (GMT)
	(envelope-from wb@freebie.xs4all.nl)
Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253])
	by smtp-vbr3.xs4all.nl (8.13.6/8.13.6) with ESMTP id k5QLQtTO037044;
	Mon, 26 Jun 2006 23:27:00 +0200 (CEST)
	(envelope-from wb@freebie.xs4all.nl)
Received: from freebie.xs4all.nl (localhost [127.0.0.1])
	by freebie.xs4all.nl (8.13.6/8.13.3) with ESMTP id k5QLQtQF093798;
	Mon, 26 Jun 2006 23:26:55 +0200 (CEST)
	(envelope-from wb@freebie.xs4all.nl)
Received: (from wb@localhost)
	by freebie.xs4all.nl (8.13.6/8.13.6/Submit) id k5QLQsse093797;
	Mon, 26 Jun 2006 23:26:55 +0200 (CEST) (envelope-from wb)
Date: Mon, 26 Jun 2006 23:26:54 +0200
From: Wilko Bulte <wb@freebie.xs4all.nl>
To: "M.Hirsch" <M.Hirsch@hirsch.it>
Message-ID: <20060626212654.GB93703@freebie.xs4all.nl>
References: <E1FuYsL-000HT3-H2@dilbert.firstcallgroup.co.uk>
	<20060626100949.G24406@fledge.watson.org>
	<20060626081029.L1114@ganymede.hub.org>
	<20060626140333.M38418@fledge.watson.org>
	<20060626235355.Q95667@atlantis.atlantis.dp.ua>
	<44A04FD2.1030001@hirsch.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44A04FD2.1030001@hirsch.it>
User-Agent: Mutt/1.5.11
X-Virus-Scanned: by XS4ALL Virus Scanner
Cc: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>, freebsd-stable@FreeBSD.ORG
Subject: Re: FreeBSD 6.x CVSUP today crashes with zero load ...
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jun 2006 21:27:04 -0000

On Mon, Jun 26, 2006 at 11:21:22PM +0200, M.Hirsch wrote..
> ECC is a way to mask broken hardware. I rather have my hardware fail 
> directly when it does first, so I can replace it _immediately_
> What's your hardware good for if it passes a "test", but fails in 
> production?
> 
> ECC is totally overrated.

Balderdash.  

Following your rationale you want your bank account data
silently be corrupted by hardware with bit errors?  Be my guest, give
me ECC any day.

Proper hardware will log the ECC errors, a proper OS tailored to that
hardware will log and notify the sysadmins.

That is how it should be done.

Wilko

-- 
Wilko Bulte				wilko@FreeBSD.org