Another Katelyn update.

Dave Farquhar General

I talked to Brad earlier today. They tried to remove Katelyn’s breathing tube today. The goal is that if she can breathe on her own, they’ll send her home for a month to gain strength, then they’ll go in and fix the heart. The damage to the sutres evidently isn’t as extensive as originally feared. Obviously this is the best option. She’s been through more this month than most of us go through in a lifetime. And obviously the home is a better place to heal, from a psychological standpoint, than a hospital.
If she can’t breathe on her own, they’ll go in much sooner, probably within days.

John and Karin are struggling. The possibility that Katelyn may die has always been there, but it didn’t hit until the infection.

Why Linux stands a chance

Dave Farquhar Linux , , , , ,

Something I read on LinuxToday on Monday made me realize something. The article was a tutorial on writing Gnome apps with Python. Not too exciting, right? Not until you realize the implications. Python is a high-level, interpreted language. Gnome produces good, professional-looking applications with Windows-like functionality like toolbars and menus and drag-and-drop.
Put two and two together. Remember the early days of computing, when practically everyone who owned one knew how to program, at least a little bit? We’d program our 8-bit microcomputers in Basic, and sometimes we’d come up with something cool. You might send your creation off to a magazine in hopes of them publishing it and sending you a little money — a friend growing up and I netted a cool $350 on a little hack we wrote over spring break one year. Other times you just uploaded your creation to a BBS, hoping that people would find it useful, and maybe someone would download it and improve it a little. IBM was big and unstoppable, and Apple made the wise decision to flood the schools with cheap hardware in hopes of making it up by selling overpriced hardware to homes and businesses (which they did), but the homebrew market kept Commodore afloat for 10 years after their last good marketing decision. The cost of entry was low, and an easy-to-learn programming language was built right in, so creative minds could start playing with it without spending hundreds or thousands of dollars on development tools and thousands of dollars going to class.

The results weren’t always professional, but a surprising amount of it was exceptionally high-quality. High enough to sell more machines. Today, some 20 years after the Commodore 64 was released, it still has a following. It’s insane.

I still think that was part of what killed the Amiga. There were free languages for it, but you had to fork over a few hundred bucks for the toolkit to make them work. A lot of people did, but not enough. The development community was small. Some of the best stuff I saw on that platform came from people who pirated the toolkit. But not enough people did, so the pool of people to learn and steal tricks from was tiny. Meanwhile, Microsoft was selling complete languages, with everything you needed, for less than Commodore was charging for its header files. The Amiga never stood a chance.

Linux and other open-source projects collectively give you a free operating system or five, but they also give hundreds of development tools. The end result is Web sites like Freshmeat that do nothing but track new software. There may be more graphical Linux freeware out there now than there is Windows freeware. Considering Linux has maybe 1/50 the installed base of Windows, that’s pretty impressive. Linux doesn’t have a killer app just yet, but it may come. It’s definitely not short of ideas. Just this past week, someone released a hack for the Nautilus file manager to make it read binary newsgroups. It reads them and is intelligent enough to group related binaries in subdirectories for you. It’s a file collector’s delight. Brilliant idea. I’ve never seen anything like that for any other OS, especially not Windows.

Free languages lower the bar. Free and capable high-level languages lower the bar even more. Even a non-programmer like me can have an idea, hack out something in Python, and even if it doesn’t work perfectly, it can serve as a springboard for someone else to grab and improve, either by revising the existing code or by translating it into a lower-level, faster language. The quality of the code isn’t nearly as important as the quality of the idea. And we all know programmers don’t have a monopoly on good ideas.

Maybe Linux will remain an underground, punk OS forever. But even if it does, it’s going to be an unbelievably good one. Look for it to be bigger than the Mac within two years.

Another Katelyn update

Dave Farquhar General

