<?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 To: Build A Read-Only Linux System</title>
	<atom:link href="http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-linux-system/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-linux-system/</link>
	<description>Blog, News &#38; Reviews</description>
	<lastBuildDate>Fri, 03 Feb 2012 16:31:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Forest Bond</title>
		<link>http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-linux-system/comment-page-2/#comment-65371</link>
		<dc:creator>Forest Bond</dc:creator>
		<pubDate>Sat, 29 Oct 2011 18:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicsupply.com/blog/?p=439#comment-65371</guid>
		<description>Hi everyone,

I&#039;m no longer at Logic Supply, but if people still have questions I can do my best to get them answered.  I&#039;ve created a new thread for this purpose on the RapidRollout forums:

&lt;a href=&quot;http://www.rapidrollout.com/forums/topic/3/&quot; rel=&quot;nofollow&quot;&gt;Configuring Ubuntu for read-only storage&lt;/a&gt;

Go ahead and post your questions there and I&#039;ll see what I can do to help!

-Forest</description>
		<content:encoded><![CDATA[<p>Hi everyone,</p>
<p>I&#8217;m no longer at Logic Supply, but if people still have questions I can do my best to get them answered.  I&#8217;ve created a new thread for this purpose on the RapidRollout forums:</p>
<p><a href="http://www.rapidrollout.com/forums/topic/3/" rel="nofollow">Configuring Ubuntu for read-only storage</a></p>
<p>Go ahead and post your questions there and I&#8217;ll see what I can do to help!</p>
<p>-Forest</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Setting up a read-only Debian system?</title>
		<link>http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-linux-system/comment-page-2/#comment-65116</link>
		<dc:creator>Setting up a read-only Debian system?</dc:creator>
		<pubDate>Tue, 25 Oct 2011 15:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicsupply.com/blog/?p=439#comment-65116</guid>
		<description>[...] a NAS.  I have been trying to make the boot flash drive read-only using the method described here:  http://www.logicsupply.com/blog/2009...-linux-system/  The method entails moving the root filesystem to an aufs filesystem so that the boot drive is [...]</description>
		<content:encoded><![CDATA[<p>[...] a NAS.  I have been trying to make the boot flash drive read-only using the method described here:  <a href="http://www.logicsupply.com/blog/2009...-linux-system/" rel="nofollow">http://www.logicsupply.com/blog/2009&#8230;-linux-system/</a>  The method entails moving the root filesystem to an aufs filesystem so that the boot drive is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FBP</title>
		<link>http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-linux-system/comment-page-2/#comment-64441</link>
		<dc:creator>FBP</dc:creator>
		<pubDate>Mon, 17 Oct 2011 19:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicsupply.com/blog/?p=439#comment-64441</guid>
		<description>I have a Seagate Dockstar (arm5 processor, 128 MB RAM, boots Debian squeeze from a usb flash drive). I have done this &quot;Read-Only Linux System&quot; procedure on a more &quot;normal&quot; computer (Intel Atom, Debian squeeze), and it works fine. But it fails on the Dockstar. It boots, it just isn&#039;t read-only. I get the following in dmesg:

[   12.960395] aufs: module is from the staging directory, the quality is unknown, you have been warned.
[   12.993986] aufs 2-standalone.tree-32-20100125
[   13.003956] aufs test_add:218:mount[124]: unsupported filesystem, /root.ro (rootfs)

I end up with no /rw or /ro mount points. Ideas?</description>
		<content:encoded><![CDATA[<p>I have a Seagate Dockstar (arm5 processor, 128 MB RAM, boots Debian squeeze from a usb flash drive). I have done this &#8220;Read-Only Linux System&#8221; procedure on a more &#8220;normal&#8221; computer (Intel Atom, Debian squeeze), and it works fine. But it fails on the Dockstar. It boots, it just isn&#8217;t read-only. I get the following in dmesg:</p>
<p>[   12.960395] aufs: module is from the staging directory, the quality is unknown, you have been warned.<br />
[   12.993986] aufs 2-standalone.tree-32-20100125<br />
[   13.003956] aufs test_add:218:mount[124]: unsupported filesystem, /root.ro (rootfs)</p>
<p>I end up with no /rw or /ro mount points. Ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Johnny</title>
		<link>http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-linux-system/comment-page-2/#comment-64425</link>
		<dc:creator>Johnny</dc:creator>
		<pubDate>Mon, 17 Oct 2011 16:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicsupply.com/blog/?p=439#comment-64425</guid>
		<description>This works except for one found one bug in Ubuntu 10.04:

dhclient breaks.
this is kind of a weird error. It reports that the libraries aren&#039;t there, but they are.

#dhclient: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
# which dhclient
/sbin/dhclient
# ldd /sbin/dhclient
	linux-vdso.so.1 =&gt;  (0x00007fffa8fff000)
	libc.so.6 =&gt; /lib/libc.so.6 (0x00007f4a3b820000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f4a3be1f000)
# ls -al /lib &#124; grep libc.so.6
lrwxrwxrwx  1 root root      14 2011-10-10 20:05 libc.so.6 -&gt; libc-2.11.1.so
root@Archives:/lib# ls -al /lib &#124; grep libc-2.11.1.so
-rwxr-xr-x  1 root root 1572232 2011-01-21 14:23 libc-2.11.1.so
lrwxrwxrwx  1 root root      14 2011-10-10 20:05 libc.so.6 -&gt; libc-2.11.1.so</description>
		<content:encoded><![CDATA[<p>This works except for one found one bug in Ubuntu 10.04:</p>
<p>dhclient breaks.<br />
this is kind of a weird error. It reports that the libraries aren&#8217;t there, but they are.</p>
<p>#dhclient: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory<br />
# which dhclient<br />
/sbin/dhclient<br />
# ldd /sbin/dhclient<br />
	linux-vdso.so.1 =&gt;  (0x00007fffa8fff000)<br />
	libc.so.6 =&gt; /lib/libc.so.6 (0x00007f4a3b820000)<br />
	/lib64/ld-linux-x86-64.so.2 (0x00007f4a3be1f000)<br />
# ls -al /lib | grep libc.so.6<br />
lrwxrwxrwx  1 root root      14 2011-10-10 20:05 libc.so.6 -&gt; libc-2.11.1.so<br />
root@Archives:/lib# ls -al /lib | grep libc-2.11.1.so<br />
-rwxr-xr-x  1 root root 1572232 2011-01-21 14:23 libc-2.11.1.so<br />
lrwxrwxrwx  1 root root      14 2011-10-10 20:05 libc.so.6 -&gt; libc-2.11.1.so</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sparsile</title>
		<link>http://www.logicsupply.com/blog/2009/01/27/how-to-build-a-read-only-linux-system/comment-page-2/#comment-43795</link>
		<dc:creator>sparsile</dc:creator>
		<pubDate>Tue, 29 Mar 2011 18:35:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.logicsupply.com/blog/?p=439#comment-43795</guid>
		<description>TK (or anyone else!), if you&#039;re still listening, I would very much appreciate a tutorial on building a RO linux system for CentOS 5.</description>
		<content:encoded><![CDATA[<p>TK (or anyone else!), if you&#8217;re still listening, I would very much appreciate a tutorial on building a RO linux system for CentOS 5.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

