Last night’s mutual cyber-binge after only two days away from the keyboard was the kicker: If we’re going anywhere for two weeks, we’ll want to bring a computer along.

And so tonight I finally ordered a dual-boot PowerBook from TerraSoft. We’re splitting the cost as a combined wedding and belated/early birthday present to each other.

Sometime this weekend, we’ll have a new computer in the house!

Sometime early last year I decided I’d like to get a PowerBook. Ideally, one dual-booting Mac OS and Linux. I spent several months saying “I don’t really need a laptop,” but I really started to like the idea after a while, and Katie started to like the idea too, and this January I went so far as to contact TerraSoft Solutions about pricing. TerraSoft maintains their own PPC Linux distribution, Yellow Dog Linux, and their stock in trade is selling Macs preconfigured to dual-boot Mac OS and Linux.

I decided not to buy one then for two reasons: We had the wedding coming up, and I figured Apple was likely to upgrade the line by summer.

Well, the wedding is next weekend, and Apple has just announced upgrades to the PowerBook line.

It may be time to start looking at PowerBooks again.

Out of curiosity, I did a Google search for the phrase “blood of the innocent” to see where APK would come up. Given that my poetry pages seem to be very popular with search engines (and that the phrase is at the top of the frikkin’ page!), I expected it to be pretty high up in the listings. 72 pages of results later, I have a thorough education in just how popular this phrase is, and with whom. Even adding in “nothing” to the search, I still got 72 pages of religious diatribes and political blogs. Sheesh. If this is what’s popular, I’m glad I’m not it.

I found this article on OSNews: A History of Apple’s Operating Systems. The article starts with the Apple II and works its way up to Mac OS X, touching all the various branches in between – as well as Apple OSes that never quite made it out the door, and other OSes – like NeXtStep (whatever the capitalization is) – that influenced it on its way. Hey, where else are you going to find screenshots of the Apple I and Macintosh System 1?

It’s a fascinating read. I suspect the site will be due for another Slashdotting soon…

OK, I’m not one of those purists who thinks all computers should be encased in beige boxes. That said, 4 of the 5 computers in our apartment are fairly plain – but two of those are because the case predates any sense of design, one was an ultra-cheap computer, and one was an ultra-cheap case.

Last week, while looking for that ultra-cheap case so I could build Red Shirt, I looked at the more expensive cases, thinking I might replace the case on my main computer, and then reuse the old one for the new machine. And while there were several really nice cases, none of them really struck me – unless you count the ones that exhibited the two trendiest offenses in case design:

  1. Hiding the drive bays. Someone got the idea somewhere that drive bays, especially on a case with room for expansion, are ugly. And I can certainly see the point. But people who design cases often forget a key factor about those drive bays: people use them. That means either you’ve got to open the entire front of the case every time you pop a CD in the tray, or you end up leaving it open. Now it’s not so bad if it’s a sliding door, but if it’s hinged, then you have to worry about this huge plastic door hanging sideways in front of the computer. Not only does it get in the way every time you have to reach down with a CD, it’s uglier than just showing the drive bays would have been!
  2. Shoving the front USB and Firewire ports all the way to the bottom of the case. The idea of having these ports on the front is to make them convenient. And while putting them at the bottom may work for people who put their computers on top of their desks, a lot of people put them underneath to save space (whether for writing or for a giant monitor). That USB mini-drive isn’t so convenient when you have to get out of your chair and kneel down on the floor to plug it in. And I’ve seen cases where the ports are less than half an inch from the bottom – not so bad if you’ve got a wood floor, but if you’ve got a carpet, now you need to worry about the carpet getting caught in the ports. I’m sorry, but this is only marginally better than leaving the ports on the back.

In the end, I decided I didn’t want to assemble two computers, just one, so I bought the cheapest, smallest case I could find. (As it happens, it manages to make the USB situation worse by putting the ports on the side of the front panel – but I wasn’t expecting to use much in the way of USB devices on this box anyway, and it turns out the only ports this motherboard can handle are the built-in ones.)

SiteFinder was a “service” Verisign offered for a few weeks in 2003 in which DNS lookups to any non-existant domain in .com or .net responded with a pointer to an ad page. Techies revolted because it broke a lot of stuff. Verisign attempted to paint opponents of Site Finder as a minority of anti-innovation “technology purists” who still resent the presence of commerce on the Internet. A shorter version of my response ran on CNet’s News.com as a letter to the editor.

Mark McLaughlin’s opinion piece, “Innovation and the Internet,” simply proves that Verisign has completely missed the point. The reason so many people objected to SiteFinder is not the service it provided, nor a rejection of innovation, but that it caused a significant number of non-web applications to fail. Verisign, a company that should know better, had forgotten that the Internet is more than just the web.