When I was at church this morning, after early service, I turned around and to my surprise, Karin in the row behind me, holding Tommy (Katelyn’s brother). Ever the trooper, Tommy was alert and looking around, taking in his surroundings. Either Karin had come in late or I was being an unusually good Lutheran during the service, not looking at or talking to anybody. I think she came in late.
I asked Karin how Katelyn was. They’ve been having problems finding veins for her IVs, which is frustrating for her. I think I remember her saying, “I just want them to quit poking my baby.” She knows it’s necessary, but the people who come to put in the IVs aren’t always the most proficient at finding (and hitting) veins. On Friday or Saturday an experienced nurse came in and found a vein in her foot and hit it on the first try. She said that vein would be fine until Monday or Tuesday.

Her doctor has stepped up the antibiotics to an aggressive intravenous blend to combat her staph infection. She sounded confident that Katelyn would be coming home within a week, but the infection, if left uncontrolled, could damage the patch they put in her heart so they’re watching it closely and fighting it aggressively. She is sleeping a lot, which is good because she needs it. She’s not eating on her own right now but Karin made it sound like she has at times.

If you want to chase rainbows…

Dave Farquhar General ,

It was a Sunday, in the spring of 1998. I was 23 years old. I was driving on I-435 outside of Olathe, Kan., on my way to I-70, returning from a seminar that changed my life. But I wasn’t thinking too much about that at the moment. I’m plenty familiar with I-435 north of I-70 on the Missouri side, but I’d never driven the southern portion of I-435 before. I hate driving on Interstate highways during a storm, and the rain was coming down in buckets. I hate driving in unfamiliar areas when I’m low on fuel. My orange gas indicator was lit and my car had dinged at me a time or two: “Feed me, you dingaling!” it was saying.
Finally, I found a sign that indicated a service station. It was a couple of miles off the highway, but I took it. Better to take something you know than to take chances when you’re low on fuel. The road twisted and turned, and I didn’t know if the gas station would be on the left or right. Finally I found the station, on the left. I pulled in, swiped my credit card, fueled up, and found out once again that my 12-gallon tank actually held more than 12 gallons. Meanwhile, the storm continued to relentlessly pound the earth. I got back into my car and realized I didn’t completely remember which direction I’d come from. I took a chance on my hazy short-term memory and turned right, out of the station, praying that I’d run back into I-435 because I had no idea where the unfamiliar road would lead if I’d turned the wrong direction.

Finding I-435, I continued on my journey. The road twisted more than I liked, and when I continued onto I-470, conditions didn’t really change. But as I approached I-70, the storm lightened a little. I saw a rainbow, then another, then another. Three rainbows. No matter how the road twisted and turned–which seemed like a lot at the time, even though I had a new set of Michelins and I’d already had one opportunity to find out just how good they were–those rainbows stayed directly in front of me. The storm picked back up and the rainbows faded. The storm relented some more.

It was a good metaphor for my life at the time. I was attending a church that was simultaneously admonishing me to use my talents for the glory of God and telling me that serving God in its ministries was a right that had to be earned. My ex-girlfriend was sending mixed signals at a rate of a million a minute any time she came around, which was often. Meanwhile I fought an internal battle. I wanted her back like the desert soil wants rain, yet I knew more and more with each passing day she wasn’t good for me. On top of all that, some of her friends and acquaintances seemed to be eyeing me up, making me wonder if they weren’t trying to figure out what was wrong with me that would make her leave, and whether they were wondering if I’d be good enough for them. Some of them had just ended relationships themselves, while others hadn’t had one in a long time. I wasn’t especially interested in finding out–I was gripped by a mortal fear that they’d do the same thing she did in the end. And if that wasn’t enough, my career was falling apart. I had computers breaking left and right, no budget to replace them outright, and heavily-used spare parts that were more than three years old. For lack of anything else to use, I was routinely deploying three-year-old systems to do things they were never designed to do. Things weren’t working well and I was taking the heat.

I considered all of this, looked out at the storm, and at the rainbows beyond. A thought came to mind. “If you want to chase rainbows, you’ll have to weather a few storms.”

I didn’t catch all the rainbows, but I caught some of them. And the storms are different today. Some of them are smaller and others aren’t. But the things that got me through those old storms haven’t changed.

And some of today’s rainbows are cooler than the rainbows were then.

Why I run Debian, and some Debian tricks

