<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>A bumbling foray into tumblr…</description><title>SonicChicken</title><generator>Tumblr (3.0; @sonicchicken)</generator><link>http://sonicchicken.tumblr.com/</link><item><title>Apple Xcode, compilers and make and perl, oh my!</title><description>&lt;p&gt;Yet another instance of Apple telling me what they are doing, and me failing to pay attention. sigh&amp;#8230;&lt;/p&gt;

&lt;p&gt;In this case, I recently &amp;#8220;upgraded&amp;#8221; my system at work, from the 3rd newest to the 2nd newest version of OS X. But after I did so, I lost all my developer tools (compiler, make, perl&amp;#8217;s CPAN, etc.)&lt;/p&gt;

&lt;p&gt;It turns out that all I needed to do was reinstall Xcode, but that&amp;#8217;s now done via the App Store instead of the interwebz. Also, after installing Xcode, you need to run it so that you can have Xcode install the command line tools.&lt;/p&gt;

&lt;ol&gt;&lt;li&gt;Go to /Applications/App Store and download/install Xcode&lt;/li&gt;
&lt;li&gt;Launch Xcode (Applications/Xcode)&lt;/li&gt;
&lt;li&gt;Open Xcode preferences, Downloads, Components.&lt;/li&gt;
&lt;li&gt;On the Command Line Tools line, click the &amp;#8220;Install&amp;#8221; button.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Make sure the command line tools are in your PATH&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;&lt;p&gt;Steps #1 and #4 take a bit of time, but once they were done I had a config.h and CPAN was working again.&lt;/p&gt;

&lt;p&gt;Step #5 might take a little explanation. The command line tools that I was missing were make(1) and cc(1). I thought cc might be a little easier to find, so here&amp;#8217;s what I did:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;$ which cc
(nothing returned)
$ locate cc | grep /cc$
/Developer/usr/bin/cc
$ export PATH="$PATH:/Developer/usr/bin"
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The first command verified that my PATH did not include the cc command. The second one (locate) showed me which directory it was in. And the third one added that directory to my PATH for the current session. Once you&amp;#8217;ve verified that your tools are all working, copy that &amp;#8220;export PATH&amp;#8230;&amp;#8221; command to your .bashrc file.&lt;/p&gt;

&lt;p&gt;I might have avoided some of this trouble if I had kept up with &lt;a href="https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/WhatsNewXcode"&gt;What&amp;#8217;s New in Xcode&lt;/a&gt;&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/47808845654</link><guid>http://sonicchicken.tumblr.com/post/47808845654</guid><pubDate>Fri, 12 Apr 2013 14:45:59 -0700</pubDate><category>mac_osx</category><category>perl</category><category>xcode</category></item><item><title>Cueing up some Jim Croce…

The meanest hunk o' woman
That...</title><description>&lt;img src="http://24.media.tumblr.com/6f613371b191d19948d0c945c4cf7f06/tumblr_mjgp3unKKp1qarb8so1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Cueing up some Jim Croce…&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;The meanest hunk o' woman
That anybody ever seen
Down in the arena
&lt;/code&gt;&lt;/pre&gt;</description><link>http://sonicchicken.tumblr.com/post/46432476488</link><guid>http://sonicchicken.tumblr.com/post/46432476488</guid><pubDate>Wed, 27 Mar 2013 10:47:27 -0700</pubDate></item><item><title>Sharing mail.app Act-On rules</title><description>&lt;p&gt;One of the tools I make the most use of is email. I like Apple&amp;#8217;s mail.app (which comes with OS X), but it&amp;#8217;s vastly improved with a couple of extras from &lt;a href="http://indev.ca"&gt;indev.ca&lt;/a&gt;: &lt;a href="http://indev.ca/MailActOn.html"&gt;Mail Act-On&lt;/a&gt; and &lt;a href="http://indev.ca/MailTags.html"&gt;MailTags&lt;/a&gt;. I use this combination on all my Macs, and the only major hurdle is keeping the Act-On rules the same on all my systems. A quick browse of the indev.ca knowledge base brought me to &lt;a href="http://support.indev.ca/kb/mao-advanced-techniques/manually-moving-mail-act-on-rules"&gt;Manually moving Mail Act-On rules&lt;/a&gt;. This turns out to be fairly easy to do, if you designate one of your systems as the &amp;#8220;master&amp;#8221;. Just copy the following files from that system to your &amp;#8220;slave&amp;#8221; systems:&lt;/p&gt;

