Suddenly I wish I could buy Mopar spark plugs at Autozone

The most evil of evil software companies, SCO, has finally made good on its threats to sue a big Linux user, filing harrassing lawsuits against AutoZone and DaimlerChrysler.

Of course, SCO has yet to prove it even owns the copyrights it claims it owns, not to mention it voided any claims it might have by distributing Linux under the GPL. But that doesn’t seem to stop them from filing frivolous lawsuits.

The enemy of your enemy is your friend. Support freedom by shopping at AutoZone, or if you don’t have an AutoZone, buy anything Mopar that happens to fit your car, such as spark plugs and oil filters.

MyDoom/Novarg Gloom

Just in case anybody is curious, my employer’s virus scanners filtered roughly 3,000 copies of Novarg (a.k.a. My Doom) during working hours yesteray. If that’s not a record for us, it approaches it. I know we weren’t the only one.I’ve heard Novarg/MyDoom/My Doom called the fastest spreading virus yet. I don’t have statistics on prior viruses with me, but suffice it to say, its impact certainly felt similar to the big names from the past.

Although SCO would like people to believe it was written by a Linux zealot, I’m more inclined to believe it was created by organized crime. Maybe the creators hate SCO, or maybe the anti-SCO DDoS was just an added touch to throw investigators off.

LoveLetter was the first virus outbreak to really have much impact on my professional career, and I noticed something about it. Prior to LoveLetter, I never, ever got spam at work. Not once. After LoveLetter, I started getting lots of it. I don’t believe LoveLetter’s intent was to gather e-mail addresses for spammers, but I do believe that more than one spammer, probably independently, noticed that viruses were a very efficient way to gather a large number of e-mail addresses.

I got spam before LoveLetter, and I saw viruses before LoveLetter. But I started seeing a lot more of both very soon after LoveLetter.

I don’t buy any giant conspiracy to sell anti-virus software, nor do I buy any giant conspiracy against SCO. I do believe in bored people with nothing better to do than to write viruses, and I also believe in people who can profit off their side effects.

I’ve said it once and I’ll say it again. If you run Windows, you must run anti-virus software. You can download Grisoft AVG anti-virus software for free. Don’t open unexpected e-mail attachments, even from people you know. Even if it looks safe. Don’t send unexpected e-mail attachments either–you don’t want anyone to get the idea that’s normal. Quite frankly, in this day and age, there’s no reason to open any piece of e-mail that looks suspicious for any reason. I told someone yesterday that this is war. And I think that’s pretty accurate.

If you’re an intrepid pioneer, there’s something else you can do too, in order to be part of the solution. If you join the Linux revolution, you can pretty much consider that computer immune. Macintoshes are slightly less immune, but certainly much less vulnerable than Windows. Amiga… Well, I haven’t seen the words “Amiga” and “virus” in the same sentence since 1991 or 1992. But one thing is certain: a less homogenous field is less susceptible to things like this.

 

Time for a core dump

I’ve been keeping a low profile lately. That’s for a lot of reasons. I’ve been doing mostly routine sysadmin work lately, which is mind-numbingly boring to write about, and possibly just a little bit less mind-numbingly boring to read about. While a numb mind might not necessarily be a bad thing, there are other reasons not to write about it.
During my college career, I felt like I had less of a private life than most of my classmates because of my weekly newspaper column. I wrote some pretty intensely personal stuff in there, and frankly, it seemed like a lot of the people I hung out with learned more about me from those columns than they did from hanging out with me. Plus, with my picture being attached, I’d get recognized when I went places. I remember many a Friday night, going to Rally’s for a hamburger and having people roll down their windows at stoplights and talk to me. That was pretty cool. But it also made me self-conscious. College towns have some seedy places, you know, and I worried sometimes about whether I’d be seen in the vicinity of some of those places and what people might think.

Looking back now, I should have wondered what they would be doing in the vicinity of those places and why it was OK for them to be nearby and not me. But that’s the difference between how I think now and how I thought when I was 20.

Plus, I know now a lot fewer people read that newspaper than its circulation and advertising departments wanted anyone to think. So I could have had a lot more fun in college and no one would have known.

I’m kidding, of course. And I’m going off on tangent after tangent here.

In the fall of 1999, I willingly gave up having a private life. The upside to that is that writing about things helps me to understand them a lot better. And sometimes I get stunningly brilliant advice. The downside? Well, not everyone knows how to handle being involved in a relationship with a writer. Things are going to come up in writing that you wish wouldn’t have. I know now that’s something you have to talk about, fairly early. Writing about past girlfriends didn’t in and of itself cost me those relationships but I can think of one case where it certainly didn’t help anything. The advice I got might have been able to save that relationship; now it’s going to improve some as-yet-to-be-determined relationship.

