<?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: Leopard: How to be a super user</title>
	<atom:link href="http://macdaddyworld.com/2007/12/05/leopard-how-to-be-a-super-user/feed/" rel="self" type="application/rss+xml" />
	<link>http://macdaddyworld.com/2007/12/05/leopard-how-to-be-a-super-user/</link>
	<description>Stand back, here come the MacDaddies from Ecamm Network</description>
	<pubDate>Fri, 21 Nov 2008 18:49:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: ken</title>
		<link>http://macdaddyworld.com/2007/12/05/leopard-how-to-be-a-super-user/#comment-853</link>
		<dc:creator>ken</dc:creator>
		<pubDate>Sat, 15 Dec 2007 15:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://macdaddyworld.com/2007/12/05/leopard-how-to-be-a-super-user/#comment-853</guid>
		<description>It's a bit in the file system.  It's more than likely a migration issue since the bit is normally set in Tiger and these were all upgraders.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a bit in the file system.  It&#8217;s more than likely a migration issue since the bit is normally set in Tiger and these were all upgraders.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Muir</title>
		<link>http://macdaddyworld.com/2007/12/05/leopard-how-to-be-a-super-user/#comment-788</link>
		<dc:creator>John Muir</dc:creator>
		<pubDate>Fri, 07 Dec 2007 18:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://macdaddyworld.com/2007/12/05/leopard-how-to-be-a-super-user/#comment-788</guid>
		<description>Is this "bit" you're talking about an actual bit in a file? I'm not technical enough to know for sure what you're talking about here, but if it is indeed a single data bit *and* isn't checked with a checksum at some point it could well be simple data corruption. Single bits here and there are naturally affected over time given hard drive technology. Mind, since it is this one individually vital bit it is a striking coincidence that this one is going wrong for a comparatively large group of users.

Hard drives are far from infallible. But coincidences begin to fly in the face of statistics. Which is a nice way of saying I can't answer!</description>
		<content:encoded><![CDATA[<p>Is this &#8220;bit&#8221; you&#8217;re talking about an actual bit in a file? I&#8217;m not technical enough to know for sure what you&#8217;re talking about here, but if it is indeed a single data bit *and* isn&#8217;t checked with a checksum at some point it could well be simple data corruption. Single bits here and there are naturally affected over time given hard drive technology. Mind, since it is this one individually vital bit it is a striking coincidence that this one is going wrong for a comparatively large group of users.</p>
<p>Hard drives are far from infallible. But coincidences begin to fly in the face of statistics. Which is a nice way of saying I can&#8217;t answer!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
