├── KL10_1979.eps ├── KL10_1979.jpg ├── LICENSE ├── Makefile ├── README.md ├── appendix.tex ├── chap01.tex ├── chap02.tex ├── chap03.tex ├── chap04.tex ├── chap05.tex ├── chap06.tex ├── chap07.tex ├── chap08.tex ├── chap09.tex ├── chap10.tex ├── chap11.tex ├── chap12.tex ├── chap13.tex ├── colophon.tex ├── copyright.tex ├── epilogue.tex ├── faif-2.0.tex ├── faifv2.tex ├── gfdl.tex ├── names.txt ├── preface-williams.tex ├── rms-preface.tex ├── stignucius.eps └── stignucius.jpg /KL10_1979.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lifanxi/free-as-in-freedom-zh-cn/34a15dfb02412e64d78d869bb252fcba9d9b84ef/KL10_1979.jpg -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | 2 | GNU Free Documentation License 3 | Version 1.3, 3 November 2008 4 | 5 | 6 | Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. 7 | 8 | Everyone is permitted to copy and distribute verbatim copies 9 | of this license document, but changing it is not allowed. 10 | 11 | 0. PREAMBLE 12 | 13 | The purpose of this License is to make a manual, textbook, or other 14 | functional and useful document "free" in the sense of freedom: to 15 | assure everyone the effective freedom to copy and redistribute it, 16 | with or without modifying it, either commercially or noncommercially. 17 | Secondarily, this License preserves for the author and publisher a way 18 | to get credit for their work, while not being considered responsible 19 | for modifications made by others. 20 | 21 | This License is a kind of "copyleft", which means that derivative 22 | works of the document must themselves be free in the same sense. It 23 | complements the GNU General Public License, which is a copyleft 24 | license designed for free software. 25 | 26 | We have designed this License in order to use it for manuals for free 27 | software, because free software needs free documentation: a free 28 | program should come with manuals providing the same freedoms that the 29 | software does. But this License is not limited to software manuals; 30 | it can be used for any textual work, regardless of subject matter or 31 | whether it is published as a printed book. We recommend this License 32 | principally for works whose purpose is instruction or reference. 33 | 34 | 35 | 1. APPLICABILITY AND DEFINITIONS 36 | 37 | This License applies to any manual or other work, in any medium, that 38 | contains a notice placed by the copyright holder saying it can be 39 | distributed under the terms of this License. Such a notice grants a 40 | world-wide, royalty-free license, unlimited in duration, to use that 41 | work under the conditions stated herein. The "Document", below, 42 | refers to any such manual or work. Any member of the public is a 43 | licensee, and is addressed as "you". You accept the license if you 44 | copy, modify or distribute the work in a way requiring permission 45 | under copyright law. 46 | 47 | A "Modified Version" of the Document means any work containing the 48 | Document or a portion of it, either copied verbatim, or with 49 | modifications and/or translated into another language. 50 | 51 | A "Secondary Section" is a named appendix or a front-matter section of 52 | the Document that deals exclusively with the relationship of the 53 | publishers or authors of the Document to the Document's overall 54 | subject (or to related matters) and contains nothing that could fall 55 | directly within that overall subject. (Thus, if the Document is in 56 | part a textbook of mathematics, a Secondary Section may not explain 57 | any mathematics.) The relationship could be a matter of historical 58 | connection with the subject or with related matters, or of legal, 59 | commercial, philosophical, ethical or political position regarding 60 | them. 61 | 62 | The "Invariant Sections" are certain Secondary Sections whose titles 63 | are designated, as being those of Invariant Sections, in the notice 64 | that says that the Document is released under this License. If a 65 | section does not fit the above definition of Secondary then it is not 66 | allowed to be designated as Invariant. The Document may contain zero 67 | Invariant Sections. If the Document does not identify any Invariant 68 | Sections then there are none. 69 | 70 | The "Cover Texts" are certain short passages of text that are listed, 71 | as Front-Cover Texts or Back-Cover Texts, in the notice that says that 72 | the Document is released under this License. A Front-Cover Text may 73 | be at most 5 words, and a Back-Cover Text may be at most 25 words. 74 | 75 | A "Transparent" copy of the Document means a machine-readable copy, 76 | represented in a format whose specification is available to the 77 | general public, that is suitable for revising the document 78 | straightforwardly with generic text editors or (for images composed of 79 | pixels) generic paint programs or (for drawings) some widely available 80 | drawing editor, and that is suitable for input to text formatters or 81 | for automatic translation to a variety of formats suitable for input 82 | to text formatters. A copy made in an otherwise Transparent file 83 | format whose markup, or absence of markup, has been arranged to thwart 84 | or discourage subsequent modification by readers is not Transparent. 85 | An image format is not Transparent if used for any substantial amount 86 | of text. A copy that is not "Transparent" is called "Opaque". 87 | 88 | Examples of suitable formats for Transparent copies include plain 89 | ASCII without markup, Texinfo input format, LaTeX input format, SGML 90 | or XML using a publicly available DTD, and standard-conforming simple 91 | HTML, PostScript or PDF designed for human modification. Examples of 92 | transparent image formats include PNG, XCF and JPG. Opaque formats 93 | include proprietary formats that can be read and edited only by 94 | proprietary word processors, SGML or XML for which the DTD and/or 95 | processing tools are not generally available, and the 96 | machine-generated HTML, PostScript or PDF produced by some word 97 | processors for output purposes only. 98 | 99 | The "Title Page" means, for a printed book, the title page itself, 100 | plus such following pages as are needed to hold, legibly, the material 101 | this License requires to appear in the title page. For works in 102 | formats which do not have any title page as such, "Title Page" means 103 | the text near the most prominent appearance of the work's title, 104 | preceding the beginning of the body of the text. 105 | 106 | The "publisher" means any person or entity that distributes copies of 107 | the Document to the public. 108 | 109 | A section "Entitled XYZ" means a named subunit of the Document whose 110 | title either is precisely XYZ or contains XYZ in parentheses following 111 | text that translates XYZ in another language. (Here XYZ stands for a 112 | specific section name mentioned below, such as "Acknowledgements", 113 | "Dedications", "Endorsements", or "History".) To "Preserve the Title" 114 | of such a section when you modify the Document means that it remains a 115 | section "Entitled XYZ" according to this definition. 116 | 117 | The Document may include Warranty Disclaimers next to the notice which 118 | states that this License applies to the Document. These Warranty 119 | Disclaimers are considered to be included by reference in this 120 | License, but only as regards disclaiming warranties: any other 121 | implication that these Warranty Disclaimers may have is void and has 122 | no effect on the meaning of this License. 123 | 124 | 2. VERBATIM COPYING 125 | 126 | You may copy and distribute the Document in any medium, either 127 | commercially or noncommercially, provided that this License, the 128 | copyright notices, and the license notice saying this License applies 129 | to the Document are reproduced in all copies, and that you add no 130 | other conditions whatsoever to those of this License. You may not use 131 | technical measures to obstruct or control the reading or further 132 | copying of the copies you make or distribute. However, you may accept 133 | compensation in exchange for copies. If you distribute a large enough 134 | number of copies you must also follow the conditions in section 3. 135 | 136 | You may also lend copies, under the same conditions stated above, and 137 | you may publicly display copies. 138 | 139 | 140 | 3. COPYING IN QUANTITY 141 | 142 | If you publish printed copies (or copies in media that commonly have 143 | printed covers) of the Document, numbering more than 100, and the 144 | Document's license notice requires Cover Texts, you must enclose the 145 | copies in covers that carry, clearly and legibly, all these Cover 146 | Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on 147 | the back cover. Both covers must also clearly and legibly identify 148 | you as the publisher of these copies. The front cover must present 149 | the full title with all words of the title equally prominent and 150 | visible. You may add other material on the covers in addition. 151 | Copying with changes limited to the covers, as long as they preserve 152 | the title of the Document and satisfy these conditions, can be treated 153 | as verbatim copying in other respects. 154 | 155 | If the required texts for either cover are too voluminous to fit 156 | legibly, you should put the first ones listed (as many as fit 157 | reasonably) on the actual cover, and continue the rest onto adjacent 158 | pages. 159 | 160 | If you publish or distribute Opaque copies of the Document numbering 161 | more than 100, you must either include a machine-readable Transparent 162 | copy along with each Opaque copy, or state in or with each Opaque copy 163 | a computer-network location from which the general network-using 164 | public has access to download using public-standard network protocols 165 | a complete Transparent copy of the Document, free of added material. 166 | If you use the latter option, you must take reasonably prudent steps, 167 | when you begin distribution of Opaque copies in quantity, to ensure 168 | that this Transparent copy will remain thus accessible at the stated 169 | location until at least one year after the last time you distribute an 170 | Opaque copy (directly or through your agents or retailers) of that 171 | edition to the public. 172 | 173 | It is requested, but not required, that you contact the authors of the 174 | Document well before redistributing any large number of copies, to 175 | give them a chance to provide you with an updated version of the 176 | Document. 177 | 178 | 179 | 4. MODIFICATIONS 180 | 181 | You may copy and distribute a Modified Version of the Document under 182 | the conditions of sections 2 and 3 above, provided that you release 183 | the Modified Version under precisely this License, with the Modified 184 | Version filling the role of the Document, thus licensing distribution 185 | and modification of the Modified Version to whoever possesses a copy 186 | of it. In addition, you must do these things in the Modified Version: 187 | 188 | A. Use in the Title Page (and on the covers, if any) a title distinct 189 | from that of the Document, and from those of previous versions 190 | (which should, if there were any, be listed in the History section 191 | of the Document). You may use the same title as a previous version 192 | if the original publisher of that version gives permission. 193 | B. List on the Title Page, as authors, one or more persons or entities 194 | responsible for authorship of the modifications in the Modified 195 | Version, together with at least five of the principal authors of the 196 | Document (all of its principal authors, if it has fewer than five), 197 | unless they release you from this requirement. 198 | C. State on the Title page the name of the publisher of the 199 | Modified Version, as the publisher. 200 | D. Preserve all the copyright notices of the Document. 201 | E. Add an appropriate copyright notice for your modifications 202 | adjacent to the other copyright notices. 203 | F. Include, immediately after the copyright notices, a license notice 204 | giving the public permission to use the Modified Version under the 205 | terms of this License, in the form shown in the Addendum below. 206 | G. Preserve in that license notice the full lists of Invariant Sections 207 | and required Cover Texts given in the Document's license notice. 208 | H. Include an unaltered copy of this License. 209 | I. Preserve the section Entitled "History", Preserve its Title, and add 210 | to it an item stating at least the title, year, new authors, and 211 | publisher of the Modified Version as given on the Title Page. If 212 | there is no section Entitled "History" in the Document, create one 213 | stating the title, year, authors, and publisher of the Document as 214 | given on its Title Page, then add an item describing the Modified 215 | Version as stated in the previous sentence. 216 | J. Preserve the network location, if any, given in the Document for 217 | public access to a Transparent copy of the Document, and likewise 218 | the network locations given in the Document for previous versions 219 | it was based on. These may be placed in the "History" section. 220 | You may omit a network location for a work that was published at 221 | least four years before the Document itself, or if the original 222 | publisher of the version it refers to gives permission. 223 | K. For any section Entitled "Acknowledgements" or "Dedications", 224 | Preserve the Title of the section, and preserve in the section all 225 | the substance and tone of each of the contributor acknowledgements 226 | and/or dedications given therein. 227 | L. Preserve all the Invariant Sections of the Document, 228 | unaltered in their text and in their titles. Section numbers 229 | or the equivalent are not considered part of the section titles. 230 | M. Delete any section Entitled "Endorsements". Such a section 231 | may not be included in the Modified Version. 232 | N. Do not retitle any existing section to be Entitled "Endorsements" 233 | or to conflict in title with any Invariant Section. 234 | O. Preserve any Warranty Disclaimers. 235 | 236 | If the Modified Version includes new front-matter sections or 237 | appendices that qualify as Secondary Sections and contain no material 238 | copied from the Document, you may at your option designate some or all 239 | of these sections as invariant. To do this, add their titles to the 240 | list of Invariant Sections in the Modified Version's license notice. 241 | These titles must be distinct from any other section titles. 242 | 243 | You may add a section Entitled "Endorsements", provided it contains 244 | nothing but endorsements of your Modified Version by various 245 | parties--for example, statements of peer review or that the text has 246 | been approved by an organization as the authoritative definition of a 247 | standard. 248 | 249 | You may add a passage of up to five words as a Front-Cover Text, and a 250 | passage of up to 25 words as a Back-Cover Text, to the end of the list 251 | of Cover Texts in the Modified Version. Only one passage of 252 | Front-Cover Text and one of Back-Cover Text may be added by (or 253 | through arrangements made by) any one entity. If the Document already 254 | includes a cover text for the same cover, previously added by you or 255 | by arrangement made by the same entity you are acting on behalf of, 256 | you may not add another; but you may replace the old one, on explicit 257 | permission from the previous publisher that added the old one. 258 | 259 | The author(s) and publisher(s) of the Document do not by this License 260 | give permission to use their names for publicity for or to assert or 261 | imply endorsement of any Modified Version. 262 | 263 | 264 | 5. COMBINING DOCUMENTS 265 | 266 | You may combine the Document with other documents released under this 267 | License, under the terms defined in section 4 above for modified 268 | versions, provided that you include in the combination all of the 269 | Invariant Sections of all of the original documents, unmodified, and 270 | list them all as Invariant Sections of your combined work in its 271 | license notice, and that you preserve all their Warranty Disclaimers. 272 | 273 | The combined work need only contain one copy of this License, and 274 | multiple identical Invariant Sections may be replaced with a single 275 | copy. If there are multiple Invariant Sections with the same name but 276 | different contents, make the title of each such section unique by 277 | adding at the end of it, in parentheses, the name of the original 278 | author or publisher of that section if known, or else a unique number. 279 | Make the same adjustment to the section titles in the list of 280 | Invariant Sections in the license notice of the combined work. 281 | 282 | In the combination, you must combine any sections Entitled "History" 283 | in the various original documents, forming one section Entitled 284 | "History"; likewise combine any sections Entitled "Acknowledgements", 285 | and any sections Entitled "Dedications". You must delete all sections 286 | Entitled "Endorsements". 287 | 288 | 289 | 6. COLLECTIONS OF DOCUMENTS 290 | 291 | You may make a collection consisting of the Document and other 292 | documents released under this License, and replace the individual 293 | copies of this License in the various documents with a single copy 294 | that is included in the collection, provided that you follow the rules 295 | of this License for verbatim copying of each of the documents in all 296 | other respects. 297 | 298 | You may extract a single document from such a collection, and 299 | distribute it individually under this License, provided you insert a 300 | copy of this License into the extracted document, and follow this 301 | License in all other respects regarding verbatim copying of that 302 | document. 303 | 304 | 305 | 7. AGGREGATION WITH INDEPENDENT WORKS 306 | 307 | A compilation of the Document or its derivatives with other separate 308 | and independent documents or works, in or on a volume of a storage or 309 | distribution medium, is called an "aggregate" if the copyright 310 | resulting from the compilation is not used to limit the legal rights 311 | of the compilation's users beyond what the individual works permit. 312 | When the Document is included in an aggregate, this License does not 313 | apply to the other works in the aggregate which are not themselves 314 | derivative works of the Document. 315 | 316 | If the Cover Text requirement of section 3 is applicable to these 317 | copies of the Document, then if the Document is less than one half of 318 | the entire aggregate, the Document's Cover Texts may be placed on 319 | covers that bracket the Document within the aggregate, or the 320 | electronic equivalent of covers if the Document is in electronic form. 321 | Otherwise they must appear on printed covers that bracket the whole 322 | aggregate. 323 | 324 | 325 | 8. TRANSLATION 326 | 327 | Translation is considered a kind of modification, so you may 328 | distribute translations of the Document under the terms of section 4. 329 | Replacing Invariant Sections with translations requires special 330 | permission from their copyright holders, but you may include 331 | translations of some or all Invariant Sections in addition to the 332 | original versions of these Invariant Sections. You may include a 333 | translation of this License, and all the license notices in the 334 | Document, and any Warranty Disclaimers, provided that you also include 335 | the original English version of this License and the original versions 336 | of those notices and disclaimers. In case of a disagreement between 337 | the translation and the original version of this License or a notice 338 | or disclaimer, the original version will prevail. 339 | 340 | If a section in the Document is Entitled "Acknowledgements", 341 | "Dedications", or "History", the requirement (section 4) to Preserve 342 | its Title (section 1) will typically require changing the actual 343 | title. 344 | 345 | 346 | 9. TERMINATION 347 | 348 | You may not copy, modify, sublicense, or distribute the Document 349 | except as expressly provided under this License. Any attempt 350 | otherwise to copy, modify, sublicense, or distribute it is void, and 351 | will automatically terminate your rights under this License. 352 | 353 | However, if you cease all violation of this License, then your license 354 | from a particular copyright holder is reinstated (a) provisionally, 355 | unless and until the copyright holder explicitly and finally 356 | terminates your license, and (b) permanently, if the copyright holder 357 | fails to notify you of the violation by some reasonable means prior to 358 | 60 days after the cessation. 359 | 360 | Moreover, your license from a particular copyright holder is 361 | reinstated permanently if the copyright holder notifies you of the 362 | violation by some reasonable means, this is the first time you have 363 | received notice of violation of this License (for any work) from that 364 | copyright holder, and you cure the violation prior to 30 days after 365 | your receipt of the notice. 366 | 367 | Termination of your rights under this section does not terminate the 368 | licenses of parties who have received copies or rights from you under 369 | this License. If your rights have been terminated and not permanently 370 | reinstated, receipt of a copy of some or all of the same material does 371 | not give you any rights to use it. 372 | 373 | 374 | 10. FUTURE REVISIONS OF THIS LICENSE 375 | 376 | The Free Software Foundation may publish new, revised versions of the 377 | GNU Free Documentation License from time to time. Such new versions 378 | will be similar in spirit to the present version, but may differ in 379 | detail to address new problems or concerns. See 380 | http://www.gnu.org/copyleft/. 381 | 382 | Each version of the License is given a distinguishing version number. 383 | If the Document specifies that a particular numbered version of this 384 | License "or any later version" applies to it, you have the option of 385 | following the terms and conditions either of that specified version or 386 | of any later version that has been published (not as a draft) by the 387 | Free Software Foundation. If the Document does not specify a version 388 | number of this License, you may choose any version ever published (not 389 | as a draft) by the Free Software Foundation. If the Document 390 | specifies that a proxy can decide which future versions of this 391 | License can be used, that proxy's public statement of acceptance of a 392 | version permanently authorizes you to choose that version for the 393 | Document. 394 | 395 | 11. RELICENSING 396 | 397 | "Massive Multiauthor Collaboration Site" (or "MMC Site") means any 398 | World Wide Web server that publishes copyrightable works and also 399 | provides prominent facilities for anybody to edit those works. A 400 | public wiki that anybody can edit is an example of such a server. A 401 | "Massive Multiauthor Collaboration" (or "MMC") contained in the site 402 | means any set of copyrightable works thus published on the MMC site. 403 | 404 | "CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 405 | license published by Creative Commons Corporation, a not-for-profit 406 | corporation with a principal place of business in San Francisco, 407 | California, as well as future copyleft versions of that license 408 | published by that same organization. 409 | 410 | "Incorporate" means to publish or republish a Document, in whole or in 411 | part, as part of another Document. 412 | 413 | An MMC is "eligible for relicensing" if it is licensed under this 414 | License, and if all works that were first published under this License 415 | somewhere other than this MMC, and subsequently incorporated in whole or 416 | in part into the MMC, (1) had no cover texts or invariant sections, and 417 | (2) were thus incorporated prior to November 1, 2008. 418 | 419 | The operator of an MMC Site may republish an MMC contained in the site 420 | under CC-BY-SA on the same site at any time before August 1, 2009, 421 | provided the MMC is eligible for relicensing. 422 | 423 | 424 | ADDENDUM: How to use this License for your documents 425 | 426 | To use this License in a document you have written, include a copy of 427 | the License in the document and put the following copyright and 428 | license notices just after the title page: 429 | 430 | Copyright (c) YEAR YOUR NAME. 431 | Permission is granted to copy, distribute and/or modify this document 432 | under the terms of the GNU Free Documentation License, Version 1.3 433 | or any later version published by the Free Software Foundation; 434 | with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. 435 | A copy of the license is included in the section entitled "GNU 436 | Free Documentation License". 437 | 438 | If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, 439 | replace the "with...Texts." line with this: 440 | 441 | with the Invariant Sections being LIST THEIR TITLES, with the 442 | Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. 443 | 444 | If you have Invariant Sections without Cover Texts, or some other 445 | combination of the three, merge those two alternatives to suit the 446 | situation. 447 | 448 | If your document contains nontrivial examples of program code, we 449 | recommend releasing these examples in parallel under your choice of 450 | free software license, such as the GNU General Public License, 451 | to permit their use in free software. 452 | -------------------------------------------------------------------------------- /Makefile: -------------------------------------------------------------------------------- 1 | all: pdf html 2 | 3 | html: 4 | htxelatex faif-2.0.tex 5 | pdf: 6 | xelatex faif-2.0.tex 7 | clean: 8 | rm -f *.html *.pdf 9 | rm -f *.log *.aux 10 | rm -f faif-2.0.4ct faif-2.0.4tc faif-2.0.css faif-2.0.dvi faif-2.0.ent faif-2.0.xref 11 | rm -f faif-2.0.fdb_latexmk faif-2.0.fls faif-2.0.idv faif-2.0.idx faif-2.0.ilg 12 | rm -f faif-2.0.ind faif-2.0.lg faif-2.0.out faif-2.0.tmp faif-2.0.toc faif-2.0.xdv 13 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | free-as-in-freedom-zh-cn 2 | ======================== 3 | -------------------------------------------------------------------------------- /appendix.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | 10 | \chapter{\ifdefined\eng 11 | Appendix A -- Hack, Hackers, and Hacking 12 | \fi 13 | \ifdefined\chs 14 | 附录 A -- 黑客的三层含义 15 | \fi} \label{Appendix A} 16 | 17 | \ifdefined\eng 18 | To understand the full meaning of the word ``hacker,'' it helps to examine the word's etymology over the years. 19 | \fi 20 | 21 | \ifdefined\chs 22 | 要理解“黑客”一词内在的含义，需要追朔这个词的词源和这么多年来的演化过程。 23 | \fi 24 | 25 | \ifdefined\eng 26 | \textit{The New Hacker Dictionary}, an online compendium of software-programmer jargon, officially lists nine different connotations of the word ``hack'' and a similar number for ``hacker.'' Then again, the same publication also includes an accompanying essay that quotes Phil Agre, an MIT hacker who warns readers not to be fooled by the word's perceived flexibility. ``Hack has only one meaning,'' argues Agre. ``An extremely subtle and profound one which defies articulation.'' Richard Stallman tries to articulate it with the phrase, ``Playful cleverness.'' 27 | \fi 28 | 29 | \ifdefined\chs 30 | 在\textit{新黑客词典}这本在线的软件程序员专业术语词典中，对“Hack”一词列出了9种不同的含义，“Hacker”一词也有相对应的多种含义。同时，上面也引用了一段麻省理工学院的黑客费尔·阿格雷所撰写的短文，这篇文篇提醒读者不要被这个词给人的第一印象所迷惑。“Hack这个词只有一种意思，”阿格雷争辩道，“这个意思非常微妙和有深度，难以用语言来描述。”理查德·斯托曼把这个词表述为一个短语：“顽皮的小聪明”。 31 | \fi 32 | 33 | \ifdefined\eng 34 | Regardless of the width or narrowness of the definition, most modern hackers trace the word back to MIT, where the term bubbled up as popular item of student jargon in the early 1950s. In 1990 the MIT Museum put together a journal documenting the hacking phenomenon. According to the journal, students who attended the institute during the fifties used the word ``hack'' the way a modern student might use the word ``goof.'' Hanging a jalopy out a dormitory window was a ``hack,'' but anything harsh or malicious -- e.g., egging a rival dorm's windows or defacing a campus statue -- fell outside the bounds. Implicit within the definition of ``hack'' was a spirit of harmless, creative fun. 35 | \fi 36 | 37 | \ifdefined\chs 38 | 不管是讨论这个词的狭义定义还是广义定义，大部分现代的黑客都会把这个词追朔到麻省理工学院，从20世纪50年代起，这个词就成为学生们互相交流时的使用的一句黑话。1990年，麻省理工学院博物馆还发表了一篇有关黑客现象的论文。根据这篇论文的描述，50年代时，这个学校的学生们使用“Hack”这个词的方式与现在的学生使用“Goof（混混）”一词的含义类似。在宿舍的窗户上挂上一个破飞机的行为就可以算是Hack。但是，任何残忍的或恶意的行为就不能算是Hack，比如怂恿另人去打破宿舍窗户或损坏学院的雕像。“Hack”一词内在含义是在不损害他人的前提下寻找创新点和乐趣的精神。 39 | \fi 40 | 41 | \ifdefined\eng 42 | This spirit would inspire the word's gerund form: ``hacking.'' A 1950s student who spent the better part of the afternoon talking on the phone or dismantling a radio might describe the activity as ``hacking.'' Again, a modern speaker would substitute the verb form of ``goof'' -- ``goofing'' or ``goofing off'' -- to describe the same activity. 43 | \fi 44 | 45 | \ifdefined\chs 46 | 这种精神赋于了Hack这个词的动名词形式“Hacking”更多活力。在20世纪50年代，如果一个学生花上大半天的时间打电话或拆装收音机，这样行为就可以被称作是“Hacking”。而在现代，人们通常会用“Goof”一词的动词形式“Goofing”或“Goofing Off”来描述这类行为。 47 | \fi 48 | 49 | \ifdefined\eng 50 | As the 1950s progressed, the word ``hack'' acquired a sharper, more rebellious edge. The MIT of the 1950s was overly competitive, and hacking emerged as both a reaction to and extension of that competitive culture. Goofs and pranks suddenly became a way to blow off steam, thumb one's nose at campus administration, and indulge creative thinking and behavior stifled by the Institute's rigorous undergraduate curriculum. With its myriad hallways and underground steam tunnels, the Institute offered plenty of exploration opportunities for the student undaunted by locked doors and ``No Trespassing'' signs. Students began to refer to their off-limits explorations as ``tunnel hacking.'' Above ground, the campus phone system offered similar opportunities. Through casual experimentation and due diligence, students learned how to perform humorous tricks. Drawing inspiration from the more traditional pursuit of tunnel hacking, students quickly dubbed this new activity ``phone hacking.'' 51 | \fi 52 | 53 | \ifdefined\chs 54 | 经过整个50年代的演化，“Hack”这个词的含义变得更加尖锐和反叛。50年代的麻省理工学院校园里充满了竞争，而且黑客的出现，正是这种竞争文化的产物和延续。Goof和Pranks（喜欢恶作剧的人）突然成为学生们发泄多余精力的方式，他们甚至会跑去学校的教务处去做鬼脸，沉溺于各种稀奇古怪的想法和被繁重的研究生课程所遏制的行为。学院众多走廊和地下蒸气管道提供了无畏于紧闭的大们和“禁止进入”标识的学生们足够多探索的机会。学生们开始把这种不被规章制度允许的探索称为“地道黑客”。在地面上，校园的电话系统也提供了类似的探索机会。通过业余的实验和一些专业的研究，学生找到一些恶作剧的办法。学生们从相对古老的“地道黑客”活动中获得了灵感，很快就参与到了这种新型的“电话黑客”活动中。 55 | \fi 56 | 57 | \ifdefined\eng 58 | The combined emphasis on creative play and restriction-free exploration would serve as the basis for the future mutations of the hacking term. The first self-described computer hackers of the 1960s MIT campus originated from a late 1950s student group called the Tech Model Railroad Club. A tight clique within the club was the Signals and Power (S\&P) Committee -- the group behind the railroad club's electrical circuitry system. The system was a sophisticated assortment of relays and switches similar to the kind that controlled the local campus phone system. To control it, a member of the group simply dialed in commands via a connected phone and watched the trains do his bidding. 59 | \fi 60 | 61 | \ifdefined\chs 62 | 强调创新游戏和无限制的探索活动，成为后来黑客活动的文化基础。20世纪60年代出现了一些最早自称为是计算机黑客的人，他们来自麻省理工学院里一个起源于50年代末期、名为铁路科技模型俱乐部（Tech Model Railroad Clus）的学生组织。这个俱乐部中有一个紧密的小团队叫做“信号与电源（S\&P）委员会”，是这个俱乐部的电子电路系统的主要负责团队。这个系统是一个由继电器和开关组成的复杂系统，有点像当时学校电话的控制系统。俱乐部的成员只须通过电话拨打一些特定的号码就可以控制火车的运行。 63 | \fi 64 | 65 | \ifdefined\eng 66 | The nascent electrical engineers responsible for building and maintaining this system saw their activity as similar in spirit to phone hacking. Adopting the hacking term, they began refining it even further. From the S\&P hacker point of view, using one less relay to operate a particular stretch of track meant having one more relay for future play. Hacking subtly shifted from a synonym for idle play to a synonym for idle play that improved the overall performance or efficiency of the club's railroad system at the same time. Soon S\&P committee members proudly referred to the entire activity of improving and reshaping the track's underlying circuitry as ``hacking'' and to the people who did it as ``hackers.'' 67 | \fi 68 | 69 | \ifdefined\chs 70 | 负责建造和维护这套系统的电子工程爱好者们把这样的活动认为是与电话黑客活动一脉相成。他们不但接受了黑客这个概念，而且还把它变得更为完善。从S\&P黑客的观点来看，如果某一段火车铁轨的控制电路中可以少用一个继电器，就意味着可以节省一个继电器供以后使用。黑客这个词的含义渐渐从“闲玩”的同义词演化成了在闲玩的同时去提高俱乐部的铁路系统的整体性能和效率。不久以后，S\&P委员会的成员就自豪的宣布，把改进和重构铁路的底层电路的活动称为“黑客活动”，而参与这样活动的人就是“黑客”。 71 | \fi 72 | 73 | \ifdefined\eng 74 | Given their affinity for sophisticated electronics -- not to mention the traditional MIT-student disregard for closed doors and ``No Trespassing'' signs -- it didn't take long before the hackers caught wind of a new machine on campus. Dubbed the TX-0, the machine was one of the first commercially marketed computers. By the end of the 1950s, the entire S\&P clique had migrated en masse over to the TX-0 control room, bringing the spirit of creative play with them. The wide-open realm of computer programming would encourage yet another mutation in etymology. ``To hack'' no longer meant soldering unusual looking circuits, but cobbling together software programs with little regard to ``official'' methods or software-writing procedures. It also meant improving the efficiency and speed of already-existing programs that tended to hog up machine resources. True to the word's roots, it also meant writing programs that served no other purpose than to amuse or entertain. 75 | \fi 76 | 77 | \ifdefined\chs 78 | 复杂的电子电路对黑客们有着天然的亲和力，抛开那些无视紧锁的大门和“禁止进入”标识的传统的麻省理工学院的学生，新一代的黑客们很快就在校园中找到了一种新的玩具。这种被称为TX-0的机器，是最早进入商用市场的计算机之一。到了20世纪50年代末，整个S\&P的团队都已经把兴趣转移到TX-0的控制室里，用他们的创新精神来折腾这个机器。从那时起，计算机程序设计领域开始进入“黑客”一词的词源。“黑客行为”不再是指焊接一些看起来很奇怪的电路板，而是更多的是与软件程序开发联系起来，还包括少许“正式”的软件开发方法或过程。它同样意味着提高效率和改进现有程序让它们运行的更快，因为只有这样才能节省更多的系统资源。从词源上来讲，这个词也指仅仅为了好玩或娱乐而编写一些没有实质性用途的程序。 79 | \fi 80 | 81 | \ifdefined\eng 82 | A classic example of this expanded hacking definition is the game Spacewar, the first computer-based video game. Developed by MIT hackers in the early 1960s, Spacewar had all the traditional hacking definitions: it was goofy and random, serving little useful purpose other than providing a nightly distraction for the dozen or so hackers who delighted in playing it. From a software perspective, however, it was a monumental testament to innovation of programming skill. It was also completely free. Because hackers had built it for fun, they saw no reason to guard their creation, sharing it extensively with other programmers. By the end of the 1960s, Spacewar had become a diversion for programmers around the world, if they had the (then rather rare) graphical displays. 83 | \fi 84 | 85 | \ifdefined\chs 86 | “空间大战（Spacewar）”游戏是体现这种黑客定义的经典例子，这是世界上第一个在电脑上运行的交互式的视频游戏。早在20世纪60年代，麻省理工学院的黑客们就开发出了这个游戏，“空间大战”游戏诠释了所有传统黑客的定义：它既无聊又随机，除了可以让一群黑客们通宵达旦的娱乐外，没有什么实质性的用途。从软件的观点来说，它倒也算是程序开发技能上的一次伟大的创新。同时，它也是一个完全自由的软件。由于黑客们只是为了好玩而设计了它，所以他们觉得没有什么理由要去刻意保护这样的创作成果。因此，这个游戏可以在程序员之间广为分享。到了20世纪60年代末，“空间大战”已经成为全世界大型机程序员们最爱的一种消遣方式。 87 | \fi 88 | 89 | \ifdefined\eng 90 | This notion of collective innovation and communal software ownership distanced the act of computer hacking in the 1960s from the tunnel hacking and phone hacking of the 1950s. The latter pursuits tended to be solo or small-group activities. Tunnel and phone hackers relied heavily on campus lore, but the off-limits nature of their activity discouraged the open circulation of new discoveries. Computer hackers, on the other hand, did their work amid a scientific field biased toward collaboration and the rewarding of innovation. Hackers and ``official'' computer scientists weren't always the best of allies, but in the rapid evolution of the field, the two species of computer programmer evolved a cooperative -- some might say symbiotic -- relationship. 91 | \fi 92 | 93 | \ifdefined\chs 94 | 60年代的计算机黑客与50年代的地道黑客和电话黑客的最大区别，就在于这种合作创新与公有的软件所有权。传统的黑客更崇尚个人或小团体的活动。地道黑客和电话黑客活动与校园里的情况紧密相关，他们这种不被规章制度所允许的活动天然的不鼓励通过公开的交流来分享新的发现。计算机黑客则不同，他们在科学领域中工作，这是一个完全基于协作和鼓励创新的氛围。黑客们与“官方”的计算机科学家并不一定是最好的搭档，但是由于计算机技术的高速发展，这两种计算机程序员之间很快就形成了一种或多或少的合作共生关系。 95 | \fi 96 | 97 | \ifdefined\eng 98 | Hackers had little respect for bureaucrats' rules. They regarded computer security systems that obstructed access to the machine as just another bug, to be worked around or fixed if possible. Thus, breaking security (but not for malicious purposes) was a recognized aspect of hacking in 1970, useful for practical jokes (the victim might say, ``I think someone's hacking me'') as well as for gaining access to the computer. But it was not central to the idea of hacking. Where there was a security obstacle, hackers were proud to display their wits in surmounting it; however, given the choice, as at the MIT AI Lab, they chose to have no obstacle and do other kinds of hacking. Where there is no security, nobody needs to break it. 99 | \fi 100 | 101 | \ifdefined\chs 102 | 黑客们大多都很讨厌官僚的制度。他们把阻碍自由访问计算机的安全系统看作是系统中的一个Bug，只要有机会，就要想办法绕过它或把它修复。因此，在1970年时，绕过安全系统（但不是出于恶意的目的）被看成是一种典型的黑客行为，这样做不但获取了计算机的访问权限，还增加了饭后的谈资（受害者可能会说：“我觉得我被黑了。”）。但这并不是黑客活动的核心理念。黑客们在遇到一些安全系统阻碍时，会发挥自己的才智绕过它们。但是，如果可以选择的话，麻省理工学院人工智能实验室的黑客们更倾向于从一开始就不要构建这样阻碍，从而可以把自己的才智用到更有意义的地方。如果没有所谓的安全系统，也就没有人想着要去破坏它。 103 | \fi 104 | 105 | \ifdefined\eng 106 | It is a testament to the original computer hackers' prodigious skill that later programmers, including Richard M. Stallman, aspired to wear the same hacker mantle. By the mid to late 1970s, the term ``hacker'' had acquired elite connotations. In a general sense, a computer hacker was any person who wrote software code for the sake of writing software code. In the particular sense, however, it was a testament to programming skill. Like the term ``artist,'' the meaning carried tribal overtones. To describe a fellow programmer as a hacker was a sign of respect. To describe oneself as a hacker was a sign of immense personal confidence. Either way, the original looseness of the computer-hacker appellation diminished as computers became more common. 107 | \fi 108 | 109 | \ifdefined\chs 110 | 这是早期计算机黑客们惊人的技能的一种证明，很多后来的程序员，包括理查德·马修·斯托曼，都渴望能够做到这一点。到了70年代中后期，“黑客”这个词又有了更精确的内涵。在一般人看来，计算机黑客是指那些可以为了写代码而写代码的人。他们觉得这是对于编程技能的一种证明。“黑客”一词跟“艺术家”这个词很像，它的涵义超越了它字面上的意思。把一名程序员称为是黑客，是对他的一种尊称，而把自己称为是黑客则表明了极强的自信。不管是哪一种情况，随着计算机的普及，“计算机黑客”这种早年很少见的称谓也变得越来越常见。 111 | \fi 112 | 113 | \ifdefined\eng 114 | As the definition tightened, ``computer'' hacking acquired additional semantic overtones. The hackers at the MIT AI Lab shared many other characteristics, including love of Chinese food, disgust for tobacco smoke, and avoidance of alcohol, tobacco and other addictive drugs. These characteristics became part of some people's understanding of what it meant to be a hacker, and the community exerted an influence on newcomers even though it did not demand conformity. However, these cultural associations disappeared with the AI Lab hacker community. Today, most hackers resemble the surrounding society on these points. 115 | \fi 116 | 117 | \ifdefined\chs 118 | 对“黑客”的定义越来越精确，“计算机”黑客则还有一层超越了字面的涵义。麻省理工学院人工智能实验室的黑客们有一些共同的特质，包括，喜欢吃中国菜、讨厌抽烟、不沾烟、酒和其它一些可能会上瘾的药物。这些特质也渐渐成为一些人心目中对黑客群体的印象，这种印象对于新加入这个群体的人也产生了潜移默化的影响。然而，这些黑客文化在人工智能实验室黑客社区中渐渐的消失了。如今，大部分黑客在这些点上表现通常都与他周围的环境保持一致。 119 | \fi 120 | 121 | \ifdefined\eng 122 | As the hackers at elite institutions such as MIT, Stanford, and Carnegie Mellon conversed about hacks they admired, they also considered the ethics of their activity, and began to speak openly of a ``hacker ethic'': the yet-unwritten rules that governed a hacker's day-to-day behavior. In the 1984 book \textit{Hackers}, author Steven Levy, after much research and consultation, codified the hacker ethic as five core hacker tenets. 123 | \fi 124 | 125 | \ifdefined\chs 126 | 麻省理工学院、斯坦福和卡耐基梅隆大学这样的精英大学中的黑客谈论他们所敬仰的黑客特质时，会谈到有关黑客活动的伦理，并开始公开宣传“黑客伦理”：这些不成文的规定影响着黑客们的日常行为。在1984年出版的《\textit{黑客}》一书中，作者史蒂文·利维在进行了很多研究和咨询以后，把黑客伦理定义为五种核心的黑客信条。 127 | \fi 128 | 129 | \ifdefined\eng 130 | In the 1980s, computer use expanded greatly, and so did security breaking. Mostly it was done by insiders with criminal intent, who were generally not hackers at all. However, occasionally the police and administrators, who defined disobedience as evil, traced a computer ``intrusion'' back to a hacker whose idea of ethics was ``Don't hurt people.'' Journalists published articles in which ``hacking'' meant breaking security, and usually endorsed the administrators' view of the matter. Although books like \textit{Hackers} did much to document the original spirit of exploration that gave rise to the hacking culture, for most newspaper reporters and readers the term ``computer hacker'' became a synonym for ``electronic burglar.'' 131 | \fi 132 | 133 | \ifdefined\chs 134 | 20世纪80年代，计算机开始普及，破坏安全系统的行为也变多了。大部分破坏安全系统的行为都具有某些犯罪动机，实施这些破坏的内鬼其实根本就不能被称作是黑客。然而，警察和计算机管理员都会把破坏规则的行为看成是一种恶意的行为，他们把这种“入侵”计算机的行为追溯到了那些持有“不能伤害别人”理念的黑客身上。一些杂志的报道中，常常会从计算机管理员的视角出发，把“黑客行为”当成是破坏安全系统的同义词。尽管像《\textit{黑客}》这样书用很多的篇幅去介绍黑客精神中的探索本质，并且弘扬黑客文化，但是对于大部分报纸记者和读者仍然把“计算机黑客”当成是“电子盗贼”的同义词。 135 | \fi 136 | 137 | \ifdefined\eng 138 | By the late 1980s, many U.S. teenagers had access to computers. Some were alienated from society; inspired by journalists' distorted picture of ``hacking,'' they expressed their resentment by breaking computer security much as other alienated teens might have done it by breaking windows. They began to call themselves ``hackers,'' but they never learned the MIT hackers' principle against malicious behavior. As younger programmers began employing their computer skills to harmful ends -- creating and disseminating computer viruses, breaking into computer systems for mischief, deliberately causing computers to crash -- the term ``hacker'' acquired a punk, nihilistic edge which attracted more people with similar attitudes. 139 | \fi 140 | 141 | \ifdefined\chs 142 | 到了80年代末，很多美国的青少年都开始有机会接触计算机。他们中的一部分有些叛逆的性格，受到杂志上歪曲了的“黑客”形象的误导，开始通过破坏计算机安全系统来发泄他们的对社会的不满，就像一些人通过砸玻璃来发泄一样。他们自称为“黑客”，但是他们从来没了解过麻省理工学院的黑客们反对恶意行为的信条。一些年轻的程序员开始在一些错误的方向利用他们的计算机才能：制作和传播计算机病毒、恶作剧入侵计算机系统、故意让计算机宕机。“黑客”这个词开始渐渐成为一个反叛、无政府主义的象征，这样的形象吸引了更多不了解黑客本质的人开始走向错误的方向。 143 | \fi 144 | 145 | \ifdefined\eng 146 | Hackers have railed against this perceived misusage of their self-designator for nearly two decades. Stallman, not one to take things lying down, coined the term ``cracking'' for ``security breaking'' so that people could more easily avoid calling it ``hacking.'' But the distinction between hacking and cracking is often misunderstood. These two descriptive terms are not meant to be exclusive. It's not that ``Hacking is here, and cracking is there, and never the twain shall meet.'' Hacking and cracking are different attributes of activities, just as ``young'' and ``tall'' are different attributes of persons. 147 | \fi 148 | 149 | \ifdefined\chs 150 | 黑客们为了改变这种错误的认识已经自发的进行了近二十年的斗争。斯托曼为了解决这个问题，创造了一个新词来表达“破坏计算机安全系统的人”的意思：“骇客”，避免人们错误的使用“黑客”一词。而且，黑客和骇客这两个词的还是常常引起人们的误解。这两个词表达的含义还是有一些重叠的地方，并不是“黑客在这里，骇客在那里，我们水火不容”。黑客行为和骇客行为只是同一种行为的不同层面上的属性，就像“年轻”和“高”是一个人的两个不同层面的属性。 151 | \fi 152 | 153 | \ifdefined\eng 154 | Most hacking does not involve security, so it is not cracking. Most cracking is done for profit or malice and not in a playful spirit, so it is not hacking. Once in a while a single act may qualify as cracking and as hacking, but that is not the usual case. The hacker spirit includes irreverence for rules, but most hacks do not break rules. Cracking is by definition disobedience, but it is not necessarily malicious or harmful. The computer security field distinguishes between ``black hat'' and ``white hat'' crackers -- i.e., crackers who turn toward destructive, malicious ends versus those who probe security in order to fix it. 155 | \fi 156 | 157 | \ifdefined\chs 158 | 其实，大部的黑客活动都与安全无关，所以不能称之为骇客活动。大部分骇客活动都是为了牟取利益或出于恶意，不会是出于“玩”的心态，所以不能称之为黑客活动。在少数情况下，可能会有个别的行为可以同时看成是黑客行为与骇客行为，但大部分情况下都不会是这样。黑客精神中包含对规则的不敬，但大部分黑客并不会去破坏规则。骇客活动从定义上来说就是不守规则，但是也并不一定就是恶意或有害的。在计算机安全领域中还区分“黑帽”骇客和“白帽”骇客，如果一个骇客的目的是搞破坏、恶意的，他就是一个“黑帽”；那些在安全系统中寻找漏洞是为了修复它的骇客，被称作为”白帽”。 159 | \fi 160 | 161 | \ifdefined\eng 162 | The hacker's central principle not to be malicious remains the primary cultural link between the notion of hacking in the early 21st century and hacking in the 1950s. It is important to note that, as the idea of computer hacking has evolved over the last four decades, the original notion of hacking -- i.e., performing pranks or exploring underground tunnels -- remains intact. In the fall of 2000, the MIT Museum paid tribute to the Institute's age-old hacking tradition with a dedicated exhibit, the Hall of Hacks. The exhibit includes a number of photographs dating back to the 1920s, including one involving a mock police cruiser. In 1993, students paid homage to the original MIT notion of hacking by placing the same police cruiser, lights flashing, atop the Institute's main dome. The cruiser's vanity license plate read IHTFP, a popular MIT acronym with many meanings. The most noteworthy version, itself dating back to the pressure-filled world of MIT student life in the 1950s, is ``I hate this fucking place.'' In 1990, however, the Museum used the acronym as a basis for a journal on the history of hacks. Titled \textit{The Journal of the Institute for Hacks, Tomfoolery, and Pranks}, it offers an adept summary of the hacking. 163 | \fi 164 | 165 | \ifdefined\chs 166 | 这种忌讳恶意行为的核心原则成为联系21世纪初的黑客与20世纪50年代的黑客的文化纽带。值得注意的是，在过去的40年中，计算机黑客概念的演化了很多。最初这个词的意思是指有点恶作剧的行为，比如发现一些隐蔽的地道，这层含义现在依然存在。2000年秋天，麻省理工学院博物馆举行了一个专门向古老的黑客传统致敬的展览，名为黑客殿堂。这个展览上展出了很多20世纪20年代的老照片，其中有一张是有人愚弄警察的巡逻车的照片。1993年，有学生向这种行为致敬，把一模一样的巡逻车、警灯放到了学院主楼的圆顶上。巡逻车的仿制车牌上写着IHTFP，这是一个在麻省理工学院很流行的缩写词，包含着很多的含义。其中最引人注意的意思是始创于20世纪50年代麻省理工学院压力最大的时候的流行语，“我憎恨这个鬼地方（I hate this fucing place）”。然而，在1990年，博物馆基于这个缩写词创作了一本期刊：《\textit{黑客、蠢举与恶作剧学报（The Journal of the Institute for Hacks, Tomfoolery, and Pranks）}》，这本期刊的主要内容有是关黑客的历史，它精妙描述了黑客活动的本质。 167 | \fi 168 | 169 | \ifdefined\eng 170 | ``In the culture of hacking, an elegant, simple creation is as highly valued as it is in pure science,'' writes \textit{Boston Globe} reporter Randolph Ryan in a 1993 article attached to the police car exhibit. ``A Hack differs from the ordinary college prank in that the event usually requires careful planning, engineering and finesse, and has an underlying wit and inventiveness,'' Ryan writes. ``The unwritten rule holds that a hack should be good-natured, non-destructive and safe. In fact, hackers sometimes assist in dismantling their own handiwork.'' 171 | \fi 172 | 173 | \ifdefined\chs 174 | “在黑客的文化中，优雅、简洁的创新是被高度评价的，就像在纯科学的领域，”《\textit{波士顿环球报}》的记者伦道夫·赖安在1993年的一篇警车展览相关的文章中写道，“黑客与一般校园中的那些喜欢恶作剧的人在一些需要细致计划、工程化和使用手段的事件中的表现不太一样，他们本质上更为聪明和具有创造力。”Ryan写道，“黑客的本质应该是好的，不能去搞破坏，应该是安全的，这是一条不成文的规则。事实上，黑客们有时也参与破坏他们自己的作品”。 175 | \fi 176 | 177 | \ifdefined\eng 178 | The urge to confine the culture of computer hacking within the same ethical boundaries is well-meaning but impossible. Although most software hacks aspire to the same spirit of elegance and simplicity, the software medium offers less chance for reversibility. Dismantling a police cruiser is easy compared with dismantling an idea, especially an idea whose time has come. 179 | \fi 180 | 181 | \ifdefined\chs 182 | 主张把计算机黑客的文化限定在特定的伦理边界中是一个不错的想法，但却是不太可能的。尽管大部分软件黑客们渴望优雅和简单的精神气质，但是软件媒体很少提供回头的机会。摆脱警察的巡逻车要比破碎一个想法更为容易，尤其是一个出现的正是时候的想法。 183 | \fi 184 | 185 | \ifdefined\eng 186 | Once a vague item of obscure student jargon, the word ``hacker'' has become a linguistic billiard ball, subject to political spin and ethical nuances. Perhaps this is why so many hackers and journalists enjoy using it. We cannot predict how people will use the word in the future. We can, however, decide how we will use it ourselves. Using the term ``cracking'' rather than ``hacking,'' when you mean ``security breaking,'' shows respect for Stallman and all the hackers mentioned in this book, and helps preserve something which all computer users have benefited from: the hacker spirit. 187 | \fi 188 | 189 | \ifdefined\chs 190 | “黑客”这个词曾经只是学生们一个含糊其辞的黑话，现在却成为了一个语言学上的一个台球，服从于政治的束缚和伦理上的差异。这也许就是为什么很多黑客和记者们喜欢使用这个词语的原因。没有人可以预料这个词以后会如何被使用，但是，我们可以决定我们自己如何去使用它。当你在谈论“破坏安全系统”时，请使用“骇客”这个词，而不要使用“黑客”，这样不但可以表现出你对斯托曼和本书中提到的其他黑客们的尊敬，也可以让黑客精神可以不断传承下去，造福更多计算机用户。 191 | \fi 192 | -------------------------------------------------------------------------------- /chap01.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | \chapter{\ifdefined\eng 10 | For Want of a Printer 11 | \fi 12 | \ifdefined\chs 13 | 从一台打印机说起 14 | \fi 15 | } 16 | 17 | \ifdefined\eng 18 | \begin{quotation} 19 | \begin{flushright} 20 | I fear the Greeks. Even when they bring gifts.\\ 21 | -- Virgil, \textit{The Aeneid} 22 | \end{flushright} 23 | \end{quotation} 24 | \fi 25 | 26 | \ifdefined\chs 27 | \begin{quotation} 28 | \begin{flushright} 29 | 我畏惧希腊人，哪怕他们带着礼物来。\\ 30 | ——维吉尔，《\textit{埃涅阿斯纪}》 31 | \end{flushright} 32 | \end{quotation} 33 | \fi 34 | 35 | \ifdefined\eng 36 | The new printer was jammed, again. 37 | \fi 38 | 39 | \ifdefined\chs 40 | 这可是台全新的打印机！怎么又卡纸了？ 41 | \fi 42 | 43 | \ifdefined\eng 44 | 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. 45 | \fi 46 | 47 | \ifdefined\chs 48 | 理查德·M·斯托曼（Richard M. Stallman）刚刚发现了这令他头痛不已的卡纸问题，那年他27岁，是麻省理工学院人工智能实验室一名资深的程序员。一个小时前，他给那台激光打印机提交了一个50页的打印任务，之后，他就忙于其它事务去了。回来时，本想拿到一叠散发着油香的文件，可这会儿，他只能站在那台毫无生机打印机前，直楞楞地看着它，上面，总共才四页并非他想要的文档。换句话说，斯托曼那份50页的文件，外加别人的半份文档，全被卡住了，成了实验室网络上的两个孤魂野鬼。 49 | \fi 50 | 51 | \ifdefined\eng 52 | 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. 53 | \fi 54 | 55 | \ifdefined\chs 56 | 干程序员这行也是有风险的：你总得等着机器干活。不过斯托曼可是个能苦中做乐的人。再怎么说，等着机器干活与盯着机器干活，毕竟是两码事。就说现在吧，斯托曼正盯着打印机，看它慢吞吞地一页一页往外吐纸。这情景对他来说可一点也不陌生。作为一个程序员，他成天都在改进机器和控制这些机器的程序，好让它们更有效率的工作。当下，他恨不得掀开这台打印机，仔细查查究竟是哪出的毛病。 57 | \fi 58 | 59 | \ifdefined\eng 60 | 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. 61 | \fi 62 | 63 | \ifdefined\chs 64 | 可惜，凭编程的能耐，没法解决机械工程的问题。斯托曼只能在重新打印文件的这会功夫，想点别的：能不能用别的办法，绕道解决这个卡纸的问题呢？ 65 | \fi 66 | 67 | \ifdefined\eng 68 | 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 a fast 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. 69 | \fi 70 | 71 | \ifdefined\chs 72 | 这台打印机来人工智能实验室有多久了？斯托曼努力的回忆着。这机器是施乐公司（Xerox Corporation）捐赠的。它可是新一代产品的原型，是从上一代的复印机改进而来。和上一代比，它不再是简单地复印，而是从网络上接收数据，打印成专业品质的文档。它诞生于著名的施乐帕罗奥多研究中心（Xerox Palo Alto Research Facility）。再过大约十年，将会发生一场打印机革命，那时，许多计算机厂商都会投身其中。而这款打印机则是这场革命的先行者。 73 | \fi 74 | 75 | \ifdefined\eng 76 | 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 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. 77 | \fi 78 | 79 | \ifdefined\chs 80 | 人工智能实验室的程序员们，本能般地喜欢折腾这些新酷产品。当初他们麻利地把这打印机请回来，把它和实验室中的各种复杂的计算设备连在了一起,结果甚是喜人。比起以前的打印机，这台新打印机打印速度飞快。平均大约一秒钟打印一页纸。以前要花二十来分钟打印的东西，如今两分钟就解决了。新机器的打印精度也更高了。让它给画个圆，它决不会给你打出个鸡蛋来；让它划条直线，它也绝不会给你拐着弯瞎划拉。 81 | \fi 82 | 83 | \ifdefined\eng 84 | It was, for all intents and purposes, a gift too good to refuse. 85 | \fi 86 | 87 | \ifdefined\chs 88 | 怎么看，这打印机都是份难以拒绝的珍贵礼物。 89 | \fi 90 | 91 | \ifdefined\eng 92 | Once the machine was in use, its flaws began to surface. Chief among the drawbacks was the machine's 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. 93 | \fi 94 | 95 | \ifdefined\chs 96 | 可没过几周，这机器的缺点就逐渐显现了。其中最要命的，就是卡纸问题。凭着工程师的直觉，程序员们很快就洞察出了这问题背后的原因。倘若是一台复印机，它旁边总会站个人直接操作它。遇到卡纸问题，这个人总能立即发现，着手解决，不至于有什么大影响。而施乐公司的那些工程师们则可以把时间和精力，用在其他更棘手的问题上了。用工程师的行话讲：这系统需要用户参与。 97 | \fi 98 | 99 | \ifdefined\eng 100 | 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 went to check up on the final output that he realized how little of it had really been printed. 101 | \fi 102 | 103 | \ifdefined\chs 104 | 如今，施乐公司在复印机的基础之上，设计了这个打印机。这个小小的变化，却使得人机关系发生了微妙而深刻的变化。现在，在同一时刻，这机器不再只服务于一个用户。它要同时给整个网络的用户提供打印服务。这些用户也不再老老实实地站在机器前面，而是坐在网络的另一端，可能还远离打印机，向这台机器发布打印命令，并指望它能按要求完成任务。等这些用户忙过其它事情回过神来，想起打印的文件时，他们才发现，大部分的内容已被一张纸卡住了。 105 | \fi 106 | 107 | \ifdefined\eng 108 | Stallman was hardly the only AI Lab denizen to notice the problem, but he also thought of a remedy. Years before, for the lab's previous printer, Stallman had solved a similar problem by modifying the software program that regulated the printer, on a small PDP-11 machine, as well as the Incompatible Timesharing System that ran on the main PDP-10 computer. Stallman couldn't eliminate paper jams, but he could insert software code that made the PDP-11 check the printer periodically, and report jams back to the PDP-10. Stallman also inserted code on the PDP-10 to notify every user with a waiting print job that the printer was jammed. The notice was simple, something along the lines of ``The printer is jammed, please fix it,'' and because it went out to the people with the most pressing need to fix the problem, chances were that one of them would fix it forthwith. 109 | \fi 110 | 111 | \ifdefined\chs 112 | 斯托曼是人工智能实验室中第一个发现这个问题的人，也是他第一个提出了解决方案。几年前，实验室还用着一台旧打印机，也有类似的问题。这台打印机的控制程序，运行在实验室里的一台PDP-11计算机上。那会儿，斯托曼修改了这个控制程序，解决了这个问题。当然，他没法直接修理打印机来解决卡纸的问题。他只是修改控制程序，让程序定期检查打印机是否工作正常，再把检查结果传给实验室的核心计算机——一台PDP-10。同时，他也修改了运行在PDP-10主机上的“不兼容分时系统（ITS，Incompatible Timesharing System）“，处理这些检查结果。生怕哪个粗心用户忘了去查看打印机，斯托曼还让控制程序在卡纸的时候，向所有等待打印任务的用户发送一条提醒消息。消息简短明确：“打印机被卡住了，请前去维修。”收到这消息的人都是等着要用打印机的，所以问题就迎“人”而解。 113 | \fi 114 | 115 | \ifdefined\eng 116 | As fixes go, Stallman's was oblique but elegant. It didn't fix the mechanical side of the problem, but it did the next best thing by closing the information loop between user and machine. Thanks to a few additional lines of software code, AI Lab employees could eliminate the 10 or 15 minutes wasted each week in running back and forth to check on the printer. In programming terms, Stallman's fix took advantage of the amplified intelligence of the overall network. 117 | \fi 118 | 119 | \ifdefined\chs 120 | 斯托曼这解决方案虽然并不能说很讨巧，但却也漂亮。它没解决打印机机械部件的问题，却提出了一个次优方案：完善人机交互，及早报告问题。多亏了斯托曼加的几行代码，人工智能实验室的员工，不用再跑来跑去地查看打印机状态了。这样，每周起码节省了10到15分钟时间。用编程的术语讲，斯托曼的方案提高了网络的整体智能。 121 | \fi 122 | 123 | \ifdefined\eng 124 | ``If you got that message, you couldn't assume somebody else would fix it,'' says Stallman, recalling the logic. ``You had to go to the printer. A minute or two after the printer got in trouble, the two or three people who got messages arrive to fix the machine. Of those two or three people, one of them, at least, would usually know how to fix the problem.'' 125 | \fi 126 | 127 | \ifdefined\chs 128 | “你要是收到这条消息，你可就坐不住了。你多半等不及别人去解决卡纸问题。”斯托曼回忆着其中的逻辑，“你得亲力亲为，跑到打印机跟前。一两分钟之后，要是问题还没解决，就会聚来两三个人。这其中，总会有个人知道怎么修理。” 129 | \fi 130 | 131 | \ifdefined\eng 132 | Such clever fixes were a trademark of the AI Lab and its indigenous population of programmers. Indeed, the best programmers at the AI Lab disdained the term programmer, preferring the more slangy occupational title of hacker instead. The job title covered a host of activities -- everything from creative mirth making to the improvement of existing software and computer systems. Implicit within the title, however, was the old-fashioned notion of Yankee ingenuity. For a hacker, writing a software program that worked was only the beginning. A hacker would try to display his cleverness (and impress other hackers) by tackling an additional challenge: to make the program particularly fast, small, powerful, elegant, or somehow impressive in a clever way.\endnote{For more on the term ``hacker,'' see \nameref{Appendix A}.} 133 | \fi 134 | 135 | \ifdefined\chs 136 | 类似的巧法子是人工智能实验室的一大特色。尤其在其中的资深程序员之间，屡见不鲜。实际上，那些天才的程序员，不屑于用“程序员”这词。他们更喜欢用圈子里的行话，用“黑客”这个词。这词儿涵盖了不少内容：从抖机灵、甩包袱，到改进现有软件，优化计算机系统。而更深之处，则蕴含着旧时美国移民的智慧。对于黑客来说，有这么一条铁律：从头开发个软件只是小儿科；要想在别人面前展现自己的聪明才智（并让别人对自己留下印象），就得做点更有意思的事：改进一个程序让它体积更小、跑得更快、功能更强，代码更优雅，这才是真本事。\endnote{参考\nameref{Appendix A}，深入了解“黑客”这个词的内在含义。} 137 | \fi 138 | 139 | \ifdefined\eng 140 | Companies like Xerox made it a policy to donate their products (and software) to places where hackers typically congregated. If hackers used these products, they might go to work for the company later on. In the 60s and early 70s, they also sometimes developed programs that were useful for the manufacturer to distribute to other customers. 141 | \fi 142 | 143 | \ifdefined\chs 144 | 这条铁律，恰恰影响着施乐这样的公司，让它们乐意把自己的产品（和配套的软件）捐赠到黑客聚集的地方。要是这些黑客们对这些产品产生了兴趣，他们以后就可能有兴趣去这个公司工作。在20世纪60年代到70年代初，黑客们也常常会开发一些实用的软件，提供给公司发布给其他顾客使用。 145 | \fi 146 | 147 | \ifdefined\eng 148 | When Stallman noticed the jamming tendency in the Xerox laser printer, he thought of applying the old fix or ``hack'' to this printer. In the course of looking up the Xerox laser-printer software, however, Stallman made a troubling discovery. The printer didn't have any software, at least nothing Stallman or a fellow programmer could read. Until then, most companies had made it a form of courtesy to publish source-code files--readable text files that documented the individual software commands that told a machine what to do. Xerox, in this instance, had provided software files only in compiled, or binary, form. If programmers looked at the files, all they would see was an endless stream of ones and zeroes -- gibberish. 149 | \fi 150 | 151 | \ifdefined\chs 152 | 凭着这份礼尚往来的精神，斯托曼在这台新打印机面前并不慌张。他只要找个法子，把以前那套修改方案拿过来，修理修理这机器，或者用圈子里的话说，“黑”它一下，就万事大吉了。可是，他刚找了找这台施乐激光打印机的软件，就碰了一鼻子灰。这打印机根本不提供软件，至少没提供任何给人读的程序代码。要知道，那个时代，大多数公司都会发布软件的源代码（一系列可供人阅读的文本文件，用于详细定义程序的行为）。可当下，施乐公司提供的程序，却只有编译好的可执行文件。程序员倒是可以打开这些文件，可打开之后看见的，全是零和一。除非他们乐意去翻译这些二进制信息，否则这些东西看起来只是一堆胡言乱语。 153 | \fi 154 | 155 | \ifdefined\eng 156 | There are programs, called ``disassemblers,'' to convert the ones and zeroes into low-level machine instructions, but figuring out what those instructions actually ``do'' is a long and hard task, known as ``reverse engineering.'' To reverse engineer this program could have taken more time than five years' worth of jammed printouts. Stallman wasn't desperate enough for that, so he put the problem aside. 157 | \fi 158 | 159 | \ifdefined\chs 160 | 有一种叫作”反汇编器”的程序，可以把这些看不懂的零和一转换成机器底层指令，但是要进一步了解这些指令实际在“做”的事情则是一件费时费力的工作，这样的工作被称作“反向工程”。要想把打印机的控制程序进行反向工程，也许会花去超过五年的时间。卡纸的问题还没有严重到让斯托曼愿意花这么多时间去解决，所以他把这件事放到了一边。 161 | \fi 162 | 163 | \ifdefined\eng 164 | Xerox's unfriendly policy contrasted blatantly with the usual practices of the hacker community. For instance, to develop the program for the PDP-11 that ran the old printer, and the program for another PDP-11 that handled display terminals, the AI Lab needed a cross-assembler program to build PDP-11 programs on the PDP-10 main computer. The lab's hackers could have written one, but Stallman, a Harvard student, found such a program at Harvard's computer lab. That program was written to run on the same kind of computer, the PDP-10, albeit with a different operating system. Stallman never knew who had written the program, since the source code did not say. But he brought a copy back to the AI Lab. He then altered the source code to make it run on the AI Lab's Incompatible Timesharing System (ITS). With no muss and little fuss, the AI Lab got the program it needed for its software infrastructure. Stallman even added a few features not found in the original version, making the program more powerful. ``We wound up using it for several years,'' Stallman says. 165 | \fi 166 | 167 | \ifdefined\chs 168 | 施乐公司看上去不太友好的软件条款与黑客社区所习惯的氛围格格不入。打个比方，如果想为一台老式的打印机开发一个在PDP-11上运行的控制程序，或为另一台PDP-11开始一个处理显示终端的程序，人工智能实验室的黑客们需要在PDP-10主机上运行一个交叉汇编的程序，才能创建出他们需要的程序。他们可以自己从头开发一个这样的交叉汇编程序，但是上哈佛大学上学的斯托曼，在哈佛的计算机实验室中找到了这样一个程序。这个程序都可以在PDP-10这种型号的计算机上运行，即使两台机器上运行的操作系统不同也没有关系。斯托曼并不需要知道这份代码是谁写的，因为源代码中并没有标明。但是他可以把这份代码带到人工智能实验室，通过修改其中的一部分代码，这个程序就可以在人工智能实验室的“不兼容分时系统（ITS）”上运行了。没花多大劲，人工智能实验室就得到了一个可以用于充实他们的软件架构的程序。斯托曼甚至还在程序中加入了一些原来没有的新功能，使程序变得更加强大了。“这个程序我们一直用了很多年。”斯托曼说。 169 | \fi 170 | 171 | \ifdefined\eng 172 | From the perspective of a 1970s-era programmer, the transaction was the software equivalent of a neighbor stopping by to borrow a power tool or a cup of sugar from a neighbor. The only difference was that in borrowing a copy of the software for the AI Lab, Stallman had done nothing to deprive anyone else of the use of the program. If anything, other hackers gained in the process, because Stallman had introduced additional features that other hackers were welcome to borrow back. For instance, Stallman recalls a programmer at the private engineering firm, Bolt, Beranek \& Newman, borrowing the program. He made it run on Twenex and added a few additional features, which Stallman eventually reintegrated into the AI Lab's own source-code archive. The two programmers decided to maintain a common version together, which had the code to run either on ITS or on Twenex at the user's choice. 173 | \fi 174 | 175 | \ifdefined\chs 176 | 对于七十年代的程序员来说，把软件拷贝来拷贝去，就好比从邻居家借碗酱油那么稀松平常。所不同的是，你从邻居那拿了多少酱油，邻居就少了多少。而从别人那里拷贝一个程序出来，并不影响别人继续使用那个程序。要说有影响，也是正面的。因为斯托曼对这程序还加了些功能，别的黑客可以自由地拷来斯托曼改进的程序，这也算是计算机世界的礼尚往来了。后来，有个从Bolt, Beranek \& Newman这家公司来的程序员，拷走了斯托曼的程序，他把这个程序移植到了Twenex系统上，并加上了一些新的功能，斯托曼则又把改进后的程序拷了回来，用回到人工智能实验室里。他们两人打算共同来维护一个通用的版本，这个版本既可以在ITS上运行，也可以在Twenex上运行。 177 | \fi 178 | 179 | \ifdefined\eng 180 | ``A program would develop the way a city develops,'' says Stallman, recalling the software infrastructure of the AI Lab. ``Parts would get replaced and rebuilt. New things would get added on. But you could always look at a certain part and say, `Hmm, by the style, I see this part was written back in the early 60s and this part was written in the mid-1970s.'\hspace{0.01in}'' 181 | \fi 182 | 183 | \ifdefined\chs 184 | “开发一个程序就好比开发一座城市。”斯托曼回忆着人工智能实验室的软件设施：“有些部分会被换掉，有些得重建翻修。新的东西会逐步加进来。可如果你仔细看某个部分，也许会感慨道：‘这块从风格看应该是六十年代早期的；之后的部分估计是七十年代中期完成的。’” 185 | \fi 186 | 187 | \ifdefined\eng 188 | Through this simple system of intellectual accretion, hackers at the AI Lab and other places built up robust creations. Not every programmer participating in this culture described himself as a hacker, but most shared the sentiments of Richard M. Stallman. If a program or software fix was good enough to solve your problems, it was good enough to solve somebody else's problems. Why not share it out of a simple desire for good karma? 189 | \fi 190 | 191 | \ifdefined\chs 192 | 这套简洁的系统得以让知识逐渐积累。这种积累为发明和创造提供了稳固的基石。人工智能实验室以及世界各地的黑客们，都得益于这一系统。参与到这个文化小圈子的程序员，不一定都把自己称为黑客。不过绝大多数人都有着理查德·M·斯托曼那般的情结：要是一个程序或者一个补丁可以解决你自己的问题，它没准也能帮到别人。独乐乐不如众乐乐，何不分享给大家，起码也算积德行善了。 193 | \fi 194 | 195 | \ifdefined\eng 196 | This system of cooperation was being undermined by commercial secrecy and greed, leading to peculiar combinations of secrecy and cooperation. For instance, computer scientists at UC Berkeley had built up a powerful operating system called BSD, based on the Unix system they had obtained from AT\&T. Berkeley made BSD available for the cost of copying a tape, but would only give these tapes to schools that could present a \$50,000 source license obtained from AT\&T. The Berkeley hackers continued to share as much as AT\&T let them, but they had not perceived a conflict between the two practices. 197 | \fi 198 | 199 | \ifdefined\chs 200 | 这种合作的精神不断的被商业秘密限制和贪婪之心所侵蚀，变成了一种商业秘密和合作精神的古怪搭配。加州大学伯克利分校的计算机科学家们基于他们从AT\&T得到的Unix系统开发了一个名为BSD的操作系统。伯克利向那些已经向AT\&T支付了50000美元软件许可证费用的学院提供BSD系统，仅仅只收取复制磁带的成本费。伯克利的黑客们还是尽可能的发扬分享合作的精神，但只能在AT\&T所允许的范围内，并且他们还没有意识这两种不同的模式之间所存在的巨大冲突。 201 | \fi 202 | 203 | \ifdefined\eng 204 | Likewise, Stallman was annoyed that Xerox had not provided the source-code files, but not yet angry. He never thought of asking Xerox for a copy. ``They had already given us the laser printer,'' Stallman says. ``I could not say they owed us something more. Besides, I took for granted that the absence of source code reflected an intentional decision, and that asking them to change it would be futile.'' 205 | \fi 206 | 207 | \ifdefined\chs 208 | 施乐公司不分享源代码的行为虽然让斯托曼感到烦恼，不过倒也没激怒到他。斯托曼在找源代码的过程中，甚至都没想过去联系施乐公司：“人家都送咱打印机了，何必还非得兴师动众地直接管他们要代码呢？再说了，我敢肯定他们不发布源代码是有一种有意的行为，非要找他们要代码也是徒劳的。” 209 | \fi 210 | 211 | \ifdefined\eng 212 | Good news eventually arrived: word had it that a scientist at the computer-science department at Carnegie Mellon University had a copy of the laser printer source code. 213 | \fi 214 | 215 | \ifdefined\chs 216 | 好消息最终还是来了：一名卡耐基梅隆大学计算机科学系的教授手头有一份这台激光打印机的源代码。 217 | \fi 218 | 219 | \ifdefined\eng 220 | The association with Carnegie Mellon did not augur well. In 1979, Brian Reid, a doctoral student there, had shocked the community by refusing to share his text-formatting program, dubbed Scribe. This text formatter was the first to have mark-up commands oriented towards the desired semantics (such as ``emphasize this word'' or ``this paragraph is a quotation'') rather than low-level formatting details (``put this word in italics'' or ``narrow the margins for this paragraph''). Instead Reid sold Scribe to a Pittsburgh-area software company called Unilogic. His graduate-student career ending, Reid says he simply was looking for a way to unload the program on a set of developers that would take pains to keep it from slipping into the public domain. (Why one would consider such an outcome particularly undesirable is not clear.) To sweeten the deal, Reid also agreed to insert a set of time-dependent functions -- ``time bombs'' in software-programmer parlance -- that deactivated freely copied versions of the program after a 90-day expiration date. To avoid deactivation, users paid the software company, which then issued a code that defused the internal time-bomb anti-feature. 221 | \fi 222 | 223 | \ifdefined\chs 224 | 斯托曼对卡耐基梅隆大学并没有什么好印象。1979年，一位在卡耐基梅隆大学的计算机博士研究生，名叫布莱恩·瑞德（Brian Reid）。他开发了一个很不错的文本排版软件，名叫Scribe。但是他却拒绝公开这个软件的代码，震惊了整个开发社区。这个文本排版软件是世界上第一个可以通过标记来指定特定语意（比如“强调这个单词”或“这是一段引文”）的排版软件，而在它之前，一般的排版软件都是通过低级的排版命令（比如“把这个词改为斜体“或”缩小这一段的页边距“）来表达类似的需求。瑞德决定把Scribe出售给一家匹兹堡名叫Unilogic的公司。他当时刚好博士毕业，正打算把开发Scribe的任务转手给别人，免得它流落到公共领域（Public Domain）里。（为什么他会做出这样的决定，迄今为止还令人费解。）为了让这笔交易更具吸引力，瑞德在Scribe中动了点小手脚：他在里面放了个“定时炸弹”，让用户有90天的免费试用期，90天一过，如果用户不交费，则不能再使用这个软件。 225 | \fi 226 | 227 | \ifdefined\eng 228 | For Stallman, this was a betrayal of the programmer ethos, pure and simple. Instead of honoring the notion of share-and-share alike, Reid had inserted a way for companies to compel programmers to pay for information access. But he didn't think deeply about the question, since he didn't use Scribe much. 229 | \fi 230 | 231 | \ifdefined\chs 232 | 在斯托曼看来，这样的做法背叛了程序员应有单纯、简单的精神气质。瑞德的做法不但没有弘扬分享再传播的精神，而且竟然还助纣为虐，开辟了一条让软件公司强迫程序员为信息付费的新途径。不过斯托曼也没有太在意这个问题，因为他本人并不太使用Scribe这个软件。 233 | \fi 234 | 235 | \ifdefined\eng 236 | Unilogic gave the AI Lab a gratis copy to use, but did not remove or mention the time bomb. It worked, for a while; then one day a user reported that Scribe had stopped working. System hacker Howard Cannon spent hours debugging the binary until he found the time-bomb and patched it out. Cannon was incensed, and wasn't shy about telling the other hackers how mad he was that Unilogic had wasted his time with an intentional bug. 237 | \fi 238 | 239 | \ifdefined\chs 240 | Unilogic提供了一个免费的版本给人工智能实验室使用，但是这个版本中仍然保留了那个“定时炸弹”。这个软件在实验室中正常使用了一段时间，但是有一天，有用户发现它不能正常工作了。一位名叫霍华德·坎农（Howard Cannon）的系统工程师花了几个小时调试了这个软件，最终发现了隐藏在软件内部的“定时炸弹”，他改动了一些代码，把它绕了过去。坎农对此非常愤慨，遇到人就抱怨说Unilogic浪费了他好几个小时的时间去解决一个故意隐藏在软件中的问题。 241 | 242 | \fi 243 | 244 | \ifdefined\eng 245 | Stallman had a Lab-related reason, a few months later, to visit the Carnegie Mellon campus. During that visit, he made a point of looking for the person reported to have the printer software source code. By good fortune, the man was in his office. 246 | \fi 247 | 248 | \ifdefined\chs 249 | 几个月后，斯托曼因为工作原因，需要去卡耐基梅隆大学出差访问。访问过程中，他在计算机系找到了那位据说拥有激光打印机软件代码的教授。运气不错，那天他还刚好就在办公室。 250 | \fi 251 | 252 | \ifdefined\eng 253 | In true engineer-to-engineer fashion, the conversation was cordial but blunt. After briefly introducing himself as a visitor from MIT, Stallman requested a copy of the laser-printer source code that he wanted to modify. To his chagrin, the researcher refused. 254 | \fi 255 | 256 | \ifdefined\chs 257 | 工程师之间的讨论总是开门见山的。几句寒暄之后，斯托曼就直入主题，说明自己是为了激光打印机的控制程序代码而来，有了这份代码，他就可以对此进行一些改进。可令斯托曼感到吃惊的是，这位教授竟然拒绝了他的要求。 258 | \fi 259 | 260 | \ifdefined\eng 261 | ``He told me that he had promised not to give me a copy,'' Stallman says. 262 | \fi 263 | 264 | \ifdefined\chs 265 | “他跟我说他答应公司不能泄露代码。”斯托曼说。 266 | \fi 267 | 268 | \ifdefined\eng 269 | Memory is a funny thing. Twenty years after the fact, Stallman's mental history tape is blank in places. Not only does he not remember the motivating reason for the trip or even the time of year during which he took it, he also has no recollection of who was on the other end of the conversation. According to Reid, the person most likely to have fielded Stallman's request is Robert Sproull, a former Xerox PARC researcher and current director of Sun Laboratories, a research division of the computer-technology conglomerate Sun Microsystems. During the 1970s, Sproull had been the primary developer of the laser-printer software in question while at Xerox PARC. Around 1980, Sproull took a faculty research position at Carnegie Mellon where he continued his laser-printer work amid other projects. 270 | \fi 271 | 272 | \ifdefined\chs 273 | 记忆总是这么有趣。二十年过去了，斯托曼关于这段经历的回忆大部分都是空白。他都不记得当初为了什么事去的卡耐基梅隆大学，连具体哪年都给忘了。他也不记得那位教授是谁。根据Scribe的作者瑞德的回忆，惹到斯托曼的那位很可能是罗伯特·斯布鲁（Robert Sproull）。他曾是施乐公司PARC研究所的研究员，如今在Sun研究所任部门主管。二十世纪七十年代，斯布鲁在施乐公司PARC研究所负责激光打印机程序的主要开发者。八十年代他拿到了卡耐基梅隆大学的教职，并在那里继续他的激光打印机相关的工作。 274 | \fi 275 | 276 | \ifdefined\eng 277 | When asked directly about the request, however, Sproull draws a blank. ``I can't make a factual comment,'' writes Sproull via email. ``I have absolutely no recollection of the incident.'' 278 | \fi 279 | 280 | \ifdefined\chs 281 | 可是，直接给斯布鲁发邮件，询问当初的事情，他却不记得这事了：“实在是无可奉告。”斯布鲁在邮件中写道：“我确实没记得有这么一件事。” 282 | \fi 283 | 284 | \ifdefined\eng 285 | ``The code that Stallman was asking for was leading-edge, state-of-the-art code that Sproull had written in the year or so before going to Carnegie Mellon,'' recalls Reid. If so, that might indicate a misunderstanding that occurred, since Stallman wanted the source for the program that MIT had used for quite some time, not some newer version. But the question of which version never arose in the brief conversation. 286 | \fi 287 | 288 | \ifdefined\chs 289 | “斯托曼想要的代码包含的可都是前沿技术，那可是斯布鲁去卡耐基梅隆之前，花了几年的时间研发的成果。”瑞德回忆道。如果确实是这样，那可是一个重大的误解，因为斯托曼想要的代码是麻省理工学院已经用了很长一段时间的打印机的程序代码，并不是要的最新版本。不过在他们那次简短的交谈中，也许根本都还没来得及谈及是要的哪个版本。 290 | \fi 291 | 292 | \ifdefined\eng 293 | In talking to audiences, Stallman has made repeated reference to the incident, noting that the man's unwillingness to hand over the source code stemmed from a nondisclosure agreement, a contractual agreement between him and the Xerox Corporation giving the signatory access to the software source code in exchange for a promise of secrecy. Now a standard item of business in the software industry, the nondisclosure agreement, or NDA, was a novel development at the time, a reflection of both the commercial value of the laser printer to Xerox and the information needed to run it. ``Xerox was at the time trying to make a commercial product out of the laser printer,'' recalls Reid. ``They would have been insane to give away the source code.'' 294 | \fi 295 | 296 | \ifdefined\chs 297 | 在后来的各种演讲中，斯托曼一再提及这件事。强调斯布鲁由于签署了保密协议，从而不能泄露源代码。如今在各个IT公司，签署保密协议（NDA）已经非常普遍，而在当时为软件代码签署保密协议还算先例。这也间接地反映出施乐公司对激光打印机项目的重视程度。“施乐公司打算把激光打印机做成商业产品。”瑞德说，“他们除非疯了，才会把代码泄露出去。” 298 | \fi 299 | 300 | \ifdefined\eng 301 | For Stallman, however, the NDA was something else entirely. It was a refusal on the part of some CMU researcher to participate in a society that, until then, had encouraged software programmers to regard programs as communal resources. Like a peasant whose centuries-old irrigation ditch had grown suddenly dry, Stallman had followed the ditch to its source only to find a brand-spanking-new hydroelectric dam bearing the Xerox logo. 302 | \fi 303 | 304 | \ifdefined\chs 305 | 但在斯托曼看来，签署这种保密协议完全是一种自私的行径。那会儿大家都把软件认为是一种共有的资源，卡耐基梅隆大学一些研究员的做法，就意味着否定这个公理。这对斯托曼来说，就好比是一个农夫眼看着用来灌溉庄稼的河流干枯了。循着河道往上巡查，竟然看到一道大坝从天而降，拦住河水。大坝上赫然印着几个大字：施乐公司。 306 | \fi 307 | 308 | \ifdefined\eng 309 | For Stallman, the realization that Xerox had compelled a fellow programmer to participate in this newfangled system of compelled secrecy took a while to sink in. In the first moment, he could only see the refusal in a personal context. ``I was so angry I couldn't think of a way to express it. So I just turned away and walked out without another word,'' Stallman recalls. ``I might have slammed the door. Who knows? All I remember is wanting to get out of there. I went to his office expecting him to cooperate, so I had not thought about how I would respond if he refused. When he did, I was stunned speechless as well as disappointed and angry.'' 310 | \fi 311 | 312 | \ifdefined\chs 313 | 现在来看，那时施乐公司用各种花言巧语，把一位程序员同胞带入了这片新天地，与世隔绝。不过一开始，斯托曼也没把矛头指向施乐公司，而是怪罪到了个人性格上。“我当时非常生气，都不知道怎么表达。我二话没说，扭头就走了。”斯托曼说，“没准我还使劲摔了门，谁知道呢。我能记得的，就是当时想赶快离开。我特地拜访他的原因就是希望能与他合作，所以我完全没想到过会被拒绝。当他拒绝我的时候，我觉得无话可说，非常的失望与生气。” 314 | \fi 315 | 316 | \ifdefined\eng 317 | Twenty years after the fact, the anger still lingers, and Stallman presents the event as one that made him confront an ethical issue, though not the only such event on his path. Within the next few months, a series of events would befall both Stallman and the AI Lab hacker community that would make 30 seconds worth of tension in a remote Carnegie Mellon office seem trivial by comparison. Nevertheless, when it comes time to sort out the events that would transform Stallman from a lone hacker, instinctively suspicious of centralized authority, to a crusading activist applying traditional notions of liberty, equality, and fraternity to the world of software development, Stallman singles out the Carnegie Mellon encounter for special attention. 318 | \fi 319 | 320 | \ifdefined\chs 321 | 二十多年过去了，可斯托曼当初的怨气还在。他甚至把这个事件描述为人生转折点。然而，那之后几个月中，在人工智能实验室以及斯托曼身上发生的各种事，却比这次打印机事件还令人难以接受。斯托曼，本是一名孤独的黑客，本能地对绝对权威有戒心。在经历了这一系列事件后，变成了一位斗士，把传统的自由、平等、博爱的精神引入软件开发领域。而这次的打印机事件，在其一生的无数事件中则最值得一书。 322 | \fi 323 | 324 | \ifdefined\eng 325 | ``It was my first encounter with a nondisclosure agreement, and it immediately taught me that nondisclosure agreements have victims,'' says Stallman, firmly. ``In this case I was the victim. [My lab and I] were victims.'' 326 | \fi 327 | 328 | \ifdefined\chs 329 | “这是我第一次遭遇所谓的保密协议，但这马上让我明白，在保密协议面前，总会有一些无辜受害者。”斯托曼坚定的说，“在这次事件中，我就是那个受害者。人工智能实验室和我本人都扮演了受害者的角色。” 330 | \fi 331 | 332 | \ifdefined\eng 333 | Stallman later explained, ``If he had refused me his cooperation for personal reasons, it would not have raised any larger issue. I might have considered him a jerk, but no more. The fact that his refusal was impersonal, that he had promised in advance to be uncooperative, not just to me but to anyone whatsoever, made this a larger issue.'' 334 | \fi 335 | 336 | \ifdefined\chs 337 | 斯托曼后来解释说：“如果他只是因为个人原因拒绝与我合作，也许事情也就这样不了了之了。也许我会觉得他是一个蠢蛋，但也就仅此而已。但是事实上，他并不是因为个人原因而拒绝我，是因为他先前已经向公司保证了不会泄露源代码，不但不能把源代码给我，也不能给其它任何人，那这个事情性质就变得严重了。” 338 | \fi 339 | 340 | \ifdefined\eng 341 | Although previous events had raised Stallman's ire, he says it wasn't until his Carnegie Mellon encounter that he realized the events were beginning to intrude on a culture he had long considered sacrosanct. He said, ``I already had an idea that software should be shared, but I wasn't sure how to think about that. My thoughts weren't clear and organized to the point where I could express them in a concise fashion to the rest of the world. After this experience, I started to recognize what the issue was, and how big it was.'' 342 | \fi 343 | 344 | \ifdefined\chs 345 | 尽管之前也有过类似的不快经历，可都不能与这次的打印机事件相提并论。这次事件让斯托曼彻底意识到，这些一系列的事件，正悄悄地侵蚀自己所珍视的文化——那个神圣不可侵犯的“黑客”小圈子的核心文化。他说：“我一直有个信念，那就是软件应该可以可以被分享的，但是我不太确定应该怎么去把它变成现实。我的想法还不太成熟，也不太系统，所以没有办法把它精确的表达出来，让其它人理解。经历了这些事件，我开始渐渐认识到问题的本质和它的严重性。” 346 | \fi 347 | 348 | \ifdefined\eng 349 | As an elite programmer at one of the world's elite institutions, Stallman had been perfectly willing to ignore the compromises and bargains of his fellow programmers just so long as they didn't interfere with his own work. Until the arrival of the Xerox laser printer, Stallman had been content to look down on the machines and programs other computer users grimly tolerated. 350 | \fi 351 | 352 | \ifdefined\chs 353 | 作为一个世界顶级研究机构的顶级程序员，斯托曼之前一直都无视那些程序员同行所作的各种妥协和让步，因为他们还不至于影响到斯托曼的工作。而如今施乐激光打印机的到来，让斯托曼开始注意到其他计算机用户一直在忍受的程序和机器。 354 | \fi 355 | 356 | \ifdefined\eng 357 | Now that the laser printer had insinuated itself within the AI Lab's network, however, something had changed. The machine worked fine, barring the paper jams, but the ability to modify software according to personal taste or community need had been taken away. From the viewpoint of the software industry, the printer software represented a change in business tactics. Software had become such a valuable asset that companies no longer accepted the need to publicize source code, especially when publication meant giving potential competitors a chance to duplicate something cheaply. From Stallman's viewpoint, the printer was a Trojan Horse. After a decade of failure, software that users could not change and redistribute -- future hackers would use the term ``proprietary'' software -- had gained a foothold inside the AI Lab through the sneakiest of methods. It had come disguised as a gift. 358 | \fi 359 | 360 | \ifdefined\chs 361 | 如今，这台激光打印机已经强势入驻到人工智能实验室了，而外面的世界也悄悄发生着变化。除了偶尔卡纸以外，打印机工作还算正常。可是按照个人喜好修改软件则不可能了。从软件业的角度看，这打印机的出现是个信号，预示着软件是公司的重要财产。谁也不再愿意发布软件源代码，因为这可能会给潜在竞争对手机会，让他们可以轻松山寨自己的产品。而在斯托曼看来，这打印机简直就是个卧底。十来年的尝试，私有软件总算在人工智能实验室中占得一角。私有软件，也就是如今所说的专有软件，这次被打扮成礼物，潜入得悄无声息。 362 | \fi 363 | 364 | \ifdefined\eng 365 | That Xerox had offered some programmers access to additional gifts in exchange for secrecy was also galling, but Stallman takes pains to note that, if presented with such a quid pro quo bargain at a younger age, he just might have taken the Xerox Corporation up on its offer. The anger of the Carnegie Mellon encounter, however, had a firming effect on Stallman's own moral lassitude. Not only did it give him the necessary anger to view such future offers with suspicion, it also forced him to turn the situation around: what if a fellow hacker dropped into Stallman's office someday and it suddenly became Stallman's job to refuse the hacker's request for source code? 366 | \fi 367 | 368 | \ifdefined\chs 369 | 施乐公司后来还发出邀请，让一些程序员再使用它们的礼品。斯托曼说，要是再早几年，他没准也无法拒绝这种免费午餐。是那次打印机事件，让斯托曼建立起了道德防线。它不仅燃起了斯托曼久抑的怒火，还让他对以后的各种礼品心存戒备；它更让斯托曼开始思考一个让他自己也坐立不安的问题：要是以后哪个黑客同行进到自己的办公室，向他索要代码，他究竟会不会拒绝呢？ 370 | \fi 371 | 372 | \ifdefined\eng 373 | ``When somebody invited me to betray all my colleagues in that way, I remembered how angry I was when somebody else had done that to me and my whole lab,'' Stallman says. ``So I said, `Thank you very much for offering me this nice software package, but I can't accept it on the conditions that you're asking for, so I'm going to do without it.'\hspace{0.01in}'' 374 | \fi 375 | 376 | \ifdefined\chs 377 | “要是谁跟我建议，让我以这种方式背叛我的同事，我就会回忆起在打印机事件中，我和我的同事，被别人背叛的感觉，那份怒火终生难忘。”斯托曼说，“我会回敬给分发专有软件的人：‘谢谢你的软件，非常棒！可是我不能接受你的那些保密协议，很遗憾，我不会用它。’” 378 | \fi 379 | 380 | \ifdefined\eng 381 | It was a lesson Stallman would carry with him through the tumultuous years of the 1980s, a decade during which many of his MIT colleagues would depart the AI Lab and sign nondisclosure agreements of their own. They may have told themselves that this was a necessary evil so they could work on the best projects. For Stallman, however, the NDA called the the moral legitimacy of the project into question. What good is a technically exciting project if it is meant to be withheld from the community? 382 | \fi 383 | 384 | \ifdefined\chs 385 | 斯托曼带着这种态度，经历了动荡的八十年代。在这期间，麻省理工学院的同事们纷纷离开人工智能实验室，走进公司，签署了保密协议。大多数保密协议都有解密时间，而这则成了很多黑客们的借口。他们会辩解说：软件迟早会成为公共资源。只要保证软件在早期的开发阶段不被泄露，就可以保证让各位黑客朋友们可以进入到顶尖项目中工作。这些借口，在斯托曼看来，是迈向深渊的第一步。把一个出色的项目放到社区以外去开去，能有什么好处可言呢？ 386 | \fi 387 | 388 | \ifdefined\eng 389 | As Stallman would quickly learn, refusing such offers involved more than personal sacrifice. It involved segregating himself from fellow hackers who, though sharing a similar distaste for secrecy, tended to express that distaste in a more morally flexible fashion. Refusing another's request for source code, Stallman decided, was not only a betrayal of the scientific mission that had nurtured software development since the end of World War II, it was a violation of the Golden Rule, the baseline moral dictate to do unto others as you would have them do unto you. 390 | \fi 391 | 392 | \ifdefined\chs 393 | 斯托曼很快就会明白，要拒绝这些要求和邀请，不仅需要一些个人牺牲，更会被其他一些黑客们疏远。这些黑客虽然也对各种保密协议嗤之以鼻，但却会更圆滑地对它加以评判。拒绝提供源代码，在斯托曼看来，不仅违背了二战以来深植入软件开发中的科学精神，更违背了“己所不欲，勿施于人”的道德准则。 394 | \fi 395 | 396 | \ifdefined\eng 397 | Hence the importance of the laser printer and the encounter that resulted from it. Without it, Stallman says, his life might have followed a more ordinary path, one balancing the material comforts of a commercial programmer with the ultimate frustration of a life spent writing invisible software code. There would have been no sense of clarity, no urgency to address a problem others weren't addressing. Most importantly, there would have been no righteous anger, an emotion that, as we soon shall see, has propelled Stallman's career as surely as any political ideology or ethical belief. 398 | \fi 399 | 400 | \ifdefined\chs 401 | 打印机事件的重要意义恰在于此。正如斯托曼所言，倘若没有这次事件，他的人生也许就会落入平常，纠结着，一边开发专有软件，一边痛苦地编写没人会看到的代码。当然也不会有着如今清晰的思路，更不会去解决别人沿未想过的各种问题。最重要的，他心中也不会再有那份不平，推动着他去追求他的政治理想和道德信仰。 402 | \fi 403 | 404 | \ifdefined\eng 405 | ``From that day forward, I decided this was something I could never participate in,'' says Stallman, alluding to the practice of trading personal liberty for the sake of convenience -- Stallman's description of the NDA bargain -- as well as the overall culture that encouraged such ethically suspect deal-making in the first place. ``I decided never to make other people victims as I had been a victim.'' 406 | \fi 407 | 408 | \ifdefined\chs 409 | “从那日起，我决定绝不参与其中。”谈起软件保密协议和类似的事情，斯托曼如是说。在他看来，这是一场以个人自由换取便利的交易。“我决定绝不让第二个人为此成为像我一样的受害者。” 410 | \fi 411 | 412 | \theendnotes 413 | \setcounter{endnote}{0} 414 | -------------------------------------------------------------------------------- /chap02.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | \chapter{\ifdefined\eng 10 | 2001: A Hacker's Odyssey 11 | \fi 12 | \ifdefined\chs 13 | 黑客路漫漫 14 | \fi} 15 | 16 | \ifdefined\eng 17 | The New York University computer-science department sits inside Warren Weaver Hall, a fortress-like building located two blocks east of Washington Square Park. Industrial-strength air-conditioning vents create a surrounding moat of hot air, discouraging loiterers and solicitors alike. Visitors who breach the moat encounter another formidable barrier, a security check-in counter immediately inside the building's single entryway. 18 | \fi 19 | 20 | \ifdefined\chs 21 | 纽约大学计算机学院坐落在沃伦·韦弗大楼（Warren Weaver Hall）之中，和著名的华盛顿广场公园相隔两个街区。大楼周围充斥着从空调压缩机里传出来的股股热浪。这阵热浪好似屏障一般，驱散着各路闲杂人等。倘若冲破这道屏障，面前还会出现另一道防线：整座大楼的唯一一道入口，你被一个安检岗拦下。 22 | \fi 23 | 24 | \ifdefined\eng 25 | Beyond the security checkpoint, the atmosphere relaxes somewhat. Still, numerous signs scattered throughout the first floor preach the dangers of unsecured doors and propped-open fire exits. Taken as a whole, the signs offer a reminder: even in the relatively tranquil confines of pre-September 11, 2001, New York, one can never be too careful or too suspicious. 26 | \fi 27 | 28 | \ifdefined\chs 29 | 走过安检口，气氛似乎缓和了些。可依旧还能看到各处林立的警示牌，指向消防出口。一路下来，你会有这样的感受：哪怕是在2001年9月初的纽约，这样一座现代化的都市之中，也要记得，小心驶得万年船。 30 | \fi 31 | 32 | \ifdefined\eng 33 | The signs offer an interesting thematic counterpoint to the growing number of visitors gathering in the hall's interior atrium. A few look like NYU students. Most look like shaggy-haired concert-goers milling outside a music hall in anticipation of the main act. For one brief morning, the masses have taken over Warren Weaver Hall, leaving the nearby security attendant with nothing better to do but watch Ricki Lake on TV and shrug her shoulders toward the nearby auditorium whenever visitors ask about ``the speech.'' 34 | \fi 35 | 36 | \ifdefined\chs 37 | 可当你继续向前，走到中央大厅的时候，这份谨慎的感受却被一群人冲破了。他们之中，有些看起来像是纽约大学的学生。大部分则蓬着头，好似等待着一场盛大的音乐会。在这短暂的上午，这群人占据了沃伦·韦弗大楼。这下子，安检人员反倒闲下来了。他们不规矩的斜躺坐在椅子上，看着电视剧。要是哪位访客，问起“演讲”的事，这位保安就会连话也懒得说一句，干脆冲着旁边的大礼堂一耸肩，然后继续看他的电视剧。 38 | \fi 39 | 40 | \ifdefined\eng 41 | Once inside the auditorium, a visitor finds the person who has forced this temporary shutdown of building security procedures. The person is Richard M. Stallman, founder of the GNU Project, original president of the Free Software Foundation, winner of the 1990 MacArthur Fellowship, winner of the Association of Computing Machinery's Grace Murray Hopper Award (also in 1990), corecipient of the Takeda Foundation's 2001 Takeda Award for Social/Economic Betterment, and former AI Lab hacker. As announced over a host of hacker-related web sites, including the GNU Project's own \url{http://www.gnu.org} site, Stallman is in Manhattan, his former hometown, to deliver a much anticipated speech in rebuttal to the Microsoft Corporation's recent campaign against the GNU General Public License. 42 | \fi 43 | 44 | \ifdefined\chs 45 | 有如此神通，能让保安放半天假的这位演讲者，此时正坐在大礼堂中。他就是理查德·M·斯托曼：GNU工程的创始人，自由软件基金会的第一任主席，1990年麦克阿瑟奖（MacArthur Fellowship）获得者，同年美国计算机协会（Association of Computing Machinery）格雷斯·莫瑞·霍普奖（Grace Murray Hopper Award）获得者，2001年日本武田基金会（Takeda Foundation）的武田奖（Takeda Award）共同获得者。当然，他也是我们熟悉的那位麻省理工学院人工智能实验室的黑客。前阵子黑客相关的网站上，包括GNU工程的官方网站上（\url{http://www.gnu.org}），都刊载了一条新闻：理查德·M·斯托曼将在他的家乡，纽约曼哈顿，发表演讲，回应微软在前些时候关于GNU通用公共许可证（GNU General Public License）的抨击。 46 | \fi 47 | 48 | \ifdefined\eng 49 | The subject of Stallman's speech is the history and future of the free software movement. The location is significant. Less than a month before, Microsoft senior vice president Craig Mundie appeared at the nearby NYU Stern School of Business, delivering a speech blasting the GNU General Public License, or GNU GPL, a legal device originally conceived by Stallman 16 years before. Built to counteract the growing wave of software secrecy overtaking the computer industry -- a wave first noticed by Stallman during his 1980 troubles with the Xerox laser printer -- the GPL has evolved into a central tool of the free software community. In simplest terms, the GPL establishes a form of communal ownership -- what today's legal scholars now call the ``digital commons'' -- through the legal weight of copyright. The GPL makes this irrevocable; once an author gives code to the community in this way, that code can't be made proprietary by anyone else. Derivative versions must carry the same copyright license, if they use a substantial amount of the original source code. For this reason, critics of the GPL have taken to calling it a ``viral'' license, suggesting inaccurately that it spreads itself to every software program it touches.\endnote{Actually, the GPL's powers are not quite that potent: just putting your code in the same computer with a GPL-covered program does not put your code under the GPL. 50 | 51 | ``To compare something to a virus is very harsh,'' says Stallman. ``A spider plant is a more accurate comparison; it goes to another place if you actively take a cutting.'' 52 | 53 | For more information on the GNU General Public License, visit \url{http://www.gnu.org/copyleft/gpl.html}.} 54 | \fi 55 | 56 | \ifdefined\chs 57 | 斯托曼演讲的主题，是关于自由软件运动的历史和未来。这次演讲的地点尤为重要。不到一个月前，微软的副总裁克雷格·蒙迪就是出现在纽约大学斯特恩商学院（Stern School of Business），抨击GNU通用公共许可证（GNU General Public License）——简称GPL。GPL是斯托曼16年前想出来的法律武器，用来对抗工业界中越来越盛行的专有软件。1980年，斯托曼经历了那次施乐打印机事件之后，预感到了软件专有化的潮流逐渐到来。为了抗衡这潮流，斯托曼提出了自由软件的概念：即用户可以自由地使用，学习，修改和再发布的软件。如今，GPL已经俨然成为了自由软件社区的核心工具。简单说来，GPL是一个软件使用协议，它利用版权法，将自由软件锁定在公众可以自由使用和修改的领域。一旦锁定，这个软件就不会再被专有化。不仅仅是这个软件本身被锁定为自由软件，这个软件的任何衍生品也会成为自由软件。也就是说，倘若某个软件以GPL形式授权发布，这个软件以及任何它的衍生品，都可以被用户自由使用和修改。所谓一个软件的衍生品，也就是任何使用了该软件的代码的作品。哪怕一个软件仅仅使用了某个GPL授权软件的一小部分代码，这个软件也将被要求以自由软件形式发布。恰恰是这个原因，软件业的很多人把GPL称为病毒式许可证，因为它像病毒一般，“感染”所有它触及到的程序。\endnote{事实上，GPL的没有这么夸张的“威力”。把你的程序与另一个GPL许可证的程序放在同一台计算机上运行并不会把你的程序也变成自由软件。 58 | 59 | 斯托曼说：“把一个东西说成是病毒是一种很粗暴的类比，也许把GPL比成是吊兰还稍微贴切一些，如果你把它切下来放到别处，它会继续生长。” 60 | 61 | 要了解GNU通用公共许可证的更多信息，请访问：\url{http://www.gnu.org/copyleft/gpl.html} 62 | } 63 | 64 | 65 | \fi 66 | 67 | \ifdefined\eng 68 | In an information economy increasingly dependent on software and increasingly beholden to software standards, the GPL has become the proverbial ``big stick.'' Even companies that once derided it as ``software socialism'' have come around to recognize the benefits. Linux, the kernel developed by Finnish college student Linus Torvalds in 1991, is licensed under the GPL, as are most parts of the GNU system: GNU Emacs, the GNU Debugger, the GNU C Compiler, etc. Together, these tools form the components of the free software GNU/Linux operating system, developed, nurtured, and owned by the worldwide hacker community. Instead of viewing this community as a threat, high-tech companies like IBM, Hewlett Packard, and Sun Microsystems have come to rely upon it, selling software applications and services built to ride atop the ever-growing free software infrastructure.\endnote{Although these applications run on GNU/Linux, it does not follow that they are themselves free software. On the contrary, most of them applications are proprietary software, and respect your freedom no more than Windows does. They may contribute to the success of GNU/Linux, but they don't contribute to the goal of freedom for which it exists.} 69 | \fi 70 | 71 | \ifdefined\chs 72 | 随着信息产业的发展，全球越来越依赖软件和软件标准。在这样的环境下，谁都无法忽视GPL。哪怕曾经嘲笑过GPL的公司，也不能再把它视为空中楼阁。因为越来越多的软件都是以GPL形式授权：Linux，一个最初由芬兰大学生林纳斯·托瓦兹（Linus Torvalds）于1991年开发出的类UNIX操作系统内核；GNU Emacs；GNU调试器；GNU编译器等等都是以GPL授权的。这些工具在一起，形成了一个完整的自由操作系统。世界各地的黑客，为这套操作系统贡献着代码。每个黑客也可以自由地拥有这样一套操作系统。如今，很多计算机公司都不再把这样一套自由操作系统视为威胁。相反，IBM，惠普，Sun等公司都依赖这个操作系统，并在这套系统之上开发和出售自己的软件产品。\endnote{仅管这些软件都在GNU/Linux上运行，但它们本身不一定是自由软件，相反的，他们中的大部分都是私有软件。跟Windows一样，这些私有软件同样不尊重你的自由。虽然它们对于GNU/Linux的成功起到了一定的推动作用，但它们对于自由软件运动中实现自由的目标并没有什么贡献。} 73 | \fi 74 | 75 | \ifdefined\eng 76 | They've also come to rely upon it as a strategic weapon in the hacker community's perennial war against Microsoft, the Redmond, Washington-based company that has dominated the PC-software marketplace since the late 1980s. As owner of the popular Windows operating system, Microsoft stands to lose the most in an industry-wide shift to the GPL license. Each program in the Windows colossus is covered by copyrights and contracts (End User License Agreements, or EULAs) asserting the proprietary status of the executable, as well as the underlying source code that users can't get anyway. Incorporating code protected by the ``viral'' GPL into one of these programs is forbidden; to comply with the GPL's requirements, Microsoft would be legally required to make that whole program free software. Rival companies could then copy, modify, and sell improved versions of it, taking away the basis of Microsoft's lock over the users. 77 | \fi 78 | 79 | \ifdefined\chs 80 | 在黑客这个圈子里，这个操作系统也被当作战略武器，对抗微软公司。这个总部坐落于华盛顿州雷德蒙德市的软件公司，从二十世纪八十年代开始，已经俨然成了软件业的垄断巨头。作为Windows操作系统的拥有者，微软公司面对业界同行转向GPL许可证的事实，已经再也坐不住了。Windows中，几乎每行代码都是私有的。至少按照法律条款看，它是归微软所有。倘若有谁不慎在Windows中放入一点GPL授权的代码，整个Windows产品都会被“感染”为自由软件。在微软看来，这就好比把哪吒请进了龙宫，整个公司都得翻江倒海，它必须把整个操作系统的代码都以自由软件的形式发布。竞争对手就可以自由的复制、修改这个系统，并销售修改后的版本，这可能瞬间颠覆微软公司龙头老大的地位。 81 | \fi 82 | 83 | \ifdefined\eng 84 | Hence the company's growing concern over the GPL's rate of adoption. Hence the recent Mundie speech blasting the GPL and the ``open source'' approach to software development and sales. (Microsoft does not even acknowledge the term ``free software,'' preferring to use its attacks to direct attention towards the apolitical ``open source'' camp described in \autoref{chapter:open source}, and away from the free software movement.) And hence Stallman's decision to deliver a public rebuttal to that speech on the same campus here today. 85 | \fi 86 | 87 | \ifdefined\chs 88 | 因此，微软极度关注GPL的普及情况。也正因如此，蒙迪才来纽约大学，抨击GPL以及“开源”软件的开发销售模式。（微软并不承认“自由软件”这个概念，而是习惯把矛头指向\autoref{chapter:open source}章节中即将谈到的“开源”阵营，回避自由软件运动的存在。）这才引得斯托曼也决定来纽约大学，在同一所校园内，回应蒙迪的抨击。 89 | \fi 90 | 91 | \ifdefined\eng 92 | 20 years is a long time in the software industry. Consider this: in 1980, when Richard Stallman was cursing the AI Lab's Xerox laser printer, Microsoft, which dominates the worldwide software industry, was still a privately held startup. IBM, the company then regarded as the most powerful force in the computer hardware industry, had yet to introduce its first personal computer, thereby igniting the current low-cost PC market. Many of the technologies we now take for granted -- the World Wide Web, satellite television, 32-bit video-game consoles -- didn't even exist. The same goes for many of the companies that now fill the upper echelons of the corporate establishment, companies like AOL, Sun Microsystems, Amazon.com, Compaq, and Dell. The list goes on and on. 93 | \fi 94 | 95 | \ifdefined\chs 96 | 二十年的时间，对软件业来说，可是个不短的年头。遥想二十多年前的1980年，斯托曼还在咒骂着人工智能实验室的施乐打印机；微软，这个被当今黑客视为全球软件业巨头的公司，还是个私人的创业小公司；而IBM，这个被当年的黑客视为全球计算机业巨头的公司，还没推出个人计算机；至于IBM的个人计算机推动了整个计算机业的发展，则也是之后的事情了。而当今我们习以为常的很多技术，在那时都还没出现。包括WWW网络，卫星电视，32位终端游戏机等等。如今的很多计算机巨头，则也一样在当时还没建立。包括AOL，Sun，亚马逊，康柏，戴尔等等。 97 | \fi 98 | 99 | \ifdefined\eng 100 | Among those who value progress above freedom, 101 | the fact that the high-technology marketplace has come so far in such little time is cited both for and against the GNU GPL. Some argue in favor of the GPL, pointing to the short lifespan of most computer hardware platforms. Facing the risk of buying an obsolete product, consumers tend to flock to companies with the best long-term survival. As a result, the software marketplace has become a winner-take-all arena.\endnote{See Shubha Ghosh, ``Revealing the Microsoft Windows Source Code,'' \textit{Gigalaw.com} (January, 2000), \url{http://www.gigalaw.com/}.} The proprietary software environment, they say, leads to monopoly abuse and stagnation. Strong companies suck all the oxygen out of the marketplace for rival competitors and innovative startups. 102 | \fi 103 | 104 | \ifdefined\chs 105 | 高科技产业在这短暂时间内迅速成长的过程中，则充斥着关于GPL的争论。GPL的支持者声称：由于计算机硬件平台的短暂寿命，为了避免买到过时产品，用户会倾向于购买大品牌的产品。由此带来的结果，造成了软件市场赢者通吃的局面。\endnote{参考Shubha Ghosh于2000年1月在\textit{Gigalaw.com}上发表的文章：《Revealing the Microsoft Windows Source Code》。\url{http://www.gigalaw.com/}}而如今，由于软件被认为是专有的，具有垄断地位的公司就会滥用它的权利，使得整个产业停滞不前。垄断企业会堵住所有去路，让竞争者无法生存，也让后起的创业公司无处立足。 106 | \fi 107 | 108 | \ifdefined\eng 109 | Others argue just the opposite. Selling software is just as risky, if not more risky, than buying software, they say. Without the legal guarantees provided by proprietary software licenses, not to mention the economic prospects of a privately owned ``killer app'' (i.e., a breakthrough technology that launches an entirely new market),\endnote{Killer apps don't have to be proprietary. Still, I think the reader gets the point: the software marketplace is like the lottery. The bigger the potential payoff, the more people want to participate. For a good summary of the killer-app phenomenon, see Philip Ben-David, ``Whatever Happened to the `Killer App'?'', \textit{e-Commerce News} (December 7, 2000), \url{http://www.ecommercetimes.com/story/5893.html}.} companies lose the incentive to participate. Once again, the market stagnates and innovation declines. As Mundie himself noted in his May 3rd address on the same campus, the GPL's ``viral'' nature ``poses a threat'' to any company that relies on the uniqueness of its software as a competitive asset. Added Mundie: 110 | \begin{quote} 111 | It also fundamentally undermines the independent commercial software sector because it effectively makes it impossible to distribute software on a basis where recipients pay for the product rather than just the cost of distribution.\endnote{See Craig Mundie, ``The Commercial Software Model,'' senior vice president, Microsoft Corp., excerpted from an online transcript of Mundie's May 3, 2001, speech to the New York University Stern School of Business, \url{http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.asp}.} 112 | \end{quote} 113 | 114 | \fi 115 | 116 | \ifdefined\chs 117 | GPL的反对者，则恰恰相反。他们声称销售软件和购买软件一样，具有风险。倘若没有法律保证软件可以被私有化，人们将再也看不到杀手级应用的繁荣（所谓杀手级应用，即某种技术足以打开一片全新市场）\endnote{其实杀手级应用并不一定需要是私有化的。我觉得读者应该这么来理解：软件市场就像买彩票一样，预斯的收益越高，越多的人愿意参与其中。有关杀手级应用的现象，Philip Ben-David 2007年12月7日发表的文章《What Happened to the ``Kiler App''?》对此有清晰的阐述。\url{http://www.ecommercetimes.com/story/5893.html}}，公司也将失去继续创新的动力。正如蒙迪于五月三日在纽约大学所说的，GPL的“病毒”特性为各大公司带来了威胁，威胁着它们赖以生存的软件产品。蒙迪道： 118 | \begin{quote} 119 | 它严重地威胁着独立的商业软件。出售软件不仅仅是要收回发行成本，还有更多的人力附加价值。而GPL则让这种买卖变成天方夜谭。\endnote{参考微软资深副总裁克雷格·蒙迪的《The Commercial Software Model》一文，节选于他2001年5月3日在纽约大学斯特恩商学院所做的演讲。\url{http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.asp}} 120 | \end{quote} 121 | 122 | \fi 123 | 124 | \ifdefined\eng 125 | The mutual success of GNU/Linux and Windows over the last 10 years suggests that both sides on this question are sometimes right. However, free software activists such as Stallman think this is a side issue. The real question, they say, isn't whether free or proprietary software will succeed more, it's which one is more ethical. 126 | \fi 127 | 128 | \ifdefined\chs 129 | 在过去的10年中，无论是GNU/Linux还是Windows，都有了长足的进步，赢得了各自的成功。两者双赢的局面，似乎使得无论支持或反对GPL都有了足够的理由。但是，作为像斯托曼这样的自由软件活动家来说，成功并不是事情的关键。真正的问题并不是自由软件和私有软件哪个更为成功，而是哪个更道德。 130 | \fi 131 | 132 | \ifdefined\eng 133 | Nevertheless, the battle for momentum is an important one in the software industry. Even powerful vendors such as Microsoft rely on the support of third-party software developers whose tools, programs, and computer games make an underlying software platform such as Windows more attractive to the mainstream consumer. Citing the rapid evolution of the technology marketplace over the last 20 years, not to mention his own company's impressive track record during that period, Mundie advised listeners to not get too carried away by the free software movement's recent momentum: 134 | \fi 135 | 136 | \ifdefined\chs 137 | 不管怎么说，这场自由软件与私有软件的战役在软件工业发展史上是一次重要的事件。哪怕像微软这么强大的企业，也需要以来第三方软件开发者。恰恰是他们开发的工具，程序，游戏才使得Windows系统更加吸引用户。回顾近二十年软件业的发展，哪怕不提自家公司的成长，蒙迪依旧提醒他的听众，不要被自由软件运动的风潮吹昏头脑： 138 | \fi 139 | 140 | \ifdefined\eng 141 | \begin{quote} 142 | Two decades of experience have shown that an economic model that protects intellectual property and a business model that recoups research and development costs can create impressive economic benefits and distribute them very broadly.\endnote{\textit{Ibid.}} 143 | \end{quote} 144 | \fi 145 | 146 | \ifdefined\chs 147 | \begin{quote} 148 | 二十年的经验表明，保护知识产权的经济社会，配合降低研发成本的商业模式，可以极大地促进经济发展和财富分配。\endnote{\textit{同上。}} 149 | \end{quote} 150 | 151 | \fi 152 | 153 | \ifdefined\eng 154 | Such admonitions serve as the backdrop for Stallman's speech today. Less than a month after their utterance, Stallman stands with his back to one of the chalk boards at the front of the room, edgy to begin. 155 | \fi 156 | 157 | \ifdefined\chs 158 | 这段来自蒙迪的警告，成了斯托曼今日演讲的背景。现在，距离蒙迪演讲后不到一个月，斯托曼就站在演讲礼堂前方，背对着黑板，摩拳擦掌，迫不及待地准备发表他的演说了。 159 | \fi 160 | 161 | \ifdefined\eng 162 | If the last two decades have brought dramatic changes to the software marketplace, they have brought even more dramatic changes to Stallman himself. Gone is the skinny, clean-shaven hacker who once spent his entire days communing with his beloved PDP-10. In his place stands a heavy-set middle-aged man with long hair and rabbinical beard, a man who now spends the bulk of his time writing and answering email, haranguing fellow programmers, and giving speeches like the one today. Dressed in an aqua-colored T-shirt and brown polyester pants, Stallman looks like a desert hermit who just stepped out of a Salvation Army dressing room. 163 | \fi 164 | 165 | \ifdefined\chs 166 | 这二十年来，相比软件业翻天覆地的变化，斯托曼的改变则更加明显。当年他曾是那位精瘦，不留胡须的黑客，曾在那台PDP-10前，没日没夜地和它畅谈。而如今，在讲坛上的那位，已是人近中年，发福，留发，蓄须。他会花大把时间回复邮件，在公众或程序员面前，发表演说，组织演讲——正如今天这次一样。他今天穿着海蓝色的T恤，一条棕色的涤纶裤子，看起来好似刚刚踏出沙漠的隐士。 167 | \fi 168 | 169 | \ifdefined\eng 170 | The crowd is filled with visitors who share Stallman's fashion and grooming tastes. Many come bearing laptop computers and cellular modems, all the better to record and transmit Stallman's words to a waiting Internet audience. The gender ratio is roughly 15 males to 1 female, and 1 of the 7 or 8 females in the room comes in bearing a stuffed penguin, the official Linux mascot, while another carries a stuffed teddy bear. 171 | \fi 172 | 173 | \ifdefined\chs 174 | 人群之中，则充斥着和斯托曼有着类似打扮的听众。很多人带着笔记本电脑和蜂窝调制解调器，以及各种录音录像设备，准备把斯托曼的演讲传上互联网，那里还有更多的听众等着他的言论。听众中，男女比例大约十五比一。大约每七八个女听众里，就有一位拿着企鹅的毛绒玩具。这是Linux的吉祥物。还有些女听众则抱着泰迪熊。 175 | \fi 176 | 177 | \ifdefined\eng 178 | Agitated, Stallman leaves his post at the front of the room and takes a seat in a front-row chair, tapping commands into an already-opened laptop. For the next 10 minutes Stallman is oblivious to the growing number of students, professors, and fans circulating in front of him at the foot of the auditorium stage. 179 | \fi 180 | 181 | \ifdefined\chs 182 | 人潮涌动，斯托曼则离开了演讲台，坐在第一排的听众席上，把一直开着机的笔记本电脑拿出来，开始敲键盘。接下来的十分钟里，进来的学生，教授和粉丝逐渐走到他旁边，围观他工作。而斯托曼对此则完全不在意。 183 | \fi 184 | 185 | \ifdefined\eng 186 | Before the speech can begin, the baroque rituals of academic formality must be observed. Stallman's appearance merits not one but two introductions. Mike Uretsky, codirector of the Stern School's Center for Advanced Technology, provides the first. 187 | \fi 188 | 189 | \ifdefined\chs 190 | 既然在大学演讲，学院派的规矩是少不了的。演讲嘉宾介绍则是重要一环。对斯托曼的介绍可谓阵容强大。纽约大学的两位教授分别为他做两段开场白。第一位，是来自纽约大学斯特恩商学院高新技术研究中心的主任，麦克·乌列茨基。 191 | \fi 192 | 193 | \ifdefined\eng 194 | ``The role of a university is to foster debate and to have interesting discussions,'' Uretsky says. ``This particular presentation, this seminar falls right into that mold. I find the discussion of open source particularly interesting.'' 195 | \fi 196 | 197 | \ifdefined\chs 198 | “大学之地，争辩之所；争辩之处，兴趣所在。”乌列茨基道，“本次讲座，恰是秉承此道。个人愚见，所谓开源，甚是有趣。” 199 | \fi 200 | 201 | \ifdefined\eng 202 | Before Uretsky can get another sentence out, Stallman is on his feet waving him down like a stranded motorist. 203 | \fi 204 | 205 | \ifdefined\chs 206 | 还没等乌列茨基把话说完，斯托曼就站起来挥着手喊道： 207 | \fi 208 | 209 | \ifdefined\eng 210 | ``I do free software,'' Stallman says to rising laughter. ``Open source is a different movement.'' 211 | \fi 212 | 213 | \ifdefined\chs 214 | “我是搞自由软件的，开源是另外一码事！” 215 | \fi 216 | 217 | \ifdefined\eng 218 | The laughter gives way to applause. The room is stocked with Stallman partisans, people who know of his reputation for verbal exactitude, not to mention his much publicized 1998 falling out with the open source software proponents. Most have come to anticipate such outbursts the same way radio fans once waited for Jack Benny's trademark, ``Now cut that out!'' phrase during each radio program. 219 | \fi 220 | 221 | \ifdefined\chs 222 | 这一嗓子引来了一阵哄堂大笑。笑声褪去，掌声渐起。当下，听众中绝大多数都对斯托曼的这份咬文嚼字有所耳闻，更知道在1998年，他和开源阵营支持者的那次争论。斯托曼的这一行为，就如同整点新闻一般，早在大家意料之中。 223 | \fi 224 | 225 | \ifdefined\eng 226 | Uretsky hastily finishes his introduction and cedes the stage to Edmond Schonberg, a professor in the NYU computer-science department. As a computer programmer and GNU Project contributor, Schonberg knows which linguistic land mines to avoid. He deftly summarizes Stallman's career from the perspective of a modern-day programmer. 227 | \fi 228 | 229 | \ifdefined\chs 230 | 乌列茨基草草结束介绍，走下讲堂。接下来对斯托曼做介绍的，是纽约大学计算机系的教授埃德蒙·舍恩伯格。作为一个计算机程序员，又是GNU工程的贡献者，他很清楚该如何用词。他站在当代程序员的角度，扼要回顾了斯托曼的事业。 231 | \fi 232 | 233 | \ifdefined\eng 234 | ``Richard is the perfect example of somebody who, by acting locally, started thinking globally [about] problems concerning the unavailability of source code,'' says Schonberg. ``He has developed a coherent philosophy that has forced all of us to reexamine our ideas of how software is produced, of what intellectual property means, and of what the software community actually represents.''\endnote{If this were to be said today, Stallman would object to the term ``intellectual property'' as carrying bias and confusion. See \url{http://www.gnu.org/philosophy/not-ipr.html}.} 235 | \fi 236 | 237 | \ifdefined\chs 238 | “放眼全球，脚踏实地，斯托曼是典范。他严肃地审视了软件源代码不对公众公开的事实，发展出了一套严密的逻辑体系。这套体系敦促着我们，让我们不得不重新思考如何开发软件，何谓知识产权，以及软件社区究竟是何物。”\endnote{如果他今天再来发表这样的演讲，斯托曼一定会指出“知识产权”这个词所存在的认识上的偏差和可能造成的混淆。请参考：\url{http://www.gnu.org/philosophy/not-ipr.html}} 239 | \fi 240 | 241 | \ifdefined\eng 242 | Schonberg welcomes Stallman to more applause. Stallman takes a moment to shut off his laptop, rises out of his chair, and takes the stage. 243 | \fi 244 | 245 | \ifdefined\chs 246 | 舍恩伯格的致辞迎来了更多的掌声。斯托曼在掌声中，合上笔记本电脑，挪出身子，走上讲台。 247 | \fi 248 | 249 | \ifdefined\eng 250 | At first, Stallman's address seems more Catskills comedy routine than political speech. ``I'd like to thank Microsoft for providing me the opportunity to be on this platform,'' Stallman wisecracks. ``For the past few weeks, I have felt like an author whose book was fortuitously banned somewhere.'' 251 | \fi 252 | 253 | \ifdefined\chs 254 | 演讲开始，斯托曼表现得更像是个老练的喜剧演员，让人没法察觉这是一场严肃的政论讲座。“我首先要感谢微软公司给了我这样一次机会，来到贵校，畅抒己见。”斯托曼玩笑道，“过去几周里，我都觉得自己像个没落作家，自己的作品都无人问津。” 255 | \fi 256 | 257 | \ifdefined\eng 258 | For the uninitiated, Stallman dives into a quick free software warm-up analogy. He likens a software program to a cooking recipe. Both provide useful step-by-step instructions on how to complete a desired task and can be easily modified if a user has special desires or circumstances. ``You don't have to follow a recipe exactly,'' Stallman notes. ``You can leave out some ingredients. Add some mushrooms, 'cause you like mushrooms. Put in less salt because your doctor said you should cut down on salt -- whatever.'' 259 | \fi 260 | 261 | \ifdefined\chs 262 | 为了照顾新人，斯托曼用一套类比，简要介绍了自由软件。他把软件代码比作烹饪菜谱。二者都提供清晰的步骤，说明如何一步一步完成某个特定任务。同时，人们都可以很容易地按照自己的需求，对它们进行修改。“你不用按照菜谱的每一步严格执行操作。”斯托曼说，“你可以少放点调料。喜欢蘑菇，放些蘑菇；口味淡就少放盐；加点胡椒粉什么的。” 263 | \fi 264 | 265 | \ifdefined\eng 266 | Most importantly, Stallman says, software programs and recipes are both easy to share. In giving a recipe to a dinner guest, a cook loses little more than time and the cost of the paper the recipe was written on. Software programs require even less, usually a few mouse-clicks and a modicum of electricity. In both instances, however, the person giving the information gains two things: increased friendship and the ability to borrow interesting recipes in return. 267 | \fi 268 | 269 | \ifdefined\chs 270 | 最重要的，斯托曼强调，软件和菜谱都很容易被分享。倘若有位客人来家里吃晚餐，那么把菜谱给他无非是花些时间，费点笔墨。拷贝软件则要求更少，只要轻点鼠标，费点电。而分享之后，你则起码有两份收获：增进了友谊；同时，下次你需要帮忙的时候，对方也会有所回报。 271 | \fi 272 | 273 | \ifdefined\eng 274 | ``Imagine what it would be like if recipes were packaged inside black boxes,'' Stallman says, shifting gears. ``You couldn't see what ingredients they're using, let alone change them, and imagine if you made a copy for a friend. They would call you a pirate and try to put you in prison for years. That world would create tremendous outrage from all the people who are used to sharing recipes. But that is exactly what the world of proprietary software is like. A world in which common decency towards other people is prohibited or prevented.'' 275 | \fi 276 | 277 | \ifdefined\chs 278 | “想象一下，要是菜谱全被封锁在一个黑匣子里，那会如何？”斯托曼话峰一转，“你不知道他们用了什么调料，只有他们才能更改配方。你如果把菜谱抄出一份，送给朋友，他们就把你叫贼，把你关进牢房，长达数年。如果你早就习惯了把菜谱传来传去，这样的世界一定会让你觉得不可理喻。可这一切恰恰发生在专有软件的世界之中。在这个世界里，很平常的社交行为被严格禁止，或者被想方设法避免。” 279 | \fi 280 | 281 | \ifdefined\eng 282 | With this introductory analogy out of the way, Stallman launches into a retelling of the Xerox laser-printer episode. Like the recipe analogy, the laser-printer story is a useful rhetorical device. With its parable-like structure, it dramatizes just how quickly things can change in the software world. Drawing listeners back to an era before Amazon.com one-click shopping, Microsoft Windows, and Oracle databases, it asks the listener to examine the notion of software ownership free of its current corporate logos. 283 | \fi 284 | 285 | \ifdefined\chs 286 | 类比过后，斯托曼又提起了施乐打印机事件。和烹饪菜谱的类比一样，打印机事件也是一个称手的工具。两者介绍完，听众就可以了解到如今的软件业究竟发生了多大改变。斯托曼的介绍，把听众拉回了曾经那个年代，那时还没有亚马逊和它的一键支付；没有微软和它的Windows系统；没有甲骨文数据库。这样的背景之下，听众有了很大的想象空间，可以不受当下这些所谓的大公司影响，重新审视所谓的软件所有权。 287 | \fi 288 | 289 | \ifdefined\eng 290 | Stallman delivers the story with all the polish and practice of a local district attorney conducting a closing argument. When he gets to the part about the Carnegie Mellon professor refusing to lend him a copy of the printer source code, Stallman pauses. 291 | \fi 292 | 293 | \ifdefined\chs 294 | 讲起施乐打印机事件，斯托曼是轻车孰路。他好似律师做法庭最后陈词一般，字斟句酌。当说到卡耐基梅隆大学的那位计算机教授拒绝给他源代码的时候，斯托曼道： 295 | \fi 296 | 297 | \ifdefined\eng 298 | ``He had betrayed us,'' Stallman says. ``But he didn't just do it to us. Chances are he did it to you.'' 299 | \fi 300 | 301 | \ifdefined\chs 302 | “他背叛了我们。”斯托曼稍有停顿，接着说，“但他不止背叛了我们，更有可能背叛你！” 303 | \fi 304 | 305 | \ifdefined\eng 306 | On the word ``you,'' Stallman points his index finger accusingly at an unsuspecting member of the audience. The targeted audience member's eyebrows flinch slightly, but Stallman's own eyes have moved on. Slowly and deliberately, Stallman picks out a second listener to nervous titters from the crowd. ``And I think, mostly likely, he did it to you, too,'' he says, pointing at an audience member three rows behind the first. 307 | \fi 308 | 309 | \ifdefined\chs 310 | “你”字一出，斯托曼就伸出食指，指向在座听众。听众之中，有人稍有皱眉。而斯托曼的目光，则移到了前排，一位听众正在低头偷笑。“而且我觉得，他更有可能背叛你。”斯托曼指着刚才偷笑的那位听众。 311 | \fi 312 | 313 | \ifdefined\eng 314 | By the time Stallman has a third audience member picked out, the titters have given away to general laughter. The gesture seems a bit staged, because it is. Still, when it comes time to wrap up the Xerox laser-printer story, Stallman does so with a showman's flourish. ``He probably did it to most of the people here in this room -- except a few, maybe, who weren't born yet in 1980,'' Stallman says, drawing more laughs. ``[That's] because he had promised to refuse to cooperate with just about the entire population of the planet Earth.'' 315 | \fi 316 | 317 | \ifdefined\chs 318 | 这个临场的包袱，把一个人的窃笑变成了全场大笑。各种行为，好似舞台剧一般。笑声中，他总结道：“要想不被他背叛，你只能盼着晚点投胎。”笑声又起，“因为这位教授承诺，拒绝和地球上大多数人合作。” 319 | \fi 320 | 321 | \ifdefined\eng 322 | Stallman lets the comment sink in for a half-beat. ``He had signed a nondisclosure agreement,'' Stallman adds. 323 | \fi 324 | 325 | \ifdefined\chs 326 | 斯托曼一字一顿：“他签署了保密协议。” 327 | \fi 328 | 329 | \ifdefined\eng 330 | Richard Matthew Stallman's rise from frustrated academic to political leader over the last 20 years speaks to many things. It speaks to Stallman's stubborn nature and prodigious will. It speaks to the clearly articulated vision and values of the free software movement Stallman helped build. It speaks to the high-quality software programs Stallman has built, programs that have cemented Stallman's reputation as a programming legend. It speaks to the growing momentum of the GPL, a legal innovation that many Stallman observers see as his most momentous accomplishment. 331 | \fi 332 | 333 | \ifdefined\chs 334 | 理查德·马修·斯托曼，从久经历练的学术精英，到一呼百应的运动领袖。这一蜕变本身就饱含寓意。它诉说着斯托曼的顽强与固执，诉说着他的决心和毅力。更清晰地诠释了自由软件运动的价值和远见。这之中，也当然包含了斯托曼编写的高质量代码，字里行间，凝结了斯托曼的心血，将他的经历，铸成了传奇。传奇之上，更能看到GPL不可遏制的蓬勃生命力。而GPL本身，作为法律界的一大创新，已经被公认为斯托曼的重要成就。 335 | \fi 336 | 337 | \ifdefined\eng 338 | Most importantly, it speaks to the changing nature of political power in a world increasingly beholden to computer technology and the software programs that power that technology. 339 | \fi 340 | 341 | \ifdefined\chs 342 | 当下，计算机和相关软件技术已成为整个世界的一大支柱。理查德的经历，也更彰显了在如此背景之下，政权民意的风云变化。 343 | \fi 344 | 345 | \ifdefined\eng 346 | Maybe that's why, even at a time when most high-technology stars are on the wane, Stallman's star has grown. Since launching the GNU Project in 1984,\endnote{The acronym GNU stands for ``GNU's not Unix.'' In another portion of the May 29, 2001, NYU speech, Stallman summed up the acronym's origin: 347 | 348 | \begin{quote} 349 | We hackers always look for a funny or naughty name for a program, because naming a program is half the fun of writing the program. We also had a tradition of recursive acronyms, to say that the program that you're writing is similar to some existing program\ldots I looked for a recursive acronym for Something Is Not UNIX. And I tried all 26 letters and discovered that none of them was a word. I decided to make it a contraction. That way I could have a three-letter acronym, for Something's Not UNIX. And I tried letters, and I came across the word ``GNU.'' That was it. 350 | 351 | Although a fan of puns, Stallman recommends that software users pronounce the ``g'' at the beginning of the acronym (i.e., ``gah-new''). Not only does this avoid confusion with the word ``gnu,'' the name of the African antelope, Connochaetes gnou, it also avoids confusion with the adjective ``new.'' ``We've been working on it for 17 years now, so it is not exactly new any more,'' Stallman says. 352 | \end{quote} 353 | 354 | Source: author notes and online transcript of ``Free Software: Freedom and Cooperation,'' Richard Stallman's May 29, 2001, speech at New York University, \url{http://www.gnu.org/events/rms-nyu-2001-transcript.txt}.} Stallman has been at turns ignored, satirized, vilified, and attacked--both from within and without the free software movement. Through it all, the GNU Project has managed to meet its milestones, albeit with a few notorious delays, and stay relevant in a software marketplace several orders of magnitude more complex than the one it entered 18 years ago. So too has the free software ideology, an ideology meticulously groomed by Stallman himself. 355 | \fi 356 | 357 | \ifdefined\chs 358 | 这一切的一切，也许恰恰能解释，为什么斯托曼发起的运动能如此长久不衰，而很多当年的名牌大厂，却早已风光不再的原因。遥想当年，1984年，斯托曼刚刚发起了GNU工程\endnote{GNU是“GNU's not Unix”的缩写。斯托曼在2001年5月29日纽约大学的演讲中，讲述了这个缩写的起源： 359 | 360 | \begin{quote} 361 | 作为黑客，我们总是想给程序起一些有趣或古怪的名字，因为给程序起名字也是编写程序的乐趣中的一部分。我们也有一种使用递归缩写的传统喜好，用这样的方式表明我们所新写的程序与某个现有的程序具有一定的相似性……在为GNU工程起名字时，我试图寻找一个递归缩写来表达“Something Is Not UNIX”含义，我用26个字母去取代“Something”，但得到的结果都差强人意，看起来并不像是一个单词。于是我决定把Is这个单词采用缩写的形式，这样我就可以得到一个三个字母缩写词，也就是说是“Something's Not UNIX”。我尝试了各个字母，最终决定选用“GNU”这个词。 362 | 363 | GNU作为一个双关词，斯托曼建议软件用户在发音时，对第一个字母“g”进行发音（也就是说，把它读作“gah-new”）。这一方面是为了避免与表示白尾角马这种非州羚羊的单词“gnu”发生混淆，另一方面也是避免与“新（new）”这个形容词发生混淆。“我们已经为GNU工程奋斗了17年，它也一点也不‘新’了。” 364 | \end{quote} 365 | 366 | 来源：作者的笔记，以及斯托曼2001年5月29日在纽约大学演讲的在线讲稿“Free Software: Freedom and Cooperation”。\url{http://www.gnu.org/events/rms-nyu-2001-transcript.txt} 367 | }。面对这一工程，自由软件运动内外，都充斥着对这个工程的无视，嘲讽，甚至攻击。一路走来，GNU工程虽然有过几次跳票延期，却还能在大多数时候按时交付，完成一个又一个的发布计划。踏过了十八个寒暑，GNU工程也日渐成熟，在软件市场中，得以赢得一席之地。而这近二十年来，自由软件的理想被理查德精心呵护，渐渐传遍大江南北。 368 | \fi 369 | 370 | \ifdefined\eng 371 | To understand the reasons behind this currency, it helps to examine Richard Stallman both in his own words and in the words of the people who have collaborated and battled with him along the way. The Richard Stallman character sketch is not a complicated one. If any person exemplifies the old adage ``what you see is what you get,'' it's Stallman. 372 | \fi 373 | 374 | \ifdefined\chs 375 | 要想了解这潮流背后的缘由，须得兼听八方言论。这不仅包括斯托曼自己的评价，更要倾听和他在同一战壕里作战的战友们的叙述。其实，斯托曼的个性并不复杂，倘若你坚信“所见即所得”，那么斯托曼这个人就不难被理解。 376 | \fi 377 | 378 | \ifdefined\eng 379 | ``I think if you want to understand Richard Stallman the human being, you really need to see all of the parts as a consistent whole,'' advises Eben Moglen, legal counsel to the Free Software Foundation and professor of law at Columbia University Law School. ``All those personal eccentricities that lots of people see as obstacles to getting to know Stallman really `are' Stallman: Richard's strong sense of personal frustration, his enormous sense of principled ethical commitment, his inability to compromise, especially on issues he considers fundamental. These are all the very reasons Richard did what he did when he did.'' 380 | \fi 381 | 382 | \ifdefined\chs 383 | “想要了解斯托曼这个人，你必须要把各处细节联系起来，看成一个有机的整体。”伊本·莫格林（Eben Moglen）说道。他是自由软件基金会法律顾问，同时也是哥伦比亚大学法学院教授。“在斯托曼身上有着各种古怪脾气，这也许会把人拒之千里。而这份不同寻常，恰恰就构成了斯托曼这个活生生的人。他对挫败异常敏感，他对道德准则恪守不渝。他不肯妥协的个性，在关键问题上不肯让步的固执，这一切的总和，最终让我们看到了当今的斯托曼。” 384 | \fi 385 | 386 | \ifdefined\eng 387 | Explaining how a journey that started with a laser printer would eventually lead to a sparring match with the world's richest corporation is no easy task. It requires a thoughtful examination of the forces that have made software ownership so important in today's society. It also requires a thoughtful examination of a man who, like many political leaders before him, understands the malleability of human memory. It requires an ability to interpret the myths and politically laden code words that have built up around Stallman over time. Finally, it requires an understanding of Stallman's genius as a programmer and his failures and successes in translating that genius to other pursuits. 388 | \fi 389 | 390 | \ifdefined\chs 391 | 一个简单的打印机事件，变成了燎原之火，燃遍全球，足以和全球最富有的软件公司抗衡。要想回顾和解释这一切，并非易事。首先要了解软件所有权，以及它是如何走到当今的重要位置的；更要和人类健忘的本性做斗争；还要能从关于斯托曼的各种神话和攻击之中，看出本质。最后，还要能理解斯托曼在软件领域的过人天赋；以及他如何把这份天赋用到其他领域；还有在这一过程中的各种成败得失。 392 | \fi 393 | 394 | \ifdefined\eng 395 | When it comes to offering his own summary of the journey, Stallman acknowledges the fusion of personality and principle observed by Moglen. ``Stubbornness is my strong suit,'' he says. ``Most people who attempt to do anything of any great difficulty eventually get discouraged and give up. I never gave up.'' 396 | \fi 397 | 398 | \ifdefined\chs 399 | 当我请斯托曼做一番自我总结的时候，他也强调了莫格林提到的个性和原则：“坚强固执是我的本性。很多人在尝试做一些事，遇到了困难，就退缩放弃了。可我从不言弃。” 400 | \fi 401 | 402 | \ifdefined\eng 403 | He also credits blind chance. Had it not been for that run-in over the Xerox laser printer, had it not been for the personal and political conflicts that closed out his career as an MIT employee, had it not been for a half dozen other timely factors, Stallman finds it very easy to picture his life following a different career path. That being said, Stallman gives thanks to the forces and circumstances that put him in the position to make a difference. 404 | \fi 405 | 406 | \ifdefined\chs 407 | 他也同样感激自己的运气。倘若当初没有那次打印机事件，没有其中的各种人事冲突，没有当年的各种机缘巧合，他也许不会放弃麻省理工学院的研究职位，不会重新抉择，选择一条与众不同的道路，并为之奋斗终身。是身边的各种因素，最终让斯托曼得以做出不同凡响的成绩。 408 | \fi 409 | 410 | \ifdefined\eng 411 | ``I had just the right skills,'' says Stallman, summing up his decision for launching the GNU Project to the audience. ``Nobody was there but me, so I felt like, `I'm elected. I have to work on this. If not me, who?'\hspace{0.01in}'' 412 | \fi 413 | 414 | \ifdefined\chs 415 | “我正好有合适的技能。”斯托曼回顾着当初发起GNU工程的决定，总结道，“除了我以外，没人在做这事。我就觉得：‘责任在身，我若不做，舍我其谁。’” 416 | \fi 417 | 418 | \theendnotes 419 | \setcounter{endnote}{0} 420 | -------------------------------------------------------------------------------- /chap12.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | 10 | 11 | \chapter{\ifdefined\eng 12 | A Brief Journey through Hacker Hell 13 | \fi 14 | \ifdefined\chs 15 | 开往黑客地狱的短暂旅途 16 | \fi 17 | } 18 | \chaptermark{A Brief Journey} 19 | 20 | \ifdefined\eng 21 | [RMS: In this chapter my only change is to add a few notes labeled like 22 | this one.] 23 | \fi 24 | 25 | \ifdefined\chs 26 | [RMS: 在这一章中，我只添加了少量的注释，以这样的形式出现。] 27 | \fi 28 | 29 | 30 | \ifdefined\eng 31 | Richard Stallman stares, unblinking, through the windshield of a rental car, waiting for the light to change as we make our way through downtown Kihei. 32 | \fi 33 | 34 | \ifdefined\chs 35 | 理查德·斯托曼双目凝视着车外，眼睛一眨不眨，我们正坐在这辆租来汽车里途经津汇城区，等待着信号灯变绿。 36 | \fi 37 | 38 | \ifdefined\eng 39 | The two of us are headed to the nearby town of Pa'ia, where we are scheduled to meet up with some software programmers and their wives for dinner in about an hour or so. 40 | \fi 41 | 42 | \ifdefined\chs 43 | 我们正在前往附近一个名为芭雅的小镇，去会见一些软件开发者和他们的妻子，然后一同去参加一小时以后另一地点开场的晚宴。 44 | \fi 45 | 46 | \ifdefined\eng 47 | It's about two hours after Stallman's speech at the Maui High Performance Center, and Kihei, a town that seemed so inviting before the speech, now seems profoundly uncooperative. Like most beach cities, Kihei is a one-dimensional exercise in suburban sprawl. Driving down its main drag, with its endless succession of burger stands, realty agencies, and bikini shops, it's hard not to feel like a steel-coated morsel passing through the alimentary canal of a giant commercial tapeworm. The feeling is exacerbated by the lack of side roads. With nowhere to go but forward, traffic moves in spring-like lurches. 200 yards ahead, a light turns green. By the time we are moving, the light is yellow again. 48 | \fi 49 | 50 | \ifdefined\chs 51 | 斯托曼刚刚在茂宜高性能计算中心完成一次演讲，晚宴的开始时间距离演讲结束只有两小时时间。演讲开始前，津汇对我们的到来显得如此的热情，而现在，则让人感觉到它处处在为难我们。跟很多海边城市一样，津汇只有一条主干道贯穿全城。行驶在津汇的主干道上，看着路边的汉堡店、房产中介和比基尼商店，让人感觉到像是一条巨大的绦虫正在吞下一片穿着钢盔铁甲的食物。除了一直向前开，没有别的选择，车流就像一条蜿蜒的溪流。200码开外，信号灯变绿了。当我们开始往前挪动车子时，灯又变黄了。 52 | \fi 53 | 54 | \ifdefined\eng 55 | For Stallman, a lifetime resident of the east coast, the prospect of spending the better part of a sunny Hawaiian afternoon trapped in slow traffic is enough to trigger an embolism. [RMS: Since I was driving, I was also losing time to answer my email, and that's a real pain since I can barely keep up anyway.] Even worse is the knowledge that, with just a few quick right turns a quarter mile back, this whole situation easily could have been avoided. Unfortunately, we are at the mercy of the driver ahead of us, a programmer from the lab who knows the way and who has decided to take us to Pa'ia via the scenic route instead of via the nearby Pilani Highway. 56 | \fi 57 | 58 | \ifdefined\chs 59 | 对于斯托曼这样长期在东部生活的人来说，把夏威夷午后明媚的阳光浪费在拥堵的马路上足以诱发他的脑血栓。[RMS：因为如果我在开车，我就无法回复电子邮件，这对于我来说实在是太痛苦了。] 更糟糕的是，其实在四分之一英里前，有一些可以右转的道路，如果车辆趁早转弯，就可以避免这可怕的交通拥堵。不幸的是，我们需要跟着前面车辆，那辆车的司机是一名实验室的程序员，他认识去往目的地的路，并且是他决定带我们从芭雅的观光道路通行，而不是绕行附近的彼拉尼高速公路。 60 | \fi 61 | 62 | \ifdefined\eng 63 | ``This is terrible,'' says Stallman between frustrated sighs. ``Why didn't we take the other route?'' 64 | \fi 65 | 66 | \ifdefined\chs 67 | 斯托曼叹着气失望的说：“这实在是太可怕了，我们为什么没走另一条路呢？” 68 | \fi 69 | 70 | \ifdefined\eng 71 | Again, the light a quarter mile ahead of us turns green. Again, we creep forward a few more car lengths. This process continues for another 10 minutes, until we finally reach a major crossroad promising access to the adjacent highway. 72 | \fi 73 | 74 | \ifdefined\chs 75 | 终于，我们前方1/4英里处的信号灯变绿了。但我们仍然只能前进很短的一段距。10分钟内这样的过程重复了好几次，直到我们最终慢慢的挪到了相临一条公路的十字路口后。 76 | \fi 77 | 78 | \ifdefined\eng 79 | The driver ahead of us ignores it and continues through the intersection. 80 | \fi 81 | 82 | \ifdefined\chs 83 | 我们前面的车没有理会这个十字路口，继续向前行驶。 84 | \fi 85 | 86 | \ifdefined\eng 87 | ``Why isn't he turning?'' moans Stallman, throwing up his hands in frustration. ``Can you believe this?'' 88 | \fi 89 | 90 | \ifdefined\chs 91 | 斯托曼沮丧的挥动着双手，抱怨道：“他为什么不拐弯呢？你们不觉得奇怪吗？” 92 | \fi 93 | 94 | \ifdefined\eng 95 | I decide not to answer either. I find the fact that I am sitting in a car with Stallman in the driver seat, in Maui no less, unbelievable enough. Until two hours ago, I didn't even know Stallman knew how to drive. Now, listening to Yo-Yo Ma's cello playing the mournful bass notes of ``Appalachian Journey'' on the car stereo and watching the sunset pass by on our left, I do my best to fade into the upholstery. 96 | \fi 97 | 98 | \ifdefined\chs 99 | 我决定不必要回答这两个问题。我知道我正与斯托曼在毛伊岛同乘一辆车，他在开车，这让人很难以至信。事实上，两小时前我还不知道斯托曼会不会开车。而现在，我们在车上欣赏着马友友的“阿巴拉契旅行”专辑中大提琴所发出的让人感到悲伤的低音音符，看着太阳渐渐从我们的左边落下，我尽可能的让自己沉浸在这样的氛围中。 100 | \fi 101 | 102 | \ifdefined\eng 103 | When the next opportunity to turn finally comes up, Stallman hits his right turn signal in an attempt to cue the driver ahead of us. No such luck. Once again, we creep slowly through the intersection, coming to a stop a good 200 yards before the next light. By now, Stallman is livid. 104 | \fi 105 | 106 | \ifdefined\chs 107 | 当下一个转弯的机会出现的时候，斯托曼打开了右转向灯，试图提醒前车的司机。不过仍然没有好运气。我们又一次慢慢的驶过了十字路口，在距离下一个信号灯至少200码的地方停了下来。斯托曼终于忍不住大发雷霆。 108 | \fi 109 | 110 | \ifdefined\eng 111 | ``It's like he's deliberately ignoring us,'' he says, gesturing and pantomiming like an air craft carrier landing-signals officer in a futile attempt to catch our guide's eye. The guide appears unfazed, and for the next five minutes all we see is a small portion of his head in the rearview mirror. 112 | \fi 113 | 114 | \ifdefined\chs 115 | “他简直就是故意无视我们的存在。”他愤愤地说。一面又像机场的信号官指挥飞机降落一样打着手势，尝试着吸引向导的注意力。向导像是完全没有注意到这一点，在接下来的5分钟里，我们只能在他的后视镜里看到他一小部分的脑袋。 116 | \fi 117 | 118 | \ifdefined\eng 119 | I look out Stallman's window. Nearby Kahoolawe and Lanai Islands provide an ideal frame for the setting sun. It's a breathtaking view, the kind that makes moments like this a bit more bearable if you're a Hawaiian native, I suppose. I try to direct Stallman's attention to it, but Stallman, by now obsessed by the inattentiveness of the driver ahead of us, blows me off. 120 | \fi 121 | 122 | \ifdefined\chs 123 | 我从斯托曼的车窗向外看，附近的卡胡拉威岛和拉拿夷岛与落日一起构成了一副美丽的画面。这是一副美得让人窒息的画面，我想，如果你一个夏威夷本地人，一定会因为这样的美景而忘记了堵车的烦恼。我试图把斯托曼的注意力引向这里，但是他的注意力仍然一心集中在前面那个无视我们的司机身上，完全不搭理我。 124 | \fi 125 | 126 | \ifdefined\eng 127 | When the driver passes through another green light, completely ignoring a ``Pilani Highway Next Right,'' I grit my teeth. I remember an early warning relayed to me by BSD programmer Keith Bostic. ``Stallman does not suffer fools gladly,'' Bostic warned me. ``If somebody says or does something stupid, he'll look them in the eye and say, `That's stupid.'\hspace{0.01in}'' 128 | \fi 129 | 130 | \ifdefined\chs 131 | 司机开过另一个亮着绿灯的路口，完全无视边上“下一个路口向右转驶入彼拉尼高速”的标识。我咂了咂嘴。我记起以前一位BSD程序员基思·博斯蒂克警告过我：“斯托曼无法容忍傻瓜，如果有人说了或者做了一些什么蠢事，他会看着他的眼睛说：‘这样做太愚蠢了。’“ 132 | \fi 133 | 134 | \ifdefined\eng 135 | Looking at the oblivious driver ahead of us, I realize that it's the stupidity, not the inconvenience, that's killing Stallman right now. 136 | \fi 137 | 138 | \ifdefined\chs 139 | 看着前方心不在焉的司机，我觉得他做的就是所谓的蠢事，而不只是一些不太聪明的事，这些蠢事正在让斯托曼备受煎熬。 140 | \fi 141 | 142 | \ifdefined\eng 143 | ``It's as if he picked this route with absolutely no thought on how to get there efficiently,'' Stallman says. 144 | \fi 145 | 146 | \ifdefined\chs 147 | ”他好像完全没有想过应该如何有效的到达目的地，所以才选择了这么一条路。”斯托曼说。 148 | \fi 149 | 150 | \ifdefined\eng 151 | The word ``efficiently'' hangs in the air like a bad odor. Few things irritate the hacker mind more than inefficiency. It was the inefficiency of checking the Xerox laser printer two or three times a day that triggered Stallman's initial inquiry into the printer source code. It was the inefficiency of rewriting software tools hijacked by commercial software vendors that led Stallman to battle Symbolics and to launch the GNU Project. If, as Jean Paul Sartre once opined, hell is other people, hacker hell is duplicating other people's stupid mistakes, and it's no exaggeration to say that Stallman's entire life has been an attempt to save mankind from these fiery depths. 152 | \fi 153 | 154 | \ifdefined\chs 155 | “有效”这个词像是一股坏气味停留在了空中。很少有事情能比“低效”更刺激到一个黑客的神经了。当年，正是因为施乐的打印机一天要检修两三次所来带的低效才激发了斯托曼想要获取打印机源代码的想法。也正是因为要重头编写被商业公司所绑架的商用软件的低效，才引发了斯托曼与Symbolics之间的斗争，从而诞生了GNU工程。让-保罗·萨特曾经说，如果别人是地狱，那么黑客的地狱就是重复其它人愚蠢的错误，毫不夸张的说，斯托曼的一生，就是在尝试把人类从地狱的火焰中拯救出来。 156 | \fi 157 | 158 | \ifdefined\eng 159 | This hell metaphor becomes all the more apparent as we take in the slowly passing scenery. With its multitude of shops, parking lots, and poorly timed street lights, Kihei seems less like a city and more like a poorly designed software program writ large. Instead of rerouting traffic and distributing vehicles through side streets and expressways, city planners have elected to run everything through a single main drag. From a hacker perspective, sitting in a car amidst all this mess is like listening to a CD rendition of nails on a chalkboard at full volume. 160 | \fi 161 | 162 | \ifdefined\chs 163 | 这种有关地狱的隐喻在我们缓慢通过这美景时变得更为明显。四处都是商场、停车场和缺乏设计的信号灯，看上去不像是个城市，倒更像是一个设计得很糟糕的软件。城市的规划者把城市设计成所有的车辆都要通过主干道，而不是把车流分散到支路和高速公路上。从黑客的角度来说，坐在车里并被围困在这一团糟的交通中，就像是用最大的音量听一张录有在木板上钉钉子声音的CD。 164 | \fi 165 | 166 | \ifdefined\eng 167 | ``Imperfect systems infuriate hackers,'' observes Steven Levy, another warning I should have listened to before climbing into the car with Stallman. ``This is one reason why hackers generally hate driving cars -- the system of randomly programmed red lights and oddly laid out one-way streets causes delays which are so goddamn \textit{unnecessary} [Levy's emphasis] that the impulse is to rearrange signs, open up traffic-light control boxes . . . redesign the entire system.''\endnote{See Steven Levy, \textit{Hackers} (Penguin USA [paperback], 1984): 40.} 168 | \fi 169 | 170 | \ifdefined\chs 171 | “不完美的系统会激怒黑客。”史蒂芬·李维说过这样的话，这是我决定与斯托曼同坐一辆车前应该听取的另一个忠告，“这是黑客们通常不喜欢开车的原因之一：这是一个充满不确定性的程序，交通信号灯总是随机的变化，还有横七竖八的单行道，导致交通经常堵塞。这实在是太\textit{不必要}了（李维强调说），只要让黑客们重新安排一下信号灯，打开交通灯控制盒，重新设计整个系统。” \endnote{参考史蒂芬·李维的《\textit{黑客}》一书（企鹅出版社，美国，平装，1984年）第40页。} 172 | \fi 173 | 174 | \ifdefined\eng 175 | More frustrating, however, is the duplicity of our trusted guide. Instead of searching out a clever shortcut -- as any true hacker would do on instinct -- the driver ahead of us has instead chosen to play along with the city planners' game. Like Virgil in Dante's \textit{Inferno}, our guide is determined to give us the full guided tour of this hacker hell whether we want it or not. 176 | \fi 177 | 178 | \ifdefined\chs 179 | 更让人感到沮丧的事，是我们的向导的愚笨，他没有像一个黑客那样本能的做出最聪明的选择，选择一条更为聪明的捷径，而是坚持陪着城市设计者玩他们愚蠢的游戏。像但丁《\textit{神曲}》中的维吉尔一样，不管我们是否希望，他都打定主意要让我们完整的体验这个黑客的地狱。 180 | \fi 181 | 182 | \ifdefined\eng 183 | Before I can make this observation to Stallman, the driver finally hits his right turn signal. Stallman's hunched shoulders relax slightly, and for a moment the air of tension within the car dissipates. The tension comes back, however, as the driver in front of us slows down. ``Construction Ahead'' signs line both sides of the street, and even though the Pilani Highway lies less than a quarter mile off in the distance, the two-lane road between us and the highway is blocked by a dormant bulldozer and two large mounds of dirt. 184 | \fi 185 | 186 | \ifdefined\chs 187 | 在我还没有来得及告诉斯托曼我的发现以前，前方的司机终于在路口右转了。斯托曼耸起的肩膀总于放松了一些，车里紧张的空气稍稍消散了一些。然而，当前面的司机把车慢慢停下来时，紧张的气氛又回来了。道路两侧的放着“前方施工”的标识，虽然彼拉尼高速公路就在前方不到四分之一英里的距离，我们的车与高速公路间的一条两车道的公路被一辆停着的推土车和两大堆土方完全堵住了。 188 | \fi 189 | 190 | \ifdefined\eng 191 | It takes Stallman a few seconds to register what's going on as our guide begins executing a clumsy five-point U-turn in front of us. When he catches a glimpse of the bulldozer and the ``No Through Access'' signs just beyond, Stallman finally boils over. 192 | \fi 193 | 194 | \ifdefined\chs 195 | 我们的向导在我们的面前忽然把车笨拙的调了一个头，斯托曼一时都没有反应过来。当他看到了面前的推土机和“禁止通行”标识后，他终于再一次爆发了。 196 | \fi 197 | 198 | \ifdefined\eng 199 | ``Why, why, why?'' he whines, throwing his head back. ``You should have known the road was blocked. You should have known this way wouldn't work. You did this deliberately.'' [RMS: I meant that he chose the slow road deliberately. As explained below, I think these quotes are not exact.] 200 | \fi 201 | 202 | \ifdefined\chs 203 | “为什么，为什么，为什么？”他抱怨道，把头一仰，“你早该知道前面的路被封住了，你早该知道不能走这条路。你是故意这么做的。” [RMS：我原来的意思是说他故意选择了那条拥堵的路，跟下面所解释的一样，我觉得这里所引用的我说的话并不准确。] 204 | \fi 205 | 206 | \ifdefined\eng 207 | The driver finishes the turn and passes us on the way back toward the main drag. As he does so, he shakes his head and gives us an apologetic shrug. Coupled with a toothy grin, the driver's gesture reveals a touch of mainlander frustration but is tempered with a protective dose of islander fatalism. Coming through the sealed windows of our rental car, it spells out a succinct message: ``Hey, it's Maui; what are you gonna do?'' 208 | \fi 209 | 210 | \ifdefined\chs 211 | 向导的车已经调好了头，从我们身边开过，开回那条拥塞的主干道。在他经过我们身边时，他摇了摇了头，给了我们一个抱歉的耸肩。他露出牙齿，司机的姿势显示出了一个外地人的失望，但是这已经被岛国人的宿命所中和了。从我们租来车关闭的窗户望出去，我们似乎看到了这么一句话：“嘿，这就是毛依岛，你想做什么？” 212 | \fi 213 | 214 | \ifdefined\eng 215 | Stallman can take it no longer. 216 | \fi 217 | 218 | \ifdefined\chs 219 | 斯托曼再也无法忍受了。 220 | \fi 221 | 222 | \ifdefined\eng 223 | ``Don't you fucking smile!'' he shouts, fogging up the glass as he does so. ``It's your fucking fault. This all could have been so much easier if we had just done it my way.'' [RMS: These quotes appear to be inaccurate, because I don't use ``fucking'' as an adverb. This was not an interview, so Williams would not have had a tape recorder running. I'm sure things happened overall as described, but these quotations probably reflect his understanding rather than my words.] 224 | \fi 225 | 226 | \ifdefined\chs 227 | “你可不可以不要再笑了！”他咆哮道，雾气蒙上了他的眼镜片，“这全他妈是你的错。如果听我的走另一条路就不会这样了。”[RMS：这些话记录的似乎并不准确，因为我从来不把“他妈的”当成副词来使用。由于我说这些话里并不是在接受采访，所以威廉姆斯并没有录下我说的话。我很确定这里的文字确实还愿了当时的情景，但是这些话也许是反应了他对我所说的话的个人理解，并不是我的原话。] 228 | \fi 229 | 230 | \ifdefined\eng 231 | Stallman accents the words ``my way'' by gripping the steering wheel and pulling himself towards it twice. The image of Stallman's lurching frame is like that of a child throwing a temper tantrum in a car seat, an image further underlined by the tone of Stallman's voice. Halfway between anger and anguish, Stallman seems to be on the verge of tears. 232 | \fi 233 | 234 | \ifdefined\chs 235 | 斯托曼加重了“听我的”一词，紧紧的抓住方向盘并两次把它拉向自己。斯托曼的样子就像是一个在汽车座位里发脾气的小孩子，他的声音进一步加强了这样的形象。斯托曼又生气又郁闷，眼泪几乎就要掉下来。 236 | \fi 237 | 238 | \ifdefined\eng 239 | Fortunately, the tears do not arrive. Like a summer cloudburst, the tantrum ends almost as soon as it begins. After a few whiny gasps, Stallman shifts the car into reverse and begins executing his own U-turn. By the time we are back on the main drag, his face is as impassive as it was when we left the hotel 30 minutes earlier. 240 | \fi 241 | 242 | \ifdefined\chs 243 | 幸运的是，眼泪最终没有到来。就像夏天的暴雨，斯托曼的愤怒转瞬即逝。他轻轻叹了口气，把车挂到倒档，并开始调头。当我们回到城市主干道上时，他的表情让人过目不忘，就跟我们提前半小时离开酒店时的表情一样。 244 | \fi 245 | 246 | \ifdefined\eng 247 | It takes less than five minutes to reach the next cross-street. This one offers easy highway access, and within seconds, we are soon speeding off toward Pa'ia at a relaxing rate of speed. The sun that once loomed bright and yellow over Stallman's left shoulder is now burning a cool orange-red in our rearview mirror. It lends its color to the gauntlet wili wili trees flying past us on both sides of the highway. 248 | \fi 249 | 250 | \ifdefined\chs 251 | 我们花了不到五分钟时间，到达了下一个十字路口。这里可以容易的驶入高速公路，很快，我们就加大马力向着芭雅驶去。刚才斯托曼左肩上若隐若现的黄色太阳现在变成了橙红色出现在我们的后视镜中。金色的阳光撒向高速公路两边的树木。 252 | \fi 253 | 254 | \ifdefined\eng 255 | For the next 20 minutes, the only sound in our vehicle, aside from the ambient hum of the car's engine and tires, is the sound of a cello and a violin trio playing the mournful strains of an Appalachian folk tune. 256 | \fi 257 | 258 | \ifdefined\chs 259 | 接下来的20分钟，只剩下了汽车的声音，包含着引擎和轮胎的轰鸣声。像是大提琴与小提琴的三重奏，演绎着阿巴拉契的民歌旋律。 260 | \fi 261 | 262 | \theendnotes 263 | \setcounter{endnote}{0} 264 | -------------------------------------------------------------------------------- /colophon.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | \ifdefined\chs 10 | 11 | \fi 12 | 13 | \ifdefined\eng 14 | \fi 15 | 16 | \ifdefined\chs 17 | 18 | \fi 19 | 20 | \ifdefined\eng 21 | \chapter*{Colophon} 22 | \fi 23 | 24 | \ifdefined\chs 25 | 26 | \fi 27 | 28 | \ifdefined\eng 29 | The front and back covers of this book were designed and produced by 30 | Rob Myers using Inkscape, the free software vector graphics program. 31 | Jeanne Rasata also contributed to the cover design. 32 | \fi 33 | 34 | \ifdefined\chs 35 | 36 | \fi 37 | 38 | \ifdefined\eng 39 | The typsetting was done by John Sullivan at the Free Software 40 | Foundation using \LaTeX, GNU Emacs, Evince, and the GNU Image 41 | Manipulation Program (GIMP). The primary font is 10-point Computer 42 | Modern. 43 | \fi 44 | 45 | \ifdefined\chs 46 | 47 | \fi 48 | 49 | \ifdefined\eng 50 | Digital versions of the book, including the \LaTeX\- source code, are 51 | available at \url{http://www.fsf.org/faif}. Improvements are welcome, 52 | and can be sent to \url{sales@gnu.org}. 53 | \fi 54 | 55 | \ifdefined\chs 56 | 57 | \fi 58 | 59 | -------------------------------------------------------------------------------- /copyright.tex: -------------------------------------------------------------------------------- 1 | \ifdefined\eng 2 | \noindent This is \textit{Free as in Freedom 2.0: Richard Stallman and 3 | the Free Software Revolution}, a revision of \textit{Free as in 4 | Freedom: Richard Stallman's Crusade for Free Software}. 5 | \fi 6 | 7 | \ifdefined\chs 8 | \noindent 本书是《\textit{Free as in Freedom 2.0：理查德·斯托曼与自由软件运动}》，这是《\textit{Free as in 9 | Freedom：理查德·斯托曼的自由软件的运动}》一书的修订本。 10 | \fi 11 | \bigskip 12 | 13 | \noindent Copyright \copyright{} 2002, 2010 Sam Williams\\ 14 | Copyright \copyright{} 2010 Richard M. Stallman\\ 15 | Permission is granted to copy, distribute and/or modify 16 | this document under the terms of the GNU Free Documentation License, 17 | Version 1.3 or any later version published by the Free Software 18 | Foundation; with no Invariant Sections, no Front-Cover Texts, and no 19 | Back-Cover Texts. A copy of the license is included in the section 20 | entitled ``GNU Free Documentation License.'' 21 | 22 | \bigskip 23 | 24 | \ifdefined\eng 25 | \noindent Published by the Free Software Foundation\\ 26 | 51 Franklin St., Fifth Floor\\ 27 | Boston, MA 02110-1335\\ 28 | USA\\ 29 | ISBN: 9780983159216\\ 30 | \fi 31 | 32 | \bigskip 33 | 34 | 35 | \ifdefined\eng 36 | \noindent The cover photograph of Richard Stallman is by Peter Hinely. The PDP-10 photograph in Chapter 7 is by Rodney Brooks. The photograph of St. IGNUcius in Chapter 8 is by Stian Eikeland. 37 | \fi 38 | 39 | \ifdefined\chs 40 | \noindent 封面上理查德·斯托曼的照片由Peter Hinely提供。第7章中PDP-10照片由Rodney Brooks提供。第8章中圣·IGNUcius的照片由Stian Eikeland提供。 41 | \fi 42 | -------------------------------------------------------------------------------- /faif-2.0.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | 10 | \documentclass[UTF8, a4paper, 10pt]{book} 11 | \usepackage{ctex} 12 | \usepackage{url} 13 | %% \usepackage[utf8x]{inputenc} 14 | \usepackage[Lenny]{fncychap} 15 | \clubpenalty=10000 16 | \widowpenalty=10000 17 | 18 | %% PDF setup 19 | \usepackage{hyperref} 20 | \hypersetup{colorlinks=true, 21 | citecolor=blue, 22 | filecolor=blue, 23 | linkcolor=blue, 24 | urlcolor=blue, 25 | bookmarksopen=true, 26 | pdftitle=Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution, 27 | pdfauthor=Richard Stallman and Sam Williams, 28 | pdftex} 29 | 30 | %% Index 31 | \usepackage{makeidx} 32 | \makeindex 33 | 34 | %% Endnotes 35 | \usepackage{endnotes} 36 | \renewcommand\notesname {Endnotes} 37 | 38 | %% Photos 39 | \usepackage{graphicx} 40 | \usepackage[labelformat=empty,font={small,it}, width=3.75in]{caption} 41 | 42 | %% Paper size 43 | \usepackage{geometry} 44 | \geometry{papersize={6in,9in}} 45 | 46 | \setcounter{errorcontextlines}{10} 47 | 48 | %% Output Language 49 | \def\eng{eng} 50 | \def\chs{chs} 51 | 52 | \begin{document} 53 | \title{\ifdefined\eng 54 | Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution 55 | \fi 56 | \ifdefined\chs 57 | Free as in Freedom (2.0): 理查德·斯托曼与自由软件运动 58 | \fi 59 | } 60 | \author{\ifdefined\eng 61 | Sam Williams \\ Second edition revisions by Richard M. Stallman 62 | \fi 63 | \ifdefined\chs 64 | 萨姆·威廉姆斯 \\ 第二版：理查德·斯托曼修订版 65 | \fi} 66 | \date{} 67 | 68 | \maketitle 69 | \thispagestyle{empty} 70 | \frontmatter 71 | \include{copyright} 72 | \thispagestyle{empty} 73 | \tableofcontents 74 | \include{rms-preface} 75 | \include{preface-williams} 76 | 77 | \mainmatter 78 | \include{chap01} 79 | \include{chap02} 80 | \include{chap03} 81 | \include{chap04} 82 | \include{chap05} 83 | \include{chap06} 84 | \include{chap07} 85 | \include{chap08} 86 | \include{chap09} 87 | \include{chap10} 88 | \include{chap11} 89 | \include{chap12} 90 | \include{chap13} 91 | 92 | \backmatter 93 | \include{epilogue} 94 | \include{appendix} 95 | \include{gfdl} 96 | \printindex 97 | \include{colophon} 98 | \end{document} 99 | 100 | % Initial LaTeX formatting by John Sullivan at the FSF, 2010 101 | -------------------------------------------------------------------------------- /faifv2.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | 10 | \documentclass[UTF8, a4paper, 10pt]{book} 11 | \usepackage{ctex} 12 | \usepackage{url} 13 | %% \usepackage[utf8x]{inputenc} 14 | \usepackage[Lenny]{fncychap} 15 | \clubpenalty=10000 16 | \widowpenalty=10000 17 | 18 | %% PDF setup 19 | \usepackage{hyperref} 20 | \hypersetup{colorlinks=true, 21 | citecolor=blue, 22 | filecolor=blue, 23 | linkcolor=blue, 24 | urlcolor=blue, 25 | bookmarksopen=true, 26 | pdftitle=Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution, 27 | pdfauthor=Richard Stallman and Sam Williams, 28 | pdftex} 29 | 30 | %% Index 31 | \usepackage{makeidx} 32 | \makeindex 33 | 34 | %% Endnotes 35 | \usepackage{endnotes} 36 | \renewcommand\notesname {Endnotes} 37 | 38 | %% Photos 39 | \usepackage{graphicx} 40 | \usepackage[labelformat=empty,font={small,it}, width=3.75in]{caption} 41 | 42 | %% Paper size 43 | \usepackage{geometry} 44 | \geometry{papersize={6in,9in}} 45 | 46 | \setcounter{errorcontextlines}{10} 47 | 48 | %% Output Language 49 | \def\eng{eng} 50 | \def\chs{chs} 51 | 52 | \begin{document} 53 | \title{\ifdefined\eng 54 | Free as in Freedom (2.0): Richard Stallman and the Free Software Revolution 55 | \fi 56 | \ifdefined\chs 57 | Free as in Freedom (2.0): 理查德·斯托曼与自由软件运动 58 | \fi 59 | } 60 | \author{\ifdefined\eng 61 | Sam Williams \\ Second edition revisions by Richard M. Stallman 62 | \fi 63 | \ifdefined\chs 64 | 萨姆·威廉姆斯 \\ 第二版：理查德·斯托曼修订版 65 | \fi} 66 | \date{} 67 | 68 | \maketitle 69 | \thispagestyle{empty} 70 | \frontmatter 71 | \include{copyright} 72 | \thispagestyle{empty} 73 | \tableofcontents 74 | \include{rms-preface} 75 | \include{preface-williams} 76 | 77 | \mainmatter 78 | \include{chap01} 79 | \include{chap02} 80 | \include{chap03} 81 | \include{chap04} 82 | \include{chap05} 83 | \include{chap06} 84 | \include{chap07} 85 | \include{chap08} 86 | \include{chap09} 87 | \include{chap10} 88 | \include{chap11} 89 | \include{chap12} 90 | \include{chap13} 91 | 92 | \backmatter 93 | \include{epilogue} 94 | \include{appendix} 95 | \include{gfdl} 96 | \printindex 97 | \include{colophon} 98 | \end{document} 99 | 100 | % Initial LaTeX formatting by John Sullivan at the FSF, 2010 101 | -------------------------------------------------------------------------------- /gfdl.tex: -------------------------------------------------------------------------------- 1 | \chapter{Appendix B -- GNU Free Documentation License} \label{Appendix B} 2 | \ifdefined\chs 3 | 4 | \fi 5 | 6 | \ifdefined\eng 7 | \phantomsection % so hyperref creates bookmarks 8 | \fi 9 | 10 | \ifdefined\chs 11 | 12 | \fi 13 | 14 | \ifdefined\eng 15 | \begin{center} 16 | \fi 17 | 18 | \ifdefined\chs 19 | 20 | \fi 21 | 22 | \ifdefined\eng 23 | Version 1.3, 3 November 2008 24 | \fi 25 | 26 | \ifdefined\chs 27 | 28 | \fi 29 | 30 | \ifdefined\eng 31 | \fi 32 | 33 | \ifdefined\chs 34 | 35 | \fi 36 | 37 | \ifdefined\eng 38 | Copyright \copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. 39 | 40 | \bigskip 41 | 42 | \url{http://fsf.org/} 43 | 44 | \bigskip 45 | 46 | Everyone is permitted to copy and distribute verbatim copies 47 | of this license document, but changing it is not allowed. 48 | \end{center} 49 | \fi 50 | 51 | \ifdefined\chs 52 | 53 | \fi 54 | 55 | \ifdefined\eng 56 | \fi 57 | 58 | \ifdefined\chs 59 | 60 | \fi 61 | 62 | \ifdefined\eng 63 | \begin{center} 64 | {\bf\large Preamble} 65 | \end{center} 66 | \fi 67 | 68 | \ifdefined\chs 69 | 70 | \fi 71 | 72 | \ifdefined\eng 73 | The purpose of this License is to make a manual, textbook, or other 74 | functional and useful document ``free'' in the sense of freedom: to 75 | assure everyone the effective freedom to copy and redistribute it, 76 | with or without modifying it, either commercially or noncommercially. 77 | Secondarily, this License preserves for the author and publisher a way 78 | to get credit for their work, while not being considered responsible 79 | for modifications made by others. 80 | \fi 81 | 82 | \ifdefined\chs 83 | 84 | \fi 85 | 86 | \ifdefined\eng 87 | This License is a kind of ``copyleft'', which means that derivative 88 | works of the document must themselves be free in the same sense. It 89 | complements the GNU General Public License, which is a copyleft 90 | license designed for free software. 91 | \fi 92 | 93 | \ifdefined\chs 94 | 95 | \fi 96 | 97 | \ifdefined\eng 98 | We have designed this License in order to use it for manuals for free 99 | software, because free software needs free documentation: a free 100 | program should come with manuals providing the same freedoms that the 101 | software does. But this License is not limited to software manuals; 102 | it can be used for any textual work, regardless of subject matter or 103 | whether it is published as a printed book. We recommend this License 104 | principally for works whose purpose is instruction or reference. 105 | \fi 106 | 107 | \ifdefined\chs 108 | 109 | \fi 110 | 111 | \ifdefined\eng 112 | \fi 113 | 114 | \ifdefined\chs 115 | 116 | \fi 117 | 118 | \ifdefined\eng 119 | \begin{center} 120 | {\Large\bf 1. APPLICABILITY AND DEFINITIONS\par} 121 | \phantomsection 122 | \end{center} 123 | \fi 124 | 125 | \ifdefined\chs 126 | 127 | \fi 128 | 129 | \ifdefined\eng 130 | This License applies to any manual or other work, in any medium, that 131 | contains a notice placed by the copyright holder saying it can be 132 | distributed under the terms of this License. Such a notice grants a 133 | world-wide, royalty-free license, unlimited in duration, to use that 134 | work under the conditions stated herein. The ``\textbf{Document}'', below, 135 | refers to any such manual or work. Any member of the public is a 136 | licensee, and is addressed as ``\textbf{you}''. You accept the license if you 137 | copy, modify or distribute the work in a way requiring permission 138 | under copyright law. 139 | \fi 140 | 141 | \ifdefined\chs 142 | 143 | \fi 144 | 145 | \ifdefined\eng 146 | A ``\textbf{Modified Version}'' of the Document means any work containing the 147 | Document or a portion of it, either copied verbatim, or with 148 | modifications and/or translated into another language. 149 | \fi 150 | 151 | \ifdefined\chs 152 | 153 | \fi 154 | 155 | \ifdefined\eng 156 | A ``\textbf{Secondary Section}'' is a named appendix or a front-matter section of 157 | the Document that deals exclusively with the relationship of the 158 | publishers or authors of the Document to the Document's overall subject 159 | (or to related matters) and contains nothing that could fall directly 160 | within that overall subject. (Thus, if the Document is in part a 161 | textbook of mathematics, a Secondary Section may not explain any 162 | mathematics.) The relationship could be a matter of historical 163 | connection with the subject or with related matters, or of legal, 164 | commercial, philosophical, ethical or political position regarding 165 | them. 166 | \fi 167 | 168 | \ifdefined\chs 169 | 170 | \fi 171 | 172 | \ifdefined\eng 173 | The ``\textbf{Invariant Sections}'' are certain Secondary Sections whose titles 174 | are designated, as being those of Invariant Sections, in the notice 175 | that says that the Document is released under this License. If a 176 | section does not fit the above definition of Secondary then it is not 177 | allowed to be designated as Invariant. The Document may contain zero 178 | Invariant Sections. If the Document does not identify any Invariant 179 | Sections then there are none. 180 | \fi 181 | 182 | \ifdefined\chs 183 | 184 | \fi 185 | 186 | \ifdefined\eng 187 | The ``\textbf{Cover Texts}'' are certain short passages of text that are listed, 188 | as Front-Cover Texts or Back-Cover Texts, in the notice that says that 189 | the Document is released under this License. A Front-Cover Text may 190 | be at most 5 words, and a Back-Cover Text may be at most 25 words. 191 | \fi 192 | 193 | \ifdefined\chs 194 | 195 | \fi 196 | 197 | \ifdefined\eng 198 | A ``\textbf{Transparent}'' copy of the Document means a machine-readable copy, 199 | represented in a format whose specification is available to the 200 | general public, that is suitable for revising the document 201 | straightforwardly with generic text editors or (for images composed of 202 | pixels) generic paint programs or (for drawings) some widely available 203 | drawing editor, and that is suitable for input to text formatters or 204 | for automatic translation to a variety of formats suitable for input 205 | to text formatters. A copy made in an otherwise Transparent file 206 | format whose markup, or absence of markup, has been arranged to thwart 207 | or discourage subsequent modification by readers is not Transparent. 208 | An image format is not Transparent if used for any substantial amount 209 | of text. A copy that is not ``Transparent'' is called ``\textbf{Opaque}''. 210 | \fi 211 | 212 | \ifdefined\chs 213 | 214 | \fi 215 | 216 | \ifdefined\eng 217 | Examples of suitable formats for Transparent copies include plain 218 | ASCII without markup, Texinfo input format, LaTeX input format, SGML 219 | or XML using a publicly available DTD, and standard-conforming simple 220 | HTML, PostScript or PDF designed for human modification. Examples of 221 | transparent image formats include PNG, XCF and JPG. Opaque formats 222 | include proprietary formats that can be read and edited only by 223 | proprietary word processors, SGML or XML for which the DTD and/or 224 | processing tools are not generally available, and the 225 | machine-generated HTML, PostScript or PDF produced by some word 226 | processors for output purposes only. 227 | \fi 228 | 229 | \ifdefined\chs 230 | 231 | \fi 232 | 233 | \ifdefined\eng 234 | The ``\textbf{Title Page}'' means, for a printed book, the title page itself, 235 | plus such following pages as are needed to hold, legibly, the material 236 | this License requires to appear in the title page. For works in 237 | formats which do not have any title page as such, ``Title Page'' means 238 | the text near the most prominent appearance of the work's title, 239 | preceding the beginning of the body of the text. 240 | \fi 241 | 242 | \ifdefined\chs 243 | 244 | \fi 245 | 246 | \ifdefined\eng 247 | The ``\textbf{publisher}'' means any person or entity that distributes 248 | copies of the Document to the public. 249 | \fi 250 | 251 | \ifdefined\chs 252 | 253 | \fi 254 | 255 | \ifdefined\eng 256 | A section ``\textbf{Entitled XYZ}'' means a named subunit of the Document whose 257 | title either is precisely XYZ or contains XYZ in parentheses following 258 | text that translates XYZ in another language. (Here XYZ stands for a 259 | specific section name mentioned below, such as ``\textbf{Acknowledgements}'', 260 | ``\textbf{Dedications}'', ``\textbf{Endorsements}'', or ``\textbf{History}''.) 261 | To ``\textbf{Preserve the Title}'' 262 | of such a section when you modify the Document means that it remains a 263 | section ``Entitled XYZ'' according to this definition. 264 | \fi 265 | 266 | \ifdefined\chs 267 | 268 | \fi 269 | 270 | \ifdefined\eng 271 | The Document may include Warranty Disclaimers next to the notice which 272 | states that this License applies to the Document. These Warranty 273 | Disclaimers are considered to be included by reference in this 274 | License, but only as regards disclaiming warranties: any other 275 | implication that these Warranty Disclaimers may have is void and has 276 | no effect on the meaning of this License. 277 | \fi 278 | 279 | \ifdefined\chs 280 | 281 | \fi 282 | 283 | \ifdefined\eng 284 | \fi 285 | 286 | \ifdefined\chs 287 | 288 | \fi 289 | 290 | \ifdefined\eng 291 | \begin{center} 292 | {\Large\bf 2. VERBATIM COPYING\par} 293 | \phantomsection 294 | \end{center} 295 | \fi 296 | 297 | \ifdefined\chs 298 | 299 | \fi 300 | 301 | \ifdefined\eng 302 | You may copy and distribute the Document in any medium, either 303 | commercially or noncommercially, provided that this License, the 304 | copyright notices, and the license notice saying this License applies 305 | to the Document are reproduced in all copies, and that you add no other 306 | conditions whatsoever to those of this License. You may not use 307 | technical measures to obstruct or control the reading or further 308 | copying of the copies you make or distribute. However, you may accept 309 | compensation in exchange for copies. If you distribute a large enough 310 | number of copies you must also follow the conditions in section~3. 311 | \fi 312 | 313 | \ifdefined\chs 314 | 315 | \fi 316 | 317 | \ifdefined\eng 318 | You may also lend copies, under the same conditions stated above, and 319 | you may publicly display copies. 320 | \fi 321 | 322 | \ifdefined\chs 323 | 324 | \fi 325 | 326 | \ifdefined\eng 327 | \fi 328 | 329 | \ifdefined\chs 330 | 331 | \fi 332 | 333 | \ifdefined\eng 334 | \begin{center} 335 | {\Large\bf 3. COPYING IN QUANTITY\par} 336 | \phantomsection 337 | \end{center} 338 | \fi 339 | 340 | \ifdefined\chs 341 | 342 | \fi 343 | 344 | \ifdefined\eng 345 | \fi 346 | 347 | \ifdefined\chs 348 | 349 | \fi 350 | 351 | \ifdefined\eng 352 | If you publish printed copies (or copies in media that commonly have 353 | printed covers) of the Document, numbering more than 100, and the 354 | Document's license notice requires Cover Texts, you must enclose the 355 | copies in covers that carry, clearly and legibly, all these Cover 356 | Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on 357 | the back cover. Both covers must also clearly and legibly identify 358 | you as the publisher of these copies. The front cover must present 359 | the full title with all words of the title equally prominent and 360 | visible. You may add other material on the covers in addition. 361 | Copying with changes limited to the covers, as long as they preserve 362 | the title of the Document and satisfy these conditions, can be treated 363 | as verbatim copying in other respects. 364 | \fi 365 | 366 | \ifdefined\chs 367 | 368 | \fi 369 | 370 | \ifdefined\eng 371 | If the required texts for either cover are too voluminous to fit 372 | legibly, you should put the first ones listed (as many as fit 373 | reasonably) on the actual cover, and continue the rest onto adjacent 374 | pages. 375 | \fi 376 | 377 | \ifdefined\chs 378 | 379 | \fi 380 | 381 | \ifdefined\eng 382 | If you publish or distribute Opaque copies of the Document numbering 383 | more than 100, you must either include a machine-readable Transparent 384 | copy along with each Opaque copy, or state in or with each Opaque copy 385 | a computer-network location from which the general network-using 386 | public has access to download using public-standard network protocols 387 | a complete Transparent copy of the Document, free of added material. 388 | If you use the latter option, you must take reasonably prudent steps, 389 | when you begin distribution of Opaque copies in quantity, to ensure 390 | that this Transparent copy will remain thus accessible at the stated 391 | location until at least one year after the last time you distribute an 392 | Opaque copy (directly or through your agents or retailers) of that 393 | edition to the public. 394 | \fi 395 | 396 | \ifdefined\chs 397 | 398 | \fi 399 | 400 | \ifdefined\eng 401 | It is requested, but not required, that you contact the authors of the 402 | Document well before redistributing any large number of copies, to give 403 | them a chance to provide you with an updated version of the Document. 404 | \fi 405 | 406 | \ifdefined\chs 407 | 408 | \fi 409 | 410 | \ifdefined\eng 411 | \fi 412 | 413 | \ifdefined\chs 414 | 415 | \fi 416 | 417 | \ifdefined\eng 418 | \begin{center} 419 | {\Large\bf 4. MODIFICATIONS\par} 420 | \phantomsection 421 | \end{center} 422 | \fi 423 | 424 | \ifdefined\chs 425 | 426 | \fi 427 | 428 | \ifdefined\eng 429 | You may copy and distribute a Modified Version of the Document under 430 | the conditions of sections 2 and 3 above, provided that you release 431 | the Modified Version under precisely this License, with the Modified 432 | Version filling the role of the Document, thus licensing distribution 433 | and modification of the Modified Version to whoever possesses a copy 434 | of it. In addition, you must do these things in the Modified Version: 435 | \fi 436 | 437 | \ifdefined\chs 438 | 439 | \fi 440 | 441 | \ifdefined\eng 442 | \begin{itemize} 443 | \item[A.] 444 | Use in the Title Page (and on the covers, if any) a title distinct 445 | from that of the Document, and from those of previous versions 446 | (which should, if there were any, be listed in the History section 447 | of the Document). You may use the same title as a previous version 448 | if the original publisher of that version gives permission. 449 | 450 | \item[B.] 451 | List on the Title Page, as authors, one or more persons or entities 452 | responsible for authorship of the modifications in the Modified 453 | Version, together with at least five of the principal authors of the 454 | Document (all of its principal authors, if it has fewer than five), 455 | unless they release you from this requirement. 456 | 457 | \item[C.] 458 | State on the Title page the name of the publisher of the 459 | Modified Version, as the publisher. 460 | 461 | \item[D.] 462 | Preserve all the copyright notices of the Document. 463 | 464 | \item[E.] 465 | Add an appropriate copyright notice for your modifications 466 | adjacent to the other copyright notices. 467 | 468 | \item[F.] 469 | Include, immediately after the copyright notices, a license notice 470 | giving the public permission to use the Modified Version under the 471 | terms of this License, in the form shown in the Addendum below. 472 | 473 | \item[G.] 474 | Preserve in that license notice the full lists of Invariant Sections 475 | and required Cover Texts given in the Document's license notice. 476 | 477 | \item[H.] 478 | Include an unaltered copy of this License. 479 | 480 | \item[I.] 481 | Preserve the section Entitled ``History'', Preserve its Title, and add 482 | to it an item stating at least the title, year, new authors, and 483 | publisher of the Modified Version as given on the Title Page. If 484 | there is no section Entitled ``History'' in the Document, create one 485 | stating the title, year, authors, and publisher of the Document as 486 | given on its Title Page, then add an item describing the Modified 487 | Version as stated in the previous sentence. 488 | 489 | \item[J.] 490 | Preserve the network location, if any, given in the Document for 491 | public access to a Transparent copy of the Document, and likewise 492 | the network locations given in the Document for previous versions 493 | it was based on. These may be placed in the ``History'' section. 494 | You may omit a network location for a work that was published at 495 | least four years before the Document itself, or if the original 496 | publisher of the version it refers to gives permission. 497 | 498 | \item[K.] 499 | For any section Entitled ``Acknowledgements'' or ``Dedications'', 500 | Preserve the Title of the section, and preserve in the section all 501 | the substance and tone of each of the contributor acknowledgements 502 | and/or dedications given therein. 503 | 504 | \item[L.] 505 | Preserve all the Invariant Sections of the Document, 506 | unaltered in their text and in their titles. Section numbers 507 | or the equivalent are not considered part of the section titles. 508 | 509 | \item[M.] 510 | Delete any section Entitled ``Endorsements''. Such a section 511 | may not be included in the Modified Version. 512 | 513 | \item[N.] 514 | Do not retitle any existing section to be Entitled ``Endorsements'' 515 | or to conflict in title with any Invariant Section. 516 | 517 | \item[O.] 518 | Preserve any Warranty Disclaimers. 519 | \end{itemize} 520 | \fi 521 | 522 | \ifdefined\chs 523 | 524 | \fi 525 | 526 | \ifdefined\eng 527 | If the Modified Version includes new front-matter sections or 528 | appendices that qualify as Secondary Sections and contain no material 529 | copied from the Document, you may at your option designate some or all 530 | of these sections as invariant. To do this, add their titles to the 531 | list of Invariant Sections in the Modified Version's license notice. 532 | These titles must be distinct from any other section titles. 533 | \fi 534 | 535 | \ifdefined\chs 536 | 537 | \fi 538 | 539 | \ifdefined\eng 540 | You may add a section Entitled ``Endorsements'', provided it contains 541 | nothing but endorsements of your Modified Version by various 542 | parties---for example, statements of peer review or that the text has 543 | been approved by an organization as the authoritative definition of a 544 | standard. 545 | \fi 546 | 547 | \ifdefined\chs 548 | 549 | \fi 550 | 551 | \ifdefined\eng 552 | You may add a passage of up to five words as a Front-Cover Text, and a 553 | passage of up to 25 words as a Back-Cover Text, to the end of the list 554 | of Cover Texts in the Modified Version. Only one passage of 555 | Front-Cover Text and one of Back-Cover Text may be added by (or 556 | through arrangements made by) any one entity. If the Document already 557 | includes a cover text for the same cover, previously added by you or 558 | by arrangement made by the same entity you are acting on behalf of, 559 | you may not add another; but you may replace the old one, on explicit 560 | permission from the previous publisher that added the old one. 561 | \fi 562 | 563 | \ifdefined\chs 564 | 565 | \fi 566 | 567 | \ifdefined\eng 568 | The author(s) and publisher(s) of the Document do not by this License 569 | give permission to use their names for publicity for or to assert or 570 | imply endorsement of any Modified Version. 571 | \fi 572 | 573 | \ifdefined\chs 574 | 575 | \fi 576 | 577 | \ifdefined\eng 578 | \pagebreak 579 | \begin{center} 580 | {\Large\bf 5. COMBINING DOCUMENTS\par} 581 | \phantomsection 582 | \end{center} 583 | \fi 584 | 585 | \ifdefined\chs 586 | 587 | \fi 588 | 589 | \ifdefined\eng 590 | \fi 591 | 592 | \ifdefined\chs 593 | 594 | \fi 595 | 596 | \ifdefined\eng 597 | You may combine the Document with other documents released under this 598 | License, under the terms defined in section~4 above for modified 599 | versions, provided that you include in the combination all of the 600 | Invariant Sections of all of the original documents, unmodified, and 601 | list them all as Invariant Sections of your combined work in its 602 | license notice, and that you preserve all their Warranty Disclaimers. 603 | \fi 604 | 605 | \ifdefined\chs 606 | 607 | \fi 608 | 609 | \ifdefined\eng 610 | The combined work need only contain one copy of this License, and 611 | multiple identical Invariant Sections may be replaced with a single 612 | copy. If there are multiple Invariant Sections with the same name but 613 | different contents, make the title of each such section unique by 614 | adding at the end of it, in parentheses, the name of the original 615 | author or publisher of that section if known, or else a unique number. 616 | Make the same adjustment to the section titles in the list of 617 | Invariant Sections in the license notice of the combined work. 618 | \fi 619 | 620 | \ifdefined\chs 621 | 622 | \fi 623 | 624 | \ifdefined\eng 625 | In the combination, you must combine any sections Entitled ``History'' 626 | in the various original documents, forming one section Entitled 627 | ``History''; likewise combine any sections Entitled ``Acknowledgements'', 628 | and any sections Entitled ``Dedications''. You must delete all sections 629 | Entitled ``Endorsements''. 630 | \fi 631 | 632 | \ifdefined\chs 633 | 634 | \fi 635 | 636 | \ifdefined\eng 637 | \begin{center} 638 | {\Large\bf 6. COLLECTIONS OF DOCUMENTS\par} 639 | \phantomsection 640 | \end{center} 641 | \fi 642 | 643 | \ifdefined\chs 644 | 645 | \fi 646 | 647 | \ifdefined\eng 648 | You may make a collection consisting of the Document and other documents 649 | released under this License, and replace the individual copies of this 650 | License in the various documents with a single copy that is included in 651 | the collection, provided that you follow the rules of this License for 652 | verbatim copying of each of the documents in all other respects. 653 | \fi 654 | 655 | \ifdefined\chs 656 | 657 | \fi 658 | 659 | \ifdefined\eng 660 | You may extract a single document from such a collection, and distribute 661 | it individually under this License, provided you insert a copy of this 662 | License into the extracted document, and follow this License in all 663 | other respects regarding verbatim copying of that document. 664 | \fi 665 | 666 | \ifdefined\chs 667 | 668 | \fi 669 | 670 | \ifdefined\eng 671 | \fi 672 | 673 | \ifdefined\chs 674 | 675 | \fi 676 | 677 | \ifdefined\eng 678 | \begin{center} 679 | {\Large\bf 7. AGGREGATION WITH INDEPENDENT WORKS\par} 680 | \phantomsection 681 | \end{center} 682 | \fi 683 | 684 | \ifdefined\chs 685 | 686 | \fi 687 | 688 | \ifdefined\eng 689 | \fi 690 | 691 | \ifdefined\chs 692 | 693 | \fi 694 | 695 | \ifdefined\eng 696 | A compilation of the Document or its derivatives with other separate 697 | and independent documents or works, in or on a volume of a storage or 698 | distribution medium, is called an ``aggregate'' if the copyright 699 | resulting from the compilation is not used to limit the legal rights 700 | of the compilation's users beyond what the individual works permit. 701 | When the Document is included in an aggregate, this License does not 702 | apply to the other works in the aggregate which are not themselves 703 | derivative works of the Document. 704 | \fi 705 | 706 | \ifdefined\chs 707 | 708 | \fi 709 | 710 | \ifdefined\eng 711 | If the Cover Text requirement of section~3 is applicable to these 712 | copies of the Document, then if the Document is less than one half of 713 | the entire aggregate, the Document's Cover Texts may be placed on 714 | covers that bracket the Document within the aggregate, or the 715 | electronic equivalent of covers if the Document is in electronic form. 716 | Otherwise they must appear on printed covers that bracket the whole 717 | aggregate. 718 | \fi 719 | 720 | \ifdefined\chs 721 | 722 | \fi 723 | 724 | \ifdefined\eng 725 | \fi 726 | 727 | \ifdefined\chs 728 | 729 | \fi 730 | 731 | \ifdefined\eng 732 | \begin{center} 733 | {\Large\bf 8. TRANSLATION\par} 734 | \phantomsection 735 | \end{center} 736 | \fi 737 | 738 | \ifdefined\chs 739 | 740 | \fi 741 | 742 | \ifdefined\eng 743 | \fi 744 | 745 | \ifdefined\chs 746 | 747 | \fi 748 | 749 | \ifdefined\eng 750 | Translation is considered a kind of modification, so you may 751 | distribute translations of the Document under the terms of section~4. 752 | Replacing Invariant Sections with translations requires special 753 | permission from their copyright holders, but you may include 754 | translations of some or all Invariant Sections in addition to the 755 | original versions of these Invariant Sections. You may include a 756 | translation of this License, and all the license notices in the 757 | Document, and any Warranty Disclaimers, provided that you also include 758 | the original English version of this License and the original versions 759 | of those notices and disclaimers. In case of a disagreement between 760 | the translation and the original version of this License or a notice 761 | or disclaimer, the original version will prevail. 762 | \fi 763 | 764 | \ifdefined\chs 765 | 766 | \fi 767 | 768 | \ifdefined\eng 769 | If a section in the Document is Entitled ``Acknowledgements'', 770 | ``Dedications'', or ``History'', the requirement (section~4) to Preserve 771 | its Title (section~1) will typically require changing the actual 772 | title. 773 | \fi 774 | 775 | \ifdefined\chs 776 | 777 | \fi 778 | 779 | \ifdefined\eng 780 | \fi 781 | 782 | \ifdefined\chs 783 | 784 | \fi 785 | 786 | \ifdefined\eng 787 | \begin{center} 788 | {\Large\bf 9. TERMINATION\par} 789 | \phantomsection 790 | \end{center} 791 | \fi 792 | 793 | \ifdefined\chs 794 | 795 | \fi 796 | 797 | \ifdefined\eng 798 | \fi 799 | 800 | \ifdefined\chs 801 | 802 | \fi 803 | 804 | \ifdefined\eng 805 | You may not copy, modify, sublicense, or distribute the Document 806 | except as expressly provided under this License. Any attempt 807 | otherwise to copy, modify, sublicense, or distribute it is void, and 808 | will automatically terminate your rights under this License. 809 | \fi 810 | 811 | \ifdefined\chs 812 | 813 | \fi 814 | 815 | \ifdefined\eng 816 | However, if you cease all violation of this License, then your license 817 | from a particular copyright holder is reinstated (a) provisionally, 818 | unless and until the copyright holder explicitly and finally 819 | terminates your license, and (b) permanently, if the copyright holder 820 | fails to notify you of the violation by some reasonable means prior to 821 | 60 days after the cessation. 822 | \fi 823 | 824 | \ifdefined\chs 825 | 826 | \fi 827 | 828 | \ifdefined\eng 829 | Moreover, your license from a particular copyright holder is 830 | reinstated permanently if the copyright holder notifies you of the 831 | violation by some reasonable means, this is the first time you have 832 | received notice of violation of this License (for any work) from that 833 | copyright holder, and you cure the violation prior to 30 days after 834 | your receipt of the notice. 835 | \fi 836 | 837 | \ifdefined\chs 838 | 839 | \fi 840 | 841 | \ifdefined\eng 842 | Termination of your rights under this section does not terminate the 843 | licenses of parties who have received copies or rights from you under 844 | this License. If your rights have been terminated and not permanently 845 | reinstated, receipt of a copy of some or all of the same material does 846 | not give you any rights to use it. 847 | \fi 848 | 849 | \ifdefined\chs 850 | 851 | \fi 852 | 853 | \ifdefined\eng 854 | \fi 855 | 856 | \ifdefined\chs 857 | 858 | \fi 859 | 860 | \ifdefined\eng 861 | \begin{center} 862 | {\Large\bf 10. FUTURE REVISIONS OF THIS LICENSE\par} 863 | \phantomsection 864 | \end{center} 865 | \fi 866 | 867 | \ifdefined\chs 868 | 869 | \fi 870 | 871 | \ifdefined\eng 872 | \fi 873 | 874 | \ifdefined\chs 875 | 876 | \fi 877 | 878 | \ifdefined\eng 879 | The Free Software Foundation may publish new, revised versions 880 | of the GNU Free Documentation License from time to time. Such new 881 | versions will be similar in spirit to the present version, but may 882 | differ in detail to address new problems or concerns. See 883 | \url{http://www.gnu.org/copyleft/}. 884 | \fi 885 | 886 | \ifdefined\chs 887 | 888 | \fi 889 | 890 | \ifdefined\eng 891 | Each version of the License is given a distinguishing version number. 892 | If the Document specifies that a particular numbered version of this 893 | License ``or any later version'' applies to it, you have the option of 894 | following the terms and conditions either of that specified version or 895 | of any later version that has been published (not as a draft) by the 896 | Free Software Foundation. If the Document does not specify a version 897 | number of this License, you may choose any version ever published (not 898 | as a draft) by the Free Software Foundation. If the Document 899 | specifies that a proxy can decide which future versions of this 900 | License can be used, that proxy's public statement of acceptance of a 901 | version permanently authorizes you to choose that version for the 902 | Document. 903 | \fi 904 | 905 | \ifdefined\chs 906 | 907 | \fi 908 | 909 | \ifdefined\eng 910 | \fi 911 | 912 | \ifdefined\chs 913 | 914 | \fi 915 | 916 | \ifdefined\eng 917 | \begin{center} 918 | {\Large\bf 11. RELICENSING\par} 919 | \phantomsection 920 | \end{center} 921 | \fi 922 | 923 | \ifdefined\chs 924 | 925 | \fi 926 | 927 | \ifdefined\eng 928 | \fi 929 | 930 | \ifdefined\chs 931 | 932 | \fi 933 | 934 | \ifdefined\eng 935 | ``Massive Multiauthor Collaboration Site'' (or ``MMC Site'') means any 936 | World Wide Web server that publishes copyrightable works and also 937 | provides prominent facilities for anybody to edit those works. A 938 | public wiki that anybody can edit is an example of such a server. A 939 | ``Massive Multiauthor Collaboration'' (or ``MMC'') contained in the 940 | site means any set of copyrightable works thus published on the MMC 941 | site. 942 | \fi 943 | 944 | \ifdefined\chs 945 | 946 | \fi 947 | 948 | \ifdefined\eng 949 | ``CC-BY-SA'' means the Creative Commons Attribution-Share Alike 3.0 950 | license published by Creative Commons Corporation, a not-for-profit 951 | corporation with a principal place of business in San Francisco, 952 | California, as well as future copyleft versions of that license 953 | published by that same organization. 954 | \fi 955 | 956 | \ifdefined\chs 957 | 958 | \fi 959 | 960 | \ifdefined\eng 961 | ``Incorporate'' means to publish or republish a Document, in whole or 962 | in part, as part of another Document. 963 | \fi 964 | 965 | \ifdefined\chs 966 | 967 | \fi 968 | 969 | \ifdefined\eng 970 | An MMC is ``eligible for relicensing'' if it is licensed under this 971 | License, and if all works that were first published under this License 972 | somewhere other than this MMC, and subsequently incorporated in whole 973 | or in part into the MMC, (1) had no cover texts or invariant sections, 974 | and (2) were thus incorporated prior to November 1, 2008. 975 | \fi 976 | 977 | \ifdefined\chs 978 | 979 | \fi 980 | 981 | \ifdefined\eng 982 | The operator of an MMC Site may republish an MMC contained in the site 983 | under CC-BY-SA on the same site at any time before August 1, 2009, 984 | provided the MMC is eligible for relicensing. 985 | \fi 986 | 987 | \ifdefined\chs 988 | 989 | \fi 990 | 991 | \ifdefined\eng 992 | \fi 993 | 994 | \ifdefined\chs 995 | 996 | \fi 997 | 998 | \ifdefined\eng 999 | \begin{center} 1000 | {\Large\bf ADDENDUM: How to use this License for your documents\par} 1001 | \phantomsection 1002 | \end{center} 1003 | \fi 1004 | 1005 | \ifdefined\chs 1006 | 1007 | \fi 1008 | 1009 | \ifdefined\eng 1010 | To use this License in a document you have written, include a copy of 1011 | the License in the document and put the following copyright and 1012 | license notices just after the title page: 1013 | \fi 1014 | 1015 | \ifdefined\chs 1016 | 1017 | \fi 1018 | 1019 | \ifdefined\eng 1020 | \bigskip 1021 | \begin{quote} 1022 | Copyright \copyright{} YEAR YOUR NAME. 1023 | Permission is granted to copy, distribute and/or modify this document 1024 | under the terms of the GNU Free Documentation License, Version 1.3 1025 | or any later version published by the Free Software Foundation; 1026 | with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. 1027 | A copy of the license is included in the section entitled ``GNU 1028 | Free Documentation License''. 1029 | \end{quote} 1030 | \bigskip 1031 | 1032 | If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, 1033 | replace the ``with \dots\ Texts.'' line with this: 1034 | \fi 1035 | 1036 | \ifdefined\chs 1037 | 1038 | \fi 1039 | 1040 | \ifdefined\eng 1041 | \bigskip 1042 | \begin{quote} 1043 | with the Invariant Sections being LIST THEIR TITLES, with the 1044 | Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. 1045 | \end{quote} 1046 | \bigskip 1047 | 1048 | If you have Invariant Sections without Cover Texts, or some other 1049 | combination of the three, merge those two alternatives to suit the 1050 | situation. 1051 | \fi 1052 | 1053 | \ifdefined\chs 1054 | 1055 | \fi 1056 | 1057 | \ifdefined\eng 1058 | If your document contains nontrivial examples of program code, we 1059 | recommend releasing these examples in parallel under your choice of 1060 | free software license, such as the GNU General Public License, 1061 | to permit their use in free software. 1062 | \fi 1063 | -------------------------------------------------------------------------------- /names.txt: -------------------------------------------------------------------------------- 1 | 布莱恩·瑞德（Brian Reid） 2 | 格林布拉特 Richard Greenblatt 3 | 休伯特·德莱弗斯 Hubert Dreyfus 4 | 比尔·高斯伯 Bill Gosper 5 | 杰拉尔德·萨斯曼 Gerald Sussman 6 | 道格·英格巴特 Doug Engelbart 7 | 卡尔·米克尔松（Carl Mikkelson） 8 | 盖·斯蒂尔（Guy Steele) 9 | 史蒂芬·李维（Steven Levy） 10 | 哈尔·埃布尔森（Hal Abelson） 11 | 约瑟夫·魏岑鲍姆（Joseph Weizenbaum） 12 | 约翰·麦卡锡（John McCarthy） 13 | 马歇尔·柯克·麦库西克（Marshall Kirk McKusick） 14 | 唐·霍普金斯（Don Hopkins） 15 | N. P. 纽奎斯特所 (N. P. Newquist) 16 | 约翰·亨利（John Henry) 17 | 李奇·莫林（Rich Morin） 18 | 比尔·乔伊（Bill Joy） 19 | 詹姆斯·高斯林（James Gosling） 20 | 罗伯特·查瑟尔（Robert Chassell） 21 | 埃文·列伊博维奇（Evan Leibovitch） 22 | 艾瑞克·雷蒙德（Eric Raymond） 23 | 克林顿（Clinton） 24 | 比尔·乔伊（Bill Joy） 25 | 马克·费雪（Mark Fischer） 26 | 约翰·吉尔摩（John Gilmore） 27 | 拉里·华尔（Larry Wall） 28 | 哈尔·艾贝尔森 （Hal Abelson） 29 | 乔安妮·科斯特洛（Joanne Costello） 30 | 林纳斯·托瓦兹（Linus Torvalds） 31 | 杰里·科恩（Jerry Cohen） 32 | 基思·博斯蒂克(Keith Bostic) 33 | 布鲁斯·佩伦斯(Bruce Perens) 34 | 迈克尔·蒂曼(Michale Tiemann) 35 | 杰瑞米·埃里森(Jeremy Allison) 36 | 安德鲁·塔嫩鲍姆(Andrew Tanenbaum) 37 | 罗伯特·查瑟尔(Robert Chassell) 38 | 罗伯特·杨(Robert Young) 39 | 伊恩·默多克(Ian Murdock) 40 | 彼得·萨卢斯(Peter Salus) 41 | 埃里克·斯蒂芬·雷蒙德(Eric Steven Raymond) 埃里克·雷蒙德 42 | 克里斯汀·彼德森（Christine Peterson） 43 | 伊本·莫格林（Eben Moglen） 44 | 瑟古德·马歇尔(Thurgood Marshall) 45 | 艾利斯·哈利(Alex Haley) 46 | 特蕾西·帕蒂森(Tracy Pattison) 47 | 泰德·尼尔森(Ted Nelson) 西奥多·霍尔姆·尼尔森 48 | 49 | Stallman (1979) 参见理查德·斯托曼，人工智能实验室备忘录（1979年），《EMACS：可扩展，可定制的全屏编辑器》。本书的引文来自：http://www.gnu.org/software/emacs/emacs-paper.html 50 | Stallman (1986) 参见理查德在瑞典皇家技术研究所的演讲（1986年10月30日）：http://www.gnu.org/philosophy/stallman-kth.html 51 | Hacker 参见史蒂芬·李维（Steven Levy），《黑客》（1984年，美国企鹅出版社），第417页。 52 | N. P. 纽奎斯特所著的《大脑创作家》（The Brain Maker）一书 53 | 54 | 55 | 56 | 57 | ch01 58 | Richard M. Stallman 理查德·M·斯托曼 59 | Brian Reid 布莱恩·瑞德 60 | Robert Sproull 罗伯特·斯布鲁 61 | Howard Cannon 霍华德·坎农 62 | 63 | ch02 64 | Craig Mundie 克雷格·蒙迪 65 | Linus Torvalds 林纳斯·托瓦兹 66 | Shubha Ghos 67 | Mike Uretsky 麦克·乌列茨基 68 | Edmond Schonberg 埃德蒙·舍恩伯格 69 | Eben Moglen 伊本·莫格林 70 | 71 | ch03 72 | Alice Lippman 爱丽丝·李普曼 73 | Martin Gardner 马丁·加德纳 74 | Maurice Lippman 莫里斯·李普曼 75 | Daniel Stallman 丹尼尔·斯托曼 76 | Johnny Unitas 约翰尼·尤尼塔斯 77 | Dan Chess 丹·柴斯 78 | Seth Breidbart 赛思·布莱德巴特 79 | Steve Silberman史蒂夫·西尔贝曼 80 | 81 | ch04 82 | 83 | Michael Gross 迈克尔·格劳斯 84 | 85 | ch09 86 | 87 | Hal Abelson 哈尔·艾贝尔森 88 | Mike Fischer 麦克·费雪 89 | Joanne Costello 乔安妮·科斯特洛 90 | Mark Fischer 马克·费雪 91 | John Gilmore 约翰·吉尔摩 92 | -------------------------------------------------------------------------------- /preface-williams.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | \chapter{\ifdefined\eng 10 | Preface by Sam Williams 11 | \fi 12 | \ifdefined\chs 13 | 萨姆·威廉姆斯的前言 14 | \fi 15 | } 16 | 17 | \ifdefined\eng 18 | This summer marks the 10th anniversary of the email exchange that set 19 | in motion the writing of \textit{Free as in Freedom: Richard 20 | Stallman's Crusade for Free Software} and, by extension, the work 21 | prefaced here, \textit{Richard Stallman and the Free Software 22 | Revolution}. 23 | \fi 24 | 25 | \ifdefined\chs 26 | 27 | \fi 28 | 29 | \ifdefined\eng 30 | Needless to say, a lot has changed over the intervening decade. 31 | \fi 32 | 33 | \ifdefined\chs 34 | 35 | \fi 36 | 37 | \ifdefined\eng 38 | Originally conceived in an era of American triumphalism, the book's 39 | main storyline -- about one man's Jeremiah-like efforts to enlighten 40 | fellow software developers as to the ethical, if not economic, 41 | shortsightedness of a commercial system bent on turning the free range 42 | intellectual culture that gave birth to computer science into a rude 43 | agglomeration of proprietary gated communities -- seems almost 44 | nostalgic, a return to the days when the techno-capitalist system 45 | seemed to be working just fine, barring the criticism of a few 46 | outlying skeptics. 47 | \fi 48 | 49 | \ifdefined\chs 50 | 51 | \fi 52 | 53 | \ifdefined\eng 54 | Now that doubting the system has become almost a common virtue, it 55 | helps to look at what narrative threads, if any, remained consistent 56 | over the last ten years. 57 | \fi 58 | 59 | \ifdefined\chs 60 | 61 | \fi 62 | 63 | \ifdefined\eng 64 | While I don't follow the software industry as closely as I once did, 65 | one thing that leaps out now, even more than it did then, is the ease 66 | with which ordinary consumers have proven willing to cede vast swaths 67 | of private information and personal user liberty in exchange for 68 | riding atop the coolest technology ``platform'' or the latest networking 69 | trend. 70 | \fi 71 | 72 | \ifdefined\chs 73 | 74 | \fi 75 | 76 | \ifdefined\eng 77 | A few years ago, I might have dubbed this the ``iPod Effect,'' a 78 | shorthand salute to Apple co-founder Steve Jobs' unrivaled success in 79 | getting both the music industry and digital music listeners to put 80 | aside years of doubt and mutual animosity to rally around a single, 81 | sexy device -- the Apple iPod -- and its restrictive licensing regime, 82 | iTunes. Were I pitching the story to a magazine or newspaper nowadays, 83 | I d probably have to call it the ``iPad Effect'' or maybe the ``Kindle 84 | Effect'' both in an attempt to keep up with the evolving brand names 85 | and to acknowledge parallel, tectonic shifts in the realm of daily 86 | journalism and electronic book publishing. 87 | \fi 88 | 89 | \ifdefined\chs 90 | 91 | \fi 92 | 93 | \ifdefined\eng 94 | Lest I appear to be gratuitously plugging the above-mentioned brand 95 | names, RMS suggests that I offer equal time to a pair of web sites that 96 | can spell out their many disadvantages, especially in the realm of 97 | software liberty. I have agreed to this suggestion in the spirit of 98 | equal time. The web sites he recommends are \url{DefectiveByDesign.org} 99 | and \url{BadVista.org}. 100 | \fi 101 | 102 | \ifdefined\chs 103 | 104 | \fi 105 | 106 | \ifdefined\eng 107 | Regardless of title, the notion of corporate brand as sole guarantor 108 | of software quality in a swiftly changing world remains a hard one to 109 | dislodge, even at a time when most corporate brands are trading at or 110 | near historic lows. 111 | \fi 112 | 113 | \ifdefined\chs 114 | 115 | \fi 116 | 117 | \ifdefined\eng 118 | Ten years ago, it wasn't hard to find yourself at a technology 119 | conference listening in on a conversation (or subjected to direct 120 | tutelage) in which some old-timer, Richard Stallman included, offered 121 | a compelling vision of an alternate possibility. It was the job of 122 | these old-timers, I ultimately realized, to make sure we newbies in 123 | the journalism game recognized that the tools we prided ourselves in 124 | finally knowing how to use -- Microsoft Word, PowerPoint, Internet 125 | Explorer, just to name a few popular offerings from a single oft-cited 126 | vendor -- were but a pale shadow of towering edifice the original 127 | architects of the personal computer set out to build. 128 | \fi 129 | 130 | \ifdefined\chs 131 | 132 | \fi 133 | 134 | \ifdefined\eng 135 | Nowadays, it's almost as if the opposite situation is at hand. The 136 | edifice is now a sprawling ecosystem, a jungle teeming with ideas but 137 | offering only a few stable niches for sustainable growth. While one 138 | can still find plenty of hackers willing to grumble about, say, 139 | Vista's ongoing structural flaws, Apple's dictatorial oversight of the 140 | iPhone App Store or Google's shifting definition of the word ``evil'' 141 | -- each year brings with it a fresh crop of ``digital native'' 142 | consumers willing to trust corporate guidance in this Hobbesian realm. 143 | Maybe that's because many of the problems that once made using your 144 | desktop computer such a teeth-grinding experience have largely been 145 | paved over with the help of free software. 146 | \fi 147 | 148 | \ifdefined\chs 149 | 150 | \fi 151 | 152 | \ifdefined\eng 153 | Whatever. As consumer software reliability has improved, the race to 154 | stay one step ahead of consumer taste has put application developers 155 | in an even tighter embrace with moneyed interests. I'm not saying that 156 | the hacker ethos no longer exists or that it has even weakened in any 157 | noticeable way. I'm just saying that I doubt the programmer who 158 | generated the Facebook algorithm that rewrites the ``info'' pages so 159 | that each keyword points to a sponsored page, with an 80-percent 160 | semantic error rate to boot, spends much time in his new Porsche 161 | grousing about what the program really could have achieved if only the 162 | ``suits'' hadn't gotten in the way. 163 | \fi 164 | 165 | \ifdefined\chs 166 | 167 | \fi 168 | 169 | \ifdefined\eng 170 | True, millions of people now run mostly free software on their 171 | computers with many running free software exclusively. From an 172 | ordinary consumer perspective, however, terms like ``software'' and 173 | ``computer'' have become increasingly distant. Many 2010-era cell 174 | phones could give a 2000-era laptop a run for its money in the 175 | functionality department. And yet, when it comes time to make a cell 176 | phone purchase, how many users lend any thought to the computer or 177 | software operating system making that functionality possible? The vast 178 | majority of modern phone users base their purchasing decisions almost 179 | entirely on the number of applications offered, the robustness of the 180 | network and, most important of all, the monthly service plan. 181 | \fi 182 | 183 | \ifdefined\chs 184 | 185 | \fi 186 | 187 | \ifdefined\eng 188 | Getting a consumer in this situation to view his or her software 189 | purchase through the lens of personal liberty, as opposed to personal 190 | convenience, is becoming, if not more difficult, certainly a more 191 | complex endeavor. 192 | \fi 193 | 194 | \ifdefined\chs 195 | 196 | \fi 197 | 198 | \ifdefined\eng 199 | Given this form of pessimistic introduction, why should anyone want go 200 | on and read this book? 201 | \fi 202 | 203 | \ifdefined\chs 204 | 205 | \fi 206 | 207 | \ifdefined\eng 208 | I can offer two major reasons. 209 | \fi 210 | 211 | \ifdefined\chs 212 | 213 | \fi 214 | 215 | \ifdefined\eng 216 | The first reason is a personal one. As noted in the Epilogue of 217 | \textit{Free as in Freedom}, Richard and I parted on less than cordial 218 | terms shortly before the publication of that book. The fault, in large 219 | part, was mine. Having worked with Richard to make sure that my 220 | biographical sketch didn't run afoul of free software principles -- an 221 | effort that, I'm proud to say, made \textit{Free as in Freedom} one of 222 | the first works to employ the GNU Free Documentation License (GFDL) as 223 | a copyright mechanism -- I abruptly ended the cooperative relationship 224 | when it came time to edit the work and incorporate Richard's lengthy 225 | list of error corrections and requests for clarification. 226 | \fi 227 | 228 | \ifdefined\chs 229 | 230 | \fi 231 | 232 | \ifdefined\eng 233 | Though able to duck behind my own principles of authorial independence 234 | and journalistic objectivity, I have since come to lament not begging 235 | the book's publisher -- O'Reilly and Associates -- for additional time. 236 | Because O'Reilly had already granted my one major stipulation -- the 237 | GFDL -- and had already put up with a heavy stream of last-minute 238 | changes on my part, however, I was hesitant to push my luck. 239 | \fi 240 | 241 | \ifdefined\chs 242 | 243 | \fi 244 | 245 | \ifdefined\eng 246 | In the years immediately following the publication of \textit{Free as 247 | in Freedom}, I was able to justify my decision by noting that the 248 | GFDL, just like the GNU General Public License in the software realm, 249 | makes it possible for any reader to modify the book and resell it as a 250 | competitive work. As Ernest Hemingway once put it, ``the first draft 251 | of anything is shit.'' If Stallman or others within the hacker 252 | community saw \textit{Free as in Freedom} as a first draft at best, 253 | well, at least I had spared them the time and labor of generating 254 | their own first draft. 255 | \fi 256 | 257 | \ifdefined\chs 258 | 259 | \fi 260 | 261 | \ifdefined\eng 262 | Now that Richard has indeed delivered what amounts to a significant 263 | rewrite, I can only but remain true to my younger self and endorse the 264 | effort. Indeed, I salute it. My only remaining hope is that, seeing as 265 | how Richard's work doesn't show any sign of slowing, additional 266 | documentation gets added to the mix. 267 | \fi 268 | 269 | \ifdefined\chs 270 | 271 | \fi 272 | 273 | \ifdefined\eng 274 | Before moving on to the next reason, I should note that one of the pleasant 275 | by-products of this book is a re-opening of email communication 276 | channels between Richard and myself. The resulting communication has 277 | reacquainted me with the razor-sharp Stallman writing style. 278 | \fi 279 | 280 | \ifdefined\chs 281 | 282 | \fi 283 | 284 | \ifdefined\eng 285 | An illustrative and perhaps amusing anecdote for anyone out there who 286 | has wrangled with Richard in text: In the course of discussing the 287 | passage in which I observe and document the process of Richard losing 288 | his cool amid the rush hour traffic of Kihei, Maui, a passage that 289 | served as the basis for Chapter 7 (``A Brief Journey through Hacker 290 | Hell'') in the original book, I acknowledged a common complaint among 291 | the book's reviewers -- namely, that the episode seemed out of place, 292 | a fragment of magazine-style profile interrupting a book-length 293 | biography. I told Richard that he could discard the episode for that 294 | reason alone but noted that my decision to include it was based on two 295 | justifications. First, it offered a glimpse of the Stallman temper, 296 | something I'd been warned about but had yet to experience in a 297 | firsthand manner. Second, I felt the overall scene possessed a certain 298 | metaphorical value. Hence the chapter title. 299 | \fi 300 | 301 | \ifdefined\chs 302 | 303 | \fi 304 | 305 | \ifdefined\eng 306 | Stallman, to my surprise, agreed on both counts. His concern lay more 307 | in the two off-key words. At one point I quote him accusing the lead 308 | driver of our two-vehicle caravan with ``deliberately'' leading us 309 | down a dead-end street, an accusation that, if true, suggested a level 310 | of malice outside the bounds of the actual situation. Without the 311 | benefit of a recorded transcript -- I only had a notebook at the time, 312 | I allowed that it was likely I'd mishandled Stallman's actual wording 313 | and had made it more hurtful than originally intended. 314 | \fi 315 | 316 | \ifdefined\chs 317 | 318 | \fi 319 | 320 | \ifdefined\eng 321 | On a separate issue, meanwhile, Stallman questioned his quoted use of 322 | the word ``fucking.'' Again, I didn't have the moment on tape, but I 323 | wrote back that I distinctly recalled an impressive display of 324 | profanity, a reminder of Richard's New York roots, and was willing to 325 | stand by that memory. 326 | \fi 327 | 328 | \ifdefined\chs 329 | 330 | \fi 331 | 332 | \ifdefined\eng 333 | An email response from Richard, received the next day, restated the 334 | critique in a way that forced me to go back and re-read the first 335 | message. As it turned out, Stallman wasn't so much objecting to the 336 | ``fuck'' as the ``-ing'' portion of the quote. 337 | \fi 338 | 339 | \ifdefined\chs 340 | 341 | \fi 342 | 343 | \ifdefined\eng 344 | ``Part of the reason I doubt [the words] is that they involve using 345 | fucking as an adverb,'' Stallman wrote. ``I have never spoken that 346 | way. So I am sure the words are somewhat altered.'' 347 | \fi 348 | 349 | \ifdefined\chs 350 | 351 | \fi 352 | 353 | \ifdefined\eng 354 | Touché. 355 | \fi 356 | 357 | \ifdefined\chs 358 | 359 | \fi 360 | 361 | \ifdefined\eng 362 | The second reason a person should feel compelled to read this book 363 | cycles back to the opening theme of this preface -- how different a 364 | future we face in 2010 compared to the one we were still squinting our 365 | eyes to see back in 2000. I ll be honest: Like many Americans (and 366 | non-Americans), my worldview was altered by the events of September 367 | 11, 2001, so much so that it wasn't much longer after the publication 368 | of \textit{Free as in Freedom} that my attention drifted sharply away 369 | from the free software movement and Stallman's efforts to keep it on 370 | course. While I have managed to follow the broad trends and major 371 | issues, the day-to-day drama surrounding software standards, software 372 | copyrights and software patents has become something I largely skip 373 | over -- the Internet news equivalent of the Water Board notes in the 374 | local daily newspaper, in other words. 375 | \fi 376 | 377 | \ifdefined\chs 378 | 379 | \fi 380 | 381 | \ifdefined\eng 382 | [RMS: The September 2001 attacks, not mentioned later in the book, 383 | deserve brief comment here. Far from ``changing everything,'' as 384 | many proclaim, the attacks have, in fact, changed very little in the 385 | U.S.: There are still scoundrels in power who hate our freedoms. The 386 | only major difference is that they can now cite ``terrorists'' as an 387 | excuse for laws to take them away. See the political notes on 388 | \url{stallman.org} for more about this.] 389 | \fi 390 | 391 | \ifdefined\chs 392 | 393 | \fi 394 | 395 | \ifdefined\eng 396 | This is a lamentable development in large part because, ten years in, 397 | I finally see the maturing 21st century in what I believe to be a 398 | clear light. Again, if this were a pitch letter to some editor, I'd 399 | call it ``The Process Century.'' 400 | \fi 401 | 402 | \ifdefined\chs 403 | 404 | \fi 405 | 406 | \ifdefined\eng 407 | By that I mean I we stand at a rare point in history where, all 408 | cynicism aside, the power to change the world really does delegate 409 | down to the ordinary citizen's level. The catch, of course, is that 410 | the same power that belongs to you also belongs to everyone else. 411 | Where in past eras one might have secured change simply by winning the 412 | sympathies of a few well-placed insiders, today's reformer must bring 413 | into alignment an entire vector field of competitive ideas and 414 | interests. In short, being an effective reformer nowadays requires 415 | more than just titanic stamina and a willingness to cry out in the 416 | wilderness for a decade or more, it requires knowing how to articulate 417 | durable, scalable ideas, how to beat the system at its own game. 418 | \fi 419 | 420 | \ifdefined\chs 421 | 422 | \fi 423 | 424 | \ifdefined\eng 425 | On all counts, I would argue that Richard M. Stallman, while maybe not 426 | the archetype, is at the very least an ur-type of the successful 427 | reformer just described. 428 | \fi 429 | 430 | \ifdefined\chs 431 | 432 | \fi 433 | 434 | \ifdefined\eng 435 | While some might lament a future in which every problem seems to take 436 | a few decades of committee meetings and sub-committee hearings just to 437 | reach the correction stage, I, for one, see the alternative -- a 438 | future so responsive to individual or small group action that some 439 | self-appointed actor finally decides to put that responsiveness to the 440 | test -- as too chilling to contemplate. 441 | \fi 442 | 443 | \ifdefined\chs 444 | 445 | \fi 446 | 447 | \ifdefined\eng 448 | In short, if you are the type of person who, like me, hopes to see the 449 | 21st century follow a less bloody course than the 20th century, the 450 | Water Board -- in its many frustrating guises -- is where that battle 451 | is currently being fought. As hinted by the Virgil-inspired epigraph 452 | introducing the book's first chapter, I've always held out hope that 453 | this book might in some way become a sort of epic poem for the 454 | Internet Age. Built around a heroic but flawed central figure, its 455 | authorial stamp should be allowed to blur with age. 456 | \fi 457 | 458 | \ifdefined\chs 459 | 460 | \fi 461 | 462 | \ifdefined\eng 463 | On that note, I would like to end this preface the same way I always 464 | end this preface -- with a request for changes and contributions from 465 | any reader wishing to improve the text. \nameref{Appendix B} offers a 466 | guide on your rights as a reader to submit changes, make corrections, 467 | or even create your own spin-off version of the book. If you prefer to 468 | simply run the changes through Richard or myself, you can find the 469 | pertinent contact information on the Free Software Foundation web site. 470 | \fi 471 | 472 | \ifdefined\chs 473 | 474 | \fi 475 | 476 | \ifdefined\eng 477 | In the meantime, good luck and enjoy the book! 478 | \fi 479 | 480 | \ifdefined\chs 481 | 482 | \fi 483 | 484 | \ifdefined\eng 485 | \vspace{0.5in} 486 | \noindent Sam Williams\\ 487 | \noindent Staten Island, USA 488 | \fi 489 | 490 | \ifdefined\chs 491 | \vspace{0.5in} 492 | \noindent 萨姆·威廉姆斯\\ 493 | \noindent 于美国史泰登岛 494 | \fi 495 | -------------------------------------------------------------------------------- /rms-preface.tex: -------------------------------------------------------------------------------- 1 | %% Copyright (c) 2002, 2010 Sam Williams 2 | %% Copyright (c) 2010 Richard M. Stallman 3 | %% Permission is granted to copy, distribute and/or modify this 4 | %% document under the terms of the GNU Free Documentation License, 5 | %% Version 1.3 or any later version published by the Free Software 6 | %% Foundation; with no Invariant Sections, no Front-Cover Texts, and 7 | %% no Back-Cover Texts. A copy of the license is included in the 8 | %% file called ``gfdl.tex''. 9 | \chapter[Foreword by Richard M. Stallman]{\ifdefined\eng 10 | Foreword\\by Richard M. Stallman 11 | \fi 12 | \ifdefined\chs 13 | 理查德·斯托曼的前言 14 | \fi} 15 | 16 | \ifdefined\eng 17 | I have aimed to make this edition combine the advantages of my 18 | knowledge and Williams' interviews and outside viewpoint. The reader 19 | can judge to what extent I have achieved this. 20 | \fi 21 | 22 | \ifdefined\chs 23 | 24 | \fi 25 | 26 | \ifdefined\eng 27 | I read the published text of the English edition for the first time in 28 | 2009 when I was asked to assist in making a French translation of \textit{Free 29 | as in Freedom}. It called for more than small changes. 30 | \fi 31 | 32 | \ifdefined\chs 33 | 34 | \fi 35 | 36 | \ifdefined\eng 37 | Many facts needed correction, but deeper changes were also needed. 38 | Williams, a non-programmer, blurred fundamental technical and legal 39 | distinctions, such as that between modifying an existing program's 40 | code, on the one hand, and implementing some of its ideas in a new 41 | program, on the other. Thus, the first edition said that both Gosmacs 42 | and GNU Emacs were developed by modifying the original PDP-10 Emacs, 43 | which in fact neither one was. Likewise, it mistakenly 44 | described Linux as a ``version of Minix.'' SCO later made the same 45 | false claim in its infamous lawsuit against IBM, and both Torvalds and 46 | Tanenbaum rebutted it. 47 | \fi 48 | 49 | \ifdefined\chs 50 | 51 | \fi 52 | 53 | \ifdefined\eng 54 | The first edition overdramatized many events by projecting spurious 55 | emotions into them. For instance, it said that I ``all but shunned'' 56 | Linux in 1992, and then made a ``a dramatic about-face'' by deciding in 57 | 1993 to sponsor Debian GNU/Linux. Both my interest in 1993 and my 58 | lack of interest in 1992 were pragmatic means to pursue the same end: 59 | to complete the GNU system. The launch of the GNU Hurd kernel in 1990 60 | was also a pragmatic move directed at that same end. 61 | \fi 62 | 63 | \ifdefined\chs 64 | 65 | \fi 66 | 67 | \ifdefined\eng 68 | For all these reasons, many statements in the original edition were 69 | mistaken or incoherent. It was necessary to correct them, but not 70 | straightforward to do so with integrity short of a total rewrite, 71 | which was undesirable for other reasons. Using explicit notes for the 72 | corrections was suggested, but in most chapters the amount of change 73 | made explicit notes prohibitive. Some errors were too pervasive or 74 | too ingrained to be corrected by notes. Inline or footnotes for the 75 | rest would have overwhelmed the text in some places and made the text 76 | hard to read; footnotes would have been skipped by readers tired of 77 | looking down for them. I have therefore made corrections directly in 78 | the text. 79 | \fi 80 | 81 | \ifdefined\chs 82 | 83 | \fi 84 | 85 | \ifdefined\eng 86 | However, I have not tried to check all the facts and quotations that 87 | are outside my knowledge; most of those I have simply carried forward 88 | on Williams' authority. 89 | \fi 90 | 91 | \ifdefined\chs 92 | 93 | \fi 94 | 95 | \ifdefined\eng 96 | Williams' version contained many quotations that are critical of me. I 97 | have preserved all these, adding rebuttals when appropriate. I have 98 | not deleted any quotation, except in \autoref{chapter:open source} where I have deleted 99 | some that were about open source and did not pertain to my life or 100 | work. Likewise I have preserved (and sometimes commented on) most of 101 | Williams' own interpretations that criticized me, when they did not 102 | represent misunderstanding of facts or technology, but I have freely 103 | corrected inaccurate assertions about my work and my thoughts and 104 | feelings. I have preserved his personal impressions when presented as 105 | such, and ``I'' in the text of this edition always refers to Williams 106 | except in notes labeled ``RMS:''. 107 | \fi 108 | 109 | \ifdefined\chs 110 | 111 | \fi 112 | 113 | \ifdefined\eng 114 | In this edition, the complete system that combines GNU and Linux is 115 | always ``GNU/Linux,'' and ``Linux'' by itself always refers to Torvalds' 116 | kernel, except in quotations where the other usage is marked with 117 | ``[\textit{sic}]''. See \url{http://www.gnu.org/gnu/gnu-linux-faq.html} for more 118 | explanation of why it is erroneous and unfair to call the whole system 119 | ``Linux.'' 120 | \fi 121 | 122 | \ifdefined\chs 123 | 124 | \fi 125 | 126 | \ifdefined\eng 127 | I would like to thank John Sullivan for his many useful criticisms and 128 | suggestions. 129 | \fi 130 | 131 | \ifdefined\chs 132 | 133 | \fi 134 | -------------------------------------------------------------------------------- /stignucius.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/lifanxi/free-as-in-freedom-zh-cn/34a15dfb02412e64d78d869bb252fcba9d9b84ef/stignucius.jpg --------------------------------------------------------------------------------