Date: Mon, 26 Jun 2006 23:26:54 +0200 From: Wilko Bulte <wb@freebie.xs4all.nl> To: "M.Hirsch" <M.Hirsch@hirsch.it> Cc: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>, freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 6.x CVSUP today crashes with zero load ... Message-ID: <20060626212654.GB93703@freebie.xs4all.nl> In-Reply-To: <44A04FD2.1030001@hirsch.it> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060626212654.GB93703>