Dave Farquhar Linux , , , , , , , , , , , ,

After Dan Bowman pointed out another blogger’s recent difficulties installing Evolution on Mandrake 8.1, I had little comment other than, “That wouldn’t be an issue if you’re running Debian.” Well, I think I said a few other things because I tend to be wordy, but that was the only important thing I had to say.Debian is one of the more difficult Linux distributions to install (you have to know what hardware is in your machine–it doesn’t nicely autodetect everything like Mandrake), but it’s far and away the easiest distribution to maintain. We’ll get back to that in a minute.

Released versions of Debian tend to be ultra-conservative. The current version, Debian 2.2r5, still uses the 2.2.19 kernel, for one thing (and that’s a fairly recent change). The current 2.2 kernel is either 2.2.39 or 2.2.40. All packages (at least all the ones anyone uses anymore) are constantly checked and maintained and patched. In theory, the current stable Debian release ought to be the most bullet-proof Linux available.

Besides Debian Stable, there’s also Debian Testing and Debian Unstable. Debian Unstable is pretty cutting-edge, but I’ve had no problems running it. I just keep up with the current patches and the system runs fine. I know people who run production servers on Testing and Unstable and get away with it.

If you want the latest and greatest stuff, after you install Debian, edit the file /etc/apt/sources.list and uncomment the ftp and http lines. Next, copy and paste those lines, then edit the “stable” to read “unstable.” (Or if you’re more conservative, edit it to read “testing.”) Be aware that occasionally you’ll run into problems running packages from unstable under stable. I ran Evolution, Galeon, Dillo, Sylpheed, and a multitude of other packages from unstable just fine, but when I installed AbiWord (a really nice, lean, mean, superfast word processor, by the way) it failed to run right. I upgraded to unstable, and then it worked perfectly.

OK, let’s talk some tricks.

Want to upgrade your distribution after a new version comes out, or upgrade from stable to testing or unstable? Easy. Type this:

apt-get update ; apt-get dist-upgrade

Then Debian will go download the pieces it needs to upgrade itself.

Want to keep your system up to date with any little changes (security patches, whatever) that may have happened recently? Type this:

apt-get update ; apt-get upgrade

So Debian lets you keep a current and presumably secure installation very easily. If you run that line regularly, you can rest assured that if your system is insecure, it’s not Debian’s fault but rather a misconfiguration on your part.

Want to try out some new piece of software? Forget having to hunt down RPMs or keep track of your distribution CD. Check availability with this command sequence:

apt-get update ; apt-cache pkgnames [name of program]

Found it? Excellent. Install it with this command:

apt-get install [name of program]

And if it wasn’t as great as you heard, you can uninstall it with this command:

apt-get remove [name of program]

System acting goofy? This’ll cure much that ails you:

apt-get clean ; apt-get update ; apt-get check

So from a system administration standpoint, Debian is great. Debian developers often try to justify the difficulty of installation by saying you only have to run it once, and to a degree, they’re right.

Compiling a kernel under Debian

I found a nice document detailing customizing your kernel under Debian. The standard method works under Debian, of course, but it’s cleaner to do it within the confines of your package manager–then it doesn’t go stomping on files you modified. Plus it’s actually a little easier to let Debian handle some of the details.

Here are the notes I took while using the document.

With additions:
Use kernel-source-2.4.17

export CFLAGS=”-O3 -mcpu=i686 -march=i386 -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -malign-functions=4″
export CXXFLAGS=”-O3 -mcpu=i686 -march=i386 -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -malign-functions=4″

Using -march=i686 is known to cause instability and not improve performance by any noticeable amount. The kernel mostly ignores these settings but I set them anyway. You can alternatively set them in the file /etc/profile. If you ever find yourself compiling apps from source, you want these options set so they’ll perform optimally.

A correction:
Debian tar doesn’t seem to support the -I switch for bzip2. So I extracted the archive with the following:
bunzip2 -k -c kernel-source-2.4.17.tar.bz2 | tar -xf –

the -k switch tells bzip2 to keep the original file intact, while -c tells it to extract to stdout. The | redirects stdout to the specified program, in this case, tar. -xf tells it to extract the file.

