<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: What does &#8220;./&#8221; mean in linux?</title>
	<link>http://www.eatmybusiness.com/food/2007/04/25/what-does-mean-in-linux/12/</link>
	<description>Web Publishing Techniques</description>
	<pubDate>Thu, 21 Aug 2008 19:23:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: Sally Payne</title>
		<link>http://www.eatmybusiness.com/food/2007/04/25/what-does-mean-in-linux/12/#comment-6</link>
		<author>Sally Payne</author>
		<pubDate>Sat, 28 Apr 2007 17:04:34 +0000</pubDate>
		<guid>http://www.eatmybusiness.com/food/2007/04/25/what-does-mean-in-linux/12/#comment-6</guid>
					<description>In windows the dot and forward slash mean a directory path so just i guess they are the same in linux. but not sure!</description>
		<content:encoded><![CDATA[<p>In windows the dot and forward slash mean a directory path so just i guess they are the same in linux. but not sure!</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: William</title>
		<link>http://www.eatmybusiness.com/food/2007/04/25/what-does-mean-in-linux/12/#comment-182</link>
		<author>William</author>
		<pubDate>Fri, 28 Sep 2007 16:07:39 +0000</pubDate>
		<guid>http://www.eatmybusiness.com/food/2007/04/25/what-does-mean-in-linux/12/#comment-182</guid>
					<description>The quick and easy explanation is that Unix/Linux command shells don't search the current directory for commands, unless the current directory is listed in the $path variable. So, unless the command is built-in like 'grep', 'type', or 'ls', or the command's path is listed in the $path variable, the command shell won't find the command. Unless you specify the current directory as the path by typing "./[command]" at the command line. For more reading on the subject visit
&lt;a href="http://www.kingcomputerservices.com/unix_101/traveling_down_the_unix_$PATH.htm" rel="nofollow"&gt;http://www.kingcomputerservices.com/unix_101/traveling_down_the_unix_$PATH.htm&lt;/a&gt;. Hope that cleared things up a bit.</description>
		<content:encoded><![CDATA[<p>The quick and easy explanation is that Unix/Linux command shells don&#8217;t search the current directory for commands, unless the current directory is listed in the $path variable. So, unless the command is built-in like &#8216;grep&#8217;, &#8216;type&#8217;, or &#8216;ls&#8217;, or the command&#8217;s path is listed in the $path variable, the command shell won&#8217;t find the command. Unless you specify the current directory as the path by typing &#8220;./[command]&#8221; at the command line. For more reading on the subject visit<br />
<a href="http://www.kingcomputerservices.com/unix_101/traveling_down_the_unix_$PATH.htm" rel="nofollow">http://www.kingcomputerservices.com/unix_101/traveling_down_the_unix_$PATH.htm</a>. Hope that cleared things up a bit.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: admin</title>
		<link>http://www.eatmybusiness.com/food/2007/04/25/what-does-mean-in-linux/12/#comment-224</link>
		<author>admin</author>
		<pubDate>Fri, 05 Oct 2007 18:52:44 +0000</pubDate>
		<guid>http://www.eatmybusiness.com/food/2007/04/25/what-does-mean-in-linux/12/#comment-224</guid>
					<description>Thanks for that William. Its a really difficult phrase to search for, so that article is really useful.</description>
		<content:encoded><![CDATA[<p>Thanks for that William. Its a really difficult phrase to search for, so that article is really useful.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
