June 10, 2002. It’s been a wild ride since the dot-com boom and bust. Back then, I was in the midst of my transition from Windows to Linux on the desktop. For years, I had used Linux server-side; hell, my current employer even ran everything under Apache and BIND. But when it came to my own work station, I stuck with good ol’ Microsoft. I mean, who would want to run a web server OS as their primary desktop?

But times were changing. The dot-com bubble had burst, but Linux was making serious inroads on the desktop scene. VMware’s virtualization was gaining traction, and even Sun Microsystems seemed to have a soft spot for it. Plus, with Sendmail and Apache already running my servers, I felt like a hypocrite keeping my primary desktop locked into Windows.

I decided to give the Linux desktop a chance. My workstation at home had always been an old 1998 Dell laptop with an underpowered Pentium III. It was a clunker, but what could you do? I figured, this was as good a time as any to try out Red Hat 7.2 on it.

Installation went fairly smoothly. The machine was slow—really slow—but it got the job done. Firefox and Thunderbird were new kids on the block back then, and they worked surprisingly well. The only thing that felt awkward was typing my username and password for every application launch.

As the days turned into weeks, I started to integrate Linux more fully. I switched over my home directory from Windows NTFS to ext3, which required me to get a USB hard drive to move my files around. And man, did it feel good! No more registry issues. No more “Windows Update” pop-ups. Just a clean, uncluttered experience.

But then came the real test: presenting at work with my new Linux desktop. I had planned ahead and set up dual-boot so that if all else failed, I could just reboot into Windows. But it didn’t fail—I got to give an impromptu demo of the Linux desktop in action!

The response was mixed. Some colleagues were genuinely impressed by how smoothly everything worked for me. Others, well, let’s just say they weren’t quite as sold on the idea. One guy even said, “Linux? Really? You’ve got to be kidding me.” The skepticism didn’t hurt my feelings; I mean, who could blame them?

As the months passed, I found myself more and more attached to Linux on the desktop. But I was still skeptical about making it a permanent change. After all, if I had a major bug or issue, would the support be there? Could I really justify spending time troubleshooting something that should just “work”?

It wasn’t until I started running into real issues—that’s when my faith solidified. A critical file got corrupted during an update; suddenly, I was back to square one with Windows. Or maybe it was a nagging issue with the sound card driver—whichever it was, I spent more time fixing these things than I ever did in Windows.

Those experiences forced me to re-evaluate my position. It wasn’t just about performance or security anymore; it was about reliability and consistency. Linux had proven itself as much more reliable than its Windows counterpart, even if the learning curve was steeper at first.

So here’s where we stand now: I’ve made the switch from dual-booting to running a full desktop environment on Red Hat 7.2. It hasn’t been without its bumps and bruises, but overall, it feels like the right move. And who knows? Maybe one day, everyone will be using Linux for their primary desktop. Until then, we’ll just have to stick with what works.

In conclusion, June 10, 2002, is a date I will always remember as the beginning of my journey from skeptical observer to loyal user of Linux on the desktop. A long road still lies ahead, but it’s one I’m willing to travel.