Programming has become as much a part of our everyday lives as breathing. Some of us do it; some of us use it; all of us are affected by it. We encounter it when we use an ATM machine, drive a car, check out at the grocery store, and sit in front of the TV or computer. It's interesting and fun to do. Nothing beats the feeling of writing a good application that gets used by many others—it's a source of pride. Nothing feels worse than writing a good application that gets scrapped and never used. Actually, this brings up one of the good points of free software: you write it, put it out on the Web, and people who need it use it; nothing gets put in the bit bucket. Only in the commercial environment can a boss say, “We've decided to abort that project you've been working on for the last six months”--and your work disappears forever.
This month, we let programmers tell us how they work, from programming on clusters to building GUIs with X and Motif—it's all here. Multi-threaded programs are hot and so is Python. Learn how to use the two together; then use LCLint to debug all that new code you've been writing. We also have articles on Palm Pilot development tools and writing a simple plotting program (see “Strictly On-line”). We also talk again to Darryl Strauss to find out what is happening in the world of 3-D graphics.
Some people collect spoons, others collect languages. Eric Raymond collects languages, and his latest find is Python. We've liked Python for a long time and so decided not only to include a feature article on Python in this issue, but also publish an entire supplement devoted to it. That supplement comes to you with this issue. We hope you enjoy it.
Marjorie Richardson, Editor in Chief
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!
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader 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