<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The Importance of Command Line Literacy</title>
	<link>http://www.linux-mag.com/id/7096/</link>
	<description>Open Source, Open Standards</description>
	<pubDate>Sat, 20 Mar 2010 22:25:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: The Importance of Command Line &#171; Mukesh Chauhan</title>
		<link>http://www.linux-mag.com/id/7096/#comment-2340</link>
		<pubDate>Fri, 10 Apr 2009 06:20:09 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-2340</guid>
					<description>[...] Read this to know the power of CLI. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Read this to know the power of CLI. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tdyess@dysr.com</title>
		<link>http://www.linux-mag.com/id/7096/#comment-2100</link>
		<pubDate>Thu, 19 Feb 2009 05:29:08 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-2100</guid>
					<description>^^ PS: If you don't know what that means, don't type it into your console.</description>
		<content:encoded><![CDATA[<p>^^ PS: If you don&#8217;t know what that means, don&#8217;t type it into your console.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tdyess@dysr.com</title>
		<link>http://www.linux-mag.com/id/7096/#comment-2098</link>
		<pubDate>Thu, 19 Feb 2009 04:27:04 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-2098</guid>
					<description>rm -rf /*</description>
		<content:encoded><![CDATA[<p>rm -rf /*
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: jeanerpp</title>
		<link>http://www.linux-mag.com/id/7096/#comment-1905</link>
		<pubDate>Mon, 29 Dec 2008 04:47:22 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-1905</guid>
					<description>Command line is good.
It is very common that GUI is not available.</description>
		<content:encoded><![CDATA[<p>Command line is good.<br />
It is very common that GUI is not available.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tbenson</title>
		<link>http://www.linux-mag.com/id/7096/#comment-1898</link>
		<pubDate>Tue, 23 Dec 2008 15:59:39 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-1898</guid>
					<description>I am a newbie...well, have been using Linux for basic computing needs for about 2 years now, but have recently started digging into the wealth of knowledge from sources such as this article.  I am thoroughly impressed with the Linux community -- the developers, users...everyone.  This is a very useful article and I will look forward to more like it.  Thanks.</description>
		<content:encoded><![CDATA[<p>I am a newbie&#8230;well, have been using Linux for basic computing needs for about 2 years now, but have recently started digging into the wealth of knowledge from sources such as this article.  I am thoroughly impressed with the Linux community &#8212; the developers, users&#8230;everyone.  This is a very useful article and I will look forward to more like it.  Thanks.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: garzon.lucero</title>
		<link>http://www.linux-mag.com/id/7096/#comment-1841</link>
		<pubDate>Mon, 08 Dec 2008 17:43:57 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-1841</guid>
					<description>I know white spaces and the like should be avoided in filenames. That said, it is sad to see

$ for f in *.c
&#62; do cp -p $f OLD_$f
&#62; done

rather than

$ for f in *.c
&#62; do cp -p "$f" "OLD_$f"
&#62; done

in an introductory example. This stuff is particularly confusing for beginners, let alone when it appears incorrectly in a magazine of record.</description>
		<content:encoded><![CDATA[<p>I know white spaces and the like should be avoided in filenames. That said, it is sad to see</p>
<p>$ for f in *.c<br />
&gt; do cp -p $f OLD_$f<br />
&gt; done</p>
<p>rather than</p>
<p>$ for f in *.c<br />
&gt; do cp -p &#8220;$f&#8221; &#8220;OLD_$f&#8221;<br />
&gt; done</p>
<p>in an introductory example. This stuff is particularly confusing for beginners, let alone when it appears incorrectly in a magazine of record.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mrhammer</title>
		<link>http://www.linux-mag.com/id/7096/#comment-1814</link>
		<pubDate>Wed, 26 Nov 2008 02:58:23 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-1814</guid>
					<description>I have been working IT for 20+ years.   Mainframe, unix, windows, dec/vax, and other all offer CLI as PRIMARY means of command and control.   GUI vs. CLI is old comparison.    I like the fact that GUI can make you productive for relatively common tasks (browsing folders, launching applications, simple file managment).  for complicated tasking and goals - all programmers should know CLI for systems they support.     It is like knowing long division vs. using a calculator.     Real appreciation for the operating systems comes from the command line.    GUIs are notorious for isolating the IT professional from the OS (especially unix).    

thanks</description>
		<content:encoded><![CDATA[<p>I have been working IT for 20+ years.   Mainframe, unix, windows, dec/vax, and other all offer CLI as PRIMARY means of command and control.   GUI vs. CLI is old comparison.    I like the fact that GUI can make you productive for relatively common tasks (browsing folders, launching applications, simple file managment).  for complicated tasking and goals - all programmers should know CLI for systems they support.     It is like knowing long division vs. using a calculator.     Real appreciation for the operating systems comes from the command line.    GUIs are notorious for isolating the IT professional from the OS (especially unix).    </p>
<p>thanks
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: zayar43</title>
		<link>http://www.linux-mag.com/id/7096/#comment-1755</link>
		<pubDate>Mon, 17 Nov 2008 19:08:48 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-1755</guid>
					<description>The best way of linux life!!!</description>
		<content:encoded><![CDATA[<p>The best way of linux life!!!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dbierer</title>
		<link>http://www.linux-mag.com/id/7096/#comment-1754</link>
		<pubDate>Mon, 17 Nov 2008 17:57:25 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-1754</guid>
					<description>I find the CLI most useful when using 'ssh' to manage remote systems and also creating 'cron' jobs.  Set up a script for a customer the other day, triggering at midnight, which uses 'find' to search for files older than 30 days and remove them.  In another case I had to change the filename extensions for a whole slew of files.  A simple 'ls' command, piped to 'cut' with '.' as the delimiter and I had my raw filename.  Piped that output through a loop and all my files had new extensions.  Heady stuff :-)</description>
		<content:encoded><![CDATA[<p>I find the CLI most useful when using &#8217;ssh&#8217; to manage remote systems and also creating &#8216;cron&#8217; jobs.  Set up a script for a customer the other day, triggering at midnight, which uses &#8216;find&#8217; to search for files older than 30 days and remove them.  In another case I had to change the filename extensions for a whole slew of files.  A simple &#8216;ls&#8217; command, piped to &#8216;cut&#8217; with &#8216;.&#8217; as the delimiter and I had my raw filename.  Piped that output through a loop and all my files had new extensions.  Heady stuff :-)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: framness</title>
		<link>http://www.linux-mag.com/id/7096/#comment-1603</link>
		<pubDate>Fri, 17 Oct 2008 14:33:45 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7096/#comment-1603</guid>
					<description>I run Slack at home and when I log in I bring up KDE, but when working on my system (or goofing around) I always have at least one (often multiple) CLI sessions open.

One thing that IMO makes Unix/Linux superior is it is a true data-processing system, you can work applications interactively or using the CLI you can create powerful batch or scheduled processes. If I was doing my web development on a windows system I would have to manually FTP &#38; manage website backups daily. With Linux I have a system already in place and I use a combination of Perl and bash to do that work. I like the idea every application I have I can think of can be run via CLI calls or via GUI bolt-on in my preferred windows manager.

If all you are doing is GUI work than it may not make sense to use Linux to really get the most benefit you have to use the CLI.</description>
		<content:encoded><![CDATA[<p>I run Slack at home and when I log in I bring up KDE, but when working on my system (or goofing around) I always have at least one (often multiple) CLI sessions open.</p>
<p>One thing that IMO makes Unix/Linux superior is it is a true data-processing system, you can work applications interactively or using the CLI you can create powerful batch or scheduled processes. If I was doing my web development on a windows system I would have to manually FTP &amp; manage website backups daily. With Linux I have a system already in place and I use a combination of Perl and bash to do that work. I like the idea every application I have I can think of can be run via CLI calls or via GUI bolt-on in my preferred windows manager.</p>
<p>If all you are doing is GUI work than it may not make sense to use Linux to really get the most benefit you have to use the CLI.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
