What a great 24 hours! Votes were counted, exit poll (mostly) matched the polls leading up to the election, and most importantly, the American people voted decisively for change:
Anyone who has looked inside a computer has probably noticed that PC motherboards have a battery plugged into them. This battery is responsible for keeping alive the memory that holds the BIOS settings. When the battery goes flat, those settings are lost, and the next time the computer boots, it has forgotten about things like what hard disks are connected, or the frequency at which the clock should run.
In most of the PCs I have worked with over the years, that’s about all that happens — it’s annoying, but each time the computer boots it has lost its settings. In servers, which don’t reboot often, a flat battery could go unnoticed for months.
Yesterday, I discovered that some PCs are far less predictable when the motherboard battery is flat. I have four ~5-year-old Shuttle PCs, and some of them haven’t been turned on for a year or so. What *they* do is not start at all once the battery is flat. But if you leave the mains power connected for a while, eventually something gets enough charge that the motherboard decides it can boot after all.
In addition, with a battery on the way out, the PCs would get part way through booting and then freeze in random places. This took some time to discover — I was initially suspicious of a recent operating system upgrade, and then that a disk might be on the way out.
To keep a long story from getting any longer, the lesson learned was that it’s worth spending $1.75 every 2-3 years to keep a charge in that battery. Once it goes flat, odd things can happen.
I’ve had some requests for the experiments used in my SIGMOD 2008 paper, Serializable Isolation for Snapshot Databases, coathored with Uwe Röhm and Alan Fekete.
So here are the details:
- The patch against Berkeley DB 4.6.21 implementing our new method of serializable isolation is here: db-4.6.21-safe-si2.diff;
- The XML description of experiments uploaded to the repeatability committee is here: exp333.xml; and
- Binaries for Linux/AMD64 are here: db-4.6.21-safe-si2-linux-x86_64.tar.bz2.
Please contact me if you have any questions.