<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: ls &#8211;color considered harmful</title>
	<link>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/</link>
	<description>a web-log</description>
	<pubDate>Sat, 31 Jul 2010 16:13:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Matthew W. S. Bell</title>
		<link>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5409</link>
		<author>Matthew W. S. Bell</author>
		<pubDate>Sun, 27 Jan 2008 06:16:05 +0000</pubDate>
		<guid>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5409</guid>
					<description>Nah, you're confusing the symptom with the problem(s):

- network file-systems are rubbish
- auto-mounting is a slightly broken idea
- file/directory API is not ideal for high-latency file-systems</description>
		<content:encoded><![CDATA[<p>Nah, you're confusing the symptom with the problem(s):</p>
<p>- network file-systems are rubbish<br />
- auto-mounting is a slightly broken idea<br />
- file/directory API is not ideal for high-latency file-systems</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: ads</title>
		<link>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5413</link>
		<author>ads</author>
		<pubDate>Sun, 27 Jan 2008 09:25:02 +0000</pubDate>
		<guid>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5413</guid>
					<description>Whilst I agree with your bullet points Matthew, I would say that the default configuration of ls --color exacerbates the situation greatly. The other day, a colleague was puzzled that ls ~user1 worked when ls ~user2 hung. (His system had 'alias ls=ls --color=tty' in its defaults). Turns out, user2 had a symlink in his homedir to a filesystem that was unavailable.

This action at a distance is a clear violation of the principle of least surprise.</description>
		<content:encoded><![CDATA[<p>Whilst I agree with your bullet points Matthew, I would say that the default configuration of ls &#8211;color exacerbates the situation greatly. The other day, a colleague was puzzled that ls ~user1 worked when ls ~user2 hung. (His system had 'alias ls=ls &#8211;color=tty' in its defaults). Turns out, user2 had a symlink in his homedir to a filesystem that was unavailable.</p>
<p>This action at a distance is a clear violation of the principle of least surprise.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: James</title>
		<link>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5414</link>
		<author>James</author>
		<pubDate>Sun, 27 Jan 2008 10:51:41 +0000</pubDate>
		<guid>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5414</guid>
					<description>To quote the dircolors manpage on Debian: "FILES
       /etc/DIR_COLORS
              (Slackware, SuSE and RedHat only; ignored by GNU dircolors(1) and thus Debian.)  System-wide configuration file.

       ~/.dir_colors
              (Slackware, SuSE and RedHat only; ignored by GNU dircolors(1) and thus Debian.)  Per-user configuration file."

Also dircolors --print-directory doesn't work on Debian.</description>
		<content:encoded><![CDATA[<p>To quote the dircolors manpage on Debian: "FILES<br />
       /etc/DIR_COLORS<br />
              (Slackware, SuSE and RedHat only; ignored by GNU dircolors(1) and thus Debian.)  System-wide configuration file.</p>
<p>       ~/.dir_colors<br />
              (Slackware, SuSE and RedHat only; ignored by GNU dircolors(1) and thus Debian.)  Per-user configuration file."</p>
<p>Also dircolors &#8211;print-directory doesn't work on Debian.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: ads</title>
		<link>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5420</link>
		<author>ads</author>
		<pubDate>Sun, 27 Jan 2008 16:32:49 +0000</pubDate>
		<guid>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5420</guid>
					<description>&lt;b&gt;James&lt;/b&gt;: I've updated the article in light of your final point.</description>
		<content:encoded><![CDATA[<p><b>James</b>: I've updated the article in light of your final point.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Marius Gedminas</title>
		<link>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5431</link>
		<author>Marius Gedminas</author>
		<pubDate>Mon, 28 Jan 2008 18:12:24 +0000</pubDate>
		<guid>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5431</guid>
					<description>Do you also consider ls -l harmful?

Symlinks to automatic mountpoints are broken, period.</description>
		<content:encoded><![CDATA[<p>Do you also consider ls -l harmful?</p>
<p>Symlinks to automatic mountpoints are broken, period.</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: ads</title>
		<link>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5433</link>
		<author>ads</author>
		<pubDate>Mon, 28 Jan 2008 21:32:33 +0000</pubDate>
		<guid>http://blog.wompom.org/index.php/2008/01/26/ls-color-considered-harmful/#comment-5433</guid>
					<description>&lt;strong&gt;Marius&lt;/strong&gt;: no, it's not hugely harmful. Likewise, ls --color, with disabling orphan checking is similarly harmless. However, ls -lL is dangerous. Fortunately, people don't alias ls to ls -lL. Interestingly, I've just discovered, ls -L stats all sorts of things yet doesn't change its output on the basis of it!</description>
		<content:encoded><![CDATA[<p><strong>Marius</strong>: no, it&#8217;s not hugely harmful. Likewise, ls &#8211;color, with disabling orphan checking is similarly harmless. However, ls -lL is dangerous. Fortunately, people don't alias ls to ls -lL. Interestingly, I've just discovered, ls -L stats all sorts of things yet doesn't change its output on the basis of it!</p>
]]></content:encoded>
				</item>
</channel>
</rss>
