Time Again for Reader Input
One year ago we started Linux Journal. Answers to questionnaires we posted on Usenet helped direct LJ, and your letters and e-mail have continued to help set our course.
Partly because our initial questions were posted in comp.os.linux.misc on Usenet and partly because of where Linux was a year ago, many of the comments pointed us toward monitoring Linux development and following the more technical path of Linux-related work.
Today, in addition to our 10,000 subscribers, Linux Journal appears on hundreds of newsstands worldwide. Many of these readers have not been involved in the on-line development effort on the Internet. Because of this, their needs are different from those who initially responded to our questions back in 1993.
We have grown up along with Linux. We see one of our big jobs as helping get the word out on Linux and helping newcomers to Linux get up to speed and involved.
We want to find out more about our current readers. We ask you to fill out the information below and either fax or mail it back to us.
Thanks for your time. Your answers will help direct LJ for the next year.
Fax back to +1 206-782-7191 or mail to Linux Journal, P.O. Box 85867, Seattle, WA 98145-1867 USA.
Phil Hughes is the publisher of Linux Journal.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Roll your own dynamic dns
1 hour 5 min ago
- Please correct the URL for Salt Stack's web site
4 hours 17 min ago
- Android is Linux -- why no better inter-operation
6 hours 32 min ago
- Connecting Android device to desktop Linux via USB
7 hours 1 min ago
- Find new cell phone and tablet pc
7 hours 59 min ago
9 hours 28 min ago
- Automatically updating Guest Additions
10 hours 36 min ago
- I like your topic on android
11 hours 23 min ago
- This is the easiest tutorial
17 hours 58 min ago
- Ahh, the Koolaid.
23 hours 37 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?