&lt;ul&gt;&lt;li&gt;~/Library/Mail/Indev/ActOnRules.plist&lt;/li&gt;
&lt;li&gt;~/Library/Mail/Indev/OutboxRules.plist&lt;/li&gt;
&lt;li&gt;~/Library/Mail/Indev/MailTagsInboxRules.plist&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;Remember that the Finder won&amp;#8217;t show your ~/Library folder unless you explicitly &amp;#8220;Go To Folder&amp;#8230;&amp;#8221; (shift+apple+G on keyboard).&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/46432165122</link><guid>http://sonicchicken.tumblr.com/post/46432165122</guid><pubDate>Wed, 27 Mar 2013 10:42:34 -0700</pubDate><category>gtd</category><category>mail.app</category><category>indev</category><category>MailTags</category><category>MailActOn</category><category>mac_osx</category><category>productivity</category><category>sync</category></item><item><title>Handy one-line scripts for AWK </title><description>&lt;a href="http://www.pement.org/awk/awk1line.txt"&gt;Handy one-line scripts for AWK &lt;/a&gt;</description><link>http://sonicchicken.tumblr.com/post/40031202624</link><guid>http://sonicchicken.tumblr.com/post/40031202624</guid><pubDate>Tue, 08 Jan 2013 12:21:20 -0800</pubDate><category>awk</category><category>sysadmin</category></item><item><title>Advanced bash scripting</title><description>&lt;p&gt;The &lt;a href="http://tldp.org/LDP/abs/html/part5.html"&gt;section on advanced bash scripting tops&lt;/a&gt; is always worth going back for a re-read! There are a lot of nuggets of platinum among all the gold. :D&lt;/p&gt;

&lt;p&gt;Of course, this assumes familiarity with the previous sections of the &lt;a href="http://tldp.org/LDP/abs/html/index.html"&gt;bash scripting guide&lt;/a&gt;.&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/38155834664</link><guid>http://sonicchicken.tumblr.com/post/38155834664</guid><pubDate>Mon, 17 Dec 2012 09:41:06 -0800</pubDate><category>bash</category><category>howto</category></item><item><title>Declare your Pod encoding</title><description>&lt;p&gt;Earlier this year, a minor change to Pod::Simple caused brian d foy&amp;#8217;s Mac::Errors module to fail during testing. The underlying problem is an ASCII/UTF-8 issue. One might expect the utf8 pragma to fix this, but remember that POD ignores all the code outside of POD elements.&lt;/p&gt;

&lt;p&gt;Aristotle Pagaltzis makes an excellent point in the &lt;a href="http://www.effectiveperlprogramming.com/blog/1551#comments"&gt;comments on bdf&amp;#8217;s post&lt;/a&gt;, mentioning that it&amp;#8217;s a Bad Idea to mix your POD and program text encodings.&lt;/p&gt;

&lt;p&gt;Since I&amp;#8217;m using a Mac, UTF-8 characters are pretty likely to end up in my code and/or POD. It seems prudent to follow the suggestions from bdf&amp;#8217;s article:&lt;/p&gt;

&lt;p&gt;In the source code, include the utf8 pragma:
&amp;gt; use utf8;&lt;/p&gt;

&lt;p&gt;Declare your Pod encoding as utf8:
&amp;gt; =encoding utf8&lt;/p&gt;

&lt;hr&gt;&lt;p&gt;(update 2013-03-26) The encoding command has been a part of perlpod since at least version 5.8.8, based on that version&amp;#8217;s documentation:&lt;/p&gt;

&lt;p&gt;&lt;a href="http://perldoc.perl.org/5.8.8/perlpod.html"&gt;http://perldoc.perl.org/5.8.8/perlpod.html&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;According to that documentation, the encoding should be the first pod directive. It can appear anywhere (not necessarily within a documentation block), but it must only appear once.&lt;/p&gt;

