<?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>Backdrift</title>
	<atom:link href="http://backdrift.org/feed" rel="self" type="application/rss+xml" />
	<link>http://backdrift.org</link>
	<description></description>
	<lastBuildDate>Wed, 10 Mar 2010 13:44:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Fixing Mac OSX File Permissions and ACLs From the Command Line</title>
		<link>http://backdrift.org/fixing-mac-osx-file-permissions-and-acls-from-the-command-line</link>
		<comments>http://backdrift.org/fixing-mac-osx-file-permissions-and-acls-from-the-command-line#comments</comments>
		<pubDate>Sat, 06 Feb 2010 01:35:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[OSX]]></category>
		<category><![CDATA[permissions]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=346</guid>
		<description><![CDATA[Recently the hard drive in my mac mini running Mac OSX Leopard (10.5) failed.  Luckily I had time machine backing it up to an external USB disk.  Now, since I had to replace the drive and rebuild my system anyway I figured, why not upgrade to Snow Leopard?  Planning to just pull [...]]]></description>
		<wfw:commentRss>http://backdrift.org/fixing-mac-osx-file-permissions-and-acls-from-the-command-line/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixing &#8220;No such file or directory&#8221; locale errors</title>
		<link>http://backdrift.org/fixing-no-such-file-or-directory-locale-errors</link>
		<comments>http://backdrift.org/fixing-no-such-file-or-directory-locale-errors#comments</comments>
		<pubDate>Mon, 01 Feb 2010 19:15:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[locale]]></category>
		<category><![CDATA[locales]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=335</guid>
		<description><![CDATA[While working on a new ubuntu karmic system I ran across the following locale error when attempting to perform a dist-upgrade.  I was able to reproduce it by running &#8216;dpkg-reconfigure locales&#8217; thinking that this might fix the error, sadly it did not.
Here&#8217;s the error I was seeing:

root@harrowdown:~# dpkg-reconfigure locales
perl: warning: Setting locale failed.
perl: warning: [...]]]></description>
		<wfw:commentRss>http://backdrift.org/fixing-no-such-file-or-directory-locale-errors/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unison File Synchronizer Monitoring and Alerting with Simple Event Correlator (SEC)</title>
		<link>http://backdrift.org/unison-monitoring-and-alerting-with-sec</link>
		<comments>http://backdrift.org/unison-monitoring-and-alerting-with-sec#comments</comments>
		<pubDate>Thu, 28 Jan 2010 22:15:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[alerting]]></category>
		<category><![CDATA[alerts]]></category>
		<category><![CDATA[HA]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[monitor]]></category>
		<category><![CDATA[monitoring]]></category>
		<category><![CDATA[replication]]></category>
		<category><![CDATA[rsync]]></category>
		<category><![CDATA[unison]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=293</guid>
		<description><![CDATA[Unison File Synchronizer is a tremendous utility.  It keeps the contents of two directories in sync with one another.  It&#8217;s fast, secure, lightweight and good at sorting out collisions but unfortunately it lacks the ability to generate alerts when errors occur.  Instead it just silently makes note of the error in a [...]]]></description>
		<wfw:commentRss>http://backdrift.org/unison-monitoring-and-alerting-with-sec/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Printing the last occurrence of a string and everything below it with grep</title>
		<link>http://backdrift.org/printing-the-last-occurrance-of-a-string-and-everything-below-it-with-grep</link>
		<comments>http://backdrift.org/printing-the-last-occurrance-of-a-string-and-everything-below-it-with-grep#comments</comments>
		<pubDate>Thu, 28 Jan 2010 22:02:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[grep]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=303</guid>
		<description><![CDATA[So far the simplest way find the last occurrence of a string and print everything below it is with a combination of grep and tac (it&#8217;s cat backwards, get it?!).
Say you want to find the last instance of foo and everything that came after it in a file:

 tac /var/log/logfile &#124; grep 'foo' -m 1 [...]]]></description>
		<wfw:commentRss>http://backdrift.org/printing-the-last-occurrance-of-a-string-and-everything-below-it-with-grep/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Xen block iSCSI script with multipath support</title>
		<link>http://backdrift.org/xen-block-iscsi-script-with-multipath-support</link>
		<comments>http://backdrift.org/xen-block-iscsi-script-with-multipath-support#comments</comments>
		<pubDate>Tue, 27 Oct 2009 20:34:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[iSCSI]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[Multipath]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[Xen]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=232</guid>
		<description><![CDATA[When connecting a server to a storage area network (SAN) its important to make certain that you&#8217;re hosts are prepared for the occasional blip in SAN connectivity.  Device mapper multipath to the rescue!  Multipath is an abstraction layer between you and the raw block devices which allows for multiple I/O paths or networks [...]]]></description>
		<wfw:commentRss>http://backdrift.org/xen-block-iscsi-script-with-multipath-support/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Logging bash history to syslog using traps</title>
		<link>http://backdrift.org/logging-bash-history-to-syslog-using-traps</link>
		<comments>http://backdrift.org/logging-bash-history-to-syslog-using-traps#comments</comments>
		<pubDate>Tue, 27 Oct 2009 19:08:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[syslog]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=234</guid>
		<description><![CDATA[This is a handy way to log user&#8217;s bash histories to syslog without making any modifications to the bash source code itself.  Simply drop the following snippet into either the per-user or system-wide bash profile (~/.bash_profile and /etc/profile, respectively)

function log2syslog
&#123;
   declare COMMAND
   COMMAND=$&#40;fc -ln -0&#41;
   logger -p local1.notice [...]]]></description>
		<wfw:commentRss>http://backdrift.org/logging-bash-history-to-syslog-using-traps/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Virtual Private Servers at Backdrift</title>
		<link>http://backdrift.org/vps</link>
		<comments>http://backdrift.org/vps#comments</comments>
		<pubDate>Mon, 19 Oct 2009 01:36:35 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Hosting]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[VPS]]></category>
		<category><![CDATA[Xen]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=199</guid>
		<description><![CDATA[Currently backdrift.org is running on a Xen VM.  In order to make this more affordable and better utilize the co-located hardware, we&#8217;re offering dedicated VMs for lease on the primary backdrift.org server.
$20 per month gets you:

2x AMD Opteron VCPUs @ 2.6GHz
1G RAM
100GB Disk (on underlying RAID-1)
Un-metered bandwidth on bonded T1s (3mbps burstable)

Its a great [...]]]></description>
		<wfw:commentRss>http://backdrift.org/vps/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>iLO Cheat Sheet</title>
		<link>http://backdrift.org/ilo-cheat-sheet</link>
		<comments>http://backdrift.org/ilo-cheat-sheet#comments</comments>
		<pubDate>Mon, 19 Oct 2009 01:03:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[iLO]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=189</guid>
		<description><![CDATA[This is a list of handy key combinations I use when working with the HP iLO on some DL145 servers I manage.
Login Banner

Lights-Out 100 Management
Copyright 2000-2004 QLogic Corporation
Copyright 2004 Hewlett-Packard Development Company, L.P.
Type 'HELP' for options.  Type 'QUIT' to return to console.

Help menu

Lights-Out&#62; help
CLI Commands:
   C[hangePassword] &#60;enter&#62;
   P[ower] &#60;ON, OFF&#62; [...]]]></description>
		<wfw:commentRss>http://backdrift.org/ilo-cheat-sheet/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Xen PvGrub Howto</title>
		<link>http://backdrift.org/xen-pvgrub-howto</link>
		<comments>http://backdrift.org/xen-pvgrub-howto#comments</comments>
		<pubDate>Fri, 16 Oct 2009 15:49:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[Grub]]></category>
		<category><![CDATA[kernel]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[PVGrub]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[RHEL]]></category>
		<category><![CDATA[Xen]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=147</guid>
		<description><![CDATA[So if you&#8217;re like me you are probably somewhat lazy.  I imagine most sysadmins are.  Which must be why we put so much effort into scripting and automating repeated tasks.  If you&#8217;ve managed a Xen VM before you are likely to notice that all your kernel images live outside the VM itself. [...]]]></description>
		<wfw:commentRss>http://backdrift.org/xen-pvgrub-howto/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixing pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 umount error</title>
		<link>http://backdrift.org/fixing-pivotroot-pivot_rootsysrootsysrootinitrd-failed-2-umount-error</link>
		<comments>http://backdrift.org/fixing-pivotroot-pivot_rootsysrootsysrootinitrd-failed-2-umount-error#comments</comments>
		<pubDate>Tue, 12 May 2009 18:42:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[initrd]]></category>
		<category><![CDATA[kernel]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[rhel3]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=133</guid>
		<description><![CDATA[So last night a RHEL3 machine at went down for patching and sadly it didn&#8217;t come back.  Here&#8217;s what was sitting on the console when I got to the console.  Nice&#8230; a kernel panic :/

pivotroot: pivot_root&#40;/sysroot,/sysroot/initrd&#41; failed: 2 umount
/initrd/proc failed: 2 Freeing ununsed kernel memory: 228k freed Kernel
panic: No init found. Try passing [...]]]></description>
		<wfw:commentRss>http://backdrift.org/fixing-pivotroot-pivot_rootsysrootsysrootinitrd-failed-2-umount-error/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
