The Changelog

I started this blog 5 years ago. In that time, I've written about Linux on the desktop, photography, international peace, version control systems, ice storms, Haskell, health care, rural life, Kansas, and infants.

Today I realized something: I am the #1 hit on Google when you search for smelly ducting. This will take you to a story I wrote back in 2005 about an odd odor in our house. I believe it is my most popular story ever, with almost 100 comments -- and comments continue to trickle in, a few a week.

What's the right word to use for that? When the great worldwide democratizing force that is the Internet collectively decides that your most important blog post is about smelly ducting?

I'm glad folks know what matters. Wouldn't want to worry too much about what's going on in Iraq, Washington, or Kansas if your ducts smell, that's for sure.

Obviously every single Presidential candidate has missed out on a key issue in voters' minds. If only someone would come out with a freshly-scented ducting platform, this country could finally move forward!

I've been thinking about this for awhile, so time to put down some thoughts.

First, what is socialized medicine? If we listen to the politicians that label health care as "socialized", it seems to be "anything that is paid for by taxes and delivered free or cheaply to citizens." Putting aside the question of whether that meets the academic definition of socialism for the moment, let's look at things in the United States that are already socialized:

• K-12 education
• Police
• Fire fighters
• Public Libraries
• Roads
• Airports and air traffic control
• Military defense and offense

That's right. We trust the government with our children all day long for 13 years. For free!

Yet this is a country in which hospitals dump the homeless in the gutter for being unable to pay their bills. Even insured Americans find claims turned down for arbitrary reasons. People are afraid to change jobs for fear of losing health insurance.

Why is it bad to have the government pay for health care?

Here in the United States, our health care system is far from best in the world. It's not even top 10. Or 20. Our system encourages minimizing health care, and doesn't encourage preventative care.

I'd suggest that, in a democracy, it's best to have the government pay for health care. That's because, in a democracy, we are in control of the bureaucrats. If we wish to exercise common sense and pound into their heads that paying for preventative care makes good long-term sense, then we can do so at the ballot box.

So why the scare tactics about government being involved in health care?

Perhaps our real problem is that we have let government get out of our control? Perhaps we are too frightened of change to vote. Perhaps we've given up on a responsive government. Perhaps we think that the insurance companies and drug companies will never let us have a good health care system.

Yes, the lobbyists have a lot of power. But we have the power to remove it, and it's high time we used it.

The audacity of Obama to have hope. To say that we can do better. When Hillary Clinton falls in line with the Republicans and accuses him of having "false hope", effectively saying that we can't do any better, then is she -- or any Republicans -- really a candidate of change? I think that all these accusations from conservatives and Hillary that Obama has "false hope" has finally convinced me that he's the one to vote for. If everyone else claims that his ideas are too good, that his dreams too big, then I like him.

Oh, and you could substitute "college education" for "socialized medicine" everywhere in this article and get equally valid arguments.

As you might know from reading my blog, at my workplace, we have largely standardized on Linux on the desktop and laptop.

We use systemimager to maintain a standard desktop image and a separate standard laptop image. These images differ because there are different assumptions. The desktop machines mount /home over NFS, authenticate to LDAP, etc. This doesn't work on laptops. Moreover, desktops don't use network-manager or wifi, but laptops do.

Our desktop image uses Debian's hardware autodetection -- plus a little hacking in /etc/init.d/gdm -- to automatically adjust to a wide range of hardware. So far this has worked well.

Laptops are much more picky. Our standard laptop model had been the HP nc4400 -- a small and light 12" model that people here loved. HP discontinued that model. Their replacement was the 2510p. We ordered one in here for evaluation. Try as we might, we couldn't get it to suspend and resume properly in Linux.

So I went out scouring the field of Linux laptops. Companies such as Emperor Linux buy retail laptops from people like Lenovo, test them for Linux, and sell them -- at a premium. These were too expensive to justify at the quantities we need them.

Then I stumbled across Linux Certified. I'd never heard of them before. I called them up and asked a few questions. They don't buy retail laptops, but instead have OEMs in Taiwan build laptops to their spec. They happen to use the same OEM that Fujitsu does, I believe. (No big company builds laptops in the USA these days). I asked them about wifi chipsets, video chipsets, whether they use stock kernels. I got clueful answers to all of these.

So we ordered one of their LC2100s models. They didn't offer Debian preinstalled, but did offer Ubuntu, so I selected that. The laptop arrived a couple of days (!!) later, configured with the particular CPU, etc. that I selected.

I was surprised at the thrill I felt at taking a brand new laptop out of its box, turning it on, and watching Grub appear before my eyes. Ubuntu proceeded to boot. I then of course installed our regular Debian image on the thing to check it out.

