<?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:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Unix Tip: Commands</title>
	<atom:link href="http://gigaom.com/apple/unix-tip-commands/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/apple/unix-tip-commands/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 12:44:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dig Into Unix</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316654</link>
		<dc:creator><![CDATA[Dig Into Unix]]></dc:creator>
		<pubDate>Wed, 10 Jun 2009 21:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316654</guid>
		<description><![CDATA[[...] Now, at this point, it&#8217;s important to understand a few things about the Terminal. For one, the commands that you can type are interpreted and carried out immediately, no waiting around. So, if you tell it to remove a file, it will do it right then, with no easy way of recovering it. There isn&#8217;t a recycle bin on the command line (not without a little coaxing anyway). Secondly, since Unix was developed decades ago, many of the commands seem a bit archaic. Back when most of these utilities were written, they were all abbreviated to save space and cut down on the number of keystrokes you&#8217;d need to type. Below is a list of a few essentials, and another list from Nick&#8217;s post is here. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Now, at this point, it&#8217;s important to understand a few things about the Terminal. For one, the commands that you can type are interpreted and carried out immediately, no waiting around. So, if you tell it to remove a file, it will do it right then, with no easy way of recovering it. There isn&#8217;t a recycle bin on the command line (not without a little coaxing anyway). Secondly, since Unix was developed decades ago, many of the commands seem a bit archaic. Back when most of these utilities were written, they were all abbreviated to save space and cut down on the number of keystrokes you&#8217;d need to type. Below is a list of a few essentials, and another list from Nick&#8217;s post is here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Stig</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316653</link>
		<dc:creator><![CDATA[The Stig]]></dc:creator>
		<pubDate>Thu, 11 Jan 2007 16:10:59 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316653</guid>
		<description><![CDATA[1) pwd actually stands for Print Working Directory.

2) In the above examples the use of &#039;..&#039; to &quot;tell&quot; cd to move a level up isn&#039;t quite accurate. Instead, &#039;..&#039; is a directory itself, which links to the parent directory. All directories (or folders) have &#039;..&#039; in them, even those at the top (/). All directories have &#039;.&#039; in them as well, which is a directory which links to the current directory. The effect is the same but the semantics aren&#039;t, given the writing - &#039;..&#039; is not a special case and is not tied to the &#039;cd&#039; command but rather part of the file system.

UNIX semantics become important as you go deeper so it&#039;s best to learn these concepts properly from the start.]]></description>
		<content:encoded><![CDATA[<p>1) pwd actually stands for Print Working Directory.</p>
<p>2) In the above examples the use of &#8216;..&#8217; to &#8220;tell&#8221; cd to move a level up isn&#8217;t quite accurate. Instead, &#8216;..&#8217; is a directory itself, which links to the parent directory. All directories (or folders) have &#8216;..&#8217; in them, even those at the top (/). All directories have &#8216;.&#8217; in them as well, which is a directory which links to the current directory. The effect is the same but the semantics aren&#8217;t, given the writing &#8211; &#8216;..&#8217; is not a special case and is not tied to the &#8216;cd&#8217; command but rather part of the file system.</p>
<p>UNIX semantics become important as you go deeper so it&#8217;s best to learn these concepts properly from the start.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316652</link>
		<dc:creator><![CDATA[Thomas]]></dc:creator>
		<pubDate>Thu, 11 Jan 2007 13:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316652</guid>
		<description><![CDATA[I would put aliases last on the list of things to teach people. Over the years I can&#039;t tell you how many people got used to their aliases and after a while they couldn&#039;t use the standard interface to save their backsides.

Instead, I would get into more &quot;obscure&quot; but useful commands, such as file, cut, and so forth.]]></description>
		<content:encoded><![CDATA[<p>I would put aliases last on the list of things to teach people. Over the years I can&#8217;t tell you how many people got used to their aliases and after a while they couldn&#8217;t use the standard interface to save their backsides.</p>
<p>Instead, I would get into more &#8220;obscure&#8221; but useful commands, such as file, cut, and so forth.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lordmike</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316651</link>
		<dc:creator><![CDATA[Lordmike]]></dc:creator>
		<pubDate>Thu, 11 Jan 2007 06:43:54 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316651</guid>
		<description><![CDATA[I forgot to mention that if you use vi or vim (vim is just an improved vi editor, Vi IMproved or something like that) you edit the file by clicking a or i, a is before the cursor and i after the cursor. When you&#039;re done with the file you hit Escape key and the type :wq! to write the file and to quit. If you don&#039;t want any changes saved, you can do :q! to just quit.

More info on vi here http://www.eng.hawaii.edu/Tutor/vi.html]]></description>
		<content:encoded><![CDATA[<p>I forgot to mention that if you use vi or vim (vim is just an improved vi editor, Vi IMproved or something like that) you edit the file by clicking a or i, a is before the cursor and i after the cursor. When you&#8217;re done with the file you hit Escape key and the type :wq! to write the file and to quit. If you don&#8217;t want any changes saved, you can do :q! to just quit.</p>
<p>More info on vi here <a href="http://www.eng.hawaii.edu/Tutor/vi.html" rel="nofollow">http://www.eng.hawaii.edu/Tutor/vi.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lordmike</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316650</link>
		<dc:creator><![CDATA[Lordmike]]></dc:creator>
		<pubDate>Thu, 11 Jan 2007 06:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316650</guid>
		<description><![CDATA[The mv command is also used for renaming files. Ex. mv text1.txt text1.htm will rename text1.txt to text1.htm
Another good command is cat which is used to create files and look at files, like cat text will display the contest of the file and cat &gt; text.txt will create the file text.txt
But if you&#039;re just going to creat a text file I recommend using vi, vim, nano, emacs or any other good shell editor. Like vim text.txt will let you creat that textfile for editing at once.
Be careful when you use cp, because you can do cp text1 text2 and text2 will be overwritten with text1 if the file already exists.

Same with rm text* can be used to delete all files where the name begins with text and rm text * will delete text file plus every other file in that directory without telling you.

Use the who command and you will see every user logged on.

Use the less command to browse inside files without being able to edit them. Can be handy when reading README files etc.
less is more is a common quote(?!) and means that the command less shows more then the command more. If I remember correct, when you use more, you won&#039;t be able to scroll back up. This works with less.

grep is a good command to search a file for words etc, but I would rather use spotlight for this. And I never really got around to use it much in linux.
If someone wants to continue here on tutorial of grep I&#039;ll be glad. Seems to be a great command and probably does more then I know.]]></description>
		<content:encoded><![CDATA[<p>The mv command is also used for renaming files. Ex. mv text1.txt text1.htm will rename text1.txt to text1.htm<br />
Another good command is cat which is used to create files and look at files, like cat text will display the contest of the file and cat &gt; text.txt will create the file text.txt<br />
But if you&#8217;re just going to creat a text file I recommend using vi, vim, nano, emacs or any other good shell editor. Like vim text.txt will let you creat that textfile for editing at once.<br />
Be careful when you use cp, because you can do cp text1 text2 and text2 will be overwritten with text1 if the file already exists.</p>
<p>Same with rm text* can be used to delete all files where the name begins with text and rm text * will delete text file plus every other file in that directory without telling you.</p>
<p>Use the who command and you will see every user logged on.</p>
<p>Use the less command to browse inside files without being able to edit them. Can be handy when reading README files etc.<br />
less is more is a common quote(?!) and means that the command less shows more then the command more. If I remember correct, when you use more, you won&#8217;t be able to scroll back up. This works with less.</p>
<p>grep is a good command to search a file for words etc, but I would rather use spotlight for this. And I never really got around to use it much in linux.<br />
If someone wants to continue here on tutorial of grep I&#8217;ll be glad. Seems to be a great command and probably does more then I know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kristof</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316649</link>
		<dc:creator><![CDATA[kristof]]></dc:creator>
		<pubDate>Wed, 10 Jan 2007 23:04:22 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316649</guid>
		<description><![CDATA[Another comment that can be useful is the &quot;apropos&quot;-command. When you want to do something, and you don&#039;t know what the command for doing the thing you want to do is, just type

apropos &quot;whatYouWantToSearchFor&quot;

and it will give you a list with commands that could solve your problem.]]></description>
		<content:encoded><![CDATA[<p>Another comment that can be useful is the &#8220;apropos&#8221;-command. When you want to do something, and you don&#8217;t know what the command for doing the thing you want to do is, just type</p>
<p>apropos &#8220;whatYouWantToSearchFor&#8221;</p>
<p>and it will give you a list with commands that could solve your problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Santilli</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316648</link>
		<dc:creator><![CDATA[Nick Santilli]]></dc:creator>
		<pubDate>Wed, 10 Jan 2007 22:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316648</guid>
		<description><![CDATA[thanks Howard - taking care of that now.]]></description>
		<content:encoded><![CDATA[<p>thanks Howard &#8211; taking care of that now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Howard Melman</title>
		<link>http://gigaom.com/apple/unix-tip-commands/#comment-316647</link>
		<dc:creator><![CDATA[Howard Melman]]></dc:creator>
		<pubDate>Wed, 10 Jan 2007 22:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/2007/01/10/unix-tip-commands/#comment-316647</guid>
		<description><![CDATA[Just some typos: The last cp example says &quot;cd&quot;.  Also you probably want to bold the &quot;man ls&quot; example.]]></description>
		<content:encoded><![CDATA[<p>Just some typos: The last cp example says &#8220;cd&#8221;.  Also you probably want to bold the &#8220;man ls&#8221; example.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