&lt;p&gt;Since that&amp;#8217;s a perlpod command, it needs its own paragraph (i.e. two consecutive newlines). And since the &amp;#8220;use utf8&amp;#8221; and &amp;#8220;=encoding utf8&amp;#8221; work together, it&amp;#8217;s probably a good idea to include this in the header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;use utf8;

=encoding utf8
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The blank lines before/after encoding must be completely empty. An easy way to check that (and many other perlpod requirements) is podchecker(1).&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/37673071629</link><guid>http://sonicchicken.tumblr.com/post/37673071629</guid><pubDate>Mon, 10 Dec 2012 16:07:00 -0800</pubDate><category>perl</category><category>POD</category><category>ASCII</category><category>UTF-8</category><category>encoding</category><category>mac</category></item><item><title>Unix `find' without subdirectory traversal</title><description>&lt;p&gt;I love the `find(1)&amp;#8217; command! But sometimes I don&amp;#8217;t want the default fully-recursive behavior. For example, today I wanted to do something with all of my &amp;#8220;dot files&amp;#8221; &lt;em&gt;without&lt;/em&gt; affecting &amp;#8220;dot directories&amp;#8221; (such as .ssh) or their contents:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;find $HOME/.* -prune ! -type d -exec ls {} \;
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The `ls&amp;#8217; command is just for demonstration purposes. Substitute with a useful command of your choice.&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/35737868643</link><guid>http://sonicchicken.tumblr.com/post/35737868643</guid><pubDate>Wed, 14 Nov 2012 16:19:00 -0800</pubDate><category>find</category><category>unix</category><category>sysadmin</category></item><item><title>Math geeks</title><description>&lt;p&gt;Q: Why do math geeks get Halloween and Christmas confused?&lt;/p&gt;

&lt;p&gt;A: Because 25&lt;sub&gt;dec&lt;/sub&gt; = 31&lt;sub&gt;oct&lt;/sub&gt;.&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/35295422267</link><guid>http://sonicchicken.tumblr.com/post/35295422267</guid><pubDate>Thu, 08 Nov 2012 14:30:50 -0800</pubDate><category>humor</category><category>geek</category></item><item><title>Homebrew Packaging Guide</title><description>&lt;a href="http://afp548.com/mediawiki/index.php/Homebrew_Packaging_Guide"&gt;Homebrew Packaging Guide&lt;/a&gt;: &lt;p&gt;I originally found this on Con Poco Coco’s tumblog, but the link was broken. The URL for afp548.com seems to be the same material. Below is the original post from Con Poco Coco:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This guide is for setting up homebrew to build individual packages that can be deployed with munki or ARD.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;(404 URL: &lt;a href="http://osxdeployment.com/wiki/Homebrew_Packaging_Guide"&gt;http://osxdeployment.com/wiki/Homebrew_Packaging_Guide&lt;/a&gt;)&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/35140926908</link><guid>http://sonicchicken.tumblr.com/post/35140926908</guid><pubDate>Tue, 06 Nov 2012 11:22:58 -0800</pubDate><category>homebrew</category><category>mac_osx</category><category>sysadmin</category></item><item><title>Revisiting Those Pesky Firmware Passwords</title><description>&lt;p&gt;&lt;a class="tumblr_blog" href="http://blog.conpocococo.org/post/8171494738/revisiting-those-pesky-firmware-passwords"&gt;conpocococo&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Charles’s &lt;a href="http://Krypted.com/" target="_blank"&gt;Krypted.com &lt;/a&gt;blog has a useful post about &lt;a href="http://krypted.com/mac-os-x/those-pesky-firmware-passwords/" target="_blank"&gt;setting Apple hardware firmware passwords&lt;/a&gt;. The &lt;a href="http://code.google.com/p/efipw" target="_blank"&gt;efipw.py&lt;/a&gt; script works great on the MacBook Pro (13-inch, Mid 2010) machines I tested it on. However version 0.2b does not work on newer models (see below for list) as &lt;a href="http://paulmakowski.wordpress.com/" target="_blank"&gt;Paul Makowski&lt;/a&gt; notes on the project page. Interestingly enough the python script is still able to decrypt the password on the newer models. Thankfully one must run it as root (or via sudo) to do that otherwise this whole firmware lock exercise would be moot.&lt;/p&gt;
&lt;p&gt;The &lt;a href="http://support.apple.com/kb/HT1352" target="_blank"&gt;Apple Way(tm)&lt;/a&gt; of setting EFI firmware passwords is to use an application on the install DVD called Firmware Password Utility. Since I have gone to all the trouble of setting up &lt;a href="http://www.deploystudio.com/" target="_blank"&gt;DeployStudio&lt;/a&gt; and &lt;a href="http://code.google.com/p/munki/" target="_blank"&gt;Munki &lt;/a&gt;to automate the management of the hundreds of Macs under my care, it is poor option to boot from the DVD and manually set the firmware password. There are many reasons for this, but the number one is manual entry leads to errors. (I should note, not having verification steps also leads to errors, but that is for another blog post.)&lt;/p&gt;
&lt;p&gt;What is an automating loving sysadmin to do?&lt;/p&gt;
&lt;p&gt;&lt;a href="http://blog.conpocococo.org/post/8171494738/revisiting-those-pesky-firmware-passwords"&gt;Read More&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;</description><link>http://sonicchicken.tumblr.com/post/35140460816</link><guid>http://sonicchicken.tumblr.com/post/35140460816</guid><pubDate>Tue, 06 Nov 2012 11:14:48 -0800</pubDate><category>sysadmin</category><category>mac_osx</category><category>firmware</category><category>efi</category><category>mac</category></item><item><title>Backing up and restoring SSL certificates in 10.5 and 10.6</title><description>&lt;a href="http://www.afp548.com/article.php?story=20100425082436137"&gt;Backing up and restoring SSL certificates in 10.5 and 10.6&lt;/a&gt;</description><link>http://sonicchicken.tumblr.com/post/35140358385</link><guid>http://sonicchicken.tumblr.com/post/35140358385</guid><pubDate>Tue, 06 Nov 2012 11:12:59 -0800</pubDate><category>SSL</category><category>mac_osx</category><category>certificates</category><category>sysadmin</category></item><item><title>Con Poco Coco: Managing sshd on Mac OS X Via the Command Line</title><description>&lt;a href="http://blog.conpocococo.org/post/25507368528/managing-sshd-on-mac-os-x-via-the-command-line"&gt;Con Poco Coco: Managing sshd on Mac OS X Via the Command Line&lt;/a&gt;: &lt;p&gt;&lt;a href="http://blog.conpocococo.org/post/25507368528/managing-sshd-on-mac-os-x-via-the-command-line" class="tumblr_blog"&gt;conpocococo&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;This information is all &lt;a href="https://duckduckgo.com/?q=OS+X+Remote+Login+Allow+Access+launchctl" title="DDG search for sshd cli control" target="_blank"&gt;out there&lt;/a&gt;, but there is enough cruft mixed in, that I’m making my own post.&lt;/p&gt; &lt;h2&gt;GUI Way&lt;/h2&gt; &lt;p&gt;With mouse and keyboard, you can enable/disable sshd on Mac OS X by going to System Preferences -&gt; Sharing. Check or uncheck Remote Login. You also have the option of limiting who can…&lt;/p&gt;&lt;/blockquote&gt;</description><link>http://sonicchicken.tumblr.com/post/35140187505</link><guid>http://sonicchicken.tumblr.com/post/35140187505</guid><pubDate>Tue, 06 Nov 2012 11:09:00 -0800</pubDate><category>ssh</category><category>sshd</category><category>mac_osx</category></item><item><title>Perl EDI module</title><description>&lt;p&gt;The only EDI module I&amp;#8217;ve found for Perl is &lt;a href="http://search.cpan.org/~kraehe/XML-Edifact-0.47/XML/Edifact.pm"&gt;http://search.cpan.org/~kraehe/XML-Edifact-0.47/XML/Edifact.pm&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This module converts an EDI document to/from XML. Use other XML modules to do actual processing.&lt;/p&gt;

&lt;p&gt;Seems to be unmaintained, or perhaps it&amp;#8217;s achieved perfection? ;)&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/34304081831</link><guid>http://sonicchicken.tumblr.com/post/34304081831</guid><pubDate>Thu, 25 Oct 2012 10:37:00 -0700</pubDate><category>EDI</category><category>XML::Edifact</category><category>cpan</category><category>perl</category><category>xml</category></item><item><title>Links for the twig module (Perl XML)</title><description>&lt;p&gt;XML::Twig is a memory-efficient tree-based XML parser/processor module.&lt;/p&gt;

&lt;p&gt;The Twig home page: &lt;a href="http://www.xmltwig.org/xmltwig/"&gt;http://www.xmltwig.org/xmltwig/&lt;/a&gt; &amp;lt;&amp;#8212; START HERE!&lt;/p&gt;

&lt;p&gt;Tutorials (old): &lt;a href="http://www.xmltwig.org/tutorial/"&gt;http://www.xmltwig.org/tutorial/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;An example: &lt;a href="http://stackoverflow.com/questions/10239920/using-perl-xmlsax-to-modify-xml-documents"&gt;http://stackoverflow.com/questions/10239920/using-perl-xmlsax-to-modify-xml-documents&lt;/a&gt;
(I heart stackoverflow!)&lt;/p&gt;

&lt;p&gt;Twig 3.41 (latest as of today, possibly unstable?) &lt;a href="http://search.cpan.org/~mirod/XML-Twig-3.41/Twig.pm"&gt;http://search.cpan.org/~mirod/XML-Twig-3.41/Twig.pm&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If XML::Twig can&amp;#8217;t do what you need, check &lt;a href="http://search.cpan.org/~shlomif/XML-LibXML-2.0008/LibXML.pod"&gt;http://search.cpan.org/~shlomif/XML-LibXML-2.0008/LibXML.pod&lt;/a&gt; &amp;#8212; it&amp;#8217;s very &amp;#8220;featureful&amp;#8221;, may take a while to master.&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/34303665397</link><guid>http://sonicchicken.tumblr.com/post/34303665397</guid><pubDate>Thu, 25 Oct 2012 10:28:00 -0700</pubDate><category>perl</category><category>cpan</category><category>xml</category><category>XML::Twig</category><category>LibXML</category></item><item><title>Arduino programming with MacOSX</title><description>&lt;a href="http://arduino.cc/en/Guide/MacOSX"&gt;Arduino programming with MacOSX&lt;/a&gt;: &lt;p&gt;This guide describes setting up the Arduino programming environment on Mac OS X.&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/33645442351</link><guid>http://sonicchicken.tumblr.com/post/33645442351</guid><pubDate>Mon, 15 Oct 2012 09:27:43 -0700</pubDate><category>arduino</category><category>mac_osx</category><category>howto</category></item><item><title>folhadespaulo:

Paraquedista rompe a barreira do som em queda...</title><description>&lt;img src="http://24.media.tumblr.com/tumblr_mbxuwosUoC1qd4tigo1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;a href="http://folhadespaulo.tumblr.com/post/33640455861/paraquedista-rompe-a-barreira-do-som-em-queda" class="tumblr_blog"&gt;folhadespaulo&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;&lt;p class="MsoNormal"&gt;Paraquedista rompe a barreira do som em queda livre ao saltar da estratosfera.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Safe return after jumping from ~128,000 ft!&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/33645227536</link><guid>http://sonicchicken.tumblr.com/post/33645227536</guid><pubDate>Mon, 15 Oct 2012 09:23:09 -0700</pubDate></item><item><title>Output files by date</title><description>&lt;p&gt;This evening I needed to cat(1) a bunch of files, in date order. All of the files had &amp;#8220;LABEL&amp;#8221; in their name, but the names&amp;#8217; lexical sort didn&amp;#8217;t put them in date order. This is pretty simple in bash, using the &amp;#8220;-t -r&amp;#8221; switches on ls and using a for-loop:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;for F in `ls -t -r *LABEL*`; do
    echo "---- file $F ----"
    cat $F
done
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Perhaps a bit trivial, but some may find it useful. Enjoy!&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/25971659264</link><guid>http://sonicchicken.tumblr.com/post/25971659264</guid><pubDate>Tue, 26 Jun 2012 19:18:00 -0700</pubDate><category>bash</category><category>ls</category><category>unix</category><category>sysadmin</category></item><item><title>Log space usage</title><description>&lt;p&gt;Last month I posted a tiny awk script to &lt;a href="http://sonicchicken.tumblr.com/post/22346832734/summing-a-column-in-unix"&gt;calculate the sum of a column of numbers&lt;/a&gt;. The context there was a glob of directory names. But today I had a slightly different problem &amp;#8212; I needed to get total space used by all of the logfile directories within a tree. Fortunately, all the directories are named &amp;#8220;logs&amp;#8221;. Unfortunately, they aren&amp;#8217;t always at the same depth within the tree so I can&amp;#8217;t use a wildcarded path, e.g. &lt;em&gt;*/logs&lt;/em&gt;. But it&amp;#8217;s easy enough to manage with &lt;a href="http://www.gnu.org/software/findutils/manual/html_node/find_html/Introduction.html#Introduction" title="GNU findutils documentation"&gt;find(1)&lt;/a&gt; and the awk scriptlet that I posted last month:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;find /some/directory/path/ -type d -name logs -prune -exec du -s -k {} \; | awk '{total+=$1} END {print total}'
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This looks within the &lt;em&gt;/some/directory/path/&lt;/em&gt; tree for directories (-type d) with filename &lt;em&gt;logs&lt;/em&gt; (-name logs). Since I am passing these files to &lt;a href="http://www.unix.com/man-page/FreeBSD/1/du/" title="FreeBSD du(1) man page"&gt;du(1)&lt;/a&gt;, I don&amp;#8217;t want the find utility to look &lt;strong&gt;within&lt;/strong&gt; the &lt;em&gt;logs&lt;/em&gt; directories (-prune). I pass the found directories to du (via -exec du -s -k {} \;), and at this point it&amp;#8217;s effectively the same thing I did last month.&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/25111295351</link><guid>http://sonicchicken.tumblr.com/post/25111295351</guid><pubDate>Thu, 14 Jun 2012 13:48:00 -0700</pubDate><category>disk space</category><category>du</category><category>find</category><category>unix</category><category>sysadmin</category></item><item><title>Using Safari as an RSS reader</title><description>&lt;a href="http://www.askdavetaylor.com/how_do_i_subscribe_to_rss_feeds_with_safari.html"&gt;Using Safari as an RSS reader&lt;/a&gt;: &lt;p&gt;Dave Taylor has a very concise article on using Apple’s Safari browser as an RSS reader.&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/23759507057</link><guid>http://sonicchicken.tumblr.com/post/23759507057</guid><pubDate>Fri, 25 May 2012 16:11:57 -0700</pubDate><category>mac_osx</category><category>safari</category><category>rss_reader</category><category>apple</category><category>dave_taylor</category></item><item><title>Known hosts' ASCII art</title><description>&lt;p&gt;Want to see the ASCII art of all the systems in your ssh known_hosts file?&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;$ ssh-keygen -lv -f ~/.ssh/known_hosts
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;I know this works on recent versions of FreeBSD and Mac OS X. It probably also works on other BSD&amp;#8217;s and possibly the Linux distros.&lt;/p&gt;

&lt;p&gt;(Warning: Seeing a whole bunch of cruft in your known_hosts(5) file may cause you to spend considerable time cleaning it up! ;)&lt;/p&gt;</description><link>http://sonicchicken.tumblr.com/post/23632574266</link><guid>http://sonicchicken.tumblr.com/post/23632574266</guid><pubDate>Wed, 23 May 2012 15:30:54 -0700</pubDate><category>ssh</category><category>sysadmin</category><category>ssh-keygen</category><category>freebsd</category><category>mac_osx</category></item></channel></rss>
