Linux Journal Contents #153, January 2007
SMP and Embedded Real-Time
by Paul McKenney
What happens when multicore CPUs penetrate embedded systems?
Choosing a GUI Library for Your Embedded Device
by Martin Hansen
GUI design with QTopia and Nano-X.
The HAL Project
by Pascal Charest, Michael Lenczner and Guillaume Marceau
It's hacking, but is it art?
How to Port Linux When the Hardware Turns Soft
by David Lynch
Soul of the Pico machines
An Interview with Marten Mickos
by Glyn Moody
Marten Mickos chats about the success of MySQL.
Creating a Lulu Book Cover with Pixel
by Donald Emmack
Pixel makes a Lyx book pixel perfect.
An Automated Reliable Backup Solution
by Andrew De Ponte
A super backup solution on the cheap.
Ajax Timelines and the Semantic Web
by Ben Martin
Should we create a timeline on how we implement Timeline?
Controlling Spam with SpamAssassin
by Colin McGregor
Assassinate spam with extreme prejudice.
Tech Tips with Gnull and Voyd
Reuven M. Lerner's At the Forge
Marcel Gagné's Cooking with Linux
It's about Time!
Dave Taylor's Work the Shell
How Do People Find You on Google?
Mick Bauer's Paranoid Penguin
Running Network Services under User-Mode Linux, Part III
Jon “maddog” Hall's Beachhead
Ode to Joy
Doc Searls' Linux for Suits
Embedded at the Edge
Nicholas Petreley's /var/opinion
The GPLv2 vs. GPLv3 Debate
In Every Issue
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!
- Stunnel Security for Oracle
- SourceClear Open
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
- Parsing an RSS News Feed with a Bash Script
- 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