Linux for the Long Haul
As the system administrator, a real thorn in my side has been hardware compatibility. I've had little problem installing Linux on a variety of computers, but peripherals such as printers, scanners and Webcams can be a serious pain in the neck. Too many hours have been wasted trying to get unsupported hardware to work. However, the lesson here is to buy only from vendors who support Linux with drivers and/or detailed specifications. As more organizations adopt Linux, vendors either will have to support Linux or lose their business to those who do.
Something I find as irritating as the giant Maine mosquito is the use of proprietary protocols, standards and codecs that exclude Linux users from certain parts of the Internet. The Internet was built on open protocols, and it probably wouldn't exist in any meaningful way today if it had been locked up with proprietary standards owned by individual companies. Yet, there still are Web sites and services using closed protocols. It is highly frustrating when we cannot access on-line content because we don't have a proprietary plugin, such as ActiveX or Adobe Shockwave. For example, our school wants to use an on-line education tool to enhance our curriculum, but the company that offers this tool relies on Shockwave. So we are “locked out” because of this one missing piece.
Finally, a lack of key commercial software is a real issue. Some good people in the Free Software community don't want commercial software on Linux, but I have to be more pragmatic. When there is a fine open-source alternative to a key commercial product (such as with OpenOffice.org and Microsoft Office), I am happy to use it. Unfortunately, not all proprietary software has a good open-source equivalent. Until there is, the solution isn't eloquent. GHCA has a single Windows machine in our office for the sole purpose of running Intuit's QuickBooks. I suppose we could use Wine, but that brings its own headaches.
Despite these pitfalls, I have no regrets. Let's look at those big questions again. Is Linux ready for the desktop? Yes. Our teachers and students have been using Linux on the desktop successfully for the last five years. What about TCO? Every organization is unique, but Linux has saved us many thousands of dollars, and we're a small school! Have users adjusted? Absolutely. Was it worth the switch? There is no doubt in my mind. That's not to say there haven't been bumps in the road, but to quote Robert Frost, “I took the [road] less traveled by, and that has made all the difference.” I look forward to where this road we call Linux will lead us in the future.
Linux from Kindergarten to High School: www.linuxjournal.com/article/6349
Making the Switch to Open Source Software: www.thejournal.com/articles/16448
Harnessing the Power of Open Source Software: video.google.com/videoplay?docid=7860580137648446279
GHCA's Computer Lab: www.ghca.com/computers
Michael Surran is the head of GHCA's Computer Science department. He is responsible for building and maintaining GHCA's Linux network, and he teaches Computer Programming, Computer Technology, Research and Presentation, and the CS electives. Surran promotes open source in education both locally and regionally through newscasts and seminars.
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!
- Google's SwiftShader Released
- Interview with Patrick Volkerding
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
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