Free as in Freedom - Sam Williams (read this if .TXT) 📗
- Author: Sam Williams
- Performer: 0596002874
Book online «Free as in Freedom - Sam Williams (read this if .TXT) 📗». Author Sam Williams
The Project Gutenberg EBook of Free as in Freedom: Richard Stallman’s Crusade for Free Software, by Sam Williams ** This is a COPYRIGHTED Project Gutenberg eBook, Details Below **
** Please follow the copyright guidelines in this file. **
Copyright (C) 2002 Sam Williams.
This header should be the first thing seen when viewing this Project Gutenberg file. Please do not remove it. Do not change or edit the header without written permission.
Please read the “legal small print,” and other information about the eBook and Project Gutenberg at the bottom of this file. Included is important information about your specific rights and restrictions in how the file may be used. You can also find out about how to make a donation to Project Gutenberg, and how to get involved.
**Welcome To The World of Free Plain Vanilla Electronic Texts**
**eBooks Readable By Both Humans and By Computers, Since 1971**
*****These eBooks Were Prepared By Thousands of Volunteers!*****
Title: Free as in Freedom: Richard Stallman’s Crusade for Free Software Author: Sam Williams
Release Date: May, 2004 [EBook #5768]
[Yes, we are more than one year ahead of schedule]
[This file was first posted on August 31, 2002]
Edition: 10
Language: English
Character set encoding: ASCII
*** START OF THE PROJECT GUTENBERG EBOOK, FREE AS IN FREEDOM: RICHARD
STALLMAN’S CRUSADE FOR FREE SOFTWARE ***
This eBook was transcribed by Craig Morehouse.
Copyright (C) 2002 by Sam Williams.
Free As in Freedom: Richard Stallman’s Crusade for Free Software.
By Sam Williams
Available on the web at: http://www.faifzilla.org/
Produced under the Free Documentation License Table of Contents
Chapter 1 For Want of a Printer
Chapter 2 2001: A Hacker’s Odyssey
Chapter 3 A Portrait of the Hacker as a Young Man Chapter 4 Impeach God
Chapter 5 Small Puddle of Freedom
Chapter 6 The Emacs Commune
Chapter 8 St. Ignucius
Chapter 9 The GNU General Public License
Chapter 10 GNU/Linux
Chapter 12 A Brief Journey Through Hacker Hell Chapter 13 Continuing the Fight
Chapter 15 Appendix A : Terminology
Chapter 16 Appendix B Hack, Hackers, and Hacking Chapter 17 Appendix C GNU Free Documentation License (GFDL) Preface
The work of Richard M. Stallman literally speaks for itself. From the documented source code to the published papers to the recorded speeches, few people have expressed as much willingness to lay their thoughts and their work on the line.
Such openness-if one can pardon a momentary un-Stallman adjective-is refreshing. After all, we live in a society that treats information, especially personal information, as a valuable commodity. The question quickly arises. Why would anybody want to part with so much information and yet appear to demand nothing in return?
As we shall see in later chapters, Stallman does not part with his words or his work altruistically. Every program, speech, and on-the-record bon mot comes with a price, albeit not the kind of price most people are used to paying.
I bring this up not as a warning, but as an admission.
As a person who has spent the last year digging up facts on Stallman’s personal history, it’s more than a little intimidating going up against the Stallman oeuvre. “Never pick a fight with a man who buys his ink by the barrel,” goes the old Mark Twain adage. In the case of Stallman, never attempt the definitive biography of a man who trusts his every thought to the public record.
For the readers who have decided to trust a few hours of their time to exploring this book, I can confidently state that there are facts and quotes in here that one won’t find in any Slashdot story or Google search.
Gaining access to these facts involves paying a price, however. In the case of the book version, you can pay for these facts the traditional manner, i.e., by purchasing the book. In the case of the electronic versions, you can pay for these facts in the free software manner. Thanks to the folks at O’Reilly &
Associates, this book is being distributed under the GNU Free Documentation License, meaning you can help to improve the work or create a personalized version and release that version under the same license.
If you are reading an electronic version and prefer to accept the latter payment option, that is, if you want to improve or expand this book for future readers, I welcome your input. Starting in June, 2002, I will be publishing a bare bones HTML version of the book on the web site, http://www.faifzilla.org. My aim is to update it regularly and expand the Free as in Freedom story as events warrant. If you choose to take the latter course, please review Appendix C of this book. It provides a copy of your rights under the GNU Free Documentation License.
For those who just plan to sit back and read, online or elsewhere, I consider your attention an equally valuable form of payment. Don’t be surprised, though, if you, too, find yourself looking for other ways to reward the good will that made this work possible.
One final note: this is a work of journalism, but it is also a work of technical documentation. In the process of writing and editing this book, the editors and I have weighed the comments and factual input of various participants in the story, including Richard Stallman himself. We realize there are many technical details in this story that may benefit from additional or refined information. As this book is released under the GFDL, we are accepting patches just like we would with any free software program. Accepted changes will be posted electronically and will eventually be incorporated into future printed versions of this work. If you would like to contribute to the further improvement of this book, you can reach me at sam@inow.com. Comments and Questions Please address comments and questions concerning this book to the publisher: O’Reilly &
Associates, Inc. 1005 Gravenstein Highway North Sebastopol, CA 95472 (800) 998-9938 (in the United States or Canada) (707) 829-0515 (international/local) (707) 829-0104 (fax) There is a web page for this book, which lists errata, examples, or any additional information. The site also includes a link to a forum where you can discuss the book with the author and other readers. You can access this site at: http://www.oreilly.com/catalog/freedom/ To comment or ask technical questions about this book, send email to: bookquestions@oreilly.com For more information about books, conferences, Resource Centers, and the O’Reilly Network, see the O’Reilly web site at:
http://www.oreilly.com Acknowledgments Special thanks to Henning Gutmann for sticking by this book. Special thanks to Aaron Oas for suggesting the idea to Tracy in the first place. Thanks to Laurie Petrycki, Jeffrey Holcomb, and all the others at O’Reilly & Associates.
Thanks to Tim O’Reilly for backing this book. Thanks to all the first-draft reviewers: Bruce Perens, Eric Raymond, Eric Allman, Jon Orwant, Julie and Gerald Jay Sussman, Hal Abelson, and Guy Steele. I hope you enjoy this typo-free version. Thanks to Alice Lippman for the interviews, cookies, and photographs. Thanks to my family, Steve, Jane, Tish, and Dave. And finally, last but not least: thanks to Richard Stallman for having the guts and endurance to “show us the code.”
Sam Williams
For Want of a Printer
I fear the Greeks. Even when they bring gifts.
–Virgil The Aeneid
The new printer was jammed, again.
Richard M. Stallman, a staff software programmer at the Massachusetts Institute of Technology’s Artificial Intelligence Laboratory (AI Lab), discovered the malfunction the hard way. An hour after sending off a 50-page file to the office laser printer, Stallman, 27, broke off a productive work session to retrieve his documents. Upon arrival, he found only four pages in the printer’s tray. To make matters even more frustrating, the four pages belonged to another user, meaning that Stallman’s print job and the unfinished portion of somebody else’s print job were still trapped somewhere within the electrical plumbing of the lab’s computer network.
Waiting for machines is an occupational hazard when you’re a software programmer, so Stallman took his frustration with a grain of salt. Still, the difference between waiting for a machine and waiting on a machine is a sizable one. It wasn’t the first time he’d been forced to stand over the printer, watching pages print out one by one. As a person who spent the bulk of his days and nights improving the efficiency of machines and the software programs that controlled them, Stallman felt a natural urge to open up the machine, look at the guts, and seek out the root of the problem.
Unfortunately, Stallman’s skills as a computer programmer did not extend to the mechanical-engineering realm. As freshly printed documents poured out of the machine, Stallman had a chance to reflect on other ways to circumvent the printing jam problem.
How long ago had it been that the staff members at the AI Lab had welcomed the new printer with open arms?
Stallman wondered. The machine had been a donation from the Xerox Corporation. A cutting edge prototype, it was a modified version of the popular Xerox photocopier.
Only instead of making copies, it relied on software data piped in over a computer network to turn that data into professional-looking documents. Created by engineers at the world-famous Xerox Palo Alto Research Facility, it was, quite simply, an early taste of the desktop-printing revolution that would seize the rest of the computing industry by the end of the decade.
Driven by an instinctual urge to play with the best new equipment, programmers at the AI Lab promptly integrated the new machine into the lab’s sophisticated computing infrastructure. The results had been immediately pleasing. Unlike the lab’s old laser printer, the new Xerox machine was fast. Pages came flying out at a rate of one per second, turning a 20-minute print job into a 2-minute print job. The new machine was also more precise. Circles came out looking like circles, not ovals. Straight lines came out looking like straight lines, not low-amplitude sine waves.
It was, for all intents and purposes, a gift too good to refuse.
It wasn’t until a few weeks after its arrival that the machine’s flaws began to surface. Chief among the drawbacks was the machine’s inherent susceptibility to paper jams. Engineering-minded programmers quickly understood the reason behind the flaw. As a photocopier, the machine generally required the direct oversight of a human operator. Figuring that these human operators would always be on hand to fix a paper jam, if it occurred, Xerox engineers had devoted their time and energies to eliminating other pesky problems.
In engineering terms, user diligence was built into the system.
In modifying the machine for printer use, Xerox engineers had changed the user-machine relationship in a subtle but profound way. Instead of making the machine subservient to an individual human operator, they made it subservient to an entire networked population of human operators. Instead of standing directly over the machine, a human user on one end of the network sent his print command through an extended bucket-brigade of machines, expecting the desired content to arrive at the targeted destination and in proper form. It wasn’t until he finally
Comments (0)