Author: Dave Farquhar

Much ado about nothing and other stuff

Dave Farquhar General , , , , , , , , , ,

Much ado about nothing. The most recent report I read indicates that AOL/Time Warner and Red Hat are talking, but not about an acquisition. Sanity has entered the building…
Good thing User Friendly got a chance to get its two cents’ worth in. I got a couple bucks’ worth of laughter from it.
Much ado about something. On Sunday, Gentoo Linux developer Daniel Robbins announced that an obscure AMD Athlon bug slipped past Linux kernel developers, resulting in serious problems with Athlon- and Duron-based systems with AGP cards. This confirms some suspicions I’ve heard–one of the Linux mailing lists I subscribe to occasionally has rumblings about obscure and difficult-to-track-down Athlon problems.

The result was that Gentoo’s site was slashdotted into oblivion for a while, but hopefully it also resulted in some extra exposure for the distribution. Gentoo is another source-based distro. Lately I’ve been resigned to just using Debian to build my Linux boxes, but I’m still awfully fond of the idea of compiling your own stuff. As CPUs get faster and faster, I expect that to become more commonplace.

But I digress. The bug involves the CPU’s paging function. Older x86 CPUs used 4K pages. Starting with the Pentium, CPUs started allowing 4MB pages. But a bug in the Athlon’s implementation of this extended paging causes memory corruption when used in conjunction with an AGP cards.
Alan Cox is working on a workaround. I’m a bit surprised a patch isn’t already out there.

CPU bugs are discovered all the time, but it’s fairly rare for them to be serious. If you ever run across a Pentium-60 or Pentium-66 system, boot up Linux on it sometime and run the command dmesg. You’ll find workarounds for at least two serious bugs. A TI engineer named Robert Collins gained a fair bit of notoriety in the last decade by researching, collecting, and investigating CPU bugs. Part of it was probably due to his irreverant attitude towards Intel. (As you can see from this Wayback machine entry.) Sadly, I can’t find the story on the site anymore, since he was bought out by Dr. Dobb’s.
Catching up. I haven’t been making my rounds lately. The reason why is fairly obvious. I used my day off yesterday to have lunch with someone from my small group, then when I got home I read the e-mail I absolutely had to read, responded to those that absolutely had to get responses, answered a couple of voice messages, wrote and sent out a couple of other messages, looked up, and it was 5 p.m.

“Alright God,” I muttered. “I just gave the day to Your people. Time to go spend some time with You.” So I whipped out my handy-dandy Today’s Light Bible and read about Moses. Seemed appropriate. The inadequacy and jumping the gun and making excuses, that is. The Biblical “superheroes” were human just like us, and the book doesn’t gloss over that. Today’s Light is designed to divide the Bible into pieces so you can read the whole thing in two years. I can’t decide if I want to get through it in a year or in six months. A few years ago I read it in its entirety in four months, but that pace is a bit much. If you’re willing to spend as much time reading the Bible every day as the average person does watching TV, you can make it through in a few months. But it’s not exactly light reading, and I’m not sure I recommend that pace. If you’re willing to dedicate that kind of time to Bible study you’re probably better served by learning Greek so you can read the New Testament in the original. Then if you’ve still got your sanity you can think about tackling Hebrew.

I finally got around to reading Charlie Sebold’s entries for the last few days. One especially poignant observation: “I continue to be surprised at how much I remember about computers, and how much I forget about everything else (including far more important things).”

I sure can relate. I wish I could trade everything I remember about IBM PS/2s and Microchannel for something more useful. But I remember goofy baseball statistics too–I can recite the starting lineup and pitching rotation of the 1980 Kansas City Royals (I’ll spare you). But I can’t tell you the names of all seven people I met Sunday night.

Who put me in charge?

Dave Farquhar General

I just had to say no to someone. I didn’t want to say no. But the timing wasn’t right for everyone else. I’ve got someone here with some leadership ability but we’re going to have to sit on it for a little while longer. I don’t like that much. The other person doing the waiting really doesn’t like that much.
I think I liked things better when I had a mentor, and my mentor was the one who made the decisions and delivered the bad news. Now I don’t have a mentor, I still don’t make the decisions (because I refuse to unilaterally make decisions that affect dozens of people just because some outsider decided it would be a good idea to make me a de facto leader), and I deliver the bad news.

I like my Washington-style approach of getting tons of conflicting opinions, sorting through them, and then trusting that I have more wisdom than a garden-variety guinea pig and calling it a decision. It empowers people and it minimizes my lunkhead moves. It’s not the best approach for everyone but it works well for me. So I won’t change that.

I think I need a mentor, and the first thing I want to learn from that mentor is how to deliver bad news.

What on earth is going on?

Dave Farquhar General , , , , , , , ,

AOL-Time Warner in talks to buy Red Hat? I found this this morning. It’s intriguing, but I can’t decide if a buyout would be a good thing or a bad thing. After all, Netscape was in decline when AOL bought it. It nosedived afterward. Obviously, the problem was twofold. When AOL acquired Netscape, they didn’t acquire all of its mindshare. Some of the most talented people got fed up and left. You can take Jim Barksdale or you can leave him. The loss of Marc Andreesen and Jamie Zawinski, though, was substantial.
The second problem was that AOL wasn’t serious about competing. They bought a browser technology and basically sat on it. Netscape 4.x was fundamentally flawed, as even Zawinski acknowledges, although I would argue it was no more fundamentally flawed than IE 4.x. The Gecko engine, on which Netscape 6.x is based, is solid technology, even though it took longer to get to market than anyone had hoped. Although Netscape 6.x won’t bowl anyone over, other browsers based on the technology, such as Galeon, are absolutely fantastic. But AOL chose to release a half-hearted browser with the Netscape name on it and continued to use the IE engine in its flagship product even after the favorable agreement with Microsoft that prompted AOL to do so in the first place expired.

