Is This Any Way to Run a Railroad?
While I have never run a railroad, I am guessing that publishing a magazine is like running a railroad. You have an assortment of diverse customer needs, you have a limited budget, and you need to offer the best possible service to everyone.
But the parallel goes beyond that. In the railroad business you can make up your train out of an assortment of different cars, and based on the number of cars and the terrain you must travel through, you can pick the number of engines to pull it. As publisher of LJ, I get to pick the article mix, pick the number of pages, and pick who receives the magazine. If I do my job right, LJ gets more customers, which gets it more revenue—revenue from advertisers as well as readers—and everyone benefits.
All that said, I want to tell you what has changed at LJ, why it has changed and what you will see in the future. And, for our old customers, I want to assure you that you will continue to get the service you expect.
We take the tag line on the cover (“The Monthly Magazine of the Linux Community”) seriously. I fought for this before Issue 1 was published, and I continue to fight to make sure we stay on track. Today, however, that community is changing and we need to respond to those changes. While there is still a large Linux development community, there are other easily-identifiable “communities” needing a reliable source of Linux information. Here are a few:
Linux (and Unix) novices
Embedded systems builders
Let's take one example, web developers, and see why it is important that we give them the information they need. Linux is an ideal platform for developing web content and Linux systems make ideal web servers. But web developers have choices. When someone says, “Why should I use Linux instead of NT for my web server?” we need to have a good answer. Being able to point at books like CGI Programming in C & Perl, by Thomas Boutell, a Linux user himself, helps. Being able to show the person that a monthly magazine called Linux Journal will answer ongoing questions, offer sources for essential hardware and software, and generally offer needed support is another important part of the answer.
The first major change is that we are taking over the Linux Gazette. For those of you not familiar with it, LG is a newsletter. LG has offered an assortment of quick tips and articles that, while useful, have appealed to a smaller segment of the Linux community. We have always considered their work to be complementary to ours.
John Fisk, the creator of the Gazette, has run out of time to produce it and we struck a deal whereby LG can continue as a vendor-independent source of information. Its new home will be http://www.ssc.com/lg/, and its new editor will be Marjorie Richardson. She can be reached at firstname.lastname@example.org.
In addition, a new editor and a new home, there will be other changes to the Gazette. While we will continue to offer an on-line version, we intend to include part of the Gazette in the pages of Linux Journal. We will offer the information we consider of the greatest interest, and pointers to additional on-line information.
The way our community grows is by getting new people up to speed. We used to have a novice column. It just sort of faded away. We knew it was needed and with the introduction of “Novice-to-Novice”, we've done something about it. John Fisk is writing some articles for the series, as well as at least one other author. You can suggest new topics by sending e-mail to email@example.com or by writing to us.
When each new Linux distribution comes out there is a flood of new questions. We have started a tech answers column where vendors and consultants will answer the common questions that arise. If you have a question, you can send it to firstname.lastname@example.org, mail it in or fill out a form on our web page.
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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader 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