Linux Journal Contents #206, June 2011
Hexapod—a Linux-Powered Spider Robot
by Anton Borisov
Interview with Matt Bunting, the hexapod robot developer.
Debugging Embedded Linux Platforms with GDB and Python
by Tom Parkin
GDB provides support for scripting debugging actions using a Python interpreter.
Breaking Free the Gumstix DSP
by James McColl
Setting the Gumstix Overo Fire ablaze with the DSP.
Speech I/O for Embedded Applications
by Rick Rogers
Speech I/O works! See how to apply it in your next embedded application project.
CyanogenMod 7.0—Gingerbread in the House
by Shawn Powers
What happens when you mix powerful, Linux-powered cell phones with an active Open Source community?
Tiny Core Linux
by Joey Bernard
An intro to this very small, run-in-memory distro.
Roll Your Own Embedded Linux System with Buildroot
by Alexander Sirotkin
Embedded Linux, the easy way.
A Primer to the OAuth Protocol
OAuth is a simple way to authenticate users.
Reuven M. Lerner's At the Forge
Dave Taylor's Work the Shell
More Fun with Days and Dates
Mick Bauer's Paranoid Penguin
DNS Cache Poisoning, Part II: DNSSEC Validation
Kyle Rankin's Hack and /
Lightning Hacks—the Command Next Door
by Kyle Rankin
Doc Searls' EOF
Whatever Sinks Your Boat
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