<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Fun with Linux: The Existential File System	</title>
	<atom:link href="https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/feed/" rel="self" type="application/rss+xml" />
	<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/</link>
	<description></description>
	<lastBuildDate>Wed, 14 Nov 2007 16:03:21 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.8</generator>
	<item>
		<title>
		By: Webs		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-610</link>

		<dc:creator><![CDATA[Webs]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 16:03:21 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-610</guid>

					<description><![CDATA[LOL Greg!!!]]></description>
			<content:encoded><![CDATA[<p>LOL Greg!!!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: greg laden		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-609</link>

		<dc:creator><![CDATA[greg laden]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 15:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-609</guid>

					<description><![CDATA[What&#039;s goint to happen when Mac comes out with Bobcat at the same time that Ubuntu comes out with Bitchy Bobcat....]]></description>
			<content:encoded><![CDATA[<p>What&#8217;s goint to happen when Mac comes out with Bobcat at the same time that Ubuntu comes out with Bitchy Bobcat&#8230;.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Johnny Vector		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-608</link>

		<dc:creator><![CDATA[Johnny Vector]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 14:30:33 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-608</guid>

					<description><![CDATA[Dammit!  I told you I can&#039;t keep these cats straight!Probably because the new box doesn&#039;t have any cat on it, just a big X and a fakety-fake swirly galaxy.  Yeah, Leopard is what I mean.Posting from 00:19:e3:d4:53:3cCrap!  Now I&#039;m a MAC troll.]]></description>
			<content:encoded><![CDATA[<p>Dammit!  I told you I can&#8217;t keep these cats straight!Probably because the new box doesn&#8217;t have any cat on it, just a big X and a fakety-fake swirly galaxy.  Yeah, Leopard is what I mean.Posting from 00:19:e3:d4:53:3cCrap!  Now I&#8217;m a MAC troll.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Webs		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-607</link>

		<dc:creator><![CDATA[Webs]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 13:04:18 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-607</guid>

					<description><![CDATA[Leopard is the newest one if that is what you are referring to Johnny.Crap! Now I&#039;m a MAC troll ;)But anyways, Time Machine is just another example of taking an idea in Technology that already exists and making it easy to understand, use, and making it practical. As with nearly all Apple features.]]></description>
			<content:encoded><![CDATA[<p>Leopard is the newest one if that is what you are referring to Johnny.Crap! Now I&#8217;m a MAC troll ;)But anyways, Time Machine is just another example of taking an idea in Technology that already exists and making it easy to understand, use, and making it practical. As with nearly all Apple features.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Johnny Vector		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-606</link>

		<dc:creator><![CDATA[Johnny Vector]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 11:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-606</guid>

					<description><![CDATA[The spiffiest use for hard links has to be the Time Machine feature in OS X Jaguar.  (Jaguar, right?  Lessee, Panther, Tiger,... yeah, that&#039;s the right one.  Getting hard to keep all these cats straight.)Each snapshot in Time Machine contains your entire disk (or, the part you have chosen to back up).  But for files that haven&#039;t changed since the previous backup, it just creates another hard link to the already-copied file.  So you end up with a given file being shared between dozens (or hundreds, eventually) of different hard links in different directories.Gives the space savings of only copying changed files, while making each backup an actual complete copy of your disk at that point in time.  Sweet.Yes, I&#039;m sure this has been done before, but perhaps not with such style.  Or anyway, marketing.]]></description>
			<content:encoded><![CDATA[<p>The spiffiest use for hard links has to be the Time Machine feature in OS X Jaguar.  (Jaguar, right?  Lessee, Panther, Tiger,&#8230; yeah, that&#8217;s the right one.  Getting hard to keep all these cats straight.)Each snapshot in Time Machine contains your entire disk (or, the part you have chosen to back up).  But for files that haven&#8217;t changed since the previous backup, it just creates another hard link to the already-copied file.  So you end up with a given file being shared between dozens (or hundreds, eventually) of different hard links in different directories.Gives the space savings of only copying changed files, while making each backup an actual complete copy of your disk at that point in time.  Sweet.Yes, I&#8217;m sure this has been done before, but perhaps not with such style.  Or anyway, marketing.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-605</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 09:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-605</guid>

					<description><![CDATA[Webs:  You are absolutely correct!The confusion here ... and it is confused in the literature, this time it is not my fault :)  (not this time, anyway), is that &quot;file system&quot; can be and often is applied to two different things.  One is the way in which files are managed on the hard drive (like ext or NTFS, not what I was talking about) and the other is the way in which the system handles files.  What I wrote in my post applies to ext*, NTFS, etc. .... there is no difference.  Thank you for reading my post carefully and pointing out this issue.I could have said something like &quot;the way Linux handles files&quot;The problem with at topic like this is that any one small concise piece will always have many unconnected threads ...And yes, Troll Kevin told us he was an expert but revealed the truth when he bitched at me about how NTFS does this too, etc.  He is utterly confused. Not well trained, I suspect. But well meaning, I&#039;m sure.]]></description>
			<content:encoded><![CDATA[<p>Webs:  You are absolutely correct!The confusion here &#8230; and it is confused in the literature, this time it is not my fault 🙂  (not this time, anyway), is that &#8220;file system&#8221; can be and often is applied to two different things.  One is the way in which files are managed on the hard drive (like ext or NTFS, not what I was talking about) and the other is the way in which the system handles files.  What I wrote in my post applies to ext*, NTFS, etc. &#8230;. there is no difference.  Thank you for reading my post carefully and pointing out this issue.I could have said something like &#8220;the way Linux handles files&#8221;The problem with at topic like this is that any one small concise piece will always have many unconnected threads &#8230;And yes, Troll Kevin told us he was an expert but revealed the truth when he bitched at me about how NTFS does this too, etc.  He is utterly confused. Not well trained, I suspect. But well meaning, I&#8217;m sure.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Webs		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-604</link>

		<dc:creator><![CDATA[Webs]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 09:22:20 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-604</guid>

					<description><![CDATA[For me the only confusing thing would be mentioning &quot;Linux Filesystem&quot;. There really isn&#039;t a Linux filesystem, because you can use nearly any filesystem you want on Linux, ext2, ext3, RiserFS, JFS, etc... Likewise, on Windows 2000 you could use NTFS or FAT 32. Linux the OS knows how to handle symbolic links and hard links, but the filesystem chosen doesn&#039;t really care as the OS tells the filesystem what to write.Maybe that was the confusing part to Kevin and sorta for myself? I think I understood your underlying message though, and I hate to sound like a Linux troll. Besides my gripe above, it was a well written post about Linux. I can&#039;t wait to read the next one!]]></description>
			<content:encoded><![CDATA[<p>For me the only confusing thing would be mentioning &#8220;Linux Filesystem&#8221;. There really isn&#8217;t a Linux filesystem, because you can use nearly any filesystem you want on Linux, ext2, ext3, RiserFS, JFS, etc&#8230; Likewise, on Windows 2000 you could use NTFS or FAT 32. Linux the OS knows how to handle symbolic links and hard links, but the filesystem chosen doesn&#8217;t really care as the OS tells the filesystem what to write.Maybe that was the confusing part to Kevin and sorta for myself? I think I understood your underlying message though, and I hate to sound like a Linux troll. Besides my gripe above, it was a well written post about Linux. I can&#8217;t wait to read the next one!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-603</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 08:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-603</guid>

					<description><![CDATA[Kevin,Thanks for the comments.  Nothing I discussed regarding Linux file systems has to do with the web.  But the way linux file systems work does have important historical and pragmatic implications.  I think its OK for me to mention this without giving the details (if you read carefully you will see what I mean).I did not bother to mention that many modern file systems like NTFS have been playing catchup to the Unix file system, thanks for bringing that up.NTFS is probably the worst thing that ever happened to file systems ever, anywhere.  I&#039;ve never in my life lost data to a hard drive except one using NTFS.In any event, thanks for your expert comments.  Always appreciated.]]></description>
			<content:encoded><![CDATA[<p>Kevin,Thanks for the comments.  Nothing I discussed regarding Linux file systems has to do with the web.  But the way linux file systems work does have important historical and pragmatic implications.  I think its OK for me to mention this without giving the details (if you read carefully you will see what I mean).I did not bother to mention that many modern file systems like NTFS have been playing catchup to the Unix file system, thanks for bringing that up.NTFS is probably the worst thing that ever happened to file systems ever, anywhere.  I&#8217;ve never in my life lost data to a hard drive except one using NTFS.In any event, thanks for your expert comments.  Always appreciated.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: kevin		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-602</link>

		<dc:creator><![CDATA[kevin]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 08:39:04 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-602</guid>

					<description><![CDATA[Greg -As a fairly expert linux and windows developper, I think this post is pretty misleading and confusing. There is nothing particularly special about linux&#039;s handling of hard links (multiply-named files, as you describe them) or soft links (aka symlinks, i.e &quot;symbolic&quot; links, not &quot;simulated&quot; links). NTFS 5 has both, and other than the earlier windows filesystems which only have soft links, most every modern filesystem has both as well. And they are hardly used at all in practice... most users get along fine without *ever* explicitly creating a hard link.And none of this really has anything to do with the web, or with security, or with viruses. If anything, the only real difference for the web is that windows treats file names case insensitive while linux treats them case sensitive.For security, one could easily argue that traditional linux-style permission bits (ugo/rwx) are pretty pathetic, cumbersome, and limiting, compared to windows-style ACLs.-Kevin]]></description>
			<content:encoded><![CDATA[<p>Greg -As a fairly expert linux and windows developper, I think this post is pretty misleading and confusing. There is nothing particularly special about linux&#8217;s handling of hard links (multiply-named files, as you describe them) or soft links (aka symlinks, i.e &#8220;symbolic&#8221; links, not &#8220;simulated&#8221; links). NTFS 5 has both, and other than the earlier windows filesystems which only have soft links, most every modern filesystem has both as well. And they are hardly used at all in practice&#8230; most users get along fine without *ever* explicitly creating a hard link.And none of this really has anything to do with the web, or with security, or with viruses. If anything, the only real difference for the web is that windows treats file names case insensitive while linux treats them case sensitive.For security, one could easily argue that traditional linux-style permission bits (ugo/rwx) are pretty pathetic, cumbersome, and limiting, compared to windows-style ACLs.-Kevin</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2007/11/13/fun-with-linux-the-existential/#comment-601</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Wed, 14 Nov 2007 07:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2007/11/13/fun-with-linux-the-existential/#comment-601</guid>

					<description><![CDATA[Janne, thanks for the correction on sym vs. sim.  I&#039;m making it in the post.I usually try to mention when I post on Linux tech stuff that no one should ever consider me an expert.  If you follow my instructions very very carefully, you will ruin your afternoon.]]></description>
			<content:encoded><![CDATA[<p>Janne, thanks for the correction on sym vs. sim.  I&#8217;m making it in the post.I usually try to mention when I post on Linux tech stuff that no one should ever consider me an expert.  If you follow my instructions very very carefully, you will ruin your afternoon.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
