I regularly pick up the Linux Journal, but in February I was unable to. Now having picked up the March issue and seeing two letters about maddog's “I believe” response and how inspirational it was, I would really like to see it. Is it possible to post it on the web site?
I read with some concern your recent article on Koha [LJ, February 2003]. I wondered what would happen to small- to medium-sized software companies that currently produce competing library systems. No doubt these companies have invested real money into developing these products and need some return on their investment in order to survive. This led me to wonder about the long-term effect of free software. Any software product that has to compete with the equivalent open-source product must surely struggle to survive. This means one open-source product will eventually dominate each market niche leaving consumers with no choice. Presumably a lot of open-source products are developed by charitable professional software developers during their free time. Will the pool of professional developers shrink as there is little work available other than charity work? Why should large organisations increase their profit margins by significantly reducing the cost of software essential to their organisation? Charity is fine for those who cannot afford to pay but shouldn't be exploited by those who can.
Richard Stallman covered many of the issues you raise in the 1985 GNU Manifesto (www.gnu.org/gnu/manifesto.html), and they have been the subject of intense community discussion ever since. That page, and a web search for links to it, is a good way to catch up on the debate—Ed.
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!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Returning Values from Bash Functions
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- 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