That begs the question of what AOL would do with Red Hat if it owned it. Red Hat is still the big-name player in the Linux field, but Red Hat is concentrating on the server market. You can still buy Red Hat at retail, but on the desktop, Red Hat is arguably #3 in popularity now behind France’s Mandrake and Germany’s SuSE. Red Hat is the only Linux company that’s making money, but that’s largely by selling consulting. That’s not AOL’s core business. At this point, AOL is more of a media company than a technology company. Software just gives AOL more outlets to sell its media content. Consulting doesn’t do that.

The best possible scenario for a Red Hat buyout would be for AOL to, as Microsoft puts it, “eat its own dog food,” that is, rip out the infrastructure it bought from other companies and replace it with the technology it just developed or acquired. Since AOL is largely powered by Sun servers, it wouldn’t be terribly difficult to migrate the infrastructure to Red Hat running on Intel. Then AOL could give a big boost to its newly-acquired services division by saying, “We did it and we can help you do it too.” They can also cite Amazon’s recent successes in moving its infrastructure to Red Hat Linux. There is precedence for that; after AOL bought Time Warner, the entire company started using AOL for e-mail, a move widely questioned by anyone who’s used anything other than AOL for mail.

Of course, it would be expected that AOL would port its online service to Linux, which would create the truly odd couple of the computing field. AOL, meet sed and awk. Red Hat would certainly lose its purity and much of its credibility among the Linux die-hards. AOL would bank on making up the loss by gaining users closer to the mainstream. AOL could potentially put some Linux on its corporate desktops, but being a media company, an all-out migration to Linux everywhere within is very far-fetched.

To really make this work, AOL would either have to enter the hardware business and sell PCs at retail using its newly acquired Red Hat distribution and newly ported AOL for Linux and possibly an AOL-branded office suite based on OpenOffice, or it would have to partner with a hardware company. Partnering with a big name seems unlikely–a Compaq or an HP or an IBM wouldn’t do it for fear of retaliation from Microsoft. Sun has never expressed any interest in entering the retail computer business, and even though Sun loves to take opportunities to harm Microsoft, Sun probably wouldn’t cooperate with AOL if AOL replaced its Sun infrastructure with Red Hat Linux. Struggling eMachines might be the best bet, since it’s strictly a consumer brand, has a large presence, but hasn’t consistently turned a profit. But AOL could just as easily follow eMachines’ example, buying and re-branding low-end Far East clones and selling them at retail as loss-leaders, taking advantage of its lack of need for Windows (which accounts for roughly $75 of the cost of a retail PC) and making its profit off new subscribers to its dialup and broadband customers. A $349 PC sold at retail with a flashy GUI, decent productivity software and AOL is all the computer many consumers need.

The advantage to this scenario for everyone else is that AOL would probably dump more development into either the KDE or GNOME projects in order to give itself more and higher-quality software to offer. The official trees can either take these changes or leave them. Undoubtedly, some of the changes would be awful, and the official trees would opt to leave them. But with its 18 years’ worth of experience developing GUIs, some of the changes would likely be a good thing as well.

The more likely scenario: AOL will buy out Red Hat, not have a clue what to do with it, and Red Hat Linux will languish just like Netscape.

The even more likely scenario: AOL will come to its senses, realize that Red Hat Linux has nothing to do with its core business, and the two companies will go their separate ways.

I’m fried.

Dave Farquhar General , ,

I spent the day trying to make an old PC get on the network, and I failed valiently. The machine connects to the network just fine in DOS. Load NT4 or 2000 though, and it shuts up fast. I didn’t try Linux, though I was threatening. I tried another 3Com 3c905. Nothing. I tried it in every possible PCI slot. Nothing. I swapped in an Intel EEPro/100. Nothing. I found an old ISA 3Com 3c509 card in a rehabbed Gateway2K box. Nope. All it did was sing to me. “I have no need for friendship, friendship causes pain. It’s laughter and loving I disdain. I am a rock. I am an island.”
Actually it didn’t even do that. It just stared back at me defiantly. Even when I told it I’d throw it in the pond. That just made me madder.

Stupid Intel motherboards. Too bad when you order a brand-name PC you can’t tell them you want an Asus or a Gigabyte. I swear by Asus. Lately I’ve been swearing at Intel. Wait, who am I kidding? I’ve always trusted Intel as much as I trust Microsoft. Which is about the same as I’d trust Slick Willie Clinton with my 17-year-old daughter, if I had a 17-year-old daughter.

And the system’s not even a month out of warranty either.

I’m frustrated because I’m the third guy to take a stab at this, and I’m the guy they turn to to take the impossible situation and manage to work it out. This one beat me, and I can’t stand losing.

Good thing I get a long weekend. I’m gonna go hang out with some of my Bible-thumpin’ buddies.

Katelyn update. Katelyn didn’t have surgery today. She’s in good enough shape to not need immediate surgery, but not in good enough shape to go home. They’re going to give her as much time as they can to build up strength, then it looks like they’ll go back in, unless something really changes quickly and she’s able to go home for a month.

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.

Not much new on Katelyn

Dave Farquhar General

Not much Katelyn news. I heard a little bit last night. The doctors are preparing to go back in for surgery, which suggests the infection must be clearing. But that’s all I know.

Bad news on Katelyn

Dave Farquhar General

Bad news on Katelyn. Brad just called. The infection is, as doctors feared, attacking the sutres in her heart. That means surgery to repair the damage, but they have to clear the infection first.
Please be praying.

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.