There are many applications besides the web which make use of the DNS system, and many of them take actions that depend on whether a domain exists or not. Some of the more obvious cases occur in spam blocking. For instance, mail servers often check to see whether a the sender’s domain exists before accepting email. The DNS wildcard that powered SiteFinder broke this: suddenly, all domains would appear to be valid. A spammer could claim to be sadkjfhdsaf@asdfsadfjsdf.com, and the message would be accepted.

Another issue is DNS-propagated blacklists: at least one (ORBS, if I remember correctly) had folded and allowed its domain name to expire, but many software packages still included it in their default configurations. Since people often install software without updating, they were seeing slightly slower results at first, but the SiteFinder wildcard suddenly caused all queries to return positive, and a number of servers began rejecting all mail. (Something similar happened with Osirusoft a month earlier, but that was intentional on the part of Osirusoft’s former administrator.)

Other people are concerned about the fact that misdirected email, instead of being routed to secondary servers (in the case of a bad configuration) or bounced back by the originating ISP, is being routed through Verisign. Here, it’s a matter of trust: if you trust Verisign to do the right thing and bounce it without looking at it, then you probably have no objection. But many people saw the arbitrary creation of the wildcard in the first place as a breach of trust, casting doubt on their trustworthiness in other areas.

There are ways to resolve the issue of mistyped websites that do not break other applications. Microsoft embedded this functionality in Internet Explorer some time ago. I believe AOL has done the same in their software. While there were probably some objections, in neither case did it cause other applications to stop working.

It’s not about being technology “purists,” stifling innovation, or keeping commercialism off the Internet. It’s about recognizing the fact that the Internet is a collaborative effort, not the private domain of any one company. If Verisign had submitted its idea for review, and given others a chance to point out its flaws and to make adjustments to their own software, this could all have been avoided. As it is, it is clear that Verisign neither thought through all the consequences nor is willing to recognize that there even are consequences. And that – not a desire to “hold the Internet back” – is the reason for the backlash.

On Friday I reinstalled Red Hat 9 on my computer. On Saturday I figured out why I couldn’t build Dillo on the virtual Conectiva system (the only reason I tried to install the real thing). On Monday I made a remark on the Dillo mailing list that, after trashing the system trying to install Conectiva, “unless/until I can set up a spare system solely for trying things out, anything else… will run under User-Mode Linux.”

And that got me thinking.

A spare system wouldn’t need to be elaborate. I wouldn’t be playing games on it. I wouldn’t be doing graphics work on it. I wouldn’t even be doing web development, word processing, or checking my email. Most of the time it wouldn’t even be running – just when I wanted to try something new, or when a new release of Dillo came out and needed RPMs. And since I have a spare KVM switch, I’d only need to find space for the case, and wouldn’t need to worry about a monitor.

I’ve mentioned before that I’ve upgraded my computer piece-by-piece since 1994. Well, when you do that, you end up with a lot of spare parts left over. Sure, they’re older, slower, smaller, etc. than what you’ve got now, but if they worked when you took them out, they probably still work now. I’ve been meaning to go through all the boxes, cards, drives etc. and get rid of things I don’t need anymore, but I’d never gotten around to it. Well, on Monday I finally had motivation.

I went through looking for parts I could use to put together a spare, expendable system – one where it wouldn’t matter if the entire hard disk got wiped. I found three hard drives (two of them too small to be useful), several sticks of RAM, network and video cards, and a motherboard and a CPU that wouldn’t fit together. That left: a case, a CD-ROM, and either a CPU to go with the motherboard, or a motherboard to go with the CPU.

[A picture of Red Shirt] It turned out my boss was getting ready to throw out some old equipment, including a huge mega-tower with a 450 MHz K6-2. The motherboard I have used to hold a K6-2. (Where it is now, I have no idea – I don’t think it’s the one I fried, especially since the motherboard seems to work.) So now I had a processor. My parents had recently replaced an extremely flaky computer, so I got a CD-ROM from that. Then I went to Fry’s and picked up a $30 case and $13 floppy drive.

That’s right: I have just built a $43 computer.

Somewhere in this whole process, Katie came up with the name “Red Shirt Linux.” And while it’s mostly going to be SuSE, Conectiva, and Mandrake, the name fits.

Preliminary tryouts look promising: All the hardware works, I was able to see old data on the hard disk before I repartitioned it, I could boot tomsrtbt off of a floppy and mess around under that. I tried Conectiva first, and it failed, but I think I’ve got a bad install CD. (The UML system I built from it has network problems, and the copy I installed on Ghostwheel is what trashed my partition table, so it doesn’t surprise me that it had problems here.) I’ll run a thorough memory test overnight just to make sure, but it looks like I’ve got a PC I can mess around with without risking any data!

ยปAll pages site-wide with this tag