I got an error on make xconfig:

make: wish: command not found.

So I headed off to www.debian.org/distrib/packages. At the bottom of the page, there’s a form where you can type a filename and it’ll tell you what package it comes from. Type in “wish,” hit enter, and I get a long list, including /usr/bin/wish8.3 in a package named libs/tk8.3. Sounds promising. So I do an apt-get install tk8.3 and I’m in business. Type make xconfig again, and we’re set. This page is also a really good way to hunt down packages if you don’t know exactly how Debian named it.

Options I chose for kernel compilation:

Code maturity level options: prompt for development and/or incomplete code/drivers. I answered Yes, so I’d get modern filesystem support.
Loadable module support: I answered yes to all. I’ve read that disabling modules and compiling everything directly into the kernel can improve performance but I’m wary of that. If the kernel’s too big, the system won’t boot. And the idea of modules is to keep only what you need in memory. So I suppose there are instances where a no-modules kernel could increase performance, but there are certainly instances where it would hurt. I chose to be conservative.
Processor type and features: I changed a couple of the defaults. Double-check the processor family option; in my experience it’s usually but not always correct. Enable MTRR support unless you’re using a 486, Pentium, or AMD K5 CPU. All other reasonably modern CPUs, including AMD, Cyrix, Intel, and WinChip, support MTRRs for increased GUI performance. Since the PC I’m using only has one CPU, I disable SMP support. Then I enable local APIC and IO-APIC support on uniprocessors.
General setup: I accepted the defaults, because aggressive use of APM makes me really nervous. Under Windows, APM always does me more harm than good.
MTD: Since I don’t use any flash memory devices, I accepted the defaults of No.
Parallel port support: Curiously, this was disabled by default. This PC has a parallel port but I only use network printers, so I left it disabled to save a little memory.
Plug and play configuration: I said no to ISA plug and play support, since this machine is a laptop and won’t have any ISA PnP cards. On modern PCs that have no ISA slots, say N.
Block devices: The defaults are usually sufficient, but some configurations need RAM disk support and initrd support turned on. If you’re going to mess around with ISO images, you’ll probably want to turn on loopback device support.
Multi-device support: I’ve never seen a laptop with RAID, so the default of disabling it all works great for me.
Networking options: The defaults are fine for most uses. If you’re going to make a router or firewall out of your PC, enable Netfilter.
Telephony support: I disabled it.
ATA/IDE/MFM/RLL support: Disable it if you have an all-SCSI system. I don’t. Turn on SCSI emulation support if you use a CD-R or CD-RW. Under IDE chipset support/bugfixes, disable the chipsets your PC doesn’t have. This laptop has an Intel chipset, so all I had enabled were Generic PCI IDE chipset support, Sharing PCI IDE Interrupts support, Generic PCI bus-master support, Use PCI DMA by default when available, Intel PIIXn chipset support, PIIXn tuning support.
SCSI support: I have an all-IDE system (unfortunately), so I disabled it. Note that SCSI emulation for a CD-R counts as a SCSI device, as does a parallel port Zip drive. Since I have neither, I’m safe disabling it to save some memory and speed up boot time slightly.
IEEE 1394 (Firewire support): I disabled it since I have no Firewire ports.
I2O device support: I disabled it.
Network device support: This can be tricky. I turned off SLIP and PPP since I don’t use them. You may need PPP. I turned off ARCnet support, which you’ll probably do as well since ARCnet is very rare. I have a 100-megabit 3Com 3c556 NIC in this laptop, so I went into Ethernet 10 or 100 Mbit, drilled down to 3COM cards, and said yes to 3c590/3c900 series, since that’s the driver the 3c556 uses. I turned off the others. I like to compile support for the machine’s NIC straight into the kernel when I can, since it speeds up network configuration at boot time. On servers, I’ve been known to compile support for every type of NIC I own into the kernel, so that if I ever have to change NICs, it’ll come back up automatically without any configuration from me. I turned off wireless, token-ring, PCMCIA, ATM, amateur radio, infrared, and ISDN support.
Old CD-ROM drivers: You can probably turn this off, unless you know you have an old proprietary 1X or 2X CD-ROM drive. These were the drives that generally plugged straight into an ISA sound card, and they were very common on 486s. I sold tons of these things in 1994; I’m pretty sure that by the time I was selling PCs again in the summer of 1995, everything I was selling had an IDE drive in it.
Input core support: I don’t use USB input devices, so I turned it off.
Character devices: Near the bottom, after Ftape support, there are options for specific chipsets. You can find out what chipset you have by typing the command lspci in a shell. (You have to be root to do this–use the su command if you’re logged in as yourself, as you should be.) This laptop has an Intel 440BX chipset, so I turned off the VIA, AMD, SiS and ALI support.
Multimedia devices: Disable video for Linux unless you have a capture card. Most will disable Radio adapters as well.
File systems: I enable Ext3 and ReiserFS, along with DOS FAT and VFAT (as modules), ISO 9660 and Joliet, NTFS read-only (as module). Under network file systems, I enable SMB since I (unfortunately) work in Windows environments. I disable NFS since we have no NFS servers.
Console drivers: The defaults work for me.
Sound: Since I have onboard sound, I enable sound support and pick my chipset, in this case, ESS Maestro3. I disable all others.
USB support: I have USB ports but don’t use them. I left it enabled just in case, but I’m not sure why.
Bluetooth: I don’t use it, so I disabled it.
Kernel Hacking: I disabled Kernel debugging, the default.
Whew! Hit Save and Exit. Exit X to save some system resources while compiling and installing.

