Linux Journal Goes 100% Digital
Introducing Linux Journal 2.0
We're going all-digital. That's the news. Starting with our next issue, #209, we're going off-rack and off-mailbox, but staying on-email and on-Web, where we can grow and improve. It's the only path open to us, but it's also a good one. Hang with me as I explain why. (See also Experience the New Linux Journal for details about the new format.)
Linux Journal was the brainchild of Phil Hughes in 1993. That's when he got it in his head that a free software magazine would be a good idea, and pulled together an email list of friends—including me—to talk about it. Then one day, out of the blue, Phil halted the proceedings and announced that he now saw The Future, and it was Linux.
At the time, Linux was invisible in the trade press. None of the magazines put out by the big three computer-industry publishers--Ziff-Davis, IDG and CMP--paid any attention to it. All their eyes were on name-brand computer and network companies, plus startups in spaces those companies (all of which were advertisers) defined. UNIX was still a war between variants sold by Novell, Silicon Graphics, IBM, Sun and others, plus the BSDs. Linux was at version 0.x, and of relatively little interest outside the kernel mailing list.
Phil saw UNIX for the mess it was, and he knew how Linux was going to solve it. So, when Linux 1.0 was released in March 1994, Linux Journal promptly followed. During the 17+ years since, Linux has proven Phil right, and it is now the standard operating system for everything from picture frames to set-top boxes, plus most of the Web. (Fun fact: even Microsoft's Bing search engine is mostly hosted on Linux, through Akamai.)
But while Linux continues to win at operating systems, print magazines are losing to other media—especially digital—and have been for a long time. In fact, lately it's been getting worse.
Just this month, ABC reported that newsstand magazine sales fell 9% in the first six months of this year. The Wall Street Journal reported a drop of 9.2% for consumer magazines, with double-digit drops for celebrity weeklies like People and Star. Women's Wear Daily reported similar drops for all but one fashion magazine: Vogue, thanks to one Lady Gaga cover.
The big computer-industry trade magazines from the '90s have either disappeared or gone digital. Of the big three publishers, only IDG is still intact, and still putting out most of its original magazines in print.
We survived while others failed by getting lean and staying focused. But the costs of printing and distributing continue to go up. We could keep publishing in print if we could raise the number of advertiser pages, but we don't see that happening.
What we do see is a core readership that has stuck with us, along with Linux, for a generation. You, our readers, are at the heart of Linux, and always have been. We want to keep that heart beating.
That heart will beat with much more strength if the blood flows entirely through bits and pixels. It also will be better aligned with the world we helped create. (We were online and helping ISPs grow even before the first graphical browsers showed up.) The opportunities online are as wide as the digital horizons. And we won't be confined by the physical and cost limits of paper and ink.
Those limits include space. We can name many examples of articles, columns and regular features that have been cut to fit the limited spaces of our print pages. We also can name many examples of digital pieces that have been very successful, outside the confines of print. Working in two media has always pulled us in different directions. Now we can move forward in the winning direction, without the drag.
But we can't do it if you're not with us. For that we need two things.
The first is for you to keep subscribing. Our first all-digital edition of Linux Journal--#209--will go out on schedule, directly to all print subscribers. It will be the same magazine it always has been. It also will be searchable, interactive, printable and, therefore, also green (a small bonus, but one we do care about).
The second is to get your input and participation in making Linux Journal the magazine you want it to be. We are setting a forum for conversation with subscribers, plus a forum for conversation with non-paying readers. I also invite you to write us directly at firstname.lastname@example.org. For more help, visit our FAQ.
Linux Journal is your magazine. You're the ones who pay for it, and you're the ones whose help we need and appreciate the most. Linux always has been a construction project, and the same is true for this magazine. Please help us keep building it in ways that work best for you—and for everybody out in user space too.
Doc Searls is Senior Editor 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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- 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