<?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: That&#8217;s a rack!</title>
	<atom:link href="http://blog.xcski.com/2006/10/31/thats-a-rack/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.xcski.com/2006/10/31/thats-a-rack</link>
	<description>Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place.</description>
	<pubDate>Fri, 05 Dec 2008 10:22:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Paul Tomblin</title>
		<link>http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12402</link>
		<dc:creator>Paul Tomblin</dc:creator>
		<pubDate>Wed, 01 Nov 2006 21:43:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12402</guid>
		<description>Ok, to answer my own answer, it appears that Debian's mkinitrd is much simpler - you load the modules you want, then you type "mkinitrd -o /boot/initrd-xen.img 2.6.18-xen" and it makes the ramdisk for you.  I loaded the ramdisk for the domUs, and they didn't give that warning about mounting ext3 as ext2 any more.</description>
		<content:encoded><![CDATA[<p>Ok, to answer my own answer, it appears that Debian&#8217;s mkinitrd is much simpler - you load the modules you want, then you type &#8220;mkinitrd -o /boot/initrd-xen.img 2.6.18-xen&#8221; and it makes the ramdisk for you.  I loaded the ramdisk for the domUs, and they didn&#8217;t give that warning about mounting ext3 as ext2 any more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Tomblin</title>
		<link>http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12375</link>
		<dc:creator>Paul Tomblin</dc:creator>
		<pubDate>Tue, 31 Oct 2006 12:07:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12375</guid>
		<description>Frank, the problem is that all the instructions I've found for doing a "mkinitrd" say to use the "-v -f" options, and the version of mkinitrd on Debian Sarge doesn't take those options.</description>
		<content:encoded><![CDATA[<p>Frank, the problem is that all the instructions I&#8217;ve found for doing a &#8220;mkinitrd&#8221; say to use the &#8220;-v -f&#8221; options, and the version of mkinitrd on Debian Sarge doesn&#8217;t take those options.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Ch. Eigler</title>
		<link>http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12364</link>
		<dc:creator>Frank Ch. Eigler</dc:creator>
		<pubDate>Tue, 31 Oct 2006 03:14:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12364</guid>
		<description>xen kernels can load initrd images roughly the same way
normal ones do, and it can contain ext3.ko.
See the "ramdisk" attribute in your xen config file.</description>
		<content:encoded><![CDATA[<p>xen kernels can load initrd images roughly the same way<br />
normal ones do, and it can contain ext3.ko.<br />
See the &#8220;ramdisk&#8221; attribute in your xen config file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Barry Price</title>
		<link>http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12363</link>
		<dc:creator>Barry Price</dc:creator>
		<pubDate>Tue, 31 Oct 2006 03:10:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xcski.com/2006/10/31/thats-a-rack#comment-12363</guid>
		<description>Any excuse to say "Nice rack, Paul!" is good by me.

No ext3 support is interesting, &lt;acronym title="for some values of"&gt;fsvo&lt;/acronym&gt; "interesting".  Good luck!</description>
		<content:encoded><![CDATA[<p>Any excuse to say &#8220;Nice rack, Paul!&#8221; is good by me.</p>
<p>No ext3 support is interesting, <acronym title="for some values of">fsvo</acronym> &#8220;interesting&#8221;.  Good luck!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
