<?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/"
		>
<channel>
	<title>Comments on: How long has your server been running?</title>
	<atom:link href="http://vmguy.com/wordpress/index.php/archives/309/feed" rel="self" type="application/rss+xml" />
	<link>http://vmguy.com/wordpress/index.php/archives/309</link>
	<description>Virtualization for the little guy</description>
	<lastBuildDate>Fri, 27 Jan 2012 15:54:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Bruce</title>
		<link>http://vmguy.com/wordpress/index.php/archives/309/comment-page-1#comment-61</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Mon, 15 Dec 2008 22:11:50 +0000</pubDate>
		<guid isPermaLink="false">http://VMGUY.COM/wordpress/?p=309#comment-61</guid>
		<description>&lt;a href=&quot;#comment-55&quot; rel=&quot;nofollow&quot;&gt;@Bob Plankers &lt;/a&gt; 
You know there was a time when high uptime meant you had a rock solid system or OS.  Now I think I agree with you.  It means your neglecting patching and that introduces undo risk into your environment (security and vendor supportability).  I would be embarrassed to have servers like that in the 21st century.</description>
		<content:encoded><![CDATA[<p><a href="#comment-55" rel="nofollow">@Bob Plankers </a><br />
You know there was a time when high uptime meant you had a rock solid system or OS.  Now I think I agree with you.  It means your neglecting patching and that introduces undo risk into your environment (security and vendor supportability).  I would be embarrassed to have servers like that in the 21st century.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The VMguy</title>
		<link>http://vmguy.com/wordpress/index.php/archives/309/comment-page-1#comment-60</link>
		<dc:creator>The VMguy</dc:creator>
		<pubDate>Mon, 15 Dec 2008 15:57:14 +0000</pubDate>
		<guid isPermaLink="false">http://VMGUY.COM/wordpress/?p=309#comment-60</guid>
		<description>Good point, I&#039;ll see if I can put that in as a feature request.</description>
		<content:encoded><![CDATA[<p>Good point, I&#8217;ll see if I can put that in as a feature request.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aharden</title>
		<link>http://vmguy.com/wordpress/index.php/archives/309/comment-page-1#comment-58</link>
		<dc:creator>aharden</dc:creator>
		<pubDate>Fri, 12 Dec 2008 22:04:25 +0000</pubDate>
		<guid isPermaLink="false">http://VMGUY.COM/wordpress/?p=309#comment-58</guid>
		<description>A more impressive statistic, and one attainable even with security patching and ESX host upgrades, would be multi-year uptime of a cluster-hosted VM.</description>
		<content:encoded><![CDATA[<p>A more impressive statistic, and one attainable even with security patching and ESX host upgrades, would be multi-year uptime of a cluster-hosted VM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The VMguy</title>
		<link>http://vmguy.com/wordpress/index.php/archives/309/comment-page-1#comment-57</link>
		<dc:creator>The VMguy</dc:creator>
		<pubDate>Fri, 12 Dec 2008 21:28:53 +0000</pubDate>
		<guid isPermaLink="false">http://VMGUY.COM/wordpress/?p=309#comment-57</guid>
		<description>True, much to my dismay they are not (and running 2.5 btw).  Some companies are like that.  I agree, I&#039;m the proactive type when it comes to patching to avoid what could happen.

Some people read the recall notice when they get it in the mail and get it fixed, some wait for the part to fail.</description>
		<content:encoded><![CDATA[<p>True, much to my dismay they are not (and running 2.5 btw).  Some companies are like that.  I agree, I&#8217;m the proactive type when it comes to patching to avoid what could happen.</p>
<p>Some people read the recall notice when they get it in the mail and get it fixed, some wait for the part to fail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Stephens</title>
		<link>http://vmguy.com/wordpress/index.php/archives/309/comment-page-1#comment-56</link>
		<dc:creator>Adam Stephens</dc:creator>
		<pubDate>Fri, 12 Dec 2008 21:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://VMGUY.COM/wordpress/?p=309#comment-56</guid>
		<description>Agreed. Clearly these ESX hosts are not current in their security patching.</description>
		<content:encoded><![CDATA[<p>Agreed. Clearly these ESX hosts are not current in their security patching.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Plankers</title>
		<link>http://vmguy.com/wordpress/index.php/archives/309/comment-page-1#comment-55</link>
		<dc:creator>Bob Plankers</dc:creator>
		<pubDate>Fri, 12 Dec 2008 21:13:15 +0000</pubDate>
		<guid isPermaLink="false">http://VMGUY.COM/wordpress/?p=309#comment-55</guid>
		<description>I&#039;ve never understood uptime wars, mainly because the #1 way to keep things secure is to keep them patched, and uptime wars encourage the wrong things in that regard.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve never understood uptime wars, mainly because the #1 way to keep things secure is to keep them patched, and uptime wars encourage the wrong things in that regard.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