It needed a kernel and xserver-xorg-video-intel from lenny, as well as the ipw3945 driver for wifi, but otherwise worked with the exact same software as our HP nc4400 image. (In fact, it wasn't hard to support both laptops with that image, since both use a lot of Intel hardware.) The one trick was making hibernate call /etc/init.d/ipw3945d stop so that the ipw3945 module could be unloaded before suspend. (Why this particular chipset needs a daemon is beyond me, but oh well.)

The hardware is great. As far as I know, the ipw3945 was the only component that wasn't directly and automatically supported by DFSG-free software in lenny main. The screen is sharp and high-contrast (it's glossy, which I personally don't like, but I bet our users will). The device itself feels sturdy. It's small and dense. I haven't opened it up, but it looks like all you need is a screwdriver to do so.

The only downside is that they don't sell docking stations for it. Their standard answer on that is to buy a USB docking station. That's a partial answer, but can't handle power or video like a standard docking station will.

Also, the LC2100s is much cheaper than the HP laptop, even when configured when nicer specs in every way. That is no doubt partially due to the lack of the Windows tax.

I'm sending off an order for 4 more today, I believe.

One year ago today, I wrote that we had moved onto the farm on Jan. 20. That was quite the day: 7.5" of snow, and windy.

When we moved in, our kitchen didn't yet have its flooring or any appliances. We had a microwave sitting on a 5-gallon bucket and a borrowed dorm fridge for the "kitchen". There were other little things being finished up, too. Of course, "moving in" doesn't just happen in an afternoon either. We are still sorting through boxes from time to time, cleaning up stuff in the elevator (some of which was grandpa's), and punching down the last few network runs.

Before we moved in, we spent three months in a drafty basement apartment. Our previous house had sold, and the farmhouse wasn't ready to move into yet. And we moved out of that other house about 3 weeks after Jacob was born.

It was a busy, exhausting time. But we're so glad we did it. Jacob's room is much closer to ours, which is quite helpful. He loves to scoot around on the wood floors. Terah bought him a large pillow, and he likes it when I give him pillow rides around the house.

Older people that knew my grandparents love to drop by, too. For awhile after we moved in, we'd have people just drive on the yard to see what it looks like now. The person who pruned our trees hinted that he was curious what the inside of the house looked like, so I showed him. He grew up Amish, and said, "wow, this would be a perfect Amish house!" I guess the Amish could remove the network jacks.

We have some neighbors a mile away. They're two sisters living on their parents' farm. I think they're in their 70s or 80s. They drive whatever car their dad bought before he died 20 or 30 years ago. Last month, one of them gave me a call. I've been collecting photos for the upcoming church centennial, and she had some that she thought I might be interested in. It was snowy and cold, so I said I'd be happy to go over and look at them sometime. That wasn't quite her plan. "Oh, that's no trouble. I like to get out, and you're not far away." She brought over some wonderful photos (which I scanned), and also got to see the inside of the house for the first time in years.

That's how things go out there. Last June, we had some tourists drop by. It's been a lot of fun to be part of this community again.

Before long, Jacob is going to love playing in the elevator and walking down to the creek. Maybe he'll like making a snowman next winter, or riding a bicycle up and down the driveway someday. It will be fun to see.

Earlier today, I started reading about the DjVu family of document formats. It really sounds slick: file sizes much smaller than PNG (and incredibly smaller than TIFF or PDF) for lossless data with the DjVuText format, file sizes much smaller than JPEG with equivalent quality for the DjVuPhoto format, and an advanced DjVuDocument format that separates the background photo from the foreground text and produces a quite nice output. There are wonderful plugins for browsers on all platforms, and server-side support already in Debian for sending pages incrementally as needed by clients.

I tried this out a bit and indeed it looks great on monochrome scans, and I made a quick try of DjVuPhoto as well. That part looks great.

So here's the bad news.

Debian has no nice way to generate DjVuDocument files. There is a PS/PDF-to-DjVu converter that uses a djvu driver for Ghostscript. But Debian does not include that driver. Though, strangely, the program that depends on this driver is actually in Debian main. (Bug filed.) That program actually will make background-separated images, but only if they are separate objects in the input.

All Debian has is a program csepdjvu, which requires you to somehow manually separate the foreground and background images. Ugh.

So there is no way using software in Debian to produce DjVuDocument files with automatic separation, either from scans or from a digital source. It appears that there may not be Free Software to do this from scans either. This fact is not made clear at all in the DjVu documentation that is around.

A very sad day approaches.

Those of you old enough to remember Gopher may proceed to shed a quiet, ASCII-art tear. Gopher document type 0.

For those of you that don't know what Gopher is, here's my quick summary:

* It existed before the web.
* It is an extremely simple protocol designed to be an Internet-wide filesystem, though the bit that let you mount the Internet like a disk never quite happened, though still could. (actually I think I saw a FUSE gopher implementation recently)
* It pretty much does everything that WAP does, but about 50 times simpler. Why smartphones invented WAP instead of just using Gopher is still a mystery to me.
* XML-RPC is usually extreme overkill when you could use a simple protocol like Gopher

Now how many of you remember Veronica and Archie?