Welcome to the 100th Issue of Linux Journal
I still tend to think of myself as a newcomer to the magazine, having been on the masthead for only one-fifth of the now 100 issues. But those 20 issues have been an enriching experience. Each issue has presented its own challenges and dilemmas.
Some issues even hosted their own minor polemics. Nothing sparks comment like nudity, and our staff had a lot of fun reading and choosing which of the letters regarding the nude cover of the Python supplement to print. Then there was the “American” debate, begun in the November 2000 issue, which also spanned more than a couple of issues. Who could forget the QSOL advertisement, also from the November 2000 issue? The “improper” implication spawned some memorable press, but I'm sure it would never have happened if we hadn't made the first step and put the naked man on the cover, obviously giving QSOL the impression that we were “that kind of magazine”. QSOL's following ad was as frightening as the previous ad was suggestive, perhaps in a effort to take revenge on on those not yet prepared for their style of advertising.
These events made the letters section perhaps the most-read part of the magazine, but the most fun part of working for Linux Journal has been the interaction with both the Linux community and the rest of the hardworking Linux Journal staff.
As our magazine is one that relies on community-submitted content, I've been fortunate to be able to get to know many very talented hackers. And I'm not just talking about the famous members of the Linux community. Just as some of the best actors in the world are only seen on community stages, some of the smartest coders are garage hobbyists or work for small companies. The general high level of goodwill that emits from our authors, regular contributing editors and is evident throughout the community, consistently impresses me and makes my job a much happier one. Our reliance on you—our readers and contributors—makes this 100th issue celebration as much yours as it is ours. Sincere thanks for all of your help and support.
Richard Vernon is editor in chief of Linux Journal.
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
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- SuperTuxKart 0.9.2 Released
- Returning Values from Bash Functions
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