What's It Like To Be A Linux Journal Blogger?
Well, first of all, it’s fun, or I wouldn’t be doing it. I work with some intelligent, talented people, like Carlie Fairchild, publisher at LJ, and Katherine Druckman, our Webmistress. My job description as one of the LJ bloggers is to “write about whatever you want, as long as it is Linux related”. That’s pretty much the ideal job description for somebody like me who has been doing Linux full-time since shortly after Slackware first came out in 1993. I feel lucky to be writing for Linux Journal, which is currently celebrating its 16th year of publication, and is the original magazine of the global Linux community.
The Linux Journal audience runs the gamut from “Linux Wizard” to “Neophyte”. Given the self-selection process of the LJ readership, most of the people who come here, either directly to www.linuxjournal.com , or via to the Linux Journal Facebook page are genuinely interested in Linux.
Sometimes you feel like a lightening rod. One does encounter the occasional flame comment on a posting. But, I’m used to that. I ran the LANL, The Real Story blog from December, 2004 through July, 2005, and I can tell you that nobody on Linux Journal can flame like some of those unhappy campers who used to post on the LTRS blog. One of my previous LJ posts was even dedicated to the art of flaming, and included a couple of hints on how to fan the flames if the fire seemed in danger of dying out.
Usually, though, the LJ readership is genuinely interested in the material being covered in the articles, and the comments are positive, or at least fully engaged regarding the topic:
Why did you suggest Amarok? Rhythmbox is far superior. Any idiot knows that!
It’s a pleasure to see such enthusiasm. Seriously. Apathy is no fun at all.
Another thing I enjoy about writing here is that the LJ interactions provide constant exposure to what’s going on in the Linux world. Linux is big. Rarely a day goes by that I don’t learn something new. For example, today I heard about the Clementine project: Amarok 1.4.x forked and ported to Qt4. Amarok has been my favorite music player for a while, so I’ve made a note to myself to check out Clementine.
As Carlie told me when I hired on, “Do it as long as it’s fun. If it stops being fun, stop doing it.”
Which is exactly what I intend to do.
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
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
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