<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="5.0" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
<info>
    
    
    
    
    
    
    
    
    
    
    
<title>Back online</title><biblioid class="uri">http://norman.walsh.name/2006/12/18/backOnline</biblioid>
<volumenum>9</volumenum>
<issuenum>122</issuenum>
<pubdate>2006-12-18T10:03:23-05:00</pubdate>
<date>$Date: 2006-12-18 12:14:37 -0500 (Mon, 18 Dec 2006) $</date>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2006</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>The thing about digital technology is, either it works or it
doesn't.</para>
</abstract>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#SelfReference"/>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#ThinkPad"/>
</info>

<epigraph>
<attribution>
      <personname>
<firstname>Leslie</firstname>
	<surname>Lamport</surname>
</personname>
    </attribution>
<para xml:id="p2">A distributed system is one in which the failure of a computer
you didn't even know existed can render your own computer
unusable.</para>
</epigraph>

<para xml:id="p1">Epigraphs aside, the computer in question was my own
laptop. Halfway through a telcon (one for which I was chair and
scribe, of course, because Murphy has a perverse sense of humor), my
laptop went “click”. Black screen: no input, no output. Not even over
<command>ssh</command>, so it wasn't simply an
<wikipedia>X11</wikipedia> issue.</para>

<para xml:id="p3">Reboot, get back to where I was, “click”.</para>

<para xml:id="p4">Reboot…“click”.</para>

<para xml:id="p5">As it turns out, I'd run <command>apt-get upgrade</command> that
morning and gotten a new kernel. So I spent half the day trying to back
out the obviously busted upgrade. Long story short, it wasn't the upgrade.
Confirmation came when it did exactly the same thing in the middle
of restoring Windows (because IBM support doesn't support Linux). Twice.
It also died running a memory test overnight.</para>

<para xml:id="p6">Curiously, it went through
the IBM <citetitle>PC Doctor</citetitle> diagnostics without tripping.
So while it's boxed up now and on its way to be repaired, I'm a little
worried that they're going to have difficulty reproducing the problem.</para>

<para xml:id="p7">It took a day and a half, more or less, to get the environment
on my desktop box back into workable shape and copy all the data off
my laptop hard disk.</para>

<para xml:id="p8">I did bungle the <wikipedia>DSPAM</wikipedia> install though. As
a result, I wound up with nearly 2,000 spam messages to sort through
by hand. If you sent me mail in the last five to seven days, expected
a timely reply, and haven't heard from me, you might want to try
again. It's certainly possible that I dropped some mail on the
floor.</para>

<para xml:id="p9">Now if I can just get used to the layout on this desktop keyboard…</para>

</essay>

