<?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: New: relpath</title>
	<atom:link href="http://www.n8gray.org/blog/2004/11/17/new-relpath/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.n8gray.org/blog/2004/11/17/new-relpath/</link>
	<description>distraction in action</description>
	<pubDate>Fri,  5 Dec 2008 08:39:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: n8</title>
		<link>http://www.n8gray.org/blog/2004/11/17/new-relpath/#comment-3341</link>
		<dc:creator>n8</dc:creator>
		<pubDate>Fri, 16 Feb 2007 18:36:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.n8gray.org/sandbox/wordpress/?p=70#comment-3341</guid>
		<description>Yeah, it's a shame about the alias/symlink thing, but each serves a different purpose.  Aliases are about 1/2 hard link and 1/2 symlink.  If a target file is moved, they still point to it, but if it's deleted and another is put in it's place then they'll point to the new file.  Symlinks, OTOH, always point to a given path, whether or not the target is moved.  In fact, the "target" might not ever have existed!

It would be nice if aliases could be used from the command line, though.

BTW, I should mention that I've never had any unexpected behavior with relative paths in symlinks under OS X.</description>
		<content:encoded><![CDATA[<p>Yeah, it&#8217;s a shame about the alias/symlink thing, but each serves a different purpose.  Aliases are about 1/2 hard link and 1/2 symlink.  If a target file is moved, they still point to it, but if it&#8217;s deleted and another is put in it&#8217;s place then they&#8217;ll point to the new file.  Symlinks, OTOH, always point to a given path, whether or not the target is moved.  In fact, the &#8220;target&#8221; might not ever have existed!</p>
<p>It would be nice if aliases could be used from the command line, though.</p>
<p>BTW, I should mention that I&#8217;ve never had any unexpected behavior with relative paths in symlinks under OS X.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jefe</title>
		<link>http://www.n8gray.org/blog/2004/11/17/new-relpath/#comment-3330</link>
		<dc:creator>Jefe</dc:creator>
		<pubDate>Fri, 16 Feb 2007 09:27:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.n8gray.org/sandbox/wordpress/?p=70#comment-3330</guid>
		<description>Too bad OS X can't get their S#%T together and just work out the symlink thing once and for all.

Having both Aliases and symlinks is stupid, esp when Aliases just show up as zero length files (under HFS+ at least) and can't be followed from the command line.

Then, unless it's my imagination (or a bad version of OS X bash), it seems like relative paths in OS X symlinks only work HALF the time.  The other part of the time, you wind up with the absolute path you never wanted and a bald front tire.
--
Jefe</description>
		<content:encoded><![CDATA[<p>Too bad OS X can&#8217;t get their S#%T together and just work out the symlink thing once and for all.</p>
<p>Having both Aliases and symlinks is stupid, esp when Aliases just show up as zero length files (under HFS+ at least) and can&#8217;t be followed from the command line.</p>
<p>Then, unless it&#8217;s my imagination (or a bad version of OS X bash), it seems like relative paths in OS X symlinks only work HALF the time.  The other part of the time, you wind up with the absolute path you never wanted and a bald front tire.<br />
&#8211;<br />
Jefe</p>
]]></content:encoded>
	</item>
</channel>
</rss>
