<?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>cat brain.log &#124; less &#187; linux</title>
	<atom:link href="http://log.largevoid.com/tag/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://log.largevoid.com</link>
	<description>Getting it down on `paper`</description>
	<lastBuildDate>Mon, 06 Feb 2012 06:23:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Linux Mint: Broken</title>
		<link>http://log.largevoid.com/2011/08/linux-mint-broken/</link>
		<comments>http://log.largevoid.com/2011/08/linux-mint-broken/#comments</comments>
		<pubDate>Wed, 17 Aug 2011 01:53:51 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Lessons]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[mint]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[xfce]]></category>

		<guid isPermaLink="false">http://log.largevoid.com/?p=586</guid>
		<description><![CDATA[Here&#8217;s a nice little note to all you aspiring Linux n00bs: Avoid Linux Mint. I tried out linuxmint-11-gnome-cd-nocodecs-32bit and linuxmint-xfce-201104-dvd-32bit today, and was not impressed.  Ok, I was actually impressed once I got it to run, but only before the launcher crashed and asked to be restarted.  And then it was all down hill.  I [...]]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s a nice little note to all you aspiring Linux n00bs: Avoid Linux Mint.</p>
<p>I tried out linuxmint-11-gnome-cd-nocodecs-32bit and linuxmint-xfce-201104-dvd-32bit today, and was not impressed.  Ok, I was actually impressed once I got it to run, but only before the launcher crashed and asked to be restarted.  And then it was all down hill.  I couldn&#8217;t even get the installer to run the first time around.  I tried again with the Xfce DVD version.  This installer ran just fine, but then 800 updates required (ok, no biggie, very common).  I click to apply updates, but then I&#8217;m confronted with a package dependency error, and told to resolve dependencies first.  Next, I try to install just one thing at a time.  First up: the mint-welcome package. Does that install? Click -&gt; Apply -&gt; ok.  Looks like it was fine.  Next up, some other mint package, I don&#8217;t recall.  Anyway, this one caused the updater to crash.  Reboot, try again, crash again.  You know what? I don&#8217;t have all day.</p>
<p>Let&#8217;s try out the internet&#8230; open firefox, head to youtube for the obligatory flash test.  Video starts playing&#8230; it&#8217;s an ad.  Well, about 4 seconds before the ad finishes, the video freezes.  Page refresh: Replay the ad, and that 4 second video freeze problem again.  Ok, that means that flash support is buggy.  Well, remember how I can&#8217;t update anything with the updater software? That means I&#8217;m stuck.  I don&#8217;t feel like wading through individual packages to get this thing working.  I want a Minty out-of-box experience.  What I got was roach infested.</p>
<p>LSS (Long-Story-Short), save yourself the effort, just go xubuntu (for the xfce type).</p>
]]></content:encoded>
			<wfw:commentRss>http://log.largevoid.com/2011/08/linux-mint-broken/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Periodic Tarballs: Find and Awk</title>
		<link>http://log.largevoid.com/2010/06/periodic-tarballs-find-and-awk/</link>
		<comments>http://log.largevoid.com/2010/06/periodic-tarballs-find-and-awk/#comments</comments>
		<pubDate>Wed, 02 Jun 2010 08:43:04 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Scripts, Tricks and Hacks]]></category>
		<category><![CDATA[awk]]></category>
		<category><![CDATA[cut]]></category>
		<category><![CDATA[find]]></category>
		<category><![CDATA[gzip]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[pipe]]></category>
		<category><![CDATA[tar]]></category>

		<guid isPermaLink="false">http://log.largevoid.com/?p=355</guid>
		<description><![CDATA[I have a gang of directories. There&#8217;s a new directory each day! Each directory stores about 20k files. Over time, the performance of the directory hierarchy degrades, and it&#8217;s best for me to tar up old stuff. In linux-land, there&#8217;s always more than one way of doing things&#8230; even if it&#8217;s not the right way. [...]]]></description>
			<content:encoded><![CDATA[<p>I have a gang of directories.  There&#8217;s a new directory each day!  Each directory stores about 20k files.  Over time, the performance of the directory hierarchy degrades, and it&#8217;s best for me to tar up old stuff.</p>
<p>In linux-land, there&#8217;s always more than one way of doing things&#8230; even if it&#8217;s not the right way.  Today, we&#8217;ll explore find piped to awk piped to the shell.</p>

<div class="wp_syntax"><div class="code"><pre class="bash" style="font-family:monospace;"><span style="color: #c20cb9; font-weight: bold;">touch</span> . ; <span style="color: #c20cb9; font-weight: bold;">find</span> . <span style="color: #660033;">-type</span> d <span style="color: #660033;">-maxdepth</span> <span style="color: #000000;">1</span> <span style="color: #660033;">-mtime</span> +<span style="color: #000000;">60</span> <span style="color: #000000; font-weight: bold;">|</span> <span style="color: #c20cb9; font-weight: bold;">sort</span> <span style="color: #000000; font-weight: bold;">|</span>
<span style="color: #c20cb9; font-weight: bold;">awk</span> <span style="color: #660033;">-F</span><span style="color: #ff0000;">&quot;/&quot;</span> <span style="color: #ff0000;">'{print &quot;tar czf &quot; $2 &quot;.tar.gz --remove-files ./&quot; $2 &quot;; rmdir &quot; $2 }'</span> <span style="color: #000000; font-weight: bold;">|</span> <span style="color: #c20cb9; font-weight: bold;">sh</span></pre></div></div>

<p>Basically, make sure the current direction has been recently modified, so it&#8217;s not returned by the find command.  Then, find all sub-directories in the current directory &#8212; don&#8217;t go recursive.  Sort for a predictable sequence of operations.  Extract the file name portion (lots of ways to do this).  Generate a shell command <code>tar czf {{dirname}}.tar.gz --remove-files ./{{dirname}}; rmdir {{dirname}}</code> to build the tarball and remove the empty directory when done.  Finally, we just tell <code>sh</code> to execute it all&#8230; one directory at a time. Bam!</p>
]]></content:encoded>
			<wfw:commentRss>http://log.largevoid.com/2010/06/periodic-tarballs-find-and-awk/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Linux Commands for System Information</title>
		<link>http://log.largevoid.com/2010/04/linux-commands-for-system-informatio/</link>
		<comments>http://log.largevoid.com/2010/04/linux-commands-for-system-informatio/#comments</comments>
		<pubDate>Mon, 26 Apr 2010 19:44:51 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Reference]]></category>
		<category><![CDATA[biosdecode]]></category>
		<category><![CDATA[cli]]></category>
		<category><![CDATA[dmidecode]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://log.largevoid.com/?p=343</guid>
		<description><![CDATA[Need to remotely troubleshoot a machine? Don&#8217;t know what&#8217;s inside? Want to know what&#8217;s enabled in BIOS? Let&#8217;s keep it short and sweet (details from our reference): man biosdecode man dmidecode Ref: Linux System Information Decoded, Hess, Ken. 2010-04-23.]]></description>
			<content:encoded><![CDATA[<p>Need to remotely troubleshoot a machine?  Don&#8217;t know what&#8217;s inside?  Want to know what&#8217;s enabled in BIOS?</p>
<p>Let&#8217;s keep it short and sweet (details from our reference):<br />
<code>man biosdecode</code><br />
<code>man dmidecode</code></p>
<p>Ref: <a href="http://www.linux-mag.com/id/7768">Linux System Information Decoded</a>, Hess, Ken. 2010-04-23.</p>
]]></content:encoded>
			<wfw:commentRss>http://log.largevoid.com/2010/04/linux-commands-for-system-informatio/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>STDERR redirect into STDOUT redirect into file</title>
		<link>http://log.largevoid.com/2009/10/stderr-redirect-into-stdout-redirect-into-file/</link>
		<comments>http://log.largevoid.com/2009/10/stderr-redirect-into-stdout-redirect-into-file/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 02:00:08 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Scripts, Tricks and Hacks]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[redirect]]></category>

		<guid isPermaLink="false">http://log.largevoid.com/?p=12</guid>
		<description><![CDATA[When you want to redirect stderr to a file, you have choices.  Either redirect only stderr to a file, or redirect both stderr and stdout to the same file. The right way: Redirect stderr and stdout to [[file]]: [[command]] &#62; [[file]] 2&#62;&#38;1 Redirect stderr to [[efile]] and stdout to [[file]]: [[command]] 2&#62; [[efile]] &#62; [[file]] [...]]]></description>
			<content:encoded><![CDATA[<p>When you want to redirect stderr to a file, you have choices.  Either redirect only stderr to a file, or redirect both stderr and stdout to the same file.</p>
<p><strong>The right way:</strong></p>
<p>Redirect stderr and stdout to [[file]]:</p>
<p><code>[[command]] &gt; [[file]] 2&gt;&amp;1</code></p>
<p>Redirect stderr to [[efile]] and stdout to [[file]]:</p>
<p><code>[[command]] 2&gt; [[efile]] &gt; [[file]]</code></p>
<p><strong>The wrong way:</strong></p>
<p>Doesn’t do anything useful:</p>
<p><code>[[command]] 2&gt;&amp;1 &gt; [[file]]</code></p>
]]></content:encoded>
			<wfw:commentRss>http://log.largevoid.com/2009/10/stderr-redirect-into-stdout-redirect-into-file/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Summing a list of numbers</title>
		<link>http://log.largevoid.com/2009/10/summing-a-list-of-numbers/</link>
		<comments>http://log.largevoid.com/2009/10/summing-a-list-of-numbers/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 02:00:40 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Scripts, Tricks and Hacks]]></category>
		<category><![CDATA[awk]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://log.largevoid.com/?p=10</guid>
		<description><![CDATA[awk '{sum += $0} END {print sum}' Example: % find . -type f -exec wc {} \; &#124; tr -s " " &#124; cut -f2 -d" " &#124; awk '{sum += $0} END {print sum}' What’s going on? I want to recursively count the number of lines present in all files contained by the current [...]]]></description>
			<content:encoded><![CDATA[<p><code>awk '{sum += $0} END {print sum}'</code></p>
<p>Example:<code><br />
% find . -type f -exec wc {} \; | tr -s " " | cut -f2 -d" " | awk '{sum += $0} END {print sum}'</code></p>
<p>What’s going on? I want to recursively count the number of lines present in all files contained by the current directory. Why? Sub-directories =&gt; namespaces, and I want to know how many lines of code exist in the entire project, namespaces and all.</p>
]]></content:encoded>
			<wfw:commentRss>http://log.largevoid.com/2009/10/summing-a-list-of-numbers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  log.largevoid.com/tag/linux/feed/ ) in 0.24487 seconds, on Feb 8th, 2012 at 4:15 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 8th, 2012 at 5:15 am UTC -->
