<?xml version="1.0"?>
<rss version="2.0"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/" >
<channel>
<title>blog</title>
<link>http://www.dmo.ca//blog/</link>
<description>dmo.ca</description>
<item>
	
	<title>Migrating issues from Google Code to Github</title>
	
	<guid>http://www.dmo.ca//blog/migrating-issues-from-googlecode-to-github/</guid>
	<link>http://www.dmo.ca//blog/migrating-issues-from-googlecode-to-github/</link>
	
	
	<category>github</category>
	
	<category>googlecode</category>
	
	<category>issues</category>
	
	<category>migration</category>
	
	<category>perl</category>
	
	
	<pubDate>Sat, 22 May 2010 07:57:47 -0400</pubDate>
	<dcterms:modified>2010-05-22T12:00:32Z</dcterms:modified>
	
	<description><![CDATA[<p>I'd much rather use Git over Subversion, but I still have one project
(<a href="http://code.google.com/p/leaguerunner">leaguerunner</a>) using Subversion on
Google Code.  Migrating <a href="http://github.com/dave0/leaguerunner">the code itself</a>
to git is fairly simple, but being unable to migrate the issues still needs
some tool development.</p>

<p><a href="http://www.dmo.ca//blog/./migrating-issues-from-googlecode-to-github/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>WIND mobile towers in Ottawa</title>
	
	<guid>http://www.dmo.ca//blog/wind-mobile-towers-in-ottawa/</guid>
	<link>http://www.dmo.ca//blog/wind-mobile-towers-in-ottawa/</link>
	
	
	<category>kml</category>
	
	<category>mobile</category>
	
	<category>ottawa</category>
	
	<category>perl</category>
	
	<category>wind</category>
	
	<category>wireless</category>
	
	
	<pubDate>Thu, 11 Mar 2010 00:34:23 -0500</pubDate>
	<dcterms:modified>2010-03-11T05:38:14Z</dcterms:modified>
	
	<description><![CDATA[<p>You may have heard that <a href="http://www.windmobile.ca/">WIND Mobile</a> is going to be offering service in Ottawa
shortly.  I got curious as to what their coverage might be and started looking
for coverage maps.   I didn't find any, but I ended up <a href="http://maps.google.com/maps/ms?ie=UTF8&amp;hl=en&amp;msa=0&amp;msid=115355175763511251619.00048175356638ab92d84&amp;z=11">graphing their wireless
backbone</a> instead.</p>

<p><a href="http://www.dmo.ca//blog/./wind-mobile-towers-in-ottawa/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>Perl module for detecting virtualization</title>
	
	<guid>http://www.dmo.ca//blog/perl-module-for-virtualization-detection/</guid>
	<link>http://www.dmo.ca//blog/perl-module-for-virtualization-detection/</link>
	
	
	<category>linux</category>
	
	<category>module</category>
	
	<category>perl</category>
	
	<category>virtualization</category>
	
	
	<pubDate>Thu, 25 Feb 2010 13:38:04 -0500</pubDate>
	<dcterms:modified>2010-02-28T00:02:34Z</dcterms:modified>
	
	<description><![CDATA[<p>A while back, I <a href="http://www.dmo.ca//blog/./detecting-virtualization-on-linux/">posted</a> about detecting
virtualization on Linux from a shell, using various tricks.  Around that time,
I also implemented those tricks as a perl script for internal use at
<a href="http://www.roaringpenguin.com/">work</a> with the intent of eventually cleaning
it up for public consumption.  I finally got around to doing it, and the result
is
<a href="http://search.cpan.org/dist/Sys-Detect-Virtualization/">Sys::Detect::Virtualization</a>
availabe from CPAN, or from <a href="http://github.com/dave0/Sys-Detect-Virtualization">GitHub</a>.</p>

<p>Currently, it can only handle Linux, and is only tested on a small number of
virtualization hosts.  Patches are welcome.</p>
]]></description>
	
</item>
<item>
	
	<title>Thinkpad Voodoo Zombie Resurrection</title>
	
	<guid>http://www.dmo.ca//blog/thinkpad-voodoo-zombie-resurrection/</guid>
	<link>http://www.dmo.ca//blog/thinkpad-voodoo-zombie-resurrection/</link>
	
	
	<category>dead</category>
	
	<category>hardware</category>
	
	<category>thinkpad</category>
	
	
	<pubDate>Tue, 22 Sep 2009 21:53:09 -0400</pubDate>
	<dcterms:modified>2009-09-23T01:55:10Z</dcterms:modified>
	
	<description><![CDATA[<p>Today, my  <a href="http://www.thinkwiki.org/wiki/Category:T61">Thinkpad T61</a> decided to stop working.  While I was in the middle of reading email, it just stopped.  Completely blacked out -- no AC light, no battery light, nothing.  Here's how I got it working again.</p>

<p><a href="http://www.dmo.ca//blog/./thinkpad-voodoo-zombie-resurrection/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>VServer and 127.0.0.1</title>
	
	<guid>http://www.dmo.ca//blog/vserver-and-127.0.0.1/</guid>
	<link>http://www.dmo.ca//blog/vserver-and-127.0.0.1/</link>
	
	
	<category>fun</category>
	
	<category>linux</category>
	
	<category>loopback</category>
	
	<category>remapping</category>
	
	<category>vserver</category>
	
	
	<pubDate>Tue, 14 Jul 2009 12:20:18 -0400</pubDate>
	<dcterms:modified>2009-07-14T16:52:16Z</dcterms:modified>
	
	<description><![CDATA[<p>I recently moved <a href="http://www.roaringpenguin.com/">our</a> automated testing
systems from a KVM+Qemu setup to <a href="http://linux-vserver.org/">Linux-VServer</a>.
We didn't need the overhead of a full virtual environment, even one as
lightweight as KVM.  However, there was a little snag -- 127.0.0.1 didn't work
correctly.</p>

<p><a href="http://www.dmo.ca//blog/./vserver-and-127.0.0.1/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>Converting vimblog to ikiwiki</title>
	
	<guid>http://www.dmo.ca//blog/Converting_vimblog_to_ikiwiki/</guid>
	<link>http://www.dmo.ca//blog/Converting_vimblog_to_ikiwiki/</link>
	
	
	<category>git</category>
	
	<category>ikiwiki</category>
	
	<category>perl</category>
	
	<category>vimblog</category>
	
	
	<pubDate>Sun, 17 May 2009 11:16:08 -0400</pubDate>
	<dcterms:modified>2009-05-18T11:58:20Z</dcterms:modified>
	
	<description><![CDATA[<p>Until today, this blog ran on <a href="http://www.dmo.ca//blog/./../tag/vimblog/">vimblog</a>, a hand-rolled minimal script for
displaying blog entries.  In the last year or so, though, I've become a convert
to <a href="http://git-scm.com/">git</a>, and so what I really want to do is edit my posts on any system,
commit them to a git repository, push to a remote and have them end up as blog
entries on my server.  Fixing vimblog to do this would have been more work than
I want to deal with, but thankfully <a href="http://ikiwiki.info">ikiwiki</a> exists, and
can do most of what I need.</p>

<p>So, as of now, this blog is in ikiwiki.  To get there, I followed (more or
less, since I'm documenting after-the-fact) these steps:</p>

<p><a href="http://www.dmo.ca//blog/./Converting_vimblog_to_ikiwiki/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>Benchmarking BDB, CDB and Tokyo Cabinet on large datasets</title>
	
	<guid>http://www.dmo.ca//blog/benchmarking-hash-databases-on-large-data/</guid>
	<link>http://www.dmo.ca//blog/benchmarking-hash-databases-on-large-data/</link>
	
	
	<category>berkeleydb</category>
	
	<category>cdb</category>
	
	<category>database</category>
	
	<category>linux</category>
	
	<category>perl</category>
	
	<category>tokyocabinet</category>
	
	
	<pubDate>Fri, 01 May 2009 10:35:36 -0400</pubDate>
	<dcterms:modified>2009-05-01T14:35:36Z</dcterms:modified>
	
	<description><![CDATA[<p>At <a href="http://www.roaringpenguin.com/">my job</a> we have need of a high-performance
hash lookup database in our <a href="http://www.roaringpenguin.com/products/canit-pro">antispam product</a>.
It's used to store Bayes tokens for quick lookups on individual scanning
systems, and is read-only in the fast path (mail scanning) with updates taking
place in another process.  For the last few years, we've been using a plain old
BerkeleyDB hash database via Perl's DB_File, but with all the hype about <a href="http://tokyocabinet.sourceforge.net/">Tokyo
Cabinet</a> and its <a href="http://tokyocabinet.sourceforge.net/benchmark.pdf">benchmark
results</a> I figured it was
time to take a look.</p>

<p><a href="http://www.dmo.ca//blog/./benchmarking-hash-databases-on-large-data/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>Configuring bind9 in a chroot, lenny version</title>
	
	<guid>http://www.dmo.ca//blog/20081009143754/</guid>
	<link>http://www.dmo.ca//blog/20081009143754/</link>
	
	
	<category>bind</category>
	
	<category>chroot</category>
	
	<category>debian</category>
	
	<category>lenny</category>
	
	<category>linux</category>
	
	
	<pubDate>Thu, 09 Oct 2008 14:37:54 -0400</pubDate>
	<dcterms:modified>2009-11-01T13:26:58Z</dcterms:modified>
	
	<description><![CDATA[<p>A while ago, I blogged the <a href="http://www.dmo.ca/blog/20080412165627">chrooting of bind9 on
Debian</a>, so I wouldn't forget how to do it. Things have
changed slightly for Lenny, so here's the update.</p>

<p><a href="http://www.dmo.ca//blog/./20081009143754/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>Perl test output in a temporary vim buffer</title>
	
	<guid>http://www.dmo.ca//blog/20080910144244/</guid>
	<link>http://www.dmo.ca//blog/20080910144244/</link>
	
	<pubDate>Wed, 10 Sep 2008 14:42:44 -0400</pubDate>
	<dcterms:modified>2008-09-10T18:42:44Z</dcterms:modified>
	
	<description><![CDATA[<p>I recently came across a Vim tip explaining how to <a href="http://vim.wikia.com/wiki/Display_shell_commands%27_output_on_Vim_window">display shell commands in a
different buffer</a>.
While useful, it opens a separate scratch buffer every time you run the
command.  I wanted to make it reuse the same scratch buffer, so that whenever I
ran my unit tests using it, they overwrote the previous run's output.  As it
turns out, Vim has a way to do this.</p>

<p><a href="http://www.dmo.ca//blog/./20080910144244/#more">more</a></p>
]]></description>
	
</item>
<item>
	
	<title>Fixing the name of App::Ack on Debian</title>
	
	<guid>http://www.dmo.ca//blog/fixing-ack-on-debian/</guid>
	<link>http://www.dmo.ca//blog/fixing-ack-on-debian/</link>
	
	
	<category>ack</category>
	
	<category>alternatives</category>
	
	<category>debian</category>
	
	<category>lenny</category>
	
	<category>perl</category>
	
	
	<pubDate>Thu, 03 Jul 2008 22:54:59 -0400</pubDate>
	<dcterms:modified>2008-07-04T02:54:59Z</dcterms:modified>
	
	<description><![CDATA[<p><a href="http://search.cpan.org/dist/ack/ack">ack</a> is a great "programmer's grep" tool.
If you don't already use it, check it out.  Now, ack is packaged as part of
Debian Testing (Lenny), but unfortunately there's a name conflict.  Debian
already ships a Kanji code converter named ack, so the ack that <em>I</em> want gets
renamed to ack-grep.</p>

<p>I want to run 'ack' on all my systems, not 'ack' on some and 'ack-grep' on
others, so I abused Debian's 'alternatives' system to let me do this with:</p>

<pre><code>    update-alternatives --install ack ack /usr/bin/ack-grep 100
</code></pre>

<p>And voila, it creates me a /usr/bin/ack that Just Works, and is known to Debian
so future packages won't (I hope) break that symlink.</p>
]]></description>
	
</item>

</channel>
</rss>
