<?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 for Bad Penny</title>
	<atom:link href="http://gorrie.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://gorrie.org</link>
	<description>bound to turn up</description>
	<pubDate>Sat, 11 Oct 2008 00:45:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>Comment on The vacation laptop: ASUS EEE PC 901 by Theron Trowbridge</title>
		<link>http://gorrie.org/2008/08/31/eee-pc-901/#comment-19004</link>
		<dc:creator>Theron Trowbridge</dc:creator>
		<pubDate>Mon, 01 Sep 2008 07:15:48 +0000</pubDate>
		<guid isPermaLink="false">http://gorrie.org/2008/08/31/eee-pc-901/#comment-19004</guid>
		<description>You linked to my blog post (blog.bangsplatpresents.com) about getting Ubuntu running on the Eee PC 901.

I don't know if I qualify as an average computer user, but I am a Linux newbie.  My reason for getting the Eee PC 901 and installing a new Linux on it was to learn more about Linux, and I have learned a load.  It's a hobby machine - if I needed a reliable productivity computer, I made a poor choice :)

I didn't know about the array.org downloads - thanks for the link.</description>
		<content:encoded><![CDATA[<p>You linked to my blog post (blog.bangsplatpresents.com) about getting Ubuntu running on the Eee PC 901.</p>
<p>I don&#8217;t know if I qualify as an average computer user, but I am a Linux newbie.  My reason for getting the Eee PC 901 and installing a new Linux on it was to learn more about Linux, and I have learned a load.  It&#8217;s a hobby machine - if I needed a reliable productivity computer, I made a poor choice <img src='http://gorrie.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I didn&#8217;t know about the array.org downloads - thanks for the link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on World Economic Forum:  Digital Future [Jan 27th, 2006] by tattainue</title>
		<link>http://gorrie.org/2006/02/24/world-economic-forum-digital-future-jan-27th-2006/#comment-18427</link>
		<dc:creator>tattainue</dc:creator>
		<pubDate>Mon, 25 Aug 2008 07:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gorrie.org/2006/02/24/world-economic-forum-digital-future-jan-27th-2006/#comment-18427</guid>
		<description>Is this gonna end someday??</description>
		<content:encoded><![CDATA[<p>Is this gonna end someday??</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on osx system keychain uses a randomly generated password by Ian Gorrie</title>
		<link>http://gorrie.org/2006/07/28/osx-system-keychain-uses-a-randomly-generated-password/#comment-17264</link>
		<dc:creator>Ian Gorrie</dc:creator>
		<pubDate>Fri, 08 Aug 2008 09:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gorrie.org/2006/07/28/osx-system-keychain-uses-a-randomly-generated-password/#comment-17264</guid>
		<description>This would move the previous system keychain to a backup location, via the &lt;b&gt;&lt;i&gt;mv&lt;/i&gt;&lt;/b&gt; command and replace it with a blank keychain where the password is known.</description>
		<content:encoded><![CDATA[<p>This would move the previous system keychain to a backup location, via the <b><i>mv</i></b> command and replace it with a blank keychain where the password is known.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on osx system keychain uses a randomly generated password by ben</title>
		<link>http://gorrie.org/2006/07/28/osx-system-keychain-uses-a-randomly-generated-password/#comment-17259</link>
		<dc:creator>ben</dc:creator>
		<pubDate>Fri, 08 Aug 2008 07:51:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gorrie.org/2006/07/28/osx-system-keychain-uses-a-randomly-generated-password/#comment-17259</guid>
		<description>does this erase the old keychain or just change the password?</description>
		<content:encoded><![CDATA[<p>does this erase the old keychain or just change the password?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Real Estate by terrell</title>
		<link>http://gorrie.org/2008/07/28/real-estate/#comment-17143</link>
		<dc:creator>terrell</dc:creator>
		<pubDate>Tue, 05 Aug 2008 20:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://gorrie.org/2008/07/28/real-estate/#comment-17143</guid>
		<description>Great post, Ian. I hate that home ownership is still sold as the American Dream -- as if it's our right to own and not a privilege.</description>
		<content:encoded><![CDATA[<p>Great post, Ian. I hate that home ownership is still sold as the American Dream &#8212; as if it&#8217;s our right to own and not a privilege.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The encrypted traveler by M. Holger</title>
		<link>http://gorrie.org/2008/04/27/the-encrypted-traveler/#comment-14160</link>
		<dc:creator>M. Holger</dc:creator>
		<pubDate>Wed, 30 Apr 2008 17:05:01 +0000</pubDate>
		<guid isPermaLink="false">http://gorrie.org/2008/04/27/the-encrypted-traveler/#comment-14160</guid>
		<description>Call me paranoid, but for private data I have the machine, which is essentially data-agnostic, an external drive with a crypted container, and a thumbdrive with a crypted keychain.

I don't know the passwords to the containers, just the passwords to the keychains. The keychains unlock the containers.

I don't travel with the containers unless I have to; and if I do have a need travel with the data, then I fedex the keychain to the destination. I can't be compelled to disclose a password I don't know, thwarting would-be interlopers.

The upshot of this mechanism is that the passphrases used to secure the containers can be arbitrarily complex and unintelligible -- since I don't have to know them, let alone remember them, they can be of ridiculous strength.

The downside is that an interloper presented with the data but no key might be inclined to make things very unpleasant...</description>
		<content:encoded><![CDATA[<p>Call me paranoid, but for private data I have the machine, which is essentially data-agnostic, an external drive with a crypted container, and a thumbdrive with a crypted keychain.</p>
<p>I don&#8217;t know the passwords to the containers, just the passwords to the keychains. The keychains unlock the containers.</p>
<p>I don&#8217;t travel with the containers unless I have to; and if I do have a need travel with the data, then I fedex the keychain to the destination. I can&#8217;t be compelled to disclose a password I don&#8217;t know, thwarting would-be interlopers.</p>
<p>The upshot of this mechanism is that the passphrases used to secure the containers can be arbitrarily complex and unintelligible &#8212; since I don&#8217;t have to know them, let alone remember them, they can be of ridiculous strength.</p>
<p>The downside is that an interloper presented with the data but no key might be inclined to make things very unpleasant&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why I hate BlackBerries by Zach</title>
		<link>http://gorrie.org/2008/04/27/why-i-hate-blackberries/#comment-14086</link>
		<dc:creator>Zach</dc:creator>
		<pubDate>Mon, 28 Apr 2008 16:11:46 +0000</pubDate>
		<guid isPermaLink="false">http://gorrie.org/?p=306#comment-14086</guid>
		<description>I was recently forced, to my dismay, to buy a blackberry. To my surprise I have a hard time disliking it, at least compared to my other choices.

GSM in the US sucks. Poor coverage, bad technology. About the only advantage GSM has is the ability to swap phones without involving the carrier and the ability to use non-US handsets without jumping through hoops. When I carried both an AT&#38;T and a Sprint phone there was almost nowhere my AT&#38;T phone had coverage but my Sprint phone didn't, but the reverse was not true.

However, CDMA has crappy handsets. I was looking at getting another Palm OS device (great usability, crappy email, nonexistant push email,) a windows mobile device (crappy usability, crappy stability, but a great feature set, except that turning on push email makes the phone crash more) or a blackberry.

The blackberry gets all the right things right. Email that works, that doesn't crash the phone. Seamless and quick integration with the company directory. The features that are there work. And the BES, which AFAIK no other handset has an equivalent to.

The ability to locate the BES behind your firewall is the key point. This gives your users the ability to access resources on your internal network from their handset. No VPN client. No special configuration. Just type in URLs or open an ssh connection.

If you're using a phone as a business tool and you're often out of the office, or you need 24/7 access to your network, this feature alone makes the BB hard to argue against. 

In most respects the BB is an exceedingly average phone. However, I can't really think of any area where I find it deficient, and aside from the BES nothing really stands out as a great distinguishing feature either. It just does what it's supposed to, in what should be an average way. The only reason it's not done in an average way is because most of the other phones on the market suck and crash a lot. I have yet to see my BB crash.

I've been wondering what the state of all this is in Symbian land. Can I get push email while I'm sshing into a server and using my web browser all at the same time? I can with the BB, I can do it for a while with windows mobile (until the crash happens, at least) and I can't with palm os.</description>
		<content:encoded><![CDATA[<p>I was recently forced, to my dismay, to buy a blackberry. To my surprise I have a hard time disliking it, at least compared to my other choices.</p>
<p>GSM in the US sucks. Poor coverage, bad technology. About the only advantage GSM has is the ability to swap phones without involving the carrier and the ability to use non-US handsets without jumping through hoops. When I carried both an AT&amp;T and a Sprint phone there was almost nowhere my AT&amp;T phone had coverage but my Sprint phone didn&#8217;t, but the reverse was not true.</p>
<p>However, CDMA has crappy handsets. I was looking at getting another Palm OS device (great usability, crappy email, nonexistant push email,) a windows mobile device (crappy usability, crappy stability, but a great feature set, except that turning on push email makes the phone crash more) or a blackberry.</p>
<p>The blackberry gets all the right things right. Email that works, that doesn&#8217;t crash the phone. Seamless and quick integration with the company directory. The features that are there work. And the BES, which AFAIK no other handset has an equivalent to.</p>
<p>The ability to locate the BES behind your firewall is the key point. This gives your users the ability to access resources on your internal network from their handset. No VPN client. No special configuration. Just type in URLs or open an ssh connection.</p>
<p>If you&#8217;re using a phone as a business tool and you&#8217;re often out of the office, or you need 24/7 access to your network, this feature alone makes the BB hard to argue against. </p>
<p>In most respects the BB is an exceedingly average phone. However, I can&#8217;t really think of any area where I find it deficient, and aside from the BES nothing really stands out as a great distinguishing feature either. It just does what it&#8217;s supposed to, in what should be an average way. The only reason it&#8217;s not done in an average way is because most of the other phones on the market suck and crash a lot. I have yet to see my BB crash.</p>
<p>I&#8217;ve been wondering what the state of all this is in Symbian land. Can I get push email while I&#8217;m sshing into a server and using my web browser all at the same time? I can with the BB, I can do it for a while with windows mobile (until the crash happens, at least) and I can&#8217;t with palm os.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adventures in BSD by Ian Gorrie</title>
		<link>http://gorrie.org/2007/08/24/adventures-in-bsd/#comment-4492</link>
		<dc:creator>Ian Gorrie</dc:creator>
		<pubDate>Mon, 27 Aug 2007 10:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gorrie.org/2007/08/24/adventures-in-bsd/#comment-4492</guid>
		<description>All I need is a card that talks madwifi, which I seem to have on order now.

Problem soon to be solved.

Just wait until I start talking multivendor 802.11n around here.  I'm sure that will be even more awesome.</description>
		<content:encoded><![CDATA[<p>All I need is a card that talks madwifi, which I seem to have on order now.</p>
<p>Problem soon to be solved.</p>
<p>Just wait until I start talking multivendor 802.11n around here.  I&#8217;m sure that will be even more awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adventures in BSD by rob terhaar</title>
		<link>http://gorrie.org/2007/08/24/adventures-in-bsd/#comment-4489</link>
		<dc:creator>rob terhaar</dc:creator>
		<pubDate>Mon, 27 Aug 2007 00:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gorrie.org/2007/08/24/adventures-in-bsd/#comment-4489</guid>
		<description>just admit defeat and buy a wrt54gl and put ddwtr on it- then use the device as a wireless bridge-</description>
		<content:encoded><![CDATA[<p>just admit defeat and buy a wrt54gl and put ddwtr on it- then use the device as a wireless bridge-</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cocktail time! by Nat</title>
		<link>http://gorrie.org/2007/08/07/cocktail-time/#comment-4091</link>
		<dc:creator>Nat</dc:creator>
		<pubDate>Wed, 08 Aug 2007 20:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gorrie.org/2007/08/07/cocktail-time/#comment-4091</guid>
		<description>haha I love how you managed to throw the ???? ---&#62; profit! in there. You're a good son, I hope when I have one he will let me crash at his house and make me mojitos too.</description>
		<content:encoded><![CDATA[<p>haha I love how you managed to throw the ???? &#8212;&gt; profit! in there. You&#8217;re a good son, I hope when I have one he will let me crash at his house and make me mojitos too.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
