The Perspective from My Garage
Even now, mainstream media is getting the story all wrong—Doc reflects on the backlash against Linux in the press.
by Doc Searls
On my browser is a CNET piece titled, “Got Linux? Many Companies Say No”, by Sergio G. Non. The subhead reads, “News Analysis: Linux penguins are braying louder, but companies don't plan to adopt many of them in the near future.” The opening text paints fact as speculation, then shoots it down: “...because the economy is still weak, many tech observers believe that Linux—and its price tag of 'free'--will attract more businesses looking to cut costs. At least that's the theory. Practice indicates something else.”
The “practice”, however, is anything but. It's a Goldman Sachs survey of 100 technology executives who were asked to name their highest and lowest spending priorities. Top priorities were migrating to new versions of Windows, security software and UNIX servers. At the bottom were mainframes, supply-chain management software and Linux servers. Again, these were spending priorities. No practice involved. Also no respect for the virtues of Linux as an instrument of savings.
We finally run into actual practice about halfway through the piece, when the author reports that Amazon.com has just “saved millions by switching to Linux from UNIX in many areas of its business”. Then we read quotations from an IT consultant who says, “Many of our clients consider Linux to be a very real option for cost savings”, and “There's a definite ROI.” The same consultant later adds, “I would agree that many companies are scaling back forward-looking projects.... However, the feedback we get from our clients is that they are very interested in Linux.”
In fact, the weight of evidence in the piece actually favors Linux, on the whole. But that's not the story this CNET writer wanted to tell. There's a backlash against Linux right now in the business press, and this guy was just doing his part. To be fair, there's a backlash against everything associated with the dot-com bubble, from venture capitalists and day traders to the countless wacky ideas that attracted hugely speculative investments.
But I think the backlash hits Linux worse for a number of reasons. One reason is that there aren't many pure Linux companies left. The Business Tux population has thinned to the point where it looks like an endangered species, even while a lot of big companies like IBM are crooning their love for Linux.
Last week I purged my collection of business cards collected over the last several years, and all but a few of them went in the trash. The ones I tossed were mostly from companies that are now dead, absorbed into other companies or busy repositioning themselves as something else.
And another problem was the brief but spectacular moment Linux had in the spotlight on Wall Street, a spotlight that fell on Tux at the very peak of the Street's speculative fever. In late 1999, no fleece was more golden than Linux, even though very few investors knew what Linux did, other than appear to threaten Microsoft. Between August and December of 1999, Red Hat, Cobalt, Andover and VA Linux all had huge IPO successes. VA's debut run-up was the biggest in Wall Street history.
Today, the only one of those four companies that still proudly flies the Linux flag is Red Hat—and I say hats off to them. Cobalt was acquired by Sun. Andover was acquired by VA, which recently filed to change its name to VA Software; they've even rid its stock of the once-valuable LNUX name.
The larger problem was that too many dot-com companies were not companies at all. They were projects—ventures. They were like those businesses with false fronts that lined the streets of mining towns built overnight in the Old West and abandoned almost as fast when the lode ran out, if it was ever there in the first place. From the street they looked like real businesses in real towns, but in fact, everything in sight was a gamble.
But Linux isn't a gamble, not as a technology. But it also isn't a business—and that brings us to our third problem, which is trying to understand and explain it to real businesses. The Goldman Sachs study cited by that CNET article typifies the problem. Linux in its pure state isn't for sale. You can't look at its popularity in terms of sales.
Worse, prognostications have ways of flat-out sucking anyway. Yesterday I went through boxes in the garage looking for a document I've been saving for a dozen years because it was so spectacularly wrong, right from the minute it was printed. I couldn't find it, even though it was thick as a phone book and chock-full of evidence for the continued growth of OS/2, Novell and other brand-name LANs, the likely success of AT&T in the computer business, the continued growth and proliferation of a dozen different UNIX brands, especially AT&T's original UNIX, recently bought by Novell and rebranded as UnixWare, a lot of stuff about Lotus Notes, and the continuing share losses for Apple. There was nothing, of course, about the Internet, and nothing about Linux. There was no idea that a PC would ever be hooked up to anything more significant than a printer and a fileserver.
But I did find some wonderful other nuggets. A Sports Illustrated from November 30, 1981, had a cover story on the preseason, number one North Carolina Tar Heels, with four of the team's stars: James Worthy, Matt Doherty, Jimmy Black and Sam Perkins. Not shown is the player that would emerge not only as the team's biggest star, but the best player in the history of the sport: Michael Jordan. And there was a Popular Electronics from July 1976. “Exclusive! Now You Can Build a High-Quality Intelligent Terminal!” it says. I page through it. There are a lot of ads for CB radios and stereo gear, electronics courses and antennas. But near the front is a two-page spread, the headline of which reads, “Imagine a Microcomputer”. Below is a box with LEDs and switches on the outside and an inside that's all backplane and power supply. The copy went on:
Imagine a microcomputer with all the design savvy, ruggedness and sophistication of the best minicomputers.
Imagine a microcomputer supported by dozens of interface, memory and processor option boards. One that can be interfaced to an indefinite number of peripheral devices....
It was an ad for the MITS Altair 8800-b. It didn't succeed, but the vision sounds mighty familiar, doesn't it?
Doc Searls is senior editor of Linux Journal. His monthly column is Linux for Suits. He is also a coauthor of The Cluetrain Manifesto.
email: doc@searls.com
Doc Searls is Senior Editor of Linux Journal
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
| Designing Electronics with Linux | May 22, 2013 |
| 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 |
- Linux Systems Administrator
- New Products
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Designing Electronics with Linux
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
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!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
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?




5 hours 38 min ago
10 hours 10 min ago
10 hours 11 min ago
12 hours 11 min ago
20 hours 56 min ago
21 hours 30 min ago
22 hours 29 min ago
23 hours 19 min ago
1 day 3 hours ago
1 day 7 hours ago