From the Publisher - Ten Years of <citetitle>Linux Journal</citetitle>
With this issue, Linux Journal turns ten. I hadn't really thought about how LJ had been my job for ten years until Don suggested I write this editorial. To me, that's a good thing; I have been publishing rather than counting days. What has happened in these last ten years is amazing. Ten years ago I don't think anyone would have expected to see the L-word in ads by HP, IBM, Oracle and many other big players.
In looking around to see what I had from ten years ago that might have something to do with this editorial, I found two interesting things. The first was my copy of Yggdrasil LGX: Linux/GNU/X. This is the Fall 1993 distribution. The second was a picture of Phaedra, the daughter of Joanne Wagner, our first ad rep. The two go together because Phaedra (now 15) used to play the text game Mille Bornes, from the BSD games collection, on this version of Linux.
The distribution came in the form of a 64-page book and had a description of what it included and what it would run on on the covers. Inside you found a CD, a regular 5 1/4" boot floppy and one of those new-fangled 3.5" boot floppies. The system requirements were 4MB of RAM and from 2 to 680MB of disk space. Inside the book were installation information and a list of where to get support—12 places. One of these 12 is Russ Nelson at Crynwr Software, who still is very much an active member of what we were all calling the free software community back then.
We publish a magazine, so let me look at what I predicted back in the beginning. My editorial in issue two was a piece of fiction describing what Linux would be like in the year 2000—six years into the future. The first sentence says, “In the past 7 years we have seen Linux go from an idea for a small UNIX-like system into a movement to bring affordable, reliable multi-tasking software to anyone who could buy a rather minimal computer.” I don't think there is any argument there.
After some rambling about a program loader called MS-DOS, I went on to say, “With the advent of ISDN in the early 1990s and personal satellite stations in the late 1990s, connectivity became the big issue.” Personal satellite certainly did happen. I was wrong about ISDN (I guess I forgot it stands for It Still Does Nothing), but DSL and cable clearly filled that gap. So, I am still on track.
And that's where the track went astray. For example, I predicted that 90% of LJ subscribers would be receiving the magazine on-line. It still sounds like a great goal, but a combination of people wanting to have something to carry on the bus with them and the way subscription audits work—that is, only paper magazines count toward the official circulation—has slowed progress there. Of course, to my credit, Microsoft founder Bill Gates previously had predicted that Xenix on an Intel 80286 chip was the future of computing, so at least I was a little closer.
All my other predictions had to do with getting everyone on the Internet. In January 2001, I moved to Costa Rica. In the 1994 editorial I claimed that in 2000, I was in Yaak, Montana. So, I did move but I picked a place with a lot better weather. This move also helped me adjust my perspective about Internet connectivity. While many countries, Korea being a good example, are delivering broadband Internet service to a large percentage of their population, many other places are still without.
About nine years ago we decided we needed a Web presence. Linux and Apache sounded like the right approach, so we set up a 486DX100 with 16MB of RAM to test the waters. We agreed to evaluate what we really wanted to do when we got to 10,000 hits per month. LJ was growing and we were busy with other projects. When we finally looked at the Web site again we were at 100,000 hits per month. The system was handling it just fine. Today, we receive over 10,000 hits per hour on our Web sites.
Early on in the life of Linux, ISPs considered it to be an alternative to proprietary UNIX platforms. This was an era where dial-up was almost always the answer. Unfortunately, no intelligent serial communications boards were available with Linux drivers. I started talking to vendors and they all thought I was crazy to think there was any commercial future in Linux for them.
One company kept talking to me, though. They thought I was crazy mind you, but they did keep talking. That company was Cyclades, and I finally managed to get them to give Randy Bentson one of their boards so he could write a Linux driver. Six months later, Doris Li, their marketing manager, admitted that 50% of their domestic sales of that board were going to Linux users. Much like Russ Nelson, Cyclades is still here.
Phil Hughes
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.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| 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
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?






50 min 14 sec ago
6 hours 3 min ago
9 hours 15 min ago
11 hours 30 min ago
11 hours 58 min ago
12 hours 57 min ago
14 hours 25 min ago
15 hours 34 min ago
16 hours 20 min ago
22 hours 56 min ago