From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id D16B113877A for ; Sat, 26 Jul 2014 19:07:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ABC82E0F9B; Sat, 26 Jul 2014 19:07:30 +0000 (UTC) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) by pigeon.gentoo.org (Postfix) with ESMTP id 8E596E0F6C for ; Sat, 26 Jul 2014 19:07:29 +0000 (UTC) Received: from [212.54.42.134] (helo=smtp3.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1XB7JY-0008Jl-He for gentoo-user@lists.gentoo.org; Sat, 26 Jul 2014 21:07:28 +0200 Received: from 53579160.cm-6-8c.dynamic.ziggo.nl ([83.87.145.96] helo=data.antarean.org) by smtp3.tb.mail.iss.as9143.net with esmtp (Exim 4.76) (envelope-from ) id 1XB7JY-0002Vt-4Q for gentoo-user@lists.gentoo.org; Sat, 26 Jul 2014 21:07:28 +0200 Received: from [10.20.13.30] (unknown [10.20.13.30]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by data.antarean.org (Postfix) with ESMTPSA id 32ADC4C for ; Sat, 26 Jul 2014 21:07:12 +0200 (CEST) User-Agent: K-9 Mail for Android In-Reply-To: <201407261927.15993.michaelkintzios@gmail.com> References: <53D3E7B8.5060908@googlemail.com> <53D3F218.8040905@googlemail.com> <201407261927.15993.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Subject: Re: [gentoo-user] Re: ECC-ram, it is worth it. From: "J. Roeleveld" Date: Sat, 26 Jul 2014 21:07:26 +0200 To: gentoo-user@lists.gentoo.org Message-ID: Content-Transfer-Encoding: quoted-printable X-Ziggo-spambar: ---- X-Ziggo-spamscore: -4.9 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9,PROLO_TRUST_RDNS=-3,RDNS_DYNAMIC=0.982 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-Archives-Salt: c52748e7-e663-4578-98b7-7c6b767e4961 X-Archives-Hash: 30443386fbb56c860e8640ea8494f00e On 26 July 2014 20:27:14 CEST, Mick wrote: >On Saturday 26 Jul 2014 19:23:20 Volker Armin Hemmann wrote: >> Am 26.07.2014 19:58, schrieb Nikos Chantziaras: >> > On 26/07/14 20:39, Volker Armin Hemmann wrote: >> >> [...] >> >> and this, my children, is why I am using ECC ram. >> >=20 >> > I don't really care if the porn I'm watching has one frame with >> > corrupted pixels on it. >>=20 >> but you will care when your kernel writes the next file right over >the >> partition boundary. > >Ooh! Scary! O_O > >Isn't there some kind of kernel/fs check mechanism that ought to check >this=20 >doesn't happen? There is. But all that happens in memory... -- Joost --=20 Sent from my Android device with K-9 Mail. Please excuse my brevity.