From the Editor
Hi. I'm the new Editor of Linux Journal. If that gives you a sense of deja vu, you likely read a similar note in the September issue. I can only assume someone made LJ's five-day Editor an offer he couldn't refuse.
Similarly, I didn't see how I could say no when Phil Hughes, our Publisher, asked if I'd like to leave my ho-hum job at a state university and become Editor of a publication dedicated to nurturing and promoting the use of Linux. The little operating system that could is now a formidable force, and new product announcements are becoming the rule rather than the exception. The good press Linux is receiving in major media is exciting and impressive. And who would've thought Linux would do so well that the Santa Cruz Operation would start giving their Unix away?
Linux is still free and open, unlike the other Unix-like operating systems. The ability for users to contribute to the development of Linux creates a positive and vibrant scene. Because Linux actually works—and works well—it is truly useful instead of just fun.
Talented people devoting their time to Linux development make it possible for others at many levels of computing savvy to use Linux systems effectively. In many situations, users can just “plug and play” now; Linux is no longer just for hackers. Of course, Linux still has the free tools and open design to accommodate anyone who does want to start playing around with code.
So, I had to take this job, really.
I've actually been working with Specialized Systems Consultants, the company that publishes Linux Journal, for a couple of years now. I decided I needed to learn about this Linux thing I kept hearing about, joined a mailing list, found out Linux Journal needed some data entry done in the evening... moved on to copy editing, and now here I am.
My computing experience includes: playing with a Cyber on an old TI thermal printing terminal with a 300-baud acoustic coupler, calling up every BBS I could find back in the early '80s, trying to load programs on cassette tape for my TRS-80 Model 1, learning Turbo Pascal and CP/M (a functional OS in under 7K!) on a Kaypro II, taking computer science classes with VMS on old Heath 19 terminals, spending countless hours with Macs and Windoze machines, and, lately, trying everything I can find on my Linux machines. I may have a talent for programming, but I've put more energy into writing and editing, so I need to rely on the people actually making things happen on Linux systems—programmers and developers—for content. For you, the reader, this means well-written articles by people who know what they're talking about.
What I and the rest of the staff of Linux Journal want is simple: world domination. Short of that, we want to be the best source of information about Linux and to help promote its use. We think we can do that with how-to texts, programming tips, hardware and software reviews, examples of Linux in the “real world”, and articles for the beginner. Is there something you need or want to see? Please let me know (firstname.lastname@example.org).
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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- Rogue Wave Software's Zend Server
- 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