Linux Journal Contents #99, July 2002
autoSql and autoXml: Code Generators from the Genome Project
by Jim Kent and Heidi Brumbaugh
When working with large amounts of data, save yourself some time with these tools, developed as a result of work on the Genome Project.
Multiheading Linux Systems
by Brian Gollsneider and Arthur M. Messenger
Get set up for those jobs that require double the screen space.
Icarus Verilog: Open-Source Verilog More Than a Year Later
by Stephen Williams and Michael Baxter
More competitive than ever—and still free!
A Conversation with Stephen Williams
by Michael Baxter
Stephen reveals the secrets of just how Icarus Verilog has achieved amelioration.
Keeping Up with Python: the 2.2 Release
by Wesley J. Chun
Unification, iterators and more—the improvements to the Python 2.2 release series.
DSI: Secure Carrier-Class Linux
by The DSI Team
Security architecture specifically for clustered environments is lacking—but that will soon change.
Kernel Korner Proper Linux Kernel Coding Style
by Greg Kroah-Hartman
At the Forge Apache 2.0
by Reuven M. Lerner
Cooking with Linux Art Is but Engineered Reality
by Marcel Gagné
Paranoid Penguin Staying Current without Going Insane
by Mick Bauer
GFX Industrial Light & Magic
by Robin Rowe
Focus on Software
by David A. Bandel
Focus on Embedded Systems
In Search of the Embedded Linux “Killer App”
by Rick Lehrbaum
Linux for Suits
The Protocol Problem
by Doc Searls
by Lawrence Rosen
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SourceClear Open
- 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