There’s another downside too. When you meet a girl and then she punches your name into a search engine, if you’re a guy like me who has four years’ worth of introspective revelations out on the Web, it kind of puts you at a disadvantage in the relationship. She knows a whole lot more about you than you do about her. It kind of throws off the getting-to-know-you process. I’d really rather not say how many times that’s happened in the past year. Maybe those relationships/prospective relationships were doomed anyway. I don’t have any way of knowing. One of them really hurt a lot and I really don’t want to go through it again.

So I’ve been trying to figure out for the past few weeks what to do about all this. Closing up shop isn’t an option. Writing strictly about the newest Linux trick I’ve discovered and nothing else isn’t an option. Writing blather about the same things everyone else is blathering about is a waste of time and worthless. Yes, I’ve been saying since March that much, if not all, of the SCO Unix code duplicated in Linux is probably BSD code that both of them ripped off at different points in time. And now it’s pretty much been proven that I was right. So what? How many hundreds of other people speculated the same thing? How could some of us be more right than others?

I’m going to write what I want, but I’m having a hard time deciding what I want to write. I know I have to learn how to hold something back. Dave Farquhar needs a private life again.

For a while, this may just turn into a log of Wikipedia entries I made that day. Yes, I’m back over there again, toiling in obscurity this time. For a while I was specializing in entries about 1980s home computing. For some reason when I get to thinking about that stuff I remember a lot, and I still have a pile of old books and magazines so I can check my facts. Plus a lot of those old texts are showing up online now. So now the Wikipedia has entries on things like the Coleco Adam and the Texas Instruments TI-99/4A. Hey, I find it interesting to go back and look at why these products were failures, OK? TI should have owned the market. It didn’t. Coleco should have owned the market, and they didn’t. Atari really should have owned the market and they crashed almost as hard as Worldcom. So how did a Canadian typewriter company end up owning the home computer market? And why is it that probably four people reading this know who on earth I’m talking about now, in 2003? Call me weird, but I think that’s interesting.

And baseball, well, Darrell Porter and Dick Howser didn’t have entries. They were good men who died way too young, long before they’d given everything they had to offer to this world. Roger Maris didn’t have an entry. There was more to Roger Maris than his 61 home runs.

The entries are chronicled here, if you’re interested in what I’ve been writing lately while I’ve been ignoring this place.

DietLinux — a Linux that boots in under 10 seconds

The tinkerer in me just couldn’t stay away. I saw a reference on Linux Weekly News to DietLinux and had to look at it.
DietLinux is an example of a Linux distribution that can’t properly be called GNU/Linux, because the majority of its userspace didn’t come from the GNU project. GNU’s libc–the main API for Unixish systems, and I’ll call Linux a Unix just to hack off SCO–is replaced with an alternative, trimmed-down libc called dietlibc. It’s not feature-complete but it’s tiny. Those of you who programmed casually in the 1980s and 1990s probably remember a day when you could write a fairly sophisticated program in a few kilobytes. Under modern operating systems, a simple program that simply emits “Hello, world!” can take up 32K or more. Using dietlibc instead of GNU’s libc shrinks that program back down to a couple of kilobytes.

The majority of DietLinux’s userspace comes from Felix von Leitner, the author of dietlibc. Von Leitner reimplemented init–the program that bootstraps a Unix system once the kernel is loaded–and getty, which is the program that handles text-based logins. These unglamorous programs can eat up a fair chunk of memory, and since Unix systems typically go for long periods of time without being rebooted, it’s a bit of a waste unless you need certain features provided by the more traditional init and getty programs. He also wrote replacements for several standard utilities.

Obviously, not every program in the world designed for glibc will compile and run under dietlibc, so DietLinux won’t ever be a complete general-purpose distribution. But for network infrastructure glue-type servers providing services like firewalling, DNS and DHCP (all of which already function), it would be perfect.

I don’t know what the future plans for DietLinux are. The asmutils provide an impressive number of userspace and server utilities, written in assembly language with very low overhead, and would appear to be a nice complement to DietLinux’s infrastructure. Their use would limit DietLinux to x86, however. And the text editor e3 is tiny, full-featured, and emulates keybindings for vi, emacs, WordStar, and Pico, so it’s friendly to pretty much any command-line jockey regardless of heritage and takes little space.

It’s also not a newbie distribution. Installation requires a fair bit of skill and pretty much requires an existing Linux system to bootstrap it.

But it’s definitely something I want to keep an eye on. I’m highly tempted to put it on one of my 486s. I just wish I had more time to mess around with it.

SCO stoops to RIAA tactics

SCO is now threatening legal action against corporations that use Linux, since it supposedly infringes on their intellectual property but they haven’t revealed the infringing code yet. I guess they need to start by suing themselves.

What large market for x86 Unix?

What large market for x86 Unix?

In a bizarre turn of events, SCO has sued IBM for not less than $1 billion, claiming IBM willfully destroyed SCO’s business by handing its intellectual property over to the Linux movement.

Read more