Doing Good and Preventing Bad
Thirty years ago I was working at the Hanford Nuclear Reservation. The position focused on systems programming, but ultimately, the environment rubbed off on me. I learned a lot about nuclear power as well as the more antisocial aspects of nukes. And, I recognized a problem. Any number of issues came to mind: operational danger, waste disposal and life-cycle cost are the first three. In any case, I knew nuclear power was not going to be, as President Eisenhower had said 20 years before, “too cheap to meter”.
I wanted to make sure everyone learned what I had regarding the issues of nuclear power. But, I also wanted everyone to learn all that I had learned about alternative energy sources such as solar, biomass and wind.
I quickly found I could not deal with both issues. Understanding and teaching about alternative energy is a huge job, as is pointing out flaws in nuclear power. So, I chose. Because of all I had learned at Hanford, I felt I was more qualified to talk about the problems of nuclear-power generation.
This was my choice for “preventing bad”. The more knowledge I could disseminate, the more likely it would be that the general population would see the issues, get involved and, in the long term, prevent the US from jumping deeper into the nuclear well.
Unfortunately, new “bad” appeared. As photovoltaics became cheaper, utility companies lobbied to make it harder for customers to sell power back to the grid. Once it was proved that intertie systems to sell power back to the utilities were safe and effective, utilities came up with rate schedules where the power you sold back was at a lower price than the power they sold you, even though peak output of solar systems corresponded with very high demand. They wanted to use the law to escape the consequences of failure by making intertie systems pay to decommission failed nuclear plants.
Now, back to software. When I first saw Linux (back when kernel versions started with a dot), I merely was looking at alternatives to the “real” UNIX systems. We had been in business publishing pocket reference cards and doing training and consulting on UNIX systems for about ten years.
I decided Linux was a lot more than simply a hobby project. I felt it showed great promise, so we changed direction from being a UNIX company to being a Linux company. With over 100 issues of Linux Journal under our belt, I feel we made the right choice.
Early on, a lot of my energy went into telling people about the virtues of Linux. Much like telling people that nuclear power costs too much, this was a hard sell at first. People didn't want to hear that Linux might be a better choice than what they were working with.
Now the days of telling people that Linux is a serious contender in the OS business are gone. Even if you still don't have it on your desktop, it is unlikely you will sit down for a web surfing session without getting involved with some Linux server.
The problem is that much like solar panels on your roof are a threat to the nuclear power industry, Linux is a threat to the OS status quo. One can spend a lot of time and energy counteracting the FUD.
As Linux is proving to be a worthy alternative, the same sort of “it works but you can't put it here” arguments are appearing as they did with intertie systems. They merely go by different names: DMCA and bogus software patents are two of those names. As with nukes and solar energy, competition is fine, but what we see is the use of the legal system to harass promising new alternatives.
This work of “preventing bad” needs to be done. But, the alternative is simply to keep on truckin' with Linux—continuing to identify places where Linux solves a problem and moving ahead with the solution. So many places have either a time-consuming manual system or a poorly implemented, non-Linux system that people easily can make a career of problem solving with Linux.
The Linux movement needs both. Someone has to deal with FUD, and someone needs to move Linux into new places. To go back to my nuclear power analogy, if no one were out there developing alternative energy technology, there would be no alternative to nukes, no matter how bad a picture the antinuke activist painted.
As for me, I did my time dealing with the FUD. A lot of it was fun work, but I have pretty much moved into the “just do it with Linux” camp. I would rather show someone a solution and let them choose than spend my time counteracting anti-Linux propaganda.
I moved to Costa Rica over a year ago. On my one-year anniversary I was thinking about how things have been different. Aside from the more obvious—things like I really need to be working on my Spanish—the biggest difference I have seen is that people are more open to solutions. There is less disposable money here than in the US and less anti-Linux FUD. Thus, it is easier here to listen to someone's problem, propose a Linux-based solution and have them accept it than in the US. It is easier to think Linus was right about World Domination—except that the US might be the last country to get Linux.
By the way, besides being Linux-friendly, all electricity in Costa Rica is produced from renewable sources including hydro, geothermal, wind and solar. Maybe these two issues fit together more than I thought.
Phil Hughes is the publisher of Linux Journal.
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
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- 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