<?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: Explain: What is CHROOT?</title>
	<atom:link href="http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/</link>
	<description>Linux Tips - Information for Using Linux</description>
	<lastBuildDate>Thu, 26 Nov 2009 21:39:06 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: blaz</title>
		<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/comment-page-1/#comment-18625</link>
		<dc:creator>blaz</dc:creator>
		<pubDate>Thu, 30 Jul 2009 11:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.newlinuxuser.com/?p=154#comment-18625</guid>
		<description>good explanation. what if i chroot to /home/user/test, then create a directory in it, mount my original root file system (for example /dev/hda1) and chroot to it? Is there everything like it was or do i have two chrooted shell instances running?</description>
		<content:encoded><![CDATA[<p>good explanation. what if i chroot to /home/user/test, then create a directory in it, mount my original root file system (for example /dev/hda1) and chroot to it? Is there everything like it was or do i have two chrooted shell instances running?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tak</title>
		<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/comment-page-1/#comment-1268</link>
		<dc:creator>Tak</dc:creator>
		<pubDate>Mon, 03 Nov 2008 18:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.newlinuxuser.com/?p=154#comment-1268</guid>
		<description>Good and clear explanation.</description>
		<content:encoded><![CDATA[<p>Good and clear explanation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Creating a Linux Terminal Media Server for Your Home PC's &#124; Ubuntu Linux Help</title>
		<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/comment-page-1/#comment-1232</link>
		<dc:creator>Creating a Linux Terminal Media Server for Your Home PC's &#124; Ubuntu Linux Help</dc:creator>
		<pubDate>Fri, 14 Mar 2008 14:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.newlinuxuser.com/?p=154#comment-1232</guid>
		<description>[...] &#8220;The chroot command ‘changes the root’ to another location. Why would you want to do that? One of the more popular reasons is to create a sandbox for either an application or a user. Once a new root is declared via chroot, any references that a user or application makes to ‘/’ will resolve to the new directory. This is a pretty effective way to restrict access to the real root and therefore the real file system. In fact, sometimes that act of chrooting is referred to a jailing or a chrooted shell is referred to as a jail shell.&#8221; Read more here: http://www.newlinuxuser.com/explain-what-is-chroot/  [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;The chroot command ‘changes the root’ to another location. Why would you want to do that? One of the more popular reasons is to create a sandbox for either an application or a user. Once a new root is declared via chroot, any references that a user or application makes to ‘/’ will resolve to the new directory. This is a pretty effective way to restrict access to the real root and therefore the real file system. In fact, sometimes that act of chrooting is referred to a jailing or a chrooted shell is referred to as a jail shell.&#8221; Read more here: <a href="http://www.newlinuxuser.com/explain-what-is-chroot/" rel="nofollow">http://www.newlinuxuser.com/explain-what-is-chroot/</a>  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/comment-page-1/#comment-1169</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Wed, 30 Jan 2008 18:00:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.newlinuxuser.com/?p=154#comment-1169</guid>
		<description>The executables you want to use must be in the chroot directory. Example: chroot /home/jon will try to execute $SHELL, like /bin/bash, if no other options are given. This means /home/jon/bin/bash and it support files must exist. Run ldd /bin/bash to find out what shared libraries must exist. Also run info chroot on any linux system for a good example.</description>
		<content:encoded><![CDATA[<p>The executables you want to use must be in the chroot directory. Example: chroot /home/jon will try to execute $SHELL, like /bin/bash, if no other options are given. This means /home/jon/bin/bash and it support files must exist. Run ldd /bin/bash to find out what shared libraries must exist. Also run info chroot on any linux system for a good example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Durham</title>
		<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/comment-page-1/#comment-876</link>
		<dc:creator>Mike Durham</dc:creator>
		<pubDate>Mon, 28 Jan 2008 04:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.newlinuxuser.com/?p=154#comment-876</guid>
		<description>If the root is now &quot;/home/jon&quot; how can you run &quot;nano&quot; which presumably would be in RealRoot/bin?</description>
		<content:encoded><![CDATA[<p>If the root is now &#8220;/home/jon&#8221; how can you run &#8220;nano&#8221; which presumably would be in RealRoot/bin?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kane</title>
		<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/comment-page-1/#comment-682</link>
		<dc:creator>Kane</dc:creator>
		<pubDate>Fri, 28 Dec 2007 14:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.newlinuxuser.com/?p=154#comment-682</guid>
		<description>Jorge: just use the command &quot;exit&quot; to leave the chrooted shell.</description>
		<content:encoded><![CDATA[<p>Jorge: just use the command &#8220;exit&#8221; to leave the chrooted shell.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jmcdonald</title>
		<link>http://www.everyjoe.com/newlinuxuser/explain-what-is-chroot/comment-page-1/#comment-626</link>
		<dc:creator>jmcdonald</dc:creator>
		<pubDate>Fri, 06 Oct 2006 15:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.newlinuxuser.com/?p=154#comment-626</guid>
		<description>Hi, this explanation of chroot is quite useful, but, what if I issued the chroot command and now I want to change my / to the original place (referencing the / filesystem and anything above it at its original place), how can I perform this?

Thanks, 
Jorge</description>
		<content:encoded><![CDATA[<p>Hi, this explanation of chroot is quite useful, but, what if I issued the chroot command and now I want to change my / to the original place (referencing the / filesystem and anything above it at its original place), how can I perform this?</p>
<p>Thanks,<br />
Jorge</p>
]]></content:encoded>
	</item>
</channel>
</rss>
