Linux for the Long Haul
Five years ago, I made one of the greatest life-changing decisions in my career—I switched my organization to the GNU/Linux operating system and supporting applications. It's not uncommon to read about businesses, schools and other organizations making this switch; however, what happens afterward? How do users adjust, and what about this total cost of ownership (TCO) we always hear of? Is Linux really ready for the desktop? Was it worth it to make the switch?
In 2002, Greater Houlton Christian Academy (GHCH) adopted Linux; you can read the details as to why and how in the February 2003 issue of Linux Journal. It's not an exaggeration when I describe this as a life-changing decision, not just for me, but for the school as well. I used to be a die-hard, Microsoft fanboy; now I use open-source software almost exclusively. Our school, which once had a mish-mash of dilapidated, old, donated computers that barely worked, now is recognized as being a leader in our region because of our computer technology—all of this from that fateful decision back in 2002.
Five years after the article was published, I find myself reflective, pondering where we've been and wondering what the future holds. Did I make the right decision? Would I do it again? There's much to consider in order to answer all these questions. Because that decision initially was based on financial need, let's first look at TCO.
Sometime after we adopted Linux, Redmond released a study claiming that the TCO for Linux actually was higher than for Microsoft Windows—even though Linux can be obtained for free. Microsoft has been pushing this idea ever since with its “Get the Facts” campaign. Had such a study existed in 2002, I might have wavered on making the switch. After all, price was the driving factor for us to use Linux in the first place. In some ways, that initial decision was a desperate decision. Since then, I've had time to consider TCO. So, was Redmond right?
The initial switch saved us money, because it allowed us to put what funding we had directly into hardware while avoiding the Microsoft tax (pre-installed Windows on computers). In fact, we could not have upgraded our computers if we had to purchase proprietary software as well. That's not to say there aren't some hidden costs in having the IT staff install software on bare-bones hardware, but for us, the savings far outweighed any extra labor costs. What is more important, however, is how using Linux and open-source applications continues to save us money today.
But, before discussing this continued savings, I need to stress that software evolves. Applications improve, bugs and security holes are patched (hopefully), and new technologies emerge. With proprietary software, it can be years between major releases, and upgrading to that new release costs money. With open source, applications are improved all the time. After making the initial switch to Linux, one needs to consider how to keep up with the latest patches, upgrades and releases.
Being a tweaker who loves to squeeze every bit of efficiency from my computers, I was attracted to a distribution called Gentoo. Not only did it allow me to optimize Linux and thousands of applications for our computers, but also I found the package management system far superior to other distributions I had played with. It also forced me to learn the under-the-hood details about the Linux kernel, the GNU programs and many other OS management techniques that have helped me as a Linux administrator.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- New Products
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Validate an E-Mail Address with PHP, the Right Way
- Build a Skype Server for Your Home Phone System
- Tech Tip: Really Simple HTTP Server with Python
- Why Python?
- A Topic for Discussion - Open Source Feature-Richness?
- Not free anymore
3 hours 21 min ago
7 hours 8 min ago
- Reply to comment | Linux Journal
7 hours 16 min ago
- Understanding the Linux Kernel
9 hours 30 min ago
12 hours 40 sec ago
- Kernel Problem
22 hours 3 min ago
- BASH script to log IPs on public web server
1 day 2 hours ago
1 day 6 hours ago
- Reply to comment | Linux Journal
1 day 6 hours ago
- All the articles you talked
1 day 9 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?