Here’s a major surprise – I love computers. I find them fascinating and am always tempted to learn what I can and expand the envelope, if possible.
It’s possible this goes back to my first experience with computers, in high school in 1967. Somehow, we had two computers at school. Actually, we had one – an IBM 360 (I think) which was booted by flipping switches in the proper order and ‘fed’ with punch cards or paper tape.
What seemed like our second computer was a Model 34 Teletype, somehow connected by phone line to a computer at a local college. I played Wumpus, Golf and Horse Racing. Everything came out as printed text on that very slow teletypewriter.
In 1978 I got a Radio Shack TRS-80. Later, I got a Commodore 64 and then a series of PCs, culminating in the homebuilt Athlon XP 1600+ machine I’m composing this on.
I like being on the ‘bleeding’ edge, so I’ve kept an old computer handy and loaded Linux as the operating system. Depending on whom you believe, Linux will soon roust Windows as the operating system of choice, sending Bill Gates and the Evil Empire to the poorhouse… or it is an ill conceived idea promulgated by geeks who can’t really see who the final user will be (I saw Walter Mossberg say this yesterday on CNBC) and don’t care to design in ease of use.
I want the first choice to be true but I’m scared it’s the second. That’s not a totally fatal situation, but it certainly means Linux isn’t quite ready for prime time.
My latest install attempts (and they’re ongoing as I type this) will bear this out.
With a new, five year old, laptop (Dell D300XT), an extra hard drive for it and a great deal of curiosity, I set out to make the laptop run Linux. Since this is an extra hard drive, I should be able to swap drives and go back and forth from Windows to Linux without one affecting the other.
Since Red Hat has decided to get out of the consumer desktop end of Linux, I decided to try a new distribution. As I understand it, all Linux versions share certain core components but differ in the other programs that come in the distribution. Suse seemed like a good idea. I had read about it. It has its fans… why not?
The recommended way to install Suse seems to be by installing a small subset of Linux (in my case burning a CD-R) and then using FTP (file transfer protocol) to pluck everything else directly off a server and right onto my hard drive.
If there are detailed… or even sparse… instructions for doing this, I couldn’t find them! The Suse installer started asking questions I had no answer for within the first few seconds of the install. There was no help button to press; nowhere to go. Using Google I was able to get some answers, but every time I’d solve one problem, another would spring up in its place.
Next I went to Debian; another respected distribution. They had a few network install suggestions, but all led to boot disks that were wrong or unavailable.
Finally, I went to Red Hat’s ‘cousin’ Fedora. There’s some sort of incestuous relationship here. I’m not sure what it is, but I think in some way Fedora is part of Red Hat.
I began the installation from 3 CD’s I had downloaded overnight a few days ago. A Linux distribution, even from a cable modem, requires hours and hours of downloading and then burning of bootable ISO CD’s.
Fedora seemed to understand what my system was all about (though it looked like the installation was taking place at 800×600 resolution on my 1024×768 laptop screen). It asked what kind of system I wanted loaded and when I chose ‘desktop’, the loading began.
I’m not sure how long it was… probably around an hour… when Fedora just stopped. A screen, telling me there were four minutes left, stared at me. No motion from the hard drive. No motion from the CD. Nada.
After a while I got tired of waiting and rebooted the system. What I had was nothing. The system wouldn’t boot. Linux wasn’t installed. I have just started the process again.
Maybe I didn’t have enough patience. Maybe the computer was doing some sort of Klingon Mind Meld and didn’t want to be disturbed? How should I know?
Even if this installation is fully successful, my job won’t be done. I’ll need to figure out how to enable my wireless network card, a printer hooked to my router and configure all sorts of computing minutiae, like email parameters.
Right now, it looks like the install will continue long after I’ve gone to bed. Maybe this will give the machine a chance to decide it wants to work this time.