The end result was an up-to-date kernel (2.4.17) that was about 200K smaller than the stock 2.2.19 kernel and boots to a login prompt in 18 seconds flat, as opposed to 45 seconds before. Much of the improvement is due to the 3c590 driver loading faster as part of the kernel rather than as a module, and the kernel no longer searching for phantom SCSI devices. But Charlie Sebold told me it’s his experience that recent 2.4.x kernels boot a lot faster than earlier kernels.

It’s not perfect–I don’t have sound completely working yet–but I found some clues. I’m not overly concerned about sound support though. The system beeps at me when I have mail, and for work purposes, that’s all the sound I need. I don’t see any point in turning my PC into a multimedia tribute to Billy Joel or Star Wars or Quake III.

Linux on a Power Mac 7500

Dave Farquhar General , ,

I built a Linux box earlier this week. There was a Power Mac 7500 at work that was begging for a conversion. Actually it’s a classic Hackintosh, assembled from the pieces of a 7500 and a dead 7600, so it’s running at 133 MHz instead of its original 100 MHz, and with 128 megs of interleaved EDO RAM. And it’s SCSI. So it had plenty of memory, a server-grade disk, and a RISC-based CPU. I had to see what it could do once it was unencumbered by the Mac OS GUI.
I chose Debian, because Debian installs very little extraneous garbage and because it’s super-simple to maintain.

And I’ll never complain about the difficulty of installing Linux on a PC again. Not that I’ve complained in a really long time, but Linux on an old Mac is a pain.

It’s nearly impossible to make these old Macs boot Linux directly, so you do a dual-boot trick, installing MacOS and then installing BootX, which is a control panel that pops up early in the boot process and asks you what OS you want. The default is Linux. Pick Linux, or let it time out, and that annoying smiling guy disappears, replaced by the glorious text-mode (bet you didn’t know the Mac had one of those, did you?) screen of the Linux boot process. Oh yeah, there’s a smiling picture of Tux up in the right-hand corner while it’s all going on. It’s a cool Wizard of Oz-like effect, I think.

So you boot off your MacOS CD, make yourself a 20-meg Mac partition, install just the base OS and the multimedia stuff, which includes the Apple CD/DVD-ROM driver–I didn’t realize that wasn’t part of the base OS and was wondering why I couldn’t read CD-ROMs anymore. Then search the CD for Stuffit Expander and Disk Copy. You’ll need those too. The version of Stuffit that came bundled with MacOS 8.5 couldn’t do anything with BootX on the Debian CD, so you’ll need to find a newer version on another Mac and then sneakernet it over. Then you use Disk Copy to generate images of the boot and root CDs. Drop BootX in System Folder::Control Panels, drop the Debian Kernel in the Linux Kernels subfolder of the System Folder, insert your Debian CD, then boot off the floppies, and you’re ready to go.

