Linux Journal Survey Results
The initial answers told us two things:
Linux Journal was needed
People knew what they wanted to see in Linux Journal
In order to make sure we were still on track, we posted the same survey to Ascent in December, 1993. The letters column comes from answers to question two of the survey, “Are there any other topics you would like to see covered?” The table below shows average responses to question one of the survey.
Survey question 1 answers:
Rate your interest in the following features:
(1=not interested, 2=possible interest, 3=interested, 4=very interested, 5=that's my subject!)
Based on the results of this survey, we have tailored the content of LJ and will continue to tailor it based on reader feedback.
With regard to advertising (question 3), about 90% of those who responded supported the policy. People who felt we should let anyone advertise outnumbered those who felt that having advertising was a mistake. Many of the readers felt that advertising would help them locate new products and saw that as an advantage.
Virtually everyone who returned the survey said they would like to subscribe and about 10% offered to write articles. Interest in advertising was lower (about 3%), but that was to be expected. We thank you all for your support.
When we first started getting subscribers, about 85% were from the United States. Survey results were running more like 65% from the US. We then made an offer of free copies of LJ for user groups to give out to their members and, the response was about 50% non-US.
Our conclusion was that our higher non-US subscription rate was the problem. So, we negotiated with international distributors and now offer the same subscription rate ($19/year) anywhere on the planet. We expect this change will get our subscriber base more in line with the survey results.
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