<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Darian Shimy &#187; fail</title>
	<atom:link href="http://www.darianshimy.com/tag/fail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.darianshimy.com</link>
	<description></description>
	<lastBuildDate>Sat, 01 Oct 2011 06:06:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Google Wave Invite Users Still Waiting</title>
		<link>http://www.darianshimy.com/2009/10/google-wave-invite-users-still-waiting/</link>
		<comments>http://www.darianshimy.com/2009/10/google-wave-invite-users-still-waiting/#comments</comments>
		<pubDate>Fri, 02 Oct 2009 20:38:13 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[google wave]]></category>
		<category><![CDATA[invites]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/?p=392</guid>
		<description><![CDATA[It looks like people who were invited to Google Wave by other users (the ones that received the original invite from Google) are still waiting to get their invite.  If Google sent out 100,000 invites and each user could invite &#8230; <a href="http://www.darianshimy.com/2009/10/google-wave-invite-users-still-waiting/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.darianshimy.com/wp-content/uploads/2009/10/google_wave_logo.jpg"><img class="alignleft size-thumbnail wp-image-393" title="google_wave_logo" src="http://www.darianshimy.com/wp-content/uploads/2009/10/google_wave_logo-150x150.jpg" alt="google_wave_logo" width="150" height="150" /></a>It looks like people who were invited to <a href="http://wave.google.com">Google Wave</a> by other users (the ones that received the original invite from Google) are still waiting to get their invite.  If Google sent out 100,000 invites and each user could invite 8 more people, that&#8217;s about 800,000 people who are waiting around getting frustrated.</p>
<p>Has anyone received their invite yet?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/10/google-wave-invite-users-still-waiting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>InvalidAuthenticityToken Error in Rails</title>
		<link>http://www.darianshimy.com/2009/10/invalidauthenticitytoken-error-in-rails/</link>
		<comments>http://www.darianshimy.com/2009/10/invalidauthenticitytoken-error-in-rails/#comments</comments>
		<pubDate>Thu, 01 Oct 2009 07:07:19 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[rest]]></category>
		<category><![CDATA[ruby]]></category>
		<category><![CDATA[ruby on rails]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/?p=377</guid>
		<description><![CDATA[Working with a RESTful API in Rails can be a bit challenging at times.  One such problem is the ActionController::InvalidAuthenticityToken error.  This error is thrown when authenticity token is not present or invalid.  (This is how Rails protects itself from &#8230; <a href="http://www.darianshimy.com/2009/10/invalidauthenticitytoken-error-in-rails/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Working with a RESTful API in <a href="http://rubyonrails.org/">Rails</a> can be a bit challenging at times.  One such problem is the ActionController::InvalidAuthenticityToken error.  This error is thrown when authenticity token is not present or invalid.  (This is how Rails protects itself from <a href="http://en.wikipedia.org/wiki/Cross-site_request_forgery">CSRF</a>.)  This token should only be checked with HTML and AJAX requests.  XML requests do not need this check.  However, if the following code is run:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">$ curl <span style="color: #660033;">-d</span> <span style="color: #ff0000;">&quot;&lt;status&gt;...&lt;/status&gt;&quot;</span> <span style="color: #660033;">-X</span> POST http:<span style="color: #000000; font-weight: bold;">//</span>localhost:<span style="color: #000000;">3000</span><span style="color: #000000; font-weight: bold;">/</span>statuses.xml</pre></div></div>

<p>the InvalidAuthenticityToken error is raised.  The problem stems from an incorrect content type.  If you force the content type in the header:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">$ curl <span style="color: #660033;">-H</span> <span style="color: #ff0000;">&quot;Content-Type: application/xml&quot;</span> <span style="color: #660033;">-d</span> <span style="color: #ff0000;">&quot;&lt;status&gt;...&lt;/status&gt;&quot;</span> <span style="color: #660033;">-X</span> POST http:<span style="color: #000000; font-weight: bold;">//</span>localhost:<span style="color: #000000;">3000</span><span style="color: #000000; font-weight: bold;">/</span>statuses.xml</pre></div></div>

<p>everything works as expected.  This turns out to be a gotcha since GET requests don&#8217;t need the header. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/10/invalidauthenticitytoken-error-in-rails/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yahoo Search Index Speed</title>
		<link>http://www.darianshimy.com/2009/09/yahoo-search-index-speed/</link>
		<comments>http://www.darianshimy.com/2009/09/yahoo-search-index-speed/#comments</comments>
		<pubDate>Thu, 10 Sep 2009 06:19:00 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[realtime]]></category>
		<category><![CDATA[yahoo]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/?p=354</guid>
		<description><![CDATA[I submitted this blog to Yahoo a while ago.  Why?  It was more of a test of how fast they spider sites rather than an attempt to drive traffic.  After the submission, they stated: Thank you! Your URL has been &#8230; <a href="http://www.darianshimy.com/2009/09/yahoo-search-index-speed/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I submitted this blog to <a href="http://www.yahoo.com">Yahoo</a> a while ago.  Why?  It was more of a test of how fast they spider sites rather than an attempt to drive traffic.  After the submission, they stated:</p>
<blockquote><p>Thank you! Your URL has been added to our list of URLs to crawl. Please expect a delay of several weeks before your URL is crawled.</p></blockquote>
<p>Several weeks?  Really!</p>
<p>Since the submission, it appears Yahoo is doing their best to meet their goal of several weeks.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/09/yahoo-search-index-speed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Apps SLA</title>
		<link>http://www.darianshimy.com/2009/09/google-apps-sla/</link>
		<comments>http://www.darianshimy.com/2009/09/google-apps-sla/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 18:01:35 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Everything Else]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[gmail]]></category>
		<category><![CDATA[google]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/?p=309</guid>
		<description><![CDATA[Today we received notice from Google that we would be receiving credit for the loss of service earlier in the week. Between 12:45 PM to 2:15 PM PDT &#124; 19:45 &#8211; 21:15 GMT on Tuesday, September 1, 2009, Google Apps &#8230; <a href="http://www.darianshimy.com/2009/09/google-apps-sla/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Today we received notice from Google that we would be receiving credit for the loss of service earlier in the week.</p>
<blockquote><p>Between 12:45 PM to 2:15 PM PDT | 19:45 &#8211; 21:15 GMT on Tuesday, September 1, 2009, Google Apps Gmail users were unable to access their accounts through the Gmail web interface. &#8230; As a result of this incident, we are extending a 3-day SLA credit to your account. This credit will be reflected in an automatic 3-day extension to your Google Apps term date, and no action is needed on the part of your administrators.</p></blockquote>
<p>Looks like <a href="http://www.google.com">Google</a> like <a href="http://www.netflix.com">Netflix</a> know how to handle customer service.  If only the second worst <a href="https://www.wireless.att.com">cell phone company</a> would do the same.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/09/google-apps-sla/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Update: Fixing Rails in Snow Leopard</title>
		<link>http://www.darianshimy.com/2009/09/fixing-rails-in-snow-leopard/</link>
		<comments>http://www.darianshimy.com/2009/09/fixing-rails-in-snow-leopard/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 05:27:12 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[mac ports]]></category>
		<category><![CDATA[mongrel]]></category>
		<category><![CDATA[mysql]]></category>
		<category><![CDATA[os x]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[snow leopard]]></category>
		<category><![CDATA[thin]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/?p=256</guid>
		<description><![CDATA[I was too quick to declare success in my update to Snow Leopard earlier this week.  As it turns out, much of my recovered space came from Xcode being uninstalled.  Easy fix.  Grabbed the DVD and installed it in a &#8230; <a href="http://www.darianshimy.com/2009/09/fixing-rails-in-snow-leopard/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I was too quick to declare success in my update to Snow Leopard earlier <a href="http://www.darianshimy.com/2009/09/snow-leopard-upgrade/">this week</a>.  As it turns out, much of my recovered space came from <a href="http://developer.apple.com/TOOLS/Xcode/">Xcode</a> being uninstalled.  Easy fix.  Grabbed the DVD and installed it in a few minutes.  After doing some deeper checking, I found anything with native extensions or compiled with Leopard was not working.  Thanks for the heads up Apple.</p>
<p>With the move to 64 bit, my older 32-bit version of MySQL was moved to /usr/local/mysql-5.0.45-osx10.4-i686.  Grabbed the <a href="http://dev.mysql.com/downloads/mysql/5.1.html#macosx-dmg">latest</a> and installed the 64-bit version.  You may want to skip the preferences pane since it runs in 32-bit and causes the System Preferences to reload each time.</p>
<p><a href="http://www.macports.org/">Macports</a> needed a fresh install as well.  After that I needed to clean out the old builds with:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">$ <span style="color: #c20cb9; font-weight: bold;">sudo</span> port <span style="color: #660033;">-f</span> uninstall installed</pre></div></div>

<p>This wiped everything out and I needed to reinstall my ports.  As expected my gems were in need of help as well.  Although most were resolved with the following:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">$ <span style="color: #c20cb9; font-weight: bold;">sudo</span> gem update</pre></div></div>

<p>the MySQL gem needed some help finding it&#8217;s cousins:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">$ <span style="color: #c20cb9; font-weight: bold;">sudo</span> <span style="color: #c20cb9; font-weight: bold;">env</span> <span style="color: #007800;">ARCHFLAGS</span>=<span style="color: #ff0000;">&quot;-arch x86_64&quot;</span> gem <span style="color: #c20cb9; font-weight: bold;">install</span> mysql <span style="color: #660033;">--</span> <span style="color: #660033;">--with-mysql-config</span>=<span style="color: #000000; font-weight: bold;">/</span>usr<span style="color: #000000; font-weight: bold;">/</span>local<span style="color: #000000; font-weight: bold;">/</span>mysql<span style="color: #000000; font-weight: bold;">/</span>bin<span style="color: #000000; font-weight: bold;">/</span>mysql_config</pre></div></div>

<p>Finally, Mongrel decided to hang during the startup and WEBrick as no better.  Had to grab <a href="http://code.macournoyer.com/thin/">Thin</a>.  Worked like a champ.  Note to self: need to switch to Passenger for development.</p>
<p>I&#8217;m sure I&#8217;m missing a few things, but right now, most things seem to be working.  I&#8217;ll update this post if I find anything else.</p>
<p><strong>Update:</strong> Mongrel can be fixed by uninstalling mongrel and fast thread and reinstalling mongrel:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">$ <span style="color: #c20cb9; font-weight: bold;">sudo</span> gem uninstall mongrel fastthread
$ <span style="color: #c20cb9; font-weight: bold;">sudo</span> gem <span style="color: #c20cb9; font-weight: bold;">install</span> mongrel</pre></div></div>

]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/09/fixing-rails-in-snow-leopard/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Capistrano is Fixed in Snow Leopard</title>
		<link>http://www.darianshimy.com/2009/09/capistrano-is-fixed-in-snow-leopard/</link>
		<comments>http://www.darianshimy.com/2009/09/capistrano-is-fixed-in-snow-leopard/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 03:20:03 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[capistrano]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[os x]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[snow leopard]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/?p=249</guid>
		<description><![CDATA[There were a number of things that seemed to break with the upgrade to Snow Leopard.  The latest is my ability to deploy Rails application using Capistrano.  For some reason, the SSH connection would hang.  Looks like this was fixed &#8230; <a href="http://www.darianshimy.com/2009/09/capistrano-is-fixed-in-snow-leopard/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>There were a number of things that seemed to break with the upgrade to Snow Leopard.  The latest is my ability to deploy Rails application using Capistrano.  For some reason, the SSH connection would hang.  Looks like this was fixed today with the 2.0.15 release of <a href="http://github.com/net-ssh/net-ssh/blob/92a213629fb11f624c4624464759e4d82c5028b6/CHANGELOG.rdoc">net-ssh</a>.</p>
<p>To get things working again, just update net-ssh:</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;">$ <span style="color: #c20cb9; font-weight: bold;">sudo</span> gem update net-ssh
Updating installed gems
Updating net-ssh
Successfully installed net-ssh-2.0.15
Gems updated: net-ssh</pre></div></div>

<p>Deployments work like a charm.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/09/capistrano-is-fixed-in-snow-leopard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bad Timing of a Retrospective</title>
		<link>http://www.darianshimy.com/2009/02/bad-timing-of-a-retrospective/</link>
		<comments>http://www.darianshimy.com/2009/02/bad-timing-of-a-retrospective/#comments</comments>
		<pubDate>Thu, 12 Feb 2009 16:34:00 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[agile]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[retrospective]]></category>
		<category><![CDATA[scrum]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/2009/02/bad-timing-of-a-retrospective/</guid>
		<description><![CDATA[During the last sprint, we made a critical error in planning our meetings.&#160; Due to time constraints and people&#8217;s schedules, we scheduled the Sprint Retrospective for the last sprint after the Sprint Planning meeting for the next sprint.&#160; The retrospective &#8230; <a href="http://www.darianshimy.com/2009/02/bad-timing-of-a-retrospective/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>During the last sprint, we made a critical error in planning our meetings.&nbsp; Due to time constraints and people&#8217;s schedules, we scheduled the Sprint Retrospective for the last sprint after the Sprint Planning meeting for the next sprint.&nbsp; The retrospective was a bust.&nbsp; The team was soley focused on the next set of tasks and couldn&#8217;t understand why they needed to be in the retrospective meeting with so much work to do.&nbsp; Bad idea.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/02/bad-timing-of-a-retrospective/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Quality Apple</title>
		<link>http://www.darianshimy.com/2009/01/a-quality-apple/</link>
		<comments>http://www.darianshimy.com/2009/01/a-quality-apple/#comments</comments>
		<pubDate>Sun, 04 Jan 2009 17:04:00 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[review]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/2009/01/a-quality-apple/</guid>
		<description><![CDATA[Sadly today, I need to take my wife&#8217;s iPhone to an Apple store for a replacement.&#160; This is will be the 7th iPhone between the two of us.&#160; Here are the problems we encountered: The earphone jack stopped working, phone &#8230; <a href="http://www.darianshimy.com/2009/01/a-quality-apple/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Sadly today, I need to take my wife&#8217;s iPhone to an Apple store for a replacement.&nbsp; This is will be the 7th iPhone between the two of us.&nbsp; Here are the problems we encountered:
<ul>
<li>The earphone jack stopped working, phone replaced</li>
<li>The battery would not hold a charge, phone replaced</li>
<li>The camera would only take blurry pictures, phone replaced </li>
<li>The battery would not hold a charge, phone replaced</li>
<li>The phone continually docks, pending</li>
</ul>
<p>These are the first generation phones and I&#8217;m glad we purchased the warranty before our expiration period.&nbsp; Although they are very good about giving a replacement, I would much prefer to have the phone last longer.&nbsp; My old Nokia was indestructable.&nbsp; You could use it as a hockey puck and it kept working.&nbsp; It was also a very simple device.&nbsp; It only made calls.&nbsp; It was a phone, nothing more.&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2009/01/a-quality-apple/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Installing git on OS X</title>
		<link>http://www.darianshimy.com/2008/07/installing-git-on-os-x/</link>
		<comments>http://www.darianshimy.com/2008/07/installing-git-on-os-x/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 16:25:00 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[os x]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/2008/07/installing-git-on-os-x/</guid>
		<description><![CDATA[I finally decided to sneak a peak at git, the distributed version control system.  After some light searching, I found MacPorts to be the best bet for installing the software.  While trying to install rsync, I kept getting the following &#8230; <a href="http://www.darianshimy.com/2008/07/installing-git-on-os-x/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I finally decided to sneak a peak at <a href="http://git.or.cz/">git</a>, the distributed version control system.  After some light searching, I found <a href="http://www.macports.org/">MacPorts</a> to be the best bet for installing the software.  While trying to install <a href="http://samba.anu.edu.au/rsync/">rsync</a>, I kept getting the following error:</p>
<p><span style="font-size: x-small;"><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">% port install rsync</span><br style="font-family: &quot;Courier New&quot;,Courier,monospace;" /><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">&#8212;&gt;  Fetching rsync</span><br style="font-family: &quot;Courier New&quot;,Courier,monospace;" /><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">&#8212;&gt;  Attempting to fetch rsync-3.0.2.tar.gz from http://rsync.samba.org/ftp/rsync/</span><br style="font-family: &quot;Courier New&quot;,Courier,monospace;" /><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">&#8212;&gt;  Attempting to fetch rsync-3.0.2.tar.gz from http://svn.macports.org/repository/macports/distfiles/rsync</span><br style="font-family: &quot;Courier New&quot;,Courier,monospace;" /><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">&#8212;&gt;  Attempting to fetch rsync-3.0.2.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/</span><br style="font-family: &quot;Courier New&quot;,Courier,monospace;" /><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">&#8212;&gt;  Attempting to fetch rsync-3.0.2.tar.gz from http://svn.macports.org/repository/macports/downloads/rsync</span><br style="font-family: &quot;Courier New&quot;,Courier,monospace;" /><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">Error: Target org.macports.fetch returned: fetch failed</span><br style="font-family: &quot;Courier New&quot;,Courier,monospace;" /><span style="font-family: &quot;Courier New&quot;,Courier,monospace;">Error: Status 1 encountered during processing.</span></span></p>
<p>If you get this error, you will need to update MacPorts.  This is accomplished by the following command:</p>
<div style="font-family: &quot;Courier New&quot;,Courier,monospace;"><span style="font-size: x-small;">% port selfupdate</span></div>
<p>You can then install rsync which is needed for git.  To finish the git installation, run:</p>
<div style="font-family: &quot;Courier New&quot;,Courier,monospace;"><span style="font-size: x-small;">% port install cogito</span></div>
<p>If you have a problem with m755 and make, just run the command again.  It will work.</p>
<p><strong>Update:</strong> I just found a Mac installer of git, but I have not tried it.  You can get it <a href="http://code.google.com/p/git-osx-installer/downloads/list?can=3">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2008/07/installing-git-on-os-x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iPhone: Bleeding Edge</title>
		<link>http://www.darianshimy.com/2008/07/iphone-bleeding-edge/</link>
		<comments>http://www.darianshimy.com/2008/07/iphone-bleeding-edge/#comments</comments>
		<pubDate>Mon, 14 Jul 2008 06:55:00 +0000</pubDate>
		<dc:creator>Darian Shimy</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://www.darianshimy.com/2008/07/iphone-bleeding-edge/</guid>
		<description><![CDATA[Yes I woke up early on Friday and had a few minutes to kill before I went to work.  So what did I decide to do, update my iPhone to the new 2.0 firmware.  Me and the millions of other &#8230; <a href="http://www.darianshimy.com/2008/07/iphone-bleeding-edge/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Yes I woke up early on Friday and had a few minutes to kill before I went to work.  So what did I decide to do, update my iPhone to the new 2.0 firmware.  Me and the millions of other peeps that brought the Apple servers to their knees.  Needless to say I had to snag my wife&#8217;s iPhone for the day.</p>
<p>Before I started the upgrade I thought the chances this would be successful was next to zero.  So I did it anyways.  I started thinking why.  I really don&#8217;t need the new features right now.  Was I bored with nothing to do?</p>
<p>It was the sheer desire to have the newest and latest.  Even if it was exactily the same thing.  Afterall this upgrade didn&#8217;t cost my any money.  It was a download I was entitled to being a current customer.  It was free.  And being free it was an easy decision.  However, if there was a fee would I have been so eager?</p>
<p>Well, I don&#8217;t have the iPhone 3G just yet&#8230;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.darianshimy.com/2008/07/iphone-bleeding-edge/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

