The Cathedral & the Bazaar
Author: Eric S. Raymond
Publisher: O'Reilly & Associates
Price: $19.95 US
Reviewer: Peter H. Salus
Beginning in 1992, Eric S. Raymond has jotted notes and comments that were (and still are) net-accessible. Since 1996, several of his essays (most notably “The Cathedral & the Bazaar”) have become required reading. If anything, the obloquy heaped on Raymond by the PR folks in Redmond, WA (e.g., in the “Halloween documents”) has made him more important.
O'Reilly has done us all a good favor by collecting a number of Raymond's pieces and making them readily accessible at a price everyone can afford.
The volume contains “A Brief History of Hackerdom”, “The Cathedral & the Bazaar”, “Homesteading the Noosphere”, “The Magic Cauldron”, “The Revenge of the Hackers” and “Afterword”, plus two appendices.
These are the “commonsense” or the “Federalist papers” for the Open Source movement. They are the testimony of just why the BSDs and Linux, Perl and Python, Tcl and Java are successful: we have tens of thousands of programmers all over the world contributing to the excellence of programs and systems. We don't have an encapsulated proprietary system which no one can debug.
When I was writing A Quarter Century of UNIX (Addison-Wesley, 1994), I realized that essential to the “UNIX philosophy” was something alien to commercial programming: the changes to the kernel, the applications and the programs were all written by one or two or three hackers, not by teams of programmers. Eric Allman wrote Sendmail; Mike Lesk wrote the original uucp (even the mid-1980s version, HoneyDanBer, was by Peter Honeyman, Dan Nowitz and Brian Redman); Steve Johnson wrote yacc; Bill Joy wrote vi, etc. Brian Kernighan once told me AWK was the toughest project he ever worked on “because there were three of us” (Aho, Weinberger and Kernighan).
Of course, it's all the Internet's fault. Even with the semi-annual USENIX tape-swaps and uucp, stuff passed about more slowly. It's the Net that enabled a Finnish student to send his work to nearly every corner of the world and enabled thousands to contribute and feed stuff back to him.
In some ways, “The Magic Cauldron” is my favorite essay of Raymond's. Here, he shows that he understands the underlying economic reasons for the success of open software. This understanding is based on the anthropological study of gift exchanging and the concepts of what happens in a gift culture when “survival goods are abundant”, and therefore, the exchange is no longer interesting.
This is tied together with the notions inherent in the fact that software has two distinct values: use value and sales value. As Raymond says, use value is value as a tool; sales value is value as a salable good. One of Raymond's most interesting discussions is founded in this.
Food, equipment and books all retain value independent of the producer. If a farmer sells his farm, the food produced retains its value, etc. When a computer manufacturer (hardware or software) goes out of business or a line is discontinued, the price users are willing to pay plummets. The price users will pay is limited by “the expected future value of vendor service”.
Open-source software forces the vendor into a world of service-fee-domination and exposes “what a relatively weak prop the sale value of the secret bits in closed-source software was all along”.
The true advantage for all of us lies in the notion of high-quality software being built upon by the community, rather than being locked up in a vault or discontinued.
Raymond believes that in 2000/2001, Linux will be “in effective control of servers, data centers, ISPs and the Internet, while Microsoft maintains its grip on the desktop”. Most likely, that's correct. But with the advent of products like StarOffice and WordPerfect for Linux, there may well be inroads into the desktop market as well.
This is a fine, thought-provoking book that should be read by anyone interested in computing: open, academic or proprietary.
Peter H. Salus, the author of A Quarter Century of UNIX and Casting the Net, is Editorial Director of SSC. He can be reached at email@example.com.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SourceClear Open
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide