<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: Learning the bash shell, continued	</title>
	<atom:link href="https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/feed/" rel="self" type="application/rss+xml" />
	<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/</link>
	<description></description>
	<lastBuildDate>Sat, 30 May 2009 20:24:51 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.8</generator>
	<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/#comment-536091</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Sat, 30 May 2009 20:24:51 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2009/05/29/learning-the-bash-shell-contin-1/#comment-536091</guid>

					<description><![CDATA[Forget JanieBelle?  That&#039;s why I drink!]]></description>
			<content:encoded><![CDATA[<p>Forget JanieBelle?  That&#8217;s why I drink!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Stephanie Z		</title>
		<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/#comment-536090</link>

		<dc:creator><![CDATA[Stephanie Z]]></dc:creator>
		<pubDate>Sat, 30 May 2009 18:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2009/05/29/learning-the-bash-shell-contin-1/#comment-536090</guid>

					<description><![CDATA[&lt;i&gt;Another&lt;/i&gt; one. Can&#039;t forget JanieBelle.]]></description>
			<content:encoded><![CDATA[<p><i>Another</i> one. Can&#8217;t forget JanieBelle.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/#comment-536089</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Sat, 30 May 2009 18:55:51 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2009/05/29/learning-the-bash-shell-contin-1/#comment-536089</guid>

					<description><![CDATA[w00t!!!!  We got one!!!!]]></description>
			<content:encoded><![CDATA[<p>w00t!!!!  We got one!!!!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: GaryB, FCD		</title>
		<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/#comment-536088</link>

		<dc:creator><![CDATA[GaryB, FCD]]></dc:creator>
		<pubDate>Sat, 30 May 2009 13:25:36 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2009/05/29/learning-the-bash-shell-contin-1/#comment-536088</guid>

					<description><![CDATA[Greg, I first started reading your blog because of my interest in the evolution debate (I&#039;ve been a member of t.o. since 2002) but I&#039;m now finding an increased interest in Linux due to the information and resources you provide and link to. Although I was a programmer (emphasis on &#039;was&#039;), with a B.Sc. in CS, and currently own a computer sales and service company dealing exclusively with PCs, my change over on my personal machines to Ubuntu was in large part due to your blog.

Thanks.
]]></description>
			<content:encoded><![CDATA[<p>Greg, I first started reading your blog because of my interest in the evolution debate (I&#8217;ve been a member of t.o. since 2002) but I&#8217;m now finding an increased interest in Linux due to the information and resources you provide and link to. Although I was a programmer (emphasis on &#8216;was&#8217;), with a B.Sc. in CS, and currently own a computer sales and service company dealing exclusively with PCs, my change over on my personal machines to Ubuntu was in large part due to your blog.</p>
<p>Thanks.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/#comment-536087</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Sat, 30 May 2009 07:35:56 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2009/05/29/learning-the-bash-shell-contin-1/#comment-536087</guid>

					<description><![CDATA[I believe in bash it&#039;s hash, not rehash.  I&#039;m not sure if it rehashes as you say, but it might.  With bash there are multiple versions, and this is the kind of detail that might vary from version to version.  We need a more advanced reference book ... coming soon ... to evaluate this.

I&#039;ve updated the above post.  ]]></description>
			<content:encoded><![CDATA[<p>I believe in bash it&#8217;s hash, not rehash.  I&#8217;m not sure if it rehashes as you say, but it might.  With bash there are multiple versions, and this is the kind of detail that might vary from version to version.  We need a more advanced reference book &#8230; coming soon &#8230; to evaluate this.</p>
<p>I&#8217;ve updated the above post.  </p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: JohnnieCanuck		</title>
		<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/#comment-536086</link>

		<dc:creator><![CDATA[JohnnieCanuck]]></dc:creator>
		<pubDate>Sat, 30 May 2009 01:45:59 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2009/05/29/learning-the-bash-shell-contin-1/#comment-536086</guid>

					<description><![CDATA[Jason,

To continue the communal nit removing, am I right that you shouldn&#039;t need to login/logout to get bash to rebuild the hash table? Whereas in csh, one can use rehash, bash will do a rehash automatically on failure to find the command.

My shell experience is old and like Greg&#039;s was, incomplete.]]></description>
			<content:encoded><![CDATA[<p>Jason,</p>
<p>To continue the communal nit removing, am I right that you shouldn&#8217;t need to login/logout to get bash to rebuild the hash table? Whereas in csh, one can use rehash, bash will do a rehash automatically on failure to find the command.</p>
<p>My shell experience is old and like Greg&#8217;s was, incomplete.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jason Thibeault		</title>
		<link>https://gregladen.com/blog/2009/05/29/learning-the-bash-shell-contin-1/#comment-536085</link>

		<dc:creator><![CDATA[Jason Thibeault]]></dc:creator>
		<pubDate>Sat, 30 May 2009 00:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2009/05/29/learning-the-bash-shell-contin-1/#comment-536085</guid>

					<description><![CDATA[Just want to make a very minor semantic correction (and only because, this one, I *know* I&#039;m not going to mess up, not like that Asus thing):  referring to /bin might be confusing to a newbie, though you correctly identified it in describing it at the beginning as a folder in your home.  ~/bin and /bin are completely different -- any path starting with / indicates it is a folder in the root of the file system.  Any path starting with ~ means, start from your currently logged in user&#039;s home folder.  It&#039;s nitpicky, but might as well display the path to the user as it shows up on the screen.

Also, this happened on my computer just now:

jthibeault@laptop:~$ touch ./bin/tester.sh
jthibeault@laptop:~$ chmod +x ./bin/tester.sh
jthibeault@laptop:~$ which tester.sh
jthibeault@laptop:~$ tester.sh
bash: tester.sh: command not found

Hmm, what have we here?  It&#039;s not working for me!  More investigation:

jthibeault@laptop:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/jvm/java-6-sun-1.6.0.12/jre/bin/

Well that&#039;s interesting.  My home folder isn&#039;t on the path.  A bit more digging and I discover normally that gets added to a default .bash_profile when you first set up a new user under Ubuntu.

jthibeault@laptop:~$ ls .bash_profile
ls: cannot access .bash_profile: No such file or directory

Strangely, it also doesn&#039;t exist in /etc/skel -- which is the skeleton user info that&#039;s copied to all new users&#039; home folders.  So something might be wrong with my install.  Regardless, this can be rectified by adding this line:

export PATH=$PATH:/home/jthibeault/bin

to the end of my ~/.bashrc file (think of this as your user profile&#039;s Start Menu Startup folder, or more accurately, autoexec.bat file in old DOS parlance).  After a logout / login, I&#039;d then have ~/bin on my path, and could run my (blank) tester.sh just fine.]]></description>
			<content:encoded><![CDATA[<p>Just want to make a very minor semantic correction (and only because, this one, I *know* I&#8217;m not going to mess up, not like that Asus thing):  referring to /bin might be confusing to a newbie, though you correctly identified it in describing it at the beginning as a folder in your home.  ~/bin and /bin are completely different &#8212; any path starting with / indicates it is a folder in the root of the file system.  Any path starting with ~ means, start from your currently logged in user&#8217;s home folder.  It&#8217;s nitpicky, but might as well display the path to the user as it shows up on the screen.</p>
<p>Also, this happened on my computer just now:</p>
<p>jthibeault@laptop:~$ touch ./bin/tester.sh<br />
jthibeault@laptop:~$ chmod +x ./bin/tester.sh<br />
jthibeault@laptop:~$ which tester.sh<br />
jthibeault@laptop:~$ tester.sh<br />
bash: tester.sh: command not found</p>
<p>Hmm, what have we here?  It&#8217;s not working for me!  More investigation:</p>
<p>jthibeault@laptop:~$ echo $PATH<br />
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/lib/jvm/java-6-sun-1.6.0.12/jre/bin/</p>
<p>Well that&#8217;s interesting.  My home folder isn&#8217;t on the path.  A bit more digging and I discover normally that gets added to a default .bash_profile when you first set up a new user under Ubuntu.</p>
<p>jthibeault@laptop:~$ ls .bash_profile<br />
ls: cannot access .bash_profile: No such file or directory</p>
<p>Strangely, it also doesn&#8217;t exist in /etc/skel &#8212; which is the skeleton user info that&#8217;s copied to all new users&#8217; home folders.  So something might be wrong with my install.  Regardless, this can be rectified by adding this line:</p>
<p>export PATH=$PATH:/home/jthibeault/bin</p>
<p>to the end of my ~/.bashrc file (think of this as your user profile&#8217;s Start Menu Startup folder, or more accurately, autoexec.bat file in old DOS parlance).  After a logout / login, I&#8217;d then have ~/bin on my path, and could run my (blank) tester.sh just fine.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
