This issue is my last with Linux Journal. Don Marti, formerly technical editor of Linux Journal and editor in chief of Embedded Linux Journal, will be stepping into the role of editor in chief. As you must already know, you will be in most capable hands with Don, and I can assure you it will never be boring.
Few things inspire close human relationships like shared labor. Creating Linux Journal on a monthly basis and tackling the various other projects that come with being on the editorial staff of SSC make for a rigorous schedule and a lot of unused vacation time. As the LJ staff is a small one, we've gotten to know one another quite well. I've come to appreciate them not only for their competence and willingness to go the extra mile, but for their qualities as wonderful human beings. I'm a better person for having worked with them, and I feel confident they will continue to serve the magazine's readers very well.
Though I've been editor of Linux Journal for two years, I have met personally only two of our contributing editors. Yet, working with them on a monthly basis, I feel about them much as I feel about our in-house editorial staff. Many times their help and contributions go far beyond writing their monthly column—though their pay doesn't. I've abused and taken advantage of them, rewarding them with nothing more than my gratitude (I told them all I'd be their best friend) and LJ shwag, and they've accepted it graciously.
On this same page in the 100th issue, I cited the goodwill of the Linux community as something that makes working for this magazine a rewarding experience. That generosity made our 100th issue possible and is one more thing that makes leaving this job difficult. Our authors invest a lot of time and energy into providing information that is both accurate and useful, and believe me, they don't do it for the money. In many of the article proposals we receive, the potential author states a feeling of obligation to contribute to the community as the principal motivation for writing.
Given that our writers are, in most cases, our readers, we have the advantage of getting to know our audience very well. This makes saying good-bye more difficult, but my thanks more genuine.
So good-bye and sincere thanks to the staff, contributors and readers of Linux Journal. It's been a memorable two years.
Richard Vernon is former editor in chief of Linux Journal.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- 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