 
    
<?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>commands Archives - Complete, Concrete, Concise</title>
	<atom:link href="https://complete-concrete-concise.com/tag/commands/feed/" rel="self" type="application/rss+xml" />
	<link>https://complete-concrete-concise.com/tag/commands/</link>
	<description>Practical Information Without The Bloat</description>
	<lastBuildDate>Tue, 30 Apr 2013 19:59:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>Ubuntu 13.04 &#8211; Basic Command Line Techniques</title>
		<link>https://complete-concrete-concise.com/ubuntu-2/ubuntu-13-04/ubuntu-13-04-basic-command-line-techniques/</link>
		
		<dc:creator><![CDATA[richardsplanet]]></dc:creator>
		<pubDate>Tue, 30 Apr 2013 19:59:01 +0000</pubDate>
				<category><![CDATA[Ubuntu 13.04]]></category>
		<category><![CDATA[basic]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[commands]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[shell]]></category>
		<category><![CDATA[terminal]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[ubuntu 13.04]]></category>
		<guid isPermaLink="false">http://complete-concrete-concise.com/?p=2925</guid>

					<description><![CDATA[<p>Using the command line doesn't have to be mysterious or hard.</p>
<p>The post <a href="https://complete-concrete-concise.com/ubuntu-2/ubuntu-13-04/ubuntu-13-04-basic-command-line-techniques/">Ubuntu 13.04 &#8211; Basic Command Line Techniques</a> appeared first on <a href="https://complete-concrete-concise.com">Complete, Concrete, Concise</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="c1">
<p>This tutorial is for Ubuntu 13.04.</p>
<p>It is probably the same for every other version of Ubuntu and all other Linux distros, but I make no guarantee.</p>
</div>
<p>Linux (on which Ubuntu is based) is fundamentally a command line driven operating system. While there are graphical interfaces to many of the available commands, sometimes you need (or have no choice) to work at the command line.</p>
<p>There are five fundamental things everyone working at the command line should know (or at least be aware of):</p>
<ol>
<li>man</li>
<li>pipes</li>
<li>redirection</li>
<li>less (or more)</li>
<li>ls</li>
</ol>
<h1>man</h1>
<div class="c1">
<p><code>man</code> is short for <u>manual</u></p>
</div>
<p><code>man</code> is the help file.</p>
<p>When you want to know more about a command, you enter <code>man <em>&lt;command name&gt;</em></code> to display information about the command. For example:</p>
<pre><code>man ls</code></pre>
<p>will bring up the <code>man</code> page for the command <code>ls</code>. You could also enter <code>man man</code> to display information about the <code>man</code> command. The <code>man</code> page for <code>ls</code> looks something like this:</p>
<p><a href="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-techniques-1-big.png" target="_blank"><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-techniques-1-thumb.png" alt="" border="0" class="centered" /></a></p>
<p>To navigate through a <code>man</code> you use the following commands:</p>
<ul>
<li>q &#8211; exit (quit) the man page</li>
<li>SPACE or f &#8211; forward to the next page</li>
<li>b &#8211; backward to the previous page</li>
<li>e &#8211; forward one line</li>
<li>y &#8211; backward one line</li>
</ul>
<div class="c4">
<p>While there are <code>man</code> pages for pretty much every command, there is no <code>man</code> page for the command <code>cd</code>.</p>
</div>
<h1>Pipes</h1>
<p>Pipes allow you to send the displayed output from one command to another command.</p>
<p>In other words, when you enter a command that displays a bunch of information on the terminal (and maybe scrolls past the top of the terminal), you can use a pipe to send that information to another command.</p>
<p>The most common use of pipes is with the <code>more</code> (or, preferably, <code>less</code>) command. This is especially true when information scrolls past the top of the terminal.</p>
<p>The pipe is the vertical bar (or broken bar) symbol: &#8216;<code>|</code>&#8216;.</p>
<p>For example, any of the following commands is likely display information that will scroll past the top of the terminal:</p>
<pre><code>ls /bin
ls /etc
ls /lib</code></pre>
<p>If we pipe the output to the <code>more</code> command, then we can scroll through the output one display page at a time:</p>
<pre><code>ls /etc | more</code></pre>
<p>Another common use of pipes is with the <code>grep</code> command. (<code>grep</code> is often used to filter out unwanted information &#8211; but I won&#8217;t be covering <code>grep</code> here.)</p>
<p>You can pipe together as many commands as you like. The output from the command on the left of the pipe is sent to the command on the right of the pipe.</p>
<h1>Redirection</h1>
<p>Sometimes you need to capture the information displayed by a command. This is done using redirection.</p>
<p>The output displayed by a command can be sent to a file instead of the display.</p>
<p>The redirection operator is the greater than symbol: &#8216;&gt;&#8217;.</p>
<p>For example, suppose I want to dump a <code>man</code> page to file, so I can later look at (or print that file). I can do so by redirecting the <code>man</code> output to a file (you choose the name of the file):</p>
<pre><code>man ls > ls.txt</code></pre>
<p>The above command will send the output of the <code>man</code> page for <code>ls</code> to a file called <u>ls.txt</u>. I can then handle <u>ls.txt</u> the same way I handle any text file.</p>
<p>Another example, I could send a directory listing to a file as well:</p>
<pre><code>ls > directory_list</code></pre>
<p>The above command will send the output of <code>ls</code> to a file called <u>directory_list</u>. Again, the file can be handled the same way any other text file is handled.</p>
<p>Redirection always send stores the file in the current directory (normally, this will be your <code>/home/<i>&lt;user&gt;</i></code> directory). You can write the file to another directory by either (1) changing to a different directory (using the <code>cd</code> command), or (2) specifying the path along with the file name. <strong>Note:</strong> you may not have permission to write in other directories, so the operation will fail.</p>
<h1>less</h1>
<div class="c1">
<p><code>less</code> is an improved version of the <code>more</code> command. The main advantage of using <code>less</code> instead of <code>more</code> is that <code>less</code> lets you scroll backwards through data that has been piped to it; <code>more</code> only allows you to scroll forward through piped data. Other than that difference, <code>less</code> and <code>more</code> behave almost identically.</p>
</div>
<p><code>less</code> is used to display information one page at a time.</p>
<p>Most often it is used in conjunction with pipes to prevent output from scrolling off the top of the terminal:</p>
<pre><code>ls | less</code></pre>
<p><code>less</code> can be used to display the contents of a text file:</p>
<pre><code>less <i>&lt;file name&gt;</i></code></pre>
<p>where <i>&lt;file name&gt;</i> is the name of the text file to display.</p>
<p>To navigate through text being displayed by <code>less</code> you use the following commands:</p>
<ul>
<li>q &#8211; exit (quit) <code>less</code></li>
<li>SPACE or f &#8211; forward to the next page</li>
<li>b &#8211; backward to the previous page (does not work if <code>more</code> is displaying text from a pipe and the main reason why  <code>less</code> is preferred)</li>
<h1>ls</h1>
<div class="c1">
<p><code>ls</code> is short for <u>list</u></p>
</div>
<p><code>ls</code> is used to display the contents of a directory.</p>
<p><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-techniques-2.png" alt="" border="0" class="centered" data-recalc-dims="1"/></p>
<p>Directory contents are colour coded. Different files have different colours.</p>
<p>The default colours (in the default Ubuntu 13.04 terminal) for common file types are:</p>
<div class="c2">
<p><strong>Note:</strong> if you or someone has configured your system, or you are using a different terminal (or a different Linux distribution), the colours and their significance may be completely different.</p>
</div>
<p><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-colours.png" alt="" border="0" class="centered" data-recalc-dims="1"/></p>
<p>There are other colour combinations in use and some colours (notably purple) are reused for other file types.</p>

<p>The post <a href="https://complete-concrete-concise.com/ubuntu-2/ubuntu-13-04/ubuntu-13-04-basic-command-line-techniques/">Ubuntu 13.04 &#8211; Basic Command Line Techniques</a> appeared first on <a href="https://complete-concrete-concise.com">Complete, Concrete, Concise</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Ubuntu 12.04 &#8211; Basic Command Line Techniques</title>
		<link>https://complete-concrete-concise.com/ubuntu-2/ubuntu-12-04/ubuntu-12-04-basic-command-line-techniques/</link>
		
		<dc:creator><![CDATA[richardsplanet]]></dc:creator>
		<pubDate>Thu, 13 Dec 2012 14:57:21 +0000</pubDate>
				<category><![CDATA[Ubuntu 12.04]]></category>
		<category><![CDATA[basic]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[commands]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[shell]]></category>
		<category><![CDATA[terminal]]></category>
		<category><![CDATA[tutorial]]></category>
		<category><![CDATA[ubuntu 12.04]]></category>
		<guid isPermaLink="false">http://complete-concrete-concise.com/?p=2598</guid>

					<description><![CDATA[<p>This tutorial is for Ubuntu 12.04. It should be the same for every other version of Ubuntu and all other Linux distros, but I make no guarantee. Linux (on which Ubuntu is based) is fundamentally a command line driven operating system. While there are graphical interfaces to many of the available commands, sometimes you need [&#8230;]</p>
<p>The post <a href="https://complete-concrete-concise.com/ubuntu-2/ubuntu-12-04/ubuntu-12-04-basic-command-line-techniques/">Ubuntu 12.04 &#8211; Basic Command Line Techniques</a> appeared first on <a href="https://complete-concrete-concise.com">Complete, Concrete, Concise</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div class="c1">
<p>This tutorial is for Ubuntu 12.04.</p>
<p>It should be the same for every other version of Ubuntu and all other Linux distros, but I make no guarantee.</p>
</div>
<p>Linux (on which Ubuntu is based) is fundamentally a command line driven operating system. While there are graphical interfaces to many of the available commands, sometimes you need (or have no choice) to work at the command line.</p>
<p>There are five fundamental things everyone working at the command line should know (or at least be aware of):</p>
<ol>
<li>man</li>
<li>pipes</li>
<li>redirection</li>
<li>more</li>
<li>ls</li>
</ol>
<h1>man</h1>
<div class="c1">
<p><code>man</code> is short for <u>manual</u></p>
</div>
<p><code>man</code> is the help file.</p>
<p>When you want to know more about a command, you enter <code>man <em>&lt;command name&gt;</em></code> to display information about the command. For example:</p>
<pre><code>man ls</code></pre>
<p>will bring up the <code>man</code> page for the command <code>ls</code>. You could also enter <code>man man</code> to display information about the <code>man</code> command. The <code>man</code> page for <code>ls</code> looks something like this:</p>
<p><a href="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-techniques-1-big.png" target="_blank"><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-techniques-1-thumb.png" alt="" border="0" class="centered"/></a></p>
<p>To navigate through a <code>man</code> you use the following commands:</p>
<ul>
<li>q &#8211; exit (quit) the man page</li>
<li>SPACE or f &#8211; forward to the next page</li>
<li>b &#8211; backward to the previous page</li>
<li>e &#8211; forward one line</li>
<li>y &#8211; backward one line</li>
</ul>
<div class="c4">
<p>For some reason, there is no <code>man</code> page for the command <code>cd</code>.</p>
</div>
<h1>Pipes</h1>
<p>Pipes allow you to send the displayed output from one command to another command.</p>
<p>In other words, when you enter a command that displays a bunch of information on the terminal (and maybe scrolls past the top of the terminal), you can use a pipe to send that information to another command.</p>
<p>The most common use of pipes is with the <code>more</code> command. This is especially true when information scrolls past the top of the terminal.</p>
<p>The pipe is the vertical bar (or broken bar) symbol: &#8216;<code>|</code>&#8216;.</p>
<p>For example, any of the following commands is likely display information that will scroll past the top of the terminal:</p>
<pre><code>ls /bin
ls /etc
ls /lib</code></pre>
<p>If we pipe the output to the <code>more</code> command, then we can scroll through the output one display page at a time:</p>
<pre><code>ls /etc | more</code></pre>
<p>Another common use of pipes is with the <code>grep</code> command. (<code>grep</code> is often used to filter out unwanted information &#8211; but I won&#8217;t be covering <code>grep</code> here.)</p>
<p>You can pipe together as many commands as you like. The output from the command on the left of the pipe is sent to the command on the right of the pipe.</p>
<h1>Redirection</h1>
<p>Sometimes you need to capture the information displayed by a command. This is done using redirection.</p>
<p>The output displayed by a command can be sent to a file instead of the display.<./p></p>
<p>The redirection operator is the greater than symbol: &#8216;&#038;gt&#8217;.</p>
<p>For example, suppose I want to dump a <code>man</code> page to file, so I can later look at (or print that file). I can do so by redirecting the <code>man</code> output to a file (you choose the name of the file):</p>
<pre><code>man ls > ls.txt</code></pre>
<p>The above command will send the output of the <code>man</code> page for <code>ls</code> to a file called <u>ls.txt</u>. I can then handle <u>ls.txt</u> the same way I handle any text file.</p>
<p>Another example, I could send a directory listing to a file as well:</p>
<pre><code>ls > directory_list</code></pre>
<p>The above command will send the output of <code>ls</code> to a file called <u>directory_list</u>. Again, the file can be handled the same way any other text file is handled.</p>
<p>Redirection always send stores the file in the current directory (normally, this will be your <code>/home/<i>&lt;user&gt;</i></code> directory). You can write the file to another directory by either (1) changing to a different directory (using the <code>cd</code> command), or (2) specifying the path along with the file name. <strong>Note:</strong> you may not have permission to write in other directories, so the operation will fail.</p>
<h1>more</h1>
<p><code>more</code> is used to display information one page at a time.</p>
<p>Most often it is used in conjunction with pipes to prevent output from scrolling off the top of the terminal:</p>
<pre><code>ls | more</code></pre>
<p><code>more</code> can be used to display the contents of a text file:</p>
<pre><code>more <i>&lt;file name&gt;</i></code></pre>
<p>where <i>&lt;file name&gt;</i> is the name of the text file to display.</p>
<p>To navigate through text being displayed by <code>more</code> you use the following commands:</p>
<ul>
<li>q &#8211; exit (quit) <code>more</code></li>
<li>SPACE or f &#8211; forward to the next page</li>
<li>b &#8211; backward to the previous page (does not work if <code>more</code> is displaying text from a pipe)</li>
<div class="c1">
<p>There is a slightly more useful command called <code>less</code> that allows you to scroll forwards and backwards through piped information. Aside from that difference <code>less</code> behaves very much like <code>more</code>.</p>
<p>You can use <code>man less</code> to learn about the <code>less</code> command</p>
</div>
<h1>ls</h1>
<div class="c1">
<p><code>ls</code> is short for <u>list</u></p>
</div>
<p><code>ls</code> is used to display the contents of a directory.</p>
<p><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-techniques-2.png" alt="" border="0" class="centered"/></p>
<p>Directory contents are colour coded. Different files have different colours.</p>
<p>The default colours (in the default Ubuntu 12.04 terminal) for common file types are:</p>
<p><img decoding="async" src="//complete-concrete-concise.com/wp-content/uploads/2012/12/basic-command-line-colours.png" alt="" border="0" class="centered"/></p>
<p>There are other colour combinations in use and some colours (notably purple) are reused for other file types.</p>

<p>The post <a href="https://complete-concrete-concise.com/ubuntu-2/ubuntu-12-04/ubuntu-12-04-basic-command-line-techniques/">Ubuntu 12.04 &#8211; Basic Command Line Techniques</a> appeared first on <a href="https://complete-concrete-concise.com">Complete, Concrete, Concise</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
