Do we really have options?
I was going to explore the new trend of green IT or perhaps talk about the morality of threatening or blackmailing (your choice) software companies into fixing security holes, but an article in Computerworld about a hospital selecting a Linux-based email system with compatible features to Microsoft’s Exchange brought back to my mind a discussion I have had with others about the real choices there are in today's software wilderness.
What started the discussion was my thought that one does not have to look too hard to find a pundit saying you have options other than Vista. As a long-time Linux user and evangelist, I knew this to be truth, but with an asterisk. As a technician, I am technology agnostic. I want the best solution for the job, but, I also have to be conscious of cost, both personally and professionally. Now do not get me wrong, I am not cheap, but neither do I see value in paying more for less. So when my laptop died a couple of months ago, I sat down and did some research.
I actually had tinkered with the idea of going to a Mac. But I rapidly changed my mind. Putting the cost and requirements of the operating system aside for a moment and just looking at the hardware, it becomes clear that hardware is cheap, unless you are buying it from Apple. I wanted a dual-core machine, and about 4 GB of RAM. Disk is subject to change. I also wanted a light weight machine since it spends almost as much time on my back as it does on my desk. Today a 13" MacBook is available for $1,299 or $1,499 depending on whether you want a 160 GB disk or a 250 GB disk, each with 2 GB of RAM and a 2.4 Core2 Duo CPU. Two years ago, I was buying quad core (Intel) servers with 4 GB of RAM and 250 GB disk for $1000. The laptop I ended up with is a 15" screen on a 2.4 Core2 Duo with 3 GB of RAM and 250 GB of disk and cost me $700. I bought my wife a similar machine a month later with a 17" screen and a full keyboard for $100 less! So why would I buy a Mac? I could buy two laptops for the price of a single Mac with similar configurations.
And so, before I even have a discussion of operating systems, I have already ruled out an operating system simply because of hardware costs. Yes, I can get expensive PC compatible systems, but face facts. If an apples to apples comparison of basic features results in a higher cost of one platform over another, why would you?
So now I have my hardware. When I bought my machine, a Gateway in the case of full disclosure, it came with Vista Home on it and after making sure the hardware all worked, I set about reformatting it and loading Linux. Now before we get into the issues of the load, remember that Linux, despite the marketing and other issues, is nothing more than the kernel. The thing that makes everything else go. Sure, it is important, but, in the grand scheme of the debates over distributions, the kernel is always the same (unless we are talking BSD...different kernel). So the next choice is distribution. I am a fan of the Red Hat tree and run Fedora. I run Fedora mostly because I do a lot with Oracle and it just makes it easier to do things, so off I went to install my distribution, and very shortly ran into problems.
It would seem that the wireless network card was not detected. OK, not a big deal. A couple of Google searches and I would be able to fix that I figured. After all, my last machine suffered from the Intel 2200 patch issues and I managed to get it working, until a new kernel released and I had to do it again...and again... This time, I was stymied. The NIC did not seem to have a kernel patch or driver. At least not one I could easily find. And now, we have eliminated Linux as an operating system. So I installed Vista Ultimate.
I am also a consultant and as such, I am currently reviewing the environment of a customer who is dissatisfied with the current status quo and wants to make some changes and have flexible options without it costing an arm and a leg. Further, he needs to be able to connect multiple operating systems together to share information through files, code (SVN), email and wiki. They are currently running Windows on their primary server, which is limited to only two terminal (RDP) connections and there are several VPN connectivity issues. Further, the server is hosted by a hosting company so all administration has to be done remotely.
My suggestion is to move to Linux. Unlike my personal odyssey, most hosted companies support Windows and Linux equally and because of the requirements, such as Subversion, Jira/Confluence and multi-OS access, Linux is the most reasonable choice. Remote management is certainly easier, despite the leaps made by Windows in the realm of remote management tools. Further, there are more cost-effective software solutions available for a growing company with a limited budget. In some ways, I am lucky. The company is open-minded and willing to consider all of the options. By comparison, I had discussions with a branch of the US Federal Government that was seriously evaluating the desktop environment they had. As I dug further in to the task as it was explained, it sounded more like a customer looking to justify their current solution, because the entire back-end infrastructure, managed by another department within the organization, was 100% Windows based and they had no plans to change. And they had put in a requirement that whatever desktop system was selected, it had to work with, and be managed by, the Windows environment. I walked away from that one after the initial meeting.
In the end are there really options? Yes, we have options, but there are trade-offs. Cost versus functionality. Generic hardware versus proprietary (or availability). But at the end of the day, the options are sometimes limited, usually by politics, regardless of what we would prefer.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
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