Linux for the Long Haul
Now, pay close attention, not only has Linux dramatically increased in usability and features during the last five years, but on the same hardware, it also has increased in speed. In other words, an upgrade really feels like an upgrade! In retrospect, try this with Windows. Our current base of computer hardware, which was modern in 2002, would not even run Vista, let alone run it faster than XP. However, our latest Linux upgrade is noticeably faster than the Linux we ran a few years back. In fact, our 2002 computers that average 256MB of RAM feel faster and more responsive than today's typical computers running Windows XP or Vista, and we have the latest in open-source software installed.
So, let's finish our TCO analysis. Not only did switching to Linux save us money in the initial switch, but also, every time I perform a system upgrade by typing emerge -vauKD world (it's that easy), we're saving money. We don't have to pay a company for every upgrade of every application for every seat. More important, I'm not forced to throw away good hardware and purchase new equipment in order to implement my software upgrade cycle. If we were running a “Microsoft shop”, I'd have to retire almost every computer in our school and purchase all new equipment in order to upgrade to Vista. Now that's an expensive upgrade.
Although money is a big deal to a private school, there obviously is more to consider when switching an organization to a different operating system. A major consideration of mine was the “free as in freedom” roots of the Free Software movement. As the school's system administrator and the guy who has to make it all work, I have enjoyed this freedom during the past five years. I've taken advantage of being able to access and modify the source code. Many of my administrative duties have been simplified by customizing Linux for our school setting. Whether it is writing my own bootscripts or even creating my own software, I've been able to tailor our computer network in ways that I just could not easily or even legally do with proprietary software.
There also is a freedom from worry. I don't need to concern myself with Windows Genuine Advantage, product activation and per-seat licensing. With Linux, you don't need to worry about how many processors your servers use or how many cores your next desktop computers will have. You don't need to consider special license restrictions for virtualization. You don't have to endure audits from the Business Software Alliance. As our band teacher loves to say, “No worries!”
Freedom extends outside the four walls of our school as well. For example, although OpenOffice.org can read and write Microsoft Word documents, the real advantage is that I can provide a copy of this software freely to any teacher or student, especially if that person can't afford to buy Microsoft Office. Anything we do in the classroom, students can do at home using their own copy of the free software we use. This gives us a tremendous advantage as an educational institution.
There's something else I consider when thinking about freedom—the freedom to access my data. I personally don't mind the existence of proprietary software in the world, but I strongly oppose proprietary standards and protocols that lock users from their own data. I want our documents, whether they be school records or a student's homework, to be accessible via an open and well-documented format. A recent experience in trying to access my own data stuck in a locked, proprietary format has made me appreciate all the more the true strength of open software and standards—freedom!
Five years is a long time to consider the wisdom of a decision. As the school's system administrator, I shoulder the burden of maintaining our computers, our network and our servers. What has it been like administering Linux since the switch? I'll be honest. There have been times when I've spent days trying to get something working right in Linux. However, I still use Windows enough to know that administering a Windows network isn't all cake and ice cream either. My experience with Linux is that once a setup is working, it stays working. Sometimes the initial setup takes longer, but once everything is configured right, it just works and works well. With distributions like Ubuntu, even that initial setup is becoming easier.
Now, let's talk about the users of our Linux desktops. I'm a teacher as well, so I have to use Linux in the same way our teachers and students use it. That said, I'm a geek, and sometimes we geeks need to see the world through the eyes of a typical user. Personally, I love using Linux! I'm using it right now to type this article, and never do I think, “Oh, how I miss Microsoft Word.” Never!
In fact, it's when I'm in a Windows environment that I find myself missing this feature or that feature. This is why the argument that says Linux is playing catchup with Windows is so flawed. Sure, Linux uses a mouse and icons and menus exactly like Windows does, but what else would we use? Is a hybrid car not innovative just because it uses a steering wheel like every other car? I say, “hogwash!” Many features found in open-source software are innovative, many of which only recently, if at all, have found their way into Windows. For example, I love my multiple desktops, and my productivity suffers without them. I love tabbed browsing and have used it for years. I love KDE, but even more important, I love how the desktop environment is not welded to the operating system. Users can chose KDE or GNOME or IceWM or have no GUI at all (great for servers and robots). I love, love, love the power of the Bourne-Again shell (Bash). I could spend the entire article sharing wonderful features that are unique to Linux. However, let's get back on track.
My experience has been that average adult computer users don't understand or even care about the power of multiple desktops, scriptable shells and so forth. For them, using a computer is a means to an end. They have a job to do, and the less the computer gets in the way, the better. The challenge comes when adults are faced with the unfamiliar. I stress adults here, because working with children and teenagers has been a totally different experience. Second-graders come into the lab and, with ease, use Linux to perform any task they would in Windows or Mac OS X. Teenagers line up and ask me to burn them Linux CDs for their home computers. However, most of you reading this probably deal with adults, and we adults are often old dogs.
They say that you can't teach an old dog new tricks. I don't agree with that, but sometimes old dogs do growl and fuss and even bite when forced to learn those new tricks. This can be especially true if the users aren't very computer-savvy to begin with. This means they are relying on icons, menus and options being at specific places and doing specific things. For this reason, many open-source programs try to replicate the feel of software with which the majority of adults are familiar. This is understandable, and it makes the transition easier than you might think. Although I had a few instances of resistance when we first switched to open-source software, most of the staff adapted quite well. Training is needed, but that mechanism already should be in place, regardless of what software an organization uses. Software and user interfaces change over time, and users find themselves adapting, regardless of whether the switch is to Linux or the latest version of Windows. Although adults often resist change, they can change. Actually, after a little time, they become comfortable with the change and may even be glad for the change. I know many average computer users who now sing the praises of OpenOffice.org Writer, for example.
It has probably become apparent that during these last five years, I've become an advocate for Linux and open-source software in general. However, it would be dishonest of me to sing praises only without revealing the pitfalls I've encountered over the years.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide