January 2000
Back in Linux Journal issue #2 handy, the title of my “From the Editor” column was “Linux 2000...” The abstract goes on to say:
I see Linux as a progressive movement as well as an operating system. And, with any movement you need to chart your direction. To help with that charting I decided that rather than write the April, 1994 editorial I would just go ahead and write the one for January, 2000.
“Well, here we are and it's time to see how well I did. If you don't happen to have issue #2, you can check out the original article here.”
My first idea, that Linux would turn into a movement to provide affordable, reliable, multi-tasking software, was certainly right on. Looks like my growth prediction was a bit off, though. I estimated Linux would be in 100 million homes—seems a bit high.
I also implied that few would remember an old program loader called MS-DOS. Well, I think that has essentially happened. While it continues to live under Windows, not many people seem to realize it.
Another miss on my part was personal satellite stations in the late 1990s. They exist—you can buy a system that offers a bidirectional connection to the Internet—but the price of that connection is still too high to be practical for personal computing. What has happened is that the cost of wired Internet connectivity, most specifically DSL and cable modem, has offered significant bandwidth to many at a very low cost.
I had some predictions about Linux Journal. Specifically, I projected that 90% of our subscribers would receive their magazines via the Internet rather than on paper. This could have happened, if not for two reasons: most readers want the print version of the magazine, and our advertisers want you to see their ads. We do offer an electronic version of the articles to our subscribers at http://interactive.linuxjournal.com/, but we continue to print over 100,000 magazines each month.
I predicted two events that would make Linux a huge success. The first was the formation of MoAmI Semiconductor, a company that produced a chip where Linux was the first OS to run native. We're still waiting on this one. Linux will most likely be the first OS on Intel's Merced chip, with VA the first vendor to ship systems. And, well, keep watching Transmeta.
The second event was Linux becoming the most popular OS in computer science classes. I don't have the numbers, but it sure seems like that could have happened.
I also predicted that NT would become a niche operating system. Did it? We don't know yet, as its name is now Windows 2000 and, well, it really hasn't shipped yet. I still feel that most corporate customers waiting for Windows 2000 will, once they see it, decide Linux is the right answer for servers.
I also predicted those old Linux developers would still be writing code or books on Linux, rather than being CEOs of multi-billion dollar corporations. Generally, this seems to be true, with some also writing articles for Linux Journal. Why? Because these people are doing what they want.
I'm fairly happy with how things have turned out. I took some rather SWAGs (Scientific Wild Guesses) and wasn't totally out of line. The good news is Linux is still here, you are still here, and we are still here. Hopefully, the only big arguments of the next five years will be about programming in Perl or Python and whether to use GNOME or KDE on your Linux system.

Phil Hughes
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
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
| 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 |
| Trying to Tame the Tablet | May 08, 2013 |
| Dart: a New Web Programming Experience | May 07, 2013 |
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Home, My Backup Data Center
- What's the tweeting protocol?
- New Products
- One Hand Slapping
- Readers' Choice Awards
- RSS Feeds
Enter to Win an Adafruit Prototyping Pi Plate 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 Prototyping Pi Plate 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
- Next winner announced on 5-21-13!
Free Webinar: Linux Backup and Recovery
Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.
In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.




7 hours 7 min ago
9 hours 40 min ago
10 hours 57 min ago
11 hours 32 min ago
11 hours 55 min ago
16 hours 43 min ago
17 hours 30 min ago
19 hours 4 min ago
20 hours 40 min ago
22 hours 38 min ago