<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>FreeMacUnix.com &#187; Unix</title>
	<atom:link href="http://www.freemacunix.com/category/unix/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.freemacunix.com</link>
	<description>Terminal for the Rest of Us</description>
	<lastBuildDate>Sat, 26 Nov 2011 10:42:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>BLT &#8211; Command Line Twitter Client</title>
		<link>http://www.freemacunix.com/blt-command-line-twitter-client/</link>
		<comments>http://www.freemacunix.com/blt-command-line-twitter-client/#comments</comments>
		<pubDate>Thu, 08 Oct 2009 19:15:29 +0000</pubDate>
		<dc:creator>Chad Sweely</dc:creator>
				<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/?p=162</guid>
		<description><![CDATA[There are some scenarios in Unix/Linux when you are stuck at the command line and not able to get to a GUI interface. With this in mind, there is a Twitter client out there that will let you view your tweets at the command line. The application that will let you achieve this is called [...]]]></description>
			<content:encoded><![CDATA[<p>There are some scenarios in Unix/Linux when you are stuck at the command line and not able to get to a GUI interface. With this in mind, there is a <a href="http://www.twitter.com/" target="_blank">Twitter</a> client out there that will let you view your tweets at the command line. The application that will let you achieve this is called <a href="http://marnanel.org/projects/blt/" target="_blank" title="BLT">BLT</a> (bash loves twitter). </p>
<p>BLT is a perl application that integrates <a href="http://www.twitter.com/" target="_blank">Twitter</a> into the command-line, and to install BLT, perform the following option:</p>
<div align="center"><code>sudo cpan App::BLT</code></div>
</p>
<p>After you have BLT installed, run <code>blt</code> at the command line and it will ask you for your <a href="http://www.twitter.com/" target="_blank">Twitter</a> username and password. You may also want to run a <code>blt --check</code> to grab the latest tweets from your account after you have set up the user interface.</p>
<p><span id="more-162"></span></p>
<p>To stay up-to-date with your tweets, you will want to run the following option at the command line from your home directory:</p>
<div align="center"><code>head .blt_content</code></p>
<p><img src="http://www.freemacunix.com/images/bltscreen.png" title="BLT at the command line" /></div>
</p>
<p>Please feel free to leave any feedback that you have on this handy little <a href="http://www.twitter.com/" target="_blank">Twitter</a> application.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/blt-command-line-twitter-client/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Want An OS X Dock On Your Linux Box?</title>
		<link>http://www.freemacunix.com/want-an-os-x-dock-on-your-linux-box/</link>
		<comments>http://www.freemacunix.com/want-an-os-x-dock-on-your-linux-box/#comments</comments>
		<pubDate>Thu, 27 Aug 2009 14:24:21 +0000</pubDate>
		<dc:creator>Chad Sweely</dc:creator>
				<category><![CDATA[Mac]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/?p=151</guid>
		<description><![CDATA[If you are an Linux user and want your desktop looking more like Apple OS X, this post is for you. One of the cool things that Apple&#8217;s OS X operating system includes is the dock down at the bottom of the main desktop window. This makes your commonly-used programs easy to get to without [...]]]></description>
			<content:encoded><![CDATA[<p>If you are an Linux user and want your desktop looking more like Apple OS X, this post is for you. One of the cool things that Apple&#8217;s OS X operating system includes is the dock down at the bottom of the main desktop window. This makes your commonly-used programs easy to get to without having to go through a process of searching for them.</p>
<p>With this in mind, there is an application that you can install on your Linux box that acts a dock for you. This application is called <a href="http://kdocker.sourceforge.net/" target="_blank" title="KDocker">KDocker</a>. </p>
<p align="center"><a href="http://kdocker.sourceforge.net/" title="KDocker" target="_blank"><img src="http://www.freemacunix.com/images/fmu_kdocker.jpg" title="KDocker" border=0 /></a></p>
<p><span id="more-151"></span>
<p>This application is available for the following Linux distributions:</p>
<ul>
<li>Suse</li>
<li>Slackware</li>
<li>Red Hat</li>
<li>Debian</li>
<li>Kubuntu</li>
</ul>
<p>For easy install in Ubuntu/Gnome, you can perform the following syntax in at the command line:</p>
<p align="center"><code>sudo apt-get install kdocker</code></p>
<p>This application is great for making your Linux GUI&#8217;s appearance like Apple OS X! <img src='http://www.freemacunix.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/want-an-os-x-dock-on-your-linux-box/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Play Tetris in Emacs</title>
		<link>http://www.freemacunix.com/play-tetris-in-emacs/</link>
		<comments>http://www.freemacunix.com/play-tetris-in-emacs/#comments</comments>
		<pubDate>Wed, 06 May 2009 18:39:27 +0000</pubDate>
		<dc:creator>Chad Sweely</dc:creator>
				<category><![CDATA[Mac]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/?p=82</guid>
		<description><![CDATA[If you&#8217;re ever using Emacs (Extensible Macro System) as an editor and feeling bored, you can always play Tetris in it. Playing Tetris in Emacs only works in the GNU environment which Mac OS X also runs under. The steps for running Tetris in Emacs have been provided below: In Terminal, type emacs at the [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re ever using Emacs (Extensible Macro System) as an editor and feeling bored, you can always play Tetris in it. Playing Tetris in Emacs only works in the GNU environment which Mac OS X also runs under. The steps for running Tetris in Emacs have been provided below:</p>
<ol>
<li>In <em>Terminal</em>, type <code>emacs</code> at the comment. Emacs will then appear for you.</li>
<li>In the Emacs window, press <em>&lt;ESC&gt;</em>. This will bring you to the note buffer section (shown below).<br />
<img src="http://www.freemacunix.com/images/thumb_emacs1.jpg" /></li>
<p><span id="more-82"></span></p>
<li>Once you are in the buffer section, press <code>x</code>, type in <code>tetris</code>, and then hit Enter. </li>
<li>Tetris will then appear for you (shown below).<br />
<img src="http://www.freemacunix.com/images/thumb_emacs2.jpg" /></li>
</ol>
<p>To move your pieces around in Tetris, use your right/left arrow keys in the direction you want the piece to move. Your up/down arrow keys will change the position of the piece, and your space bar will shoot the piece down the bottom. </p>
<p>This is a fun and interesting Easter Egg included in this classic editor!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/play-tetris-in-emacs/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Having trouble finding text with grep? Try grepping with color</title>
		<link>http://www.freemacunix.com/having-trouble-finding-text-with-grep-try-grepping-with-color/</link>
		<comments>http://www.freemacunix.com/having-trouble-finding-text-with-grep-try-grepping-with-color/#comments</comments>
		<pubDate>Tue, 10 Mar 2009 18:47:46 +0000</pubDate>
		<dc:creator>Chad Sweely</dc:creator>
				<category><![CDATA[Lessons]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/?p=70</guid>
		<description><![CDATA[Having trouble finding a needle in a haystack? You can always use grep --color to find what you are looking for. This method is best used for finding a specific piece of text in a document that is all on one line, or a unique string of text within a repetitious document. I have provided [...]]]></description>
			<content:encoded><![CDATA[<p>Having trouble finding a needle in a haystack? You can always use <code>grep --color</code> to find what you are looking for. This method is best used for finding a specific piece of text in a document that is all on one line, or a unique string of text within a repetitious document. I have provided the syntax for this grep option below:</p>
<p align="center"><code>grep --color "text" filename</code></p>
<p><strong>Example:</strong><br />
<img src="http://www.freemacunix.com/images/thumb_grepcolor.png" title="Grepping with color" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/having-trouble-finding-text-with-grep-try-grepping-with-color/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LSPCI and LSUSB</title>
		<link>http://www.freemacunix.com/lspci-and-lsusb/</link>
		<comments>http://www.freemacunix.com/lspci-and-lsusb/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 19:42:15 +0000</pubDate>
		<dc:creator>Chad Sweely</dc:creator>
				<category><![CDATA[Lessons]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/?p=45</guid>
		<description><![CDATA[The commands listed in this post are more for Linux than Unix. To find out information about the hardware of your computer, you can run an lspci command. Lspci will output the specifications of your hardware in a list style arrangement as shown below: If you want to get more specific in your lspci output [...]]]></description>
			<content:encoded><![CDATA[<p>The commands listed in this post are more for Linux than Unix. To find out information about the hardware of your computer, you can run an <code>lspci</code> command. <code>Lspci</code> will output the specifications of your hardware in a list style arrangement as shown below:</p>
<p align="center"><img src="http://www.freemacunix.com/images/thumb_fmu_lspci.jpg" title="lspci example" /></p>
<p>If you want to get more specific in your <code>lspci</code> output (e.g. wanting just to display a certain brand), you can always do <code>lspci | grep -i "Productname"</code> which will only return results that includes the string from your <code>grep</code> command. For example, if I wanted to find all of the hardware made by Broadcom, I would do <code>lspci | grep -i "broadcom"</code> and the results would return only hardware that mentions Broadcom. </p>
<p><span id="more-45"></span>Although, this will only display hardware that is <em>inside</em> your computer, it will not display any hardware that is attached by USB. This is where the command <code>lsusb</code> comes in. <code>Lsusb</code> will list all of the USB ports you have in your computer and display any hardware specifications that are plugged-in to them as shown in the example below:</p>
<p align="center"><img src="http://www.freemacunix.com/images/thumb_fmu_lsusb.jpg" title="lsusb example" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/lspci-and-lsusb/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Need to find a SMALL amount of text in a BIG directory? No problem!</title>
		<link>http://www.freemacunix.com/need-to-find-a-small-amount-of-text-in-a-big-directory-no-problem/</link>
		<comments>http://www.freemacunix.com/need-to-find-a-small-amount-of-text-in-a-big-directory-no-problem/#comments</comments>
		<pubDate>Thu, 22 Jan 2009 18:49:51 +0000</pubDate>
		<dc:creator>Chad Sweely</dc:creator>
				<category><![CDATA[Lessons]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/need-to-find-a-small-amount-of-text-in-a-big-directory-no-problem/</guid>
		<description><![CDATA[Have you ever tried to grep in a directory that has a vast amount of files and you received an error like this? (below) If so, there is a simple way around this. Just use this: find . &#124; xargs grep "yahoo" * &#124; more. I will break down these processes for you: find . [...]]]></description>
			<content:encoded><![CDATA[<p>Have you ever tried to <code>grep</code> in a directory that has a vast amount of files and you received an error like this? (below)</p>
<p align="center"><img src="http://www.freemacunix.com/images/thumb_fmu_greperror.jpg" title="Grep Error" /></p>
<p>If so, there is a simple way around this. Just use this: <code>find . | xargs grep "yahoo" * | more</code>. I will break down these processes for you:</p>
<ul>
<li><code>find .</code> &#8211; <em>Find</em> is a command that outputs the location of a file. In this case by specifying a ., the search will only be done in the present directory.</li>
<li><code>xargs</code> &#8211; This allows a command to be executed from standard input. This also helps force the <code>grep</code> command (coming next) to return output, even when the directory is too large.</li>
<li><code>grep</code> &#8211; The way we will be using this command is to search through a file for a specific string. If you are looking for straight text, it is best to use quotes (e.g. &#8220;text&#8221;) to help the command line decipher exactly what you are looking for. More info on grep can be found on this <a href="http://www.freemacunix.com/searching-for-a-file-with-a-specific-string-in-the-file/" target="_blank">earlier post</a>.</li>
<li><code>more</code> &#8211; This command is optional for this process. <em>More</em> would be best used if you were expecting a full page of output returned from your search, and want to be prompted for the next page. This option would be very beneficial if the string you are searching for would be common in your results.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/need-to-find-a-small-amount-of-text-in-a-big-directory-no-problem/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Apropos</title>
		<link>http://www.freemacunix.com/apropos/</link>
		<comments>http://www.freemacunix.com/apropos/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 19:35:13 +0000</pubDate>
		<dc:creator>Chad Sweely</dc:creator>
				<category><![CDATA[Definitions]]></category>
		<category><![CDATA[Lessons]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/apropos/</guid>
		<description><![CDATA[Ever wanted to use a command to do something, but couldn&#8217;t quite figure out the actual command to accomplish what you need done? Try using apropos! Apropos is a way to browse through the help area of the Unix/Linux operating system for a command that will help achieve your goal. For example, if I wanted [...]]]></description>
			<content:encoded><![CDATA[<p>Ever wanted to use a command to do something, but couldn&#8217;t quite figure out the actual command to accomplish what you need done? Try using <code>apropos</code>! <code>Apropos</code> is a way to browse through the help area of the Unix/Linux operating system for a command that will help achieve your goal. For example, if I wanted to find commands that relate to &#8220;secure&#8221;, I would enter <code>apropos secure</code> at the command line, and the kernel would return the results listed below along with any services that involve &#8216;secure&#8217;:</p>
<p align="center"><img src="http://www.freemacunix.com/images/scrnshotapropos.png" title="Apropos Results" /></p>
<p>As always, if you wanted to get a more elaborate description on a command or service, you can always use <code>man</code> (shortened for: manual). This will display a full description, and various options of a command which you have found using <code>apropos</code>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/apropos/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Alias</title>
		<link>http://www.freemacunix.com/alias/</link>
		<comments>http://www.freemacunix.com/alias/#comments</comments>
		<pubDate>Thu, 16 Oct 2008 14:02:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Lessons]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/alias/</guid>
		<description><![CDATA[The alias command is very useful. It is kind of a shortcut in some ways. I get tired of tying ls -la so I can see all the info for my files so what i do is type alias ls 'ls -la'. What this command does is that it sets up an alias so that [...]]]></description>
			<content:encoded><![CDATA[<p>The <code>alias</code> command is very useful. It is kind of a shortcut in some ways. I get tired of tying <code>ls -la</code> so I can see all the info for my files so what i do is type <code>alias ls 'ls -la'</code>. What this command does is that it sets up an alias so that every time I type <code>ls</code> the computer treats is as though I typed <code>ls -la</code>. There are many other things you can do also. Say you have a long command you run a lot. You can alias it to something like mc.</p>
<p>Ex: <code>alias mc 'locate log_error | grep -R 192.168.1.1 *'</code></p>
<p>Your command can be as long or as short that you want to alias. I also use it to setup ssh connections.</p>
<p>Ex: <code>alias con1 'ssh usrname@192.168.1.1'</code></p>
<p>Now any time I type con1 it will try to make an ssh connection to that ip address.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/alias/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The diff command</title>
		<link>http://www.freemacunix.com/the-diff-command/</link>
		<comments>http://www.freemacunix.com/the-diff-command/#comments</comments>
		<pubDate>Tue, 12 Aug 2008 15:13:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Lessons]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/the-diff-command/</guid>
		<description><![CDATA[The diff command is a very useful command to see the differences between two files. An example of this command would be diff file1.txt file2.txt It takes file2.txt and compares it to file1.txt and displays the differences that are in file2.txt. You may also want to use the -b options in the command because that [...]]]></description>
			<content:encoded><![CDATA[<p>The diff command is a very useful command to see the differences between two files. An example of this command would be</p>
<p><code>diff file1.txt file2.txt</code></p>
<p>It takes file2.txt and compares it to file1.txt and displays the differences that are in file2.txt. You may also want to use the <code>-b</code> options in the command because that will allow it to ignore differences in white space. This command is very useful in programming when you have a backup version of a script that you just modified.  If the script no longer works it can help you track down bugs, by looking at backup version of the script that does work.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/the-diff-command/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>The kill command</title>
		<link>http://www.freemacunix.com/the-kill-command/</link>
		<comments>http://www.freemacunix.com/the-kill-command/#comments</comments>
		<pubDate>Mon, 16 Jun 2008 14:16:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Lessons]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://www.freemacunix.com/the-kill-command/</guid>
		<description><![CDATA[Today we are going to look at a command that you don&#8217;t use very much in a Unix environment. The kill command. It is used when an application is stuck or not responding. The basic form of the command is kill [option]... PID. The PID is the process ID, you can get it by using [...]]]></description>
			<content:encoded><![CDATA[<p>Today we are going to look at a command that you don&#8217;t use very much in a Unix environment. The <code>kill</code> command. It is used when an application is stuck or not responding. The basic form of the command is <code>kill [option]... PID</code>. The PID is the process ID, you can get it by using the <code>top</code> command that I talked about previously. The most common option for the <code>kill</code> command is the <code>-9</code> option. It will kill the process immediately.</p>
<p>Example</p>
<p><code>kill -9 2342</code></p>
<p>If you type <code>top</code> again you should see that the process that was associated with that PID is no longer running.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.freemacunix.com/the-kill-command/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

