<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Crying &#8220;FUD&#8221; doesn&#8217;t always mean you&#8217;re right</title>
	<atom:link href="http://elektronkind.org/2007/04/crying-fud-doesnt-always-mean-youre-right/feed" rel="self" type="application/rss+xml" />
	<link>http://elektronkind.org/2007/04/crying-fud-doesnt-always-mean-youre-right</link>
	<description>Navigator of the synapse</description>
	<pubDate>Thu, 20 Nov 2008 21:07:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: mike</title>
		<link>http://elektronkind.org/2007/04/crying-fud-doesnt-always-mean-youre-right#comment-11069</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Thu, 28 Jun 2007 21:09:11 +0000</pubDate>
		<guid isPermaLink="false">http://elektronkind.org/2007/04/crying-fud-doesnt-always-mean-youre-right/#comment-11069</guid>
		<description>This is 100% correct. I said it once on the ZFS list as well. If Linux or other OSes can't seem to get ZFS due to licensing or other stupid reasons, there is no reason why the same concepts can't be employed (besides possible oddball patent stuff.) At least the integrity checking and self-healing functions should be open for implementation, and I don't see why things like COW and inline checksumming couldn't be implemented at least to ensure data correctness. The whole pooled storage model is cool too, but the first step would definately be a welcome option. I use XFS myself, it has crashed a couple times (but recovered...) BTRFS for Linux looks promising...</description>
		<content:encoded><![CDATA[<p>This is 100% correct. I said it once on the ZFS list as well. If Linux or other OSes can&#8217;t seem to get ZFS due to licensing or other stupid reasons, there is no reason why the same concepts can&#8217;t be employed (besides possible oddball patent stuff.) At least the integrity checking and self-healing functions should be open for implementation, and I don&#8217;t see why things like COW and inline checksumming couldn&#8217;t be implemented at least to ensure data correctness. The whole pooled storage model is cool too, but the first step would definately be a welcome option. I use XFS myself, it has crashed a couple times (but recovered&#8230;) BTRFS for Linux looks promising&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Will</title>
		<link>http://elektronkind.org/2007/04/crying-fud-doesnt-always-mean-youre-right#comment-6294</link>
		<dc:creator>Will</dc:creator>
		<pubDate>Sun, 29 Apr 2007 03:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://elektronkind.org/2007/04/crying-fud-doesnt-always-mean-youre-right/#comment-6294</guid>
		<description>That's "rebuttal".

Your captcha is insufficiently intelligent.  It didn't recognize "Eleven" as an answer to "please add 5 and 6".  Ah well, I knew what it meant.</description>
		<content:encoded><![CDATA[<p>That&#8217;s &#8220;rebuttal&#8221;.</p>
<p>Your captcha is insufficiently intelligent.  It didn&#8217;t recognize &#8220;Eleven&#8221; as an answer to &#8220;please add 5 and 6&#8243;.  Ah well, I knew what it meant.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