Apple hardware–old Apple hardware at least–is generally pretty reliable, so if you’ve got ancient Macs at work you need to put to something useful, this is a good way to do it. They’ll give better file server performance than a Snap server and you can even do software RAID configurations. Old desktop Macs have two 3.5″ bays, so you can mirror disks, and there is an external SCSI port for expansion if you want to do other types of RAID or connect a tape drive. And they’d make great intranet servers.

What did I do with the Mac? I made it into a PDF server. It’s great. I print to the phantom printer, and PDFs pop up in its file share. It’s lightning fast–by the time I pop over to the share to pick up the file, the server’s had enough time to create the PDF. So this 133 MHz Mac running Linux can generate PDFs in less time than it would take to print the file. I had problems with the GNU Ghostscript package (gs), so I ended up having to use Aladdin Ghostscript (aladdin-gs) instead. No big deal to me, since I’m not a GNU bigot.

I tried to make the service available to the Macs on the network too, by installing netatalk, but the phantom printer doesn’t work right. I’m still hoping to resolve that. Making shares with netatalk is frighteningly simple, but making printers with it is less fun than configuring XFree86 by hand.

Even with the difficulties, Charlie and I had it working well for Windows clients in a couple of hours. I think it was a good investment of a couple of hours, taking a computer off the scrap heap and making something useful out of it without having to buy any software.

It’s time.

Dave Farquhar General

I’m back. I needed some time to sort everything out, regroup, and, well, be something resembling a typical 27-year-old. And thanks to Dan Bowman for pointing out some of the facilities Greymatter has to take care of problems. I’d never felt the need to look for them. But now I know. And should those fail, Apache also has facilities as well. It’s good to be root.
As for Katelyn, I’ve learned to assume that no news is good news. Brad didn’t call me at all on Wednesday, and I saw him at a meeting Wednesday night and we talked, but he didn’t mention anything about her. That means no unexpected changes, which is never a bad thing.

A story. I think I’ll just wrap things up with a story. I went and saw Luke Tuesday night. Luke talked about how people sometimes treat him because of his MDA, which confines him to a wheelchair. It was so sad. Stupid. Pointless. It reminded me of something that happened a few years ago.

I was in college. I was in a fraternity. During my junior year, a young man visited us for dinner. This wasn’t uncommon; people who were interested in the house often visited for dinner. We’d show them around, answer their questions, and whatnot. What was unusual was that this young man had a condition–polio, if memory serves–that left his legs immobile, so he walked with crutches. He moved along just fine. As I recall, he even went upstairs to get the grand tour. There was some concern that if he did move in, he’d always have to live on the second floor, as opposed to the third, to minimize the amount of climbing he’d have to do. But that wasn’t a really big deal.

He left, and someone called a meeting. So there we were, the actives, sitting in the dining room. We talked about him a little, then one guy stood up and spoke.

“You do know that if he does move in here, one of you guys has to room with him.”

“What’s wrong with that, Frank?” I asked.

“Well, I’m not gonna room with him. There’s something wrong with him. Would you want to room with him?”

I pointed at one of the guys sitting at the table with Frank. “Look at Gotsch,” I said. “He’s handicapped in a way, right? His hand’s in a cast, and he can’t do everything you and I can do. And you know what? It’s his own fault his hand’s in a cast, due to his own stupidity punching a wall. Does anyone think any less of him? That guy–” and I motioned outside–“didn’t do anything to cause his handicap. I don’t think any less of him. He can room with me.”

I paused and looked at Frank.

“Assuming he’d be willing to live around someone like you.”

I guess he wasn’t willing, because he never came back. And a big part of me was glad. Not that I didn’t want a roommate–I didn’t want someone to have to go through that garbage.

A couple months later, I moved out too.