<?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: Kernel Security vs Uptime</title>
	<atom:link href="http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/feed/" rel="self" type="application/rss+xml" />
	<link>http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/</link>
	<description>Linux, politics, and other interesting things</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:09:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: security and more &#187; security vs. uptime</title>
		<link>http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/comment-page-1/#comment-14577</link>
		<dc:creator>security and more &#187; security vs. uptime</dc:creator>
		<pubDate>Mon, 30 Jun 2008 23:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=622#comment-14577</guid>
		<description>[...] Russel Coker  have done some math about kernel security related reboots and some common uptime marketing gags. [...]</description>
		<content:encoded><![CDATA[<p>[...] Russel Coker  have done some math about kernel security related reboots and some common uptime marketing gags. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Interstellar Medium: the Free Software carnival &#187; Blog Archive &#187; Free Software carnival: 21 – 27 June 2008</title>
		<link>http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/comment-page-1/#comment-14540</link>
		<dc:creator>Interstellar Medium: the Free Software carnival &#187; Blog Archive &#187; Free Software carnival: 21 – 27 June 2008</dc:creator>
		<pubDate>Fri, 27 Jun 2008 15:59:03 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=622#comment-14540</guid>
		<description>[...] Russell Coker (Debian) notes that reboots due to kernel security patches result in a non-trivial amount of downtime. [...]</description>
		<content:encoded><![CDATA[<p>[...] Russell Coker (Debian) notes that reboots due to kernel security patches result in a non-trivial amount of downtime. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gunnar</title>
		<link>http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/comment-page-1/#comment-14539</link>
		<dc:creator>Gunnar</dc:creator>
		<pubDate>Fri, 27 Jun 2008 14:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=622#comment-14539</guid>
		<description>You say: &lt;em&gt;If you don’t have redundant servers, then that is the case. I’ll be writing more about this in future posts.&lt;/em&gt;
Well... If you don&#039;t have redundant servers, then you should not be buying marketspeak-grade irreal measures such as the many-nineness.</description>
		<content:encoded><![CDATA[<p>You say: <em>If you don’t have redundant servers, then that is the case. I’ll be writing more about this in future posts.</em><br />
Well&#8230; If you don&#8217;t have redundant servers, then you should not be buying marketspeak-grade irreal measures such as the many-nineness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neal Walfield</title>
		<link>http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/comment-page-1/#comment-14535</link>
		<dc:creator>Neal Walfield</dc:creator>
		<pubDate>Fri, 27 Jun 2008 07:19:54 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=622#comment-14535</guid>
		<description>One way to mitigate these types of problems is by applying updates at run-time.  There&#039;s a nice paper on implementing this in the Linux kernel from EuroSys 2007:

   Dynamic and Adaptive Updates of Non-Quiescent Subsystems in Commodity Operating System Kernels

   Kristis Makris, Kyung Dong Ryu 

  http://citeseerx.ist.psu.edu/viewdoc/summary;jsessionid=01EF71F4576C25F6615F21E3D8A99DC6?cid=5563105</description>
		<content:encoded><![CDATA[<p>One way to mitigate these types of problems is by applying updates at run-time.  There&#8217;s a nice paper on implementing this in the Linux kernel from EuroSys 2007:</p>
<p>   Dynamic and Adaptive Updates of Non-Quiescent Subsystems in Commodity Operating System Kernels</p>
<p>   Kristis Makris, Kyung Dong Ryu </p>
<p>  <a href="http://citeseerx.ist.psu.edu/viewdoc/summary;jsessionid=01EF71F4576C25F6615F21E3D8A99DC6?cid=5563105" rel="nofollow">http://citeseerx.ist.psu.edu/viewdoc/summary;jsessionid=01EF71F4576C25F6615F21E3D8A99DC6?cid=5563105</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Clarke</title>
		<link>http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/comment-page-1/#comment-14531</link>
		<dc:creator>David Clarke</dc:creator>
		<pubDate>Fri, 27 Jun 2008 02:37:01 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=622#comment-14531</guid>
		<description>etbe: OpenBSD is the only one I know that can do both pfsync (firewall state sync) and sasync (IPsec security association sync).  FreeBSD can currently only do the former, I believe.  NetBSD I&#039;ve never really touched, so don&#039;t know.</description>
		<content:encoded><![CDATA[<p>etbe: OpenBSD is the only one I know that can do both pfsync (firewall state sync) and sasync (IPsec security association sync).  FreeBSD can currently only do the former, I believe.  NetBSD I&#8217;ve never really touched, so don&#8217;t know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: daveg</title>
		<link>http://etbe.coker.com.au/2008/06/27/kernel-security-vs-uptime/comment-page-1/#comment-14528</link>
		<dc:creator>daveg</dc:creator>
		<pubDate>Fri, 27 Jun 2008 01:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://etbe.coker.com.au/?p=622#comment-14528</guid>
		<description>One other method for saving time when reboots are required for new kernels is using &lt;a href=&quot;http://www.xmission.com/~ebiederm/files/kexec/README&quot; rel=&quot;nofollow&quot;&gt;kexec&lt;/a&gt;. This will save you time as the system doesn&#039;t need to do a full BIOS reboot.</description>
		<content:encoded><![CDATA[<p>One other method for saving time when reboots are required for new kernels is using <a href="http://www.xmission.com/~ebiederm/files/kexec/README" rel="nofollow">kexec</a>. This will save you time as the system doesn&#8217;t need to do a full BIOS reboot.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

