Open Source Software Model
Open Source software is all the rage these days. Big companies and small companies alike are either releasing their software as Open Source or considering it. On the forefront of their minds is “Yes, it's more reliable; yes, it meets more users' needs. But how do we make money on it?”
First, we must be clear that no industry is sacrosanct in any economy. Almost all companies rely on special protection from the government, called intellectual property rights. These rights, covering both copyright and patent laws, exist because they are thought to be economically efficient—that is, they create more than they destroy. Should that prove wrong—that protecting computer software as intellectual property actually makes society poorer—then the computer industry will just have to rely solely on contract law. If society is better off with all software as Open Source, then that is how it will be, even if it makes computer programmers worse off financially.
Open Source software need not impoverish all programmers—indeed, there is good evidence that the deleterious effects of switching to all Open Source software would be only short term. Remember the Luddites? The dislocations in the weaving industry were only temporary. Forty years later, the industry was employing just as many weavers and, of course, weaving a greater amount of cloth.
If you want to see this model in action, look through this issue of Linux Journal. You'll see ad after ad, most of them for Open Source software. The way to make money in a free market is to solve someone's problem and take a cut of the benefit they receive. There are many different ways to do so, as reading the ads proves.
Second, I have been assuming that Open Source software is applicable to all types of software. This is not clearly true or false. What is definitely true is that an operating system can be Open Source and be successful, as all the readers of this magazine know. Perhaps other types of software are not as amenable to Open Source distribution. If this is the case, then the creators of such Open Source software will either not exist in the first place or will go out of business. For this type of software, the proprietary model would work best.
People have gotten rich from Open Source software, and still are. As long as you have an industry where people can get rich, you've got plenty of incentive to enter the industry.
The big question being discussed on the Free Software Business mailing list (fsb-subscribe@crynwr.com) is: “How do you create a piece of software which requires a large up-front investment of human energy?”
Companies such as Netscape or Corel can easily afford to free a major piece of code. The software has been proprietary for a number of years and has recouped its initial investment. The Crynwr Packet Driver Collection started small and was initially useful with only one driver in it, so it doesn't fit the open model. The first released version of Linux was a real UNIX kernel with a file system and serial port drivers. To the extent that it needed an up-front investment, Linus has been paid back for it.
No, recovering the investment is a tough job without intellectual property laws. Problem is, they're needed precisely for only those tough jobs. More than any other type of intellectual property, creation of most computer software involves very little capital costs. Invoking the coercion of the state (even as far as stealing a person's thoughts, when independent creation occurs) is less and less appropriate. Software creation is cheaper now than when PCs were new. The areas where Open Software cannot succeed seem smaller and smaller.
Russell Nelson has been developing Open Source software long before the term existed. His first freed software, Freemacs, came out 15 years ago. He was the progenitor of the Clarkson Packet Driver Collection, the first freed software to be recognized by PC Magazine's Technical Excellence awards. Currently, he works for Crynwr Software, founded in 1991, an Open Source support firm. He can be reached at nelson-lj@crynwr.com.
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
| 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 |
| Trying to Tame the Tablet | May 08, 2013 |
- Using Salt Stack and Vagrant for Drupal Development
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- 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?
- Home, My Backup Data Center
- New Products
- 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.




30 min 11 sec ago
1 hour 16 min ago
1 hour 37 min ago
7 hours 52 min ago
13 hours 30 min ago
19 hours 30 min ago
19 hours 52 min ago
20 hours 3 min ago
20 hours 7 min ago
20 hours 37 min ago