www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/gnu thegnuproject.zh-tw.html po/thegnuproje...


From: GNUN
Subject: www/gnu thegnuproject.zh-tw.html po/thegnuproje...
Date: Tue, 5 Dec 2017 02:29:15 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/12/05 02:29:15

Modified files:
        gnu            : thegnuproject.zh-tw.html 
        gnu/po         : thegnuproject.zh-tw.po 
Added files:
        gnu/po         : thegnuproject.zh-tw-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/thegnuproject.zh-tw.html?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.zh-tw.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/thegnuproject.zh-tw-en.html?cvsroot=www&rev=1.1

Patches:
Index: thegnuproject.zh-tw.html
===================================================================
RCS file: /web/www/www/gnu/thegnuproject.zh-tw.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- thegnuproject.zh-tw.html    24 Oct 2013 11:32:27 -0000      1.4
+++ thegnuproject.zh-tw.html    5 Dec 2017 07:29:14 -0000       1.5
@@ -1,419 +1,597 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
+<!--#set var="ENGLISH_PAGE" value="/gnu/thegnuproject.en.html" -->
 
-<HEAD>
-<TITLE>GNU ­pµe - ¦Û¥Ñ³nÅé°òª÷·|¡]FSF¡^</TITLE>
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=big5">
-<LINK REV="made" HREF="mailto:address@hidden";>
-<META HTTP-EQUIV="Keywords"
- CONTENT="GNU¡BGNU ­pµe¡BFSF¡B¦Û¥Ñ³nÅé¡B¦Û¥Ñ³nÅé°òª÷·|¡B¾ú¥v">
-</HEAD>
+<!--#include virtual="/server/header.zh-tw.html" -->
+<!-- Parent-Version: 1.77 -->
 
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000" 
LINK="#9900DD">
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>關於 GNU 專案 - GNU 專案 - 自由軟體基金會</title>
+<meta http-equiv="Keywords" content="GNU, GNU Project, GNU 專案, FSF, Free 
Software, 自由軟體, Free Software
+Foundation, 自由軟體基金會, History, 歷史" />
+
+<!--#include virtual="/gnu/po/thegnuproject.translist" -->
+<!--#include virtual="/server/banner.zh-tw.html" -->
+<h2>GNU 專案</h2>
+
+<p>
+<a href="http://www.stallman.org/";><strong>Richard Stallman</strong></a> 
著作</p>
+
+<blockquote>
+<p>
+文章原載於 <em>Open Sources</em> 一書中。理查・史托曼先生 
(Richard Stallman)<a
+href="/philosophy/open-source-misses-the-point.html"> 永遠
不是「開源」或「Open
+Source」的支持者
</a>,但基於不願讓自由軟體運動的想法在該書中完å…
¨ç¼ºå¸­ä¹‹æ•…而寫下本文。
+</p>
+<p>
+為何<a
+href="/philosophy/free-software-even-more-important.html">堅
持我們使用的軟體應該自由</a>前所未有地重要。
+</p>
+</blockquote>
+
+<h3>最早的軟體共享社群</h3>
+<p>
+1971年當我在 <acronym title="Massachusetts Institute of
+Technology">MIT</acronym> 麻省理工學院的人工智æ…
§å¯¦é©—室(英文簡稱 AI
+Lab)工作時開始,我成了軟體å…
±äº«ç¤¾ç¾¤çš„一員,而這個社群已經存在好些年了。分享軟體的行為不限於我們這個社群;這種行為跟電è
…¦çš„發展史一樣久遠
,好比分享食譜的歷史跟烹調食物的歷史同樣古老。但我們這個社群比起絕大多數人更常分享。</p>
+<p>
+AI Lab 當時採用一種稱為 <acronym title="Incompatible Timesharing
+System">ITS</acronym> (全名為 Incompatible Timesharing 
System,意思為「不相容分時系統」)
+的分時作業系統,它由實驗室的黑客職員 (1) 設計,並且以 
Digital <acronym title="Programmed Data
+Processor">PDP</acronym>-10 的組合語言編寫。這種 PDP-10 電è…
¦å±¬æ–¼é‚£å€‹ä¸–代的大型電è…
¦ä¹‹ä¸€ã€‚身為這個社群的一份子,也就是
+AI Lab 的系統黑客職員,我的工作就是改善這套系統。</p>
+<p>
+我們那時的軟體不叫「自由軟體」,因
為這個詞語還不存在,但這個概念就是從那時候的軟體延續而來。每當å
…¶ä»–大學或å…
¬å¸çš„人想要移植某程式或使用某程式時,我們都很高興讓他們利用。而當ä½
 çœ‹åˆ°æŸäººåœ¨ç”¨ä½ æ‰€ä¸çŸ¥é“的程式,或是很有趣的程式,你
都會向他們要源始程式碼,這樣你
就能讀它、改它、甚至擷取你想利用的部份來創造
新程式……等等。</p>
+<p>
+(1) 部份的大眾媒體常將「黑客 Hacker」和「安全壞客 Security
+Breaker」混為一談。我們黑客不承認那種意思的用法,而且會繼續使用黑客一詞來指那些熱愛寫程式的人、樂於發揮有趣的聰明想法的人,或是結合å
…©ç¨®ç‰¹è³ªçš„人。請讀我這篇《<a
+href="http://stallman.org/articles/on-hacking.html";>論黑客</a>》文章
。</p>
+
+<h3>社群崩解</h3>
+<p>
+1980年代早期,Digital 公司中止了 PDP-10
+系列,這使得情況劇烈改變。該系列機器在60年代期間優雅
又強大的架構,自然無法擴展成80年代開始使用的較大位址空間。這代表構成
 ITS
+的幾乎所有程式慘遭淘汰。</p>
+<p>
+在短時間內,AI Lab 
的黑客社群儼然瓦解。1981年,從實驗室分出來的 Symbolics å…
¬å¸å¹¾ä¹ŽæŒ–走所有 AI Lab
+的黑客,殘餘的社群幾乎無以為繼。(Steve Levy 
著作的《Hacker》,中譯本名為《黑客列傳》由 Jedi 與 Pluto
+翻譯,書中談論這些故事情節,同時也清
楚描繪出此社群輝煌時期的樣貌。)當 AI Lab 
在1982年買下新的 DPD-10 機臺時,其管理員決定使用
+Digital 的非自由分時系統取代 ITS。</p>
+<p>
+該世代的新電腦,例如 VAX 或 
68020,都有自己的作業系統,但是它們都不是自由軟體:你
甚至必須簽署 NDA 不揭露協議書,才能取得可執行副本。</p>
+<p>
+這代表使用電腦的第一步驟,就是要保證你
絕對不會拿軟體幫助朋友鄰居
。互助合作的社群被禁止。專有軟體的所有人設下規則:「如果ä½
 æƒ³è¦å’Œæœ‹å‹é„°å±…分享,那你就是偷盜。如果你
想要有任何改變,請求我們實現。」</p>
+<p>
+專有軟體社會系統的概念——你
不能分享或更改軟體的社會——不僅反社會、不道德、æ 
¹æœ¬å°±æ˜¯å€‹éŒ¯èª¤ï¼Œæˆ–許有些讀者
看到這裡會覺得很驚訝也不一定。不過,我們對於這種劃分民眾身份,並且讓使用è€
…感到無助的系統還能說什麼?覺得我們想法令人訝異的讀者
或許以為專有軟體社會系統是個已知事實,或是æ 
¹æ“šå°ˆæœ‰è»Ÿé«”事業推動的規則做出了判斷。軟體發行商長久
以來一直想盡辦法說服民眾這個議題就只能有一種看法。</p>
+<p>
+當軟體發行商論及「行使」其「權利」,或「停止<a
+href="/philosophy/words-to-avoid.html#Piracy">盜版</a>」時,他們所講的這些話術是次要議題。以上論述的真正意涵是,在他們視為理所當然的未明說假設中,大眾只é
 ˆè¦æŽ¥å—但不必理解。所以,請讓我們幫忙理清這一切。</p>
+<p>
+第一個假設是,軟體å…
¬å¸å°æ–¼è‡ªå®¶è»Ÿé«”有一種不可置疑的自然權利,他們因
而擁有支配所有軟體使用者
的權力。(如果這真有個什麼自然權利,那麼無論這個權利對於民眾會é€
 
成多嚴重的傷害,我們都不能拒絕。)有趣的是,美國憲法與法律傳統觀點否認這種看法;著作權不是自然權利,而是政府賦予的人為壟斷權,可以限制使用è€
…的自然權利使其不得複製。</p>
+<p>
+另一個未明說的假設是,對軟體來說最重要的事情
是它能讓你做些什麼——我們電腦使用者
不應該在意我們能擁有什麼樣的社會型態。</p>
+<p>
+第三個假設是,如果我們不給這些公司支配程式使用者
的權力,那麼我們就不會有好用的軟體(或是永遠
不會有這種功能的程式,或是可以做到那些事的程式)。這個假設看起來說得好像跟真的一樣,但是早在自由軟體運動開始之前,我們社會中就已經有很多好用的軟體都沒有這些束縛的枷鎖。</p>
+<p>
+如果我們拒絕接受這些假設,並且æ 
¹æ“šåŽŸä¾†çš„常識性道德觀把這些使用者放在優å…
ˆåœ°ä½ä¾†åˆ¤æ–·ä¹‹æ™‚,我們發現結論大不相同。電腦使用者
應能自由修改程式以符合自身需求、並自由分享軟體,因
為幫助他人是社會存在的基礎。</p>
+<p>
+這裡如果詳細敘述結論背後的演繹過程會讓篇幅
過長,所以我在此請各位讀者前往 <a 
href="/philosophy/why-free.html">
+http://www.gnu.org/philosophy/why-free.html</a> and <a
+href="/philosophy/free-software-even-more-important.html">
+http://www.gnu.org/philosophy/free-software-even-more-important.html</a> 網é 
ã€‚
+</p>
+
+<h3>嚴酷的道德選擇</h3>
+<p>
+隨著我的社群消失,想一如往常變得不再可能。所以,我面對嚴é
…·çš„道德選擇。</p>
+<p>
+最簡單的選擇,就是加å…
¥å°ˆæœ‰è»Ÿé«”世界,簽下不揭露協議並保證我不會幫助黑客同袍。這樣我大概也會開發å¿
…須保密不能揭露的軟體,然後對其他人施加
壓力讓他們也一起背叛同袍。</p>
+<p>
+我可以這樣賺錢,或許也可寫程式自娛。但是我知道,一旦我職業生涯結束後,再回過é
 
­åŽ»çœ‹æˆ‘修築了高牆以便劃分人群的那些年,就會感受到我花了大把人生將世界變成一個更糟糕的地方。</p>
+<p>
+我已體驗過身為不揭露條款終端接受者
的經歷,有人拒絕將我們實驗室印表機的控制程式源始碼交給我或
 MIT AI
+Lab。(這個控制程式缺乏某些功能,導致我們使用這臺印表機時受到極大挫折。)所以我無法告訴我自己說保密條款是無辜的。我非常生氣他拒絕和我們分享;我無法就這樣轉身然後對å
…¶ä»–人做出一樣的事來。</p>
+<p>
+另一種選擇,很直截了當但令人不開心,就是離開電è…
¦ç•Œã€‚這樣做我的技術能力就不會被濫用,但這些才能就無端浪費掉了。我雖然不會å›
 ç‚ºåŠƒåˆ†å’Œé™åˆ¶é›»è…¦ä½¿ç”¨è€…而感到罪惡,但是這些事卻不會因
為我不做而就此停止。</p>
+<p>
+所以我開始探尋程式設計師能對這個議題做些什麼好事。我問我自己,是不是有我能寫的程式,不管是一個還是很多個,如此讓社群有機會再次復興。</p>
+<p>
+答案很清楚:我們首å…
ˆéœ€è¦ä¸€å€‹ä½œæ¥­ç³»çµ±ã€‚作業系統是人們開始使用電è…
¦çš„重大軟體。有了作業系統,你
可以做很多事;沒有作業系統,你就幾乎無法操作電è…
¦ã€‚有了自由的作業系統,我們可以再次形成互助合作的黑客社群——並邀請任何人åŠ
 å…¥ã€‚此外,任何人都可以使用電腦,不會因
而暗中失去他或她的朋友。</p>
+<p>
+身為作業系統開發者,我對這項
工作有對應的技術能力。所以即便我無法將成功視為理所當然,我仍確知我適合出任這é
 …工作。我選擇讓系統和 Unix
+相容以便具有可攜性,如此 Unix 使用者
就能輕鬆轉換過來。GNU 的命名遵循黑客傳統,遞迴式é 
­æ–‡å­—縮寫,代表「GNU's Not
+Unix」,意思是「GNU 並非 Unix」;它的英語發音為實唸出 g 
子音的單音節字,華語(漢語官話)發音類似「個怒」。</p>
+<p>
+一套作業系統可不只是一個內部æ 
¸å¿ƒè€Œå·²ï¼Œé‚£æ¨£å¹¾ä¹Žæ²’有什麼å…
¶ä»–程式可以跑。1970年代,每個值得一提的作業系統都有指令處理器(外部表殼)、組譯器、編譯器、直譯器、除錯器、文字編輯器、郵件程式…等等。ITS
+有、Multics 有、VMS 也有、Unix 也一樣都有。GNU 
作業系統也會收錄這些軟體。</p>
+<p>
+後來我聽到希列爾長者 (Hillel) 所留下的這席話 (1):</p>
+
+<blockquote><p>
+     如果我不為我,誰來為我?<br />
+     如果我只為我,我又是誰?<br />
+     如果不是現在,更待何時?
+</p></blockquote>
+<p>
+發起 GNU 專案的決定基於類似的精神。</p>
+<p>
+(1) 身為無神論者,我不跟隨任何宗教é 
˜è¢–,但我偶爾會欣賞他們之中所說的一些話。</p>
+
+<h3>如 Freedom 般自由</h3>
+<p>
+「自由軟體」有時候會被誤解——它跟價æ 
¼ä¸€é»žä¹Ÿæ²’有關係。自由軟體講求的是自由。所以,在此附上自由軟體的定義。</p>
+
+<p>對你,一位特定使用者
,程式只有在滿足下列條件時才是自由軟體:</p>
+
+<ul>
+  <li>你擁有依照你
想法執行該程式的自由,無論任何用途。</li>
+
+  <li>你擁有依據你需求修改該程式的自由。(要讓這項
自由實務上有效,你必須能取用源始碼,因
為如果沒有源始碼要修改程式極為困難。)</li>
+
+  <li>你擁有再次散布程式副本的自由,無論å…
è²»æˆ–是收費。</li>
+
+  <li>你擁有散布修改後程式版本的自由,如此社群就能因你
的改善而受益。</li>
+</ul>
+<p>
+因為自由軟體英文 free software
+中的「free」指的是自由,不是價格å…
è²»ï¼Œæ‰€ä»¥éŠ·å”®è»Ÿé«”副本這件事和自由軟體之間沒有任何衝突。事實上,銷售軟體副本的自由至關重要:自由軟體集合的
 CD
+光碟販賣對於社群很重要,而銷售這些å…
‰ç¢Ÿä¹Ÿæ˜¯å‹Ÿé›†è‡ªç”±è»Ÿé«”開發資金的重要方式。因
此,那些人們無法自由納å…
¥é€™é¡žå¤§é›†åˆä¸­çš„程式就不是自由軟體。</p>
+<p>
+由於「free」英文帶有歧義,有些人一直在尋找替代用詞,但都沒有找到更好的。英文這個語言比起他è€
…
有更多單字和音調上的細微差別,但卻缺少只講述「freedom」自由意涵的簡單、不模糊單字——而「unfettered」無拘無束,則是最接近這個概念的單字。å
…
¶ä»–字詞如「liberated」、「freedom」和「open」這些,不是意義上有差別,就是有å
…¶ä»–不足之處。</p>
+
+<h3>GNU 軟體與 GNU 系統</h3>
+<p>
+要開發出一套完整的系統可說是非常大的專案。為了讓目標更為可行,我決定一旦有可用的對應自由軟體,就調整這些軟體並使用之。舉例來說,我一開始就決定採用
+TeX 作為主要的文書格式處理器;幾年過後,我決定採納 X 
視窗系統而非另外為 GNU 撰寫其他視窗系統。</p>
+<p>
+基於前述這些決定,還有其他等等這類的決定,GNU 
系統不等同於所有 GNU 軟體的集合體。GNU 系統亦包含非 GNU
+軟體,那些其他人或å…
¶ä»–專案為了自身目標而開發的程式,但因
為它們是自由軟體,我們便得以採用。</p>
+
+<h3>展開專案</h3>
+<p>
+1984å¹´1月,我辭去 MIT 的工作並且開始寫 GNU 軟體。我必é 
ˆé›¢é–‹ MIT,這樣 MIT 才無法干預我將 GNU
+以自由軟體形式散布出去。如果我還是 MIT 的員工,那麼 MIT
+可以宣稱擁有我的工作成果,並施加
他們自己的散布條款,或者
甚至將成品轉為專有軟體也不一定。我不想要在做出大量勞力之後,看見成果在我期許的用途上變得一點用處也沒有,而這個期許就是:建立新的軟體分享社群。</p>
+<p>
+不過,後來擔任 MIT AI 實驗室主任的 Winston 
教授,仍親切地邀請我繼續使用實驗室的設備。</p>
+
+<h3>最早的路</h3>
+<p>
+在 GNU 專案開始不久後,我聽說自由大學 (Free University) 
有套編譯器工具組 (Compiller Kit),它也被稱為
+VUCK。(「自由」的荷蘭語以 <em>v</em> 開頭。)這套工å…
·çµ„的設計可以處理許多語言,包括 C 和
+Pascal,而且也支援多種目標機器。於是我寫了封信向作者
詢問 GNU 是否能夠使用。</p>
+<p>
+他嘲笑似地回覆說,雖然大學是自由的,但編譯器不是。我å›
 è€Œä¸‹å®šæ±ºå¿ƒï¼Œç¬¬ä¸€å€‹è¦ç‚º GNU 
專案而寫的程式就是支援多語言、多平臺的編譯器。</p>
+<p>
+我希望不必自己寫出整個編譯器,所以取得了 Pastel 
編譯器的源始碼。Pastel 編譯器是個多平臺的編譯器,由 
Lawrence Livermore
+實驗室開發;它支援設計成系統型程式設計語言的擴充版 
Pascal,並且也以該語言寫成。我加入了 C 
前端,並且開始移植到 Motorola 68000
+電腦上。但我後來發現這個編譯器需要好幾 MB 的å 
†ç–Šç©ºé–“時只能放棄,因為當年現有的 68000 Unix 系統只允許 
64k 的空間而已。</p>
+<p>
+我接著瞭解到 Pastel
+編譯器的處理方式是將整分輸入檔å…
ˆè§£æžæˆèªžæ³•æ¨¹ï¼Œç„¶å¾Œå°‡æ•´å€‹èªžæ³•æ¨¹è½‰æ›ç‚ºã€ŒæŒ‡ä»¤ã€éˆï¼ŒæŽ¥è‘—生成整分輸出檔,整個過程從未釋放任何儲存空間。就這樣看來,結論是我å¿
…須從頭開始寫一個新的編譯器。這個新編譯器現在稱作
+<acronym title="GNU Compiler Collection">GCC</acronym>,裡面沒有用到 
Pastel
+編譯器的任何部份,不過我設法修改之前為 Pastel 
編譯器所寫的 C 
前端並拿過來用。但那是好幾年後發生的事了;在那之前,我å
…ˆåšäº† GNU
+Emacs。</p>
+
+<h3>GNU Emacs</h3>
+<p>
+在1984年9月之時我開始做 GNU 
Emacs,直到1985年初,程式終於開始能用。有了 Emacs 
後,我就能開始使用 Unix
+系統作編輯;因為我對於學習怎麼使用 vi 或 ed 
一點興趣也沒有,所以在這之前我都是用å…
¶ä»–機器作編輯的。</p>
+<p>
+此時,人們開始想要使用 GNU 
Emacs,所以問題來了,我要怎樣散布?當然,我把它放到我使用的
 MIT 電腦的匿名 FTP
+伺服器上。(這臺電腦,prep.ai.mit.edu,因而成為 GNU 的主要 
ftp 散布站;電腦幾年後退役了,我們便將名稱轉到我們的新 
ftp
+伺服器上。)但是在當時,許多有興趣的人都無法連上網際網路,所以不能從
 FTP 取得軟體副本。所以問題是,我要對他們說些什麼?</p>
+<p>
+我可以這樣說:「去找個能上網的朋友,看他要不要幫你
拷貝個軟體副本。」或者,我可以用我之前對原來 PDP-10 Emacs
+所做的方法,告訴他們說:「寄給我一個磁帶並附上回郵信封,我會把
 Emacs
+放進去然後寄回。」但我當時沒有工作,所以我也在找方法利用自由軟體賺錢。我宣布我會郵寄磁帶給想要軟體的人,一次收費150美金。就這樣,我開啟了自由軟體的散布業務,成為今日散布整套
+GNU/Linux 系統散布版的公司的始祖。</p>
+
+<h3>是不是每個人拿到的程式都是自由軟體?</h3>
+<p>
+如果有個程式是自由軟體,當它離開作者
手中之後,不代表它必é 
ˆå°ä»»ä½•æ“æœ‰å‰¯æœ¬çš„人都是自由軟體。舉例而言,<a
+href="/philosophy/categories.html#PublicDomainSoftware">å…
¬ç‰ˆè»Ÿé«”</a>(沒有受到著作權保護的軟體)是自由軟體,但是任何人都可以拿它修改成專有軟體。和這相似,許多自由軟體受到著作權保護,但是用簡單的寬容式授權條款散布,而這種散布條款å
…è¨±æ”¹ä½œç‰ˆæœ¬æ˜¯å°ˆæœ‰è»Ÿé«”。</p>
+<p>
+這個問題的典型案例是 X 視窗系統。它是 MIT 
開發的,並且是用寬容式授權條款發行的自由軟體,它一下子就被各家電è
…¦å…¬å¸æŽ¡ç”¨ã€‚他們把 X 加到自家的專有
+Unix 
系統上,只提供二進位形式,並且用同樣不可揭露的授權條款保護起來。這些
 X 的副本就和 Unix 一樣不再是自由軟體。</p>
+<p>
+X
+視窗系統的開發者不認為這是個問題——他們預期這類事情
的發生,而且刻意這樣做。他們的目標不是自由,只是「成功」,定義為:「擁有很多使用è€
…」。他們不在意到底這群使用者有沒有自由,只在意使用者
有沒有很多。</p>
+<p>
+這讓情
況變得很吊詭。當有人問說:「這個程式自由嗎?」,答案卻有所不同,å›
 ç‚ºæœ‰å…©ç¨®ä¸åŒçš„自由度計算法。如果你是根據 MIT
+發行的散布條款所提供的自由度來判斷,你會說 X 
是自由軟體。但如果你是用一般 X 使用者
的角度來評量自由度的話,那麼你
會說它是專有軟體。而大多數 X
+使用者所運行的都是 Unix 
系統隨附的專有版本,不是自由版本。</p>
+
+<h3>著作傳 (Copyleft) 和 GNU GPL</h3>
+<p>
+GNU 的目標是要給予使用者
自由,不只是廣受歡迎而已。所以我們需要利用散布條款來防止
 GNU
+軟體被轉為專有軟體。這個方法我們稱為「著作傳(唸ㄔㄨㄢˊ)」,英文為「Copyleft」。(1)</p>
+<p>
+著作傳使用著作權法,但是以相反於常見作法的方式使用:並非限制程式的利用,而是維持程式的自由。</p>
+<p>
+著作傳的中心思想是我們給予任何人執行程式、複製程式、修改程式、散布修改後版本的權利——但不å
…è¨±è‡ªè¡Œå°ç¨‹å¼åŠ å…
¥é™åˆ¶ã€‚所以,「自由軟體」定義的關鍵:自由,任何人只要取得軟體副本都能得到保障;自由成為軟體不可分割的權利。</p>
+<p>
+一份有效的著作傳式授權條款,必é 
ˆç¶­æŒä¿®æ”¹å¾Œç‰ˆæœ¬ä»ä¿æœ‰è‡ªç”±ã€‚這樣就能確保那些æ 
¹æ“šæˆ‘們作品改作而成的新作,在å…
¬é–‹ç™¼è¡¨ä¹‹å¾Œå¾—以讓我們社群取用。如果有工作的程式設計師願意以志工身分改善
+GNU 軟體時,著作傳也能防止他們的僱主說:「你
不可以分享那些修改,因
為我們要把它作為我們自己專有的軟體版本」。</p>
+<p>
+如果我們希望確保程式的每個使用者
都能得到自由,那麼修改內容必須維持自由的要求是必é 
ˆçš„。將 X
+視窗系統私有化的å…
¬å¸ï¼Œé€šå¸¸æ˜¯åšå‡ºæ”¹å‹•ä»¥ä¾¿ç§»æ¤åˆ°ä»–們家的系統與硬體上。這些更改之處和
 X
+源始碼的廣大範圍相比之下很少量,但不是瑣碎不重要。如果做出更動是拒絕給予使用è€
…自由的藉口,那麼任何人都能輕鬆利用這個藉口。</p>
+<p>
+另一個相關議題是,自由軟體和非自由軟體源始碼間的結合。這樣的結合無可避å
…
æœƒä¸è‡ªç”±ï¼›éžè‡ªç”±çš„部份所缺少的自由,就整體觀點來看依然缺失自由。如果授權條款å
…
è¨±é€™é¡žçµåˆï¼Œé‚£éº¼ç„¡ç–‘是在船上開個足以沉船的大洞。所以,著作傳的關鍵要求就是要塞住這個洞:任何附åŠ
 
到著作傳保護程式上、或是和著作傳保護程式相結合的任何東西,都å¿
…須得讓較大的結合後版本依然維持自由、受著作傳保護。</p>
+<p>
+我們為大多數 GNU 軟體使用的特定著作傳式授權實作,是 GNU 
通用公眾授權 (GNU General Public License),或簡稱 GNU
+GPL。我們也有用於其他特定情
況的不同類型著作傳式授權。GNU 
手冊也一樣受到著作傳保護,但用的是更為簡單的著作傳式授權,å›
ʍ⼠GNU GPL
+很複雜這對於手冊這類著作來說沒有必要。(2)</p>
+<p>
+(1) 在1984年或1985年的時候,Don
+Hopkins(一位很有想像力的同袍)曾寄給我一封信。在信封上他寫下好幾句有趣的話,å
…¶ä¸­ä¸€å¥æ˜¯ï¼šã€Œè‘—作傳——保留所有權利。」(原文為
+&ldquo;Copyleft&mdash;all rights 
reversed.)。我便採用「著作傳」命名我當時發展的散布概念。</p>
+
+<p>
+(2) 我們的文件現在使用 <a href="/licenses/fdl.html">GNU 
自由文件授權 (Free Documentation
+License)</a>。</p>
+
+<h3>自由軟體基金會</h3>
+
+<p>隨著有興趣使用 Emacs 的人逐漸增加,其他人也開始參與 
GNU 
專案,而我們決定是時候再次尋求資助了。所以在1985年我們成立了<a
+href="http://www.fsf.org/";>自由軟體基金會 (Free Software 
Foundation,簡稱
+FSF)</a>,作自由軟體開發的免稅慈善機構。<acronym title="Free 
Software
+Foundation">FSF</acronym> 也接手了 Emacs 
磁帶的散布事業;後來更為擴展將其他自由軟體(包括 GNU 
和非
+GNU)加到磁帶業務中,也一併銷售手冊。</p>
+
+<p>當年 FSF 的大多數收å…
¥ä¾†è‡ªè‡ªç”±è»Ÿé«”副本的銷售和相關服務(源始碼 CD、二進位檔
+CD、印刷精美的手冊等,å…
¨éƒ½å¯ä»¥è‡ªç”±åœ°å†æ¬¡æ•£å¸ƒå’Œä¿®æ”¹ï¼‰ï¼Œé‚„有豪華散布版(我們為顧客所選平臺組建的å
…¨è»Ÿé«”集合散布版)。今日 FSF 仍然<a
+href="http://shop.fsf.org/";>銷售手冊和å…
¶ä»–物品</a>,但主要資金來源是會員的會費。你可以前往 <a
+href="http://fsf.org/join";>fsf.org</a> 加å…
¥è‡ªç”±è»Ÿé«”基金會的會員。</p>
+
+<p>自由軟體基金會的僱員撰寫和維護許多 GNU 軟體包。å…
¶ä¸­æœ€è‘—名的兩個分別是 C 函式庫和外部表殼。GNU/Linux 
系統上運行的每個程式透過 GNU
+C 函式庫和 Linux 溝通,它是由自由軟體基金會員工之一的 
Roland McGrath 所開發。而大多數 GNU/Linux
+系統所使用的外部表殼是 <acronym title="Bourne Again 
Shell">BASH</acronym>,全名 Bourne
+Again Shell(1),則是由基金會員工 Brian Fox 所開發。</p>
+
+<p>我們資助這些程式的開發,因為 GNU 專案可不只是提供工å…
·æˆ–開發環境而已。我們的目標是打造
出完整的作業系統,而我們需要這些程式才能完成這個目標。</p>
+
+<p>(1)「Bourne Again Shell」是對「Bourne 
Shell」作的文字遊戲,Bourne Shell 是 Unix 
上常見的外部表殼。</p>
+
+<h3>自由軟體支援服務</h3>
+
+<p>自由軟體理念思想反對特定的廣泛商業作法,但不是反對商業。只要商業å
…¬å¸èƒ½å°Šé‡ä½¿ç”¨è€…的自由,我們便祝福他們成功。</p>
+
+<p>銷售 Emacs 副本是自由軟體事業的作法之一。當 FSF
+接手這項業務之後,我得找出å…
¶ä»–討生活的方法。我發現可以銷售之前我開發自由軟體的相關服務。這類業務åŒ
…括教學,例如 GNU Emacs
+程式是怎樣設計的、怎樣客製 GCC 
等主題,還有軟體開發等,大多則是希望將 GCC 
移植到新平臺上。</p>
+
+<p>今日有許多企業行號採用這些自由軟體的各種業務作法。有的透過
 CD
+散布自由軟體集合;也有的銷售支援服務,範圍包
括回答使用者問題、修正臭蟲、添加
重大新功能等。我們甚至開始看到有些自由軟體公司是因
為要發展新的自由軟體產品而成立。</p>
+
+<p>不過,要小心——有許多å…
¬å¸å°‡è‡ªå·±å’Œã€Œé–‹æºã€é€™å€‹è©žå½™é—œè¯åœ¨ä¸€èµ·ï¼Œä½†å¯¦éš›ä¸Šä»–們的業務著重於能é
…åˆè‡ªç”±è»Ÿé«”運作的非自由軟體。這些公司不是自由軟體å…
¬å¸ï¼Œä»–們是專有軟體公司,他們的產品是要引誘使用者
離開自由。他們稱呼這些程式為「加值軟體包
」,表達他們希望大家採納的價值觀:方便比起自由更重要。如果我們更注重自由,我們應該稱呼這些程式為「刪減自由」軟體åŒ
…。</p>
+
+<h3>技術目標</h3>
+
+<p>GNU 的主要目標是自由軟體。就算 GNU 比起 Unix
+而言沒有任何技術上的優勢,也會有社會上的優勢:能讓使用è€
…之間互助合作,還有道德上的優勢:尊重使用者的自由。</p>
+
+<p>但是將眾所皆知的良好實務標準套用到我們的工作上也是很自然的事——舉例而言,採用動æ
…‹é…ç½®è³‡æ–™çµæ§‹é¿å…
æ­¦æ–·å›ºå®šå¤§å°çš„限制,以及只要合理之處就盡可能處理所有的
+8 位元代碼等。</p>
+
+<p>此外,我們放棄了 Unix 
專注於小型記憶體大小的作法,決定不要支援 16 位å…
ƒçš„機器(當時很清楚 32 位元在 GNU
+系統完成之時將會是常態),並只有在記憶體用量超過 MB
+時才會不遺餘力降低它。在那些處理極大型檔案並非很重要的程式中,我們仍鼓勵程式設計師讀取整分輸å
…¥æª”到核心中,接著掃描內容不要擔心 I/O 問題。</p>
+
+<p>這些決定使得許多 GNU 程式在可靠性和速度上勝過它們在 
Unix 上的競爭對手。</p>
+
+<h3>捐贈的電腦</h3>
+
+<p>隨著 GNU 專案的名聲慢慢大起來,人們開始將跑著 Unix 
的電腦捐贈給專案使用。這些捐贈非常有用,因為開發 GNU 
組件的最簡單方法就是在 Unix
+上開發,接著一個一個替換掉系統上的組件。但是這引發一é
 …道德議題:我們到底應不應該擁有 Unix 系統的副本。</p>
+
+<p>Unix 是專有軟體,而 GNU
+專案的哲學理念說過我們不應使用專有軟體。但是,當我們套用「自我防衛而使用暴力合乎正義」的演繹推理過程,我的結論是:å›
 
為要開發自由版替代品以協助他人停止使用專有軟體,所以å¿
…須使用專有軟體的情況合乎情理。</p>
+
+<p>但是,即便這是合乎正義的邪惡,它依然是種邪惡。今日我們不再保有任何
 Unix
+系統副本,因
為我們已經能用自由的作業系統取代。如果我們無法以自由的作業系統取代機器上的作業系統,那我們會改為撤換那臺機器。</p>
+
+<h3>GNU 工作列表</h3>
+
+<p>隨著 GNU
+專案繼續發展,可用的和有人開發的系統組件數量逐漸增加
,如果能有一份清單列出欠
缺的組件名單會很有用。我們用這份清單募集開發者
撰寫缺失的拼圖一角。這份清單後來被熟知為「GNU
+工作列表」。除了缺少的 Unix 組件之外,我們也在清
單中列出å…
¶ä»–各種好用的軟體和文件專案,我們認為真正完善的系統應該要有的一切。</p>
+
+<p>今日 (1),GNU 工作列表中已經幾乎沒有什麼 Unix
+組件——那部份的工作已經完成,只剩下幾個不見得必
要的組件。但是這份清單充
滿許多有些人稱為「應用程式」的專案。只要能吸引到小族群使用è€
…人數以上的程式都是加入作業系統中的好東西。</p>
+
+<p>甚至遊戲都列在工作列表之中——從列表創立之初就列在å
…¶ä¸­ã€‚Unix 包含遊戲,所以自然而然 GNU 
應該也要有。但是對遊戲來說,能不能在 GNU
+上也有得玩不是個議題,所以我們沒有遵循 Unix 
上有的遊戲列表。反之,我們列出許多使用者
可能會喜歡的不同種類遊戲名單。</p>
+
+<p>(1)
+時間點為1998年。到了2009年,我們已不再維護這樣一份冗長的工作列表。社群開發自由軟體的速度之快以至於我們無法跟得上記錄的è
…³æ­¥ã€‚我們改為維護「高優å…
ˆå°ˆæ¡ˆã€åˆ—表,一份我們非常想要鼓勵人們撰寫的專案名單,長度較短。</p>
+
+<h3>GNU 函式庫 GPL</h3>
+
+<p>GNU C 函式庫使用一種特殊的著作傳式授權,稱為 GNU 
函式庫通用公眾授權(1),å…
è¨±å°ˆæœ‰è»Ÿé«”和函式庫連結。為什麼要有這條例外條款?</p>
+
+<p>這無關原則;我們沒有原則說要賦予專有軟體產品收納我們程式碼的資æ
 ¼ã€‚(那為什麼要貢獻那些é 
æœŸæœƒæ‹’絕和我們分享的專案?)讓 C 函式庫使用
+LGPL,或是讓任何函式庫使用 LGPL,是個策略問題。</p>
+
+<p>C 函式庫的用途很廣;每套專有系統或編譯器都隨附 C 
函式庫。因此,只給自由軟體使用我們的 C
+函式庫,並不會對自由軟體生æ…
‹å¸¶ä¾†ä»»ä½•å¥½è™•â€”—只會讓人更不願意使用我們的函式庫。</p>
+
+<p>唯有一套系統是個例外:GNU 系統(包括 GNU/Linux),而 GNU 
C 函式庫是它唯一的 C 函式庫。所以 GNU C
+函式庫的散布條款能決定是否可以在 GNU 
系統上編譯專有軟體。允許 GNU 
系統上有專有軟體不合道德,但是就策略面而言禁止專有軟體似乎反而阻礙人們使用
+GNU 系統,鼓勵不到自由軟體的開發。那就是為什麼使用 LGPL 
對於 C 函式庫而言是個好策略。</p>
+
+<p>至於其他函式庫,決策需要根據各個案例的不同加以考æ…
®ã€‚當某個函式庫對於協助撰寫某類程式有特殊作用時,那麼可以將它以
 GPL
+發行,限制只能讓自由軟體取用,如此就能協助å…
¶ä»–自由軟體開發者,讓他們有優勢對抗專有軟體。</p>
+
+<p>說到 GNU Readline,那是一套開發來提供 BASH 
作指令列編輯的函式庫。Readline 是以原本的 GNU GPL 
授權發行,而非函式庫
+GPL。這樣可能確實減少 Readline 
被使用的次數,但對我們來說沒有什麼損失。此時此刻,至少有個好用的應用程式å›
 ç‚ºè¦åˆ©ç”¨ Readline
+而特地做成自由軟體,那真是社群的一大收穫。</p>
+
+<p>專有軟體的開發者有金錢給予的優勢;而自由軟體開發者
需要相互創造優勢。我希望有一天我們會有許許多多受 GPL
+保護、無法和專有軟體平行運作的函式庫,能一同提供好用的模組作為建構新自由軟體的磚塊,å
…¨éƒ¨åŠ ç¸½èµ·ä¾†æˆç‚ºæ›´å·¨å¤§çš„優勢以利自由軟體向前發展。</p>
+
+<p>(1) 這個授權條款目前已經改稱為 GNU 寬鬆通用公眾授權 
(Lesser General Public
+License),避免造
成所有函式庫都該使用這個授權條款的想法。請參閱<a
+href="/philosophy/why-not-lgpl.html">為何你不應該讓你
下個函式庫使用 LGPL</a> 深入瞭解更多資訊。</p>
+
+<h3>搔個癢?</h3>
+<p>
+艾力克・雷蒙 (Eric Raymond) 
曾說:「每個軟體佳作都是從搔開發者
自身的癢處開始」。或許那種事情偶爾會發生,但是許多 GNU
+軟體的重要組件都是基於希望打造
出完整的自由作業系統而開發的。它們的創造出自遠
見和計畫,而不是衝動。</p>
+<p>
+舉例來說,我們開發了 GNU C 函式庫,是因為 Unix 
風系統要有 C 函式庫;還有 BASH,因為 Unix 
風系統要有外部表殼
+(Shell);以及 GNU tar,因為 Unix 風系統要有個 tar 
程式。對於我所撰寫的程式亦是如此——GNU C 編譯器、GNU
+Emacs、GDB 和 GNU Make 等。</p>
+<p>
+有些 GNU 程式的開發是為了處理我們自由所面臨的威脅
。所以,我們開發了 gzip 取代 Compress 程式,這是因為 <acronym
+title="Lempel-Ziv-Welch">LZW</acronym> 
專利讓社群失落了一塊。我們也資助一些人開發
+LessTif,還有最近剛啟動的 <acronym title="GNU Network Object Model
+Environment">GNOME</acronym> 和 Harmony
+專案,都是為了處理特定專有函式庫所造
成的問題(請見後面描述)。我們同時也在開發 GNU Privacy 
Guard
+來取代受歡迎的非自由加密軟體,因為使用者
不應限制在隱私與自由兩者之間做抉擇。</p>
+<p>
+當然,撰寫這些程式的人也會開始對這類工作感到有趣,而各式各樣的人基於自身需求和興趣而逐步åŠ
 å…¥è¨±å¤šåŠŸèƒ½ã€‚但那些都不是程式誕生的主因。</p>
+
+<h3>未預期的開發</h3>
+<p>
+在 GNU 專案創立之初,我想像著我們會先開發出整個 GNU 
系統,然後再整套一起發行。不過現實並非如此。</p>
+<p>
+只要隨著各個 GNU 系統的組件能在 Unix 
系統上實作出來,各個組件就能在完整的 GNU 系統出現以前å…
ˆåœ¨ Unix
+系統上替換運行。這些程式中有的很受歡迎,使用者
開始擴充這些軟體並移植——移植到各種不相容的 Unix 
版本中,也有時候被移植到其他系統去。</p>
+<p>
+這套流程讓這些程式變得更強大,並且為 GNU 
專案吸引到資金和貢獻者
。但這也可能是導致最低限度可運作系統延後許多年才完成的原å›
 ï¼Œå› ç‚º GNU
+開發者得投å…
¥æ™‚間維護這些移植版,並且為既有的組件增添新功能,所以較少接續撰寫另一é
 … GNU 還未有的組件。</p>
+
+<h3>GNU Hurd</h3>
+<p>
+到了1990年,GNU 系統幾近完成;唯一缺少的重要組件是內部æ 
¸å¿ƒã€‚我們決定要將我們的內部核心以跑在 Mach 
上的伺服器程序集合實作。Mach
+是先在卡內基梅隆大學 (Carnegie Mellon University) 
開發,後來在猶他大學 (University of Utah)
+開發的微核心;而 GNU Hurd 是跑在 Mach 
上的一群伺服器(解釋:如果要說一群 GNU 的話,因為 gnu 
是牛羚,所以英文要講 a herd
+of GNUs,而 Hurd 和 herd 同音),能執行 Unix 內部æ 
¸å¿ƒçš„許多工作。開發的啟動有所延遲,因為我們在等 Mach
+採自由軟體授權發行,這件事他們先前有承諾過。</p>
+<p>
+選擇這樣設計的其中一個原因
,是希望避開工作中看起來最艱難的部份:在沒有來源階段除錯器
 (source-level debugger)
+的幫助下為核心程式除錯。這部份的工作在 Mach 
中已經完成,所以我們打算以使用者層級程式的方法對 Hurd 
伺服器用 GDB
+除錯。但這卻花上很長一段時間才逐漸行得通,多執行序的伺服器彼此間傳送訊息反而讓除錯變得極為困難。我們耗費很多年的時間才讓
 Hurd 能穩固地運作。</p>
+
+<h3>Alix</h3>
+<p>
+GNU 的內部核心起初沒有打算叫作 Hurd。最早的名字是 
Alix——當時我最心愛的女人。Alix 是一位 Unix
+系統管理員,她曾提過自己的名字剛好很合 Unix
+系統版本的常見命名規則;她以說笑話的方式向朋友們說:「真該有人用我的名字幫å
…§éƒ¨æ 
¸å¿ƒå‘½åçš„。」我什麼話也沒說,只是下定決心要做一個名為 
Alix
+的核心來給她驚喜。</p>
+<p>
+好景不常。Michael Bushnell(現在改名 Thomas),內部æ 
¸å¿ƒçš„主要開發者,更偏好 Hurd 這個名稱,然後把 Alix
+重新定義為核心的å…
¶ä¸­ä¸€éƒ¨åˆ†â€”—捕捉系統呼叫並傳送訊息給 Hurd 
伺服器來處理它們的這部分。</p>
+<p>
+後來,Alix 和我分手,她還改了名字;另外,Hurd 
設計也改了,C 函式庫會直接傳訊息給伺服器,所以 Alix 
組件也從設計中消失了。</p>
+<p>
+而在這些事發生之前,Alix 的其中一位朋友曾偶然發現 Hurd 
源始碼中有個
+Alix,所以跟她提過這件事。因此,她確實因
緣際會知道曾有個核心是用她的名字命名的。</p>
+
+<h3>Linux 和 GNU/Linux</h3>
+<p>
+GNU Hurd
+不適合一般工作生產使用,我們也不知道它到底能不能走到那步。以能力為基礎的設計反而å›
 ç‚ºè¨­è¨ˆçš„彈性而造成直接問題,我們也不清
楚到底有沒有個解決方案。</p>
+
+<p>
+幸好,還有另一個內核。1991年林納思・托瓦茲 (Linux Torvalds) 
開發了一個 Unix 相容核心,並稱之為
+Linux。一開始它是專有軟體,不過在1992年時,他將它改為自由軟體;如果我們將
 Linux 和沒那麼完整的 GNU
+系統結合在一起,就成了一套完整的自由作業系統。(當然,把它們搭在一起本身也是個很重要的工作。)å›
 ç‚ºæœ‰äº† Linux,我們今日才得以真正運行一套 GNU
+系統。</p>
+<p>
+我們將這樣的系統版本稱為 <a 
href="/gnu/linux-and-gnu.html">GNU/Linux</a>,表達這是個 GNU 系統和
+Linux 內部æ 
¸å¿ƒçš„結合成果。請不要與世推移跟著把整套系統稱為「Linux」,å›
 ç‚ºé€™ç¨®ç¨±å‘¼æ–¹å¼ä»£è¡¨æŠŠæˆ‘們的工作成果å…
¨éƒ½æ­¸åŠŸåœ¨åˆ¥äººåä¸‹ã€‚è«‹<a
+href="/gnu/gnu-linux-faq.html">平等提及我們的貢獻</a>。</p>
+
+<h3>我們未來的挑戰</h3>
+<p>
+我們已經證明我們有能力開發廣泛的自由軟體。這不表示我們無人能敵而且勢不可擋。還有許多挑戰讓自由軟體的未來不明朗;要達成這些挑戰é
 ˆè¦æ†å¿ƒå’Œæ¯…
力,有時得持續很多年。這需要大家展現出那種珍重自由、且不願讓任何人奪走的決心。</p>
+<p>
+下面四個小節討論將分別探討這些挑戰。</p>
+
+<h3>祕密硬體</h3>
+<p>
+硬體製造商越來越傾向讓硬體規æ 
¼æˆç‚ºæ©Ÿå¯†ã€‚這使得要撰寫出自由驅動程式好讓 Linux 和 XFree86
+能支援新硬體變得更為困難。雖然我們今日已經有完整的自由系統,但只要我們無法支援明日的電è
…¦ï¼Œæˆ‘們明日就無法擁有完整的自由系統。</p>
+<p>
+有å…
©ç¨®è™•ç†é€™é¡žå•é¡Œçš„辦法。程式設計師可以做逆向工程以理解該如何支援這個硬體。剩下的我們,可以選擇自由軟體可支援的硬體;只要我們的人數增åŠ
 ï¼Œç¥•å¯†è¦æ ¼å°±æˆäº†è‡ªæˆ‘毀滅的策略。</p>
+<p>
+逆向工程可是個大工程;我們有決心堅
定的程式設計師要來承擔這些事嗎?有的——只要我們能建設出自由軟體是行事準則、非自由的é©
…
動程式無法容許的強烈感受。那麼我們之中會有許多人願意多花一些錢,或甚至多花一點時間,來讓我們可以使用自由的é©
…動程式嗎?會的,只要保有自由的決心能夠廣泛傳播。</p>
+<p>
+(2008年註:這個議題也延伸到 BIOS。有個自由的 BIOS,<a
+href="http://www.libreboot.org/";>LibreBoot</a>(coreboot 
的散布版);問題在於取得機器的規格,如此
+LibreBoot 才得以支援這些設備而不必用到非自由的 
&ldquo;Blob&rdquo;)</p>
+
+<h3>非自由函式庫</h3>
+<p>
+在自由作業系統上運行的非自由函式庫是個為自由軟體開發è€
…設計的圈套。函式庫的迷人特性是誘餌;如果你
用了這套函式庫,你就掉進圈套裡,因為你
的程式無法有用地成為自由作業系統中的一部分。(嚴æ 
¼ä¾†èªªï¼Œæˆ‘們可以收錄你的程式,但它卻因
為缺少函式庫而無法<em>執行</em>。)更糟的是,如果有個採用專有函式庫的程式變得廣受歡迎,還會誘使å
…¶ä»–沒料想到問題的程式設計師一起落入圈套中。</p>
+<p>
+這問題的第一個實例是1980年代的 Motif å·¥å…
·çµ„。雖然那時還沒有自由的作業系統,但很明顯 Motif 
會衍生後續問題。GNU
+專案以兩個作法回應:邀請各自由軟體專案像支持 Motif 
一樣地支持自由的 X Toolkit widget å…
ƒä»¶ï¼Œä»¥åŠå››è™•è©¢å•æ˜¯å¦æœ‰äººå¯ä»¥æ’°å¯«
+Motif 的自由替代品。這項工作花了許多年;由 Hungry 
Programmers 開發的 
LessTif,只在1997年就足以成熟支援絕大多數的
+Motif 應用程式。</p>
+<p>
+在1996年到1998年之間,另一個叫作 Qt 的非自由 <acronym 
title="Graphical User
+Interface">GUI</acronym> 圖形介面工具組函式庫,則被用於 
<acronym title="K Desktop
+Environment">KDE</acronym> 桌面這套實用的自由軟體集合中。</p>
+<p>
+自由的 GNU/Linux 系統無法使用 KDE,因
為我們無法利用這些函式庫。但是,有些商業型 GNU/Linux
+系統的散布商對忠守自由軟體沒那麼嚴謹,便將 KDE 加
到他們的系統中——更多功能、但較少自由的系統於焉誕生。KDE
 那群人很積極鼓勵程式設計師採用
+Qt,而這數百萬個新手「Linux 使用者
」也從沒接觸過這樣做會有問題的想法。</p>
+<p>
+自由軟體社群以兩項專案回應:GNOME 與 Harmony。</p>
+<p>
+GNOME,全名為 GNU 網路物件模型環境 (GNU Network Object Model 
Environment),是 GNU
+的桌面專案。該專案由 Miguel de Icaza 於1997年創立,在 Red Hat 
公司的支持之下開發。GNOME
+專案試圖提供類似的桌面功能,但是完å…
¨æŽ¡ç”¨è‡ªç”±è»Ÿé«”。此外,它還有一些技術上的優點,例如廣泛支援許多語言,不單只有
 C++
+而已。不過它的主要重點還是自由:不é 
ˆè¦ç”¨åˆ°ä»»ä½•éžè‡ªç”±è»Ÿé«”。</p>
+<p>
+Harmony 是個相容的替代函式庫,設計希望能在不使用 Qt 的情
況下執行 KDE 軟體。</p>
+<p>
+1998年11月時,Qt 的開發者
宣布更動授權條款,實現之後應該能讓 Qt 
變成自由軟體。雖然我們沒有辦法確定,不過我相信這件事有部份受到社群對
 Qt
+非自由的問題做出堅
強回應的影響。(新授權條款不方便而且不平等,所以能避å…
ä½¿ç”¨ Qt 的話還是比較好。)</p>
+<p>
+[後記:2000年9月,Qt 以 GNU GPL 
授權重新發行,明確解決了前述這些問題。]</p>
+<p>
+如果下個誘人的非自由函式庫出現時我們該如何因
應?整個社群會明瞭跳脫圈套的必
要性嗎?或是我們之中有許多人捨棄自由將就方便,產生更é
 å¤§çš„問題?我們的未來取決於我們的思想理念。</p>
+
+<h3>軟體專利</h3>
+<p>
+我們所面對的最可怕威脅
來自軟體專利。軟體專利能限制自由軟體不能實作某些演算法和功能,時間長達
 20 年之久。LZW
+壓縮演算法於1983年申請到專利,但我們仍然不能發行可製作適當壓縮後
 <acronym title="Graphics Interchange
+Format">GIF</acronym> 
圖片檔的自由軟體。[直到2009年所有相關專利才全數過期。] 
在1998年時,有個能製作 <acronym
+title="MPEG-1 Audio Layer 3">MP3</acronym> 壓縮音訊的自由程式因
為受到專利訴訟威脅而從散布版中移除。</p>
+<p>
+有一些辦法可以處理專利:我們可以搜尋專利無效的證據,我們也可以改尋求å
…¶ä»–方式來完成同件事情
。但是這些方法不見得每次都管用;有時候這å…
©ç¨®æ–¹æ³•éƒ½è¾¦ä¸åˆ°ï¼Œå°ˆåˆ©å¯è¿«ä½¿æ‰€æœ‰è‡ªç”±è»Ÿé«”都欠
缺某些使用者想要的功能。在長時間等待
後,專利終於過期(MP3
+專利群預計在2018年時å…
¨æ•¸éŽæœŸï¼‰ï¼Œä½†é‚£æ™‚候我們能做些什麼?</p>
+<p>
+我們之中因
為自由的價值而重視自由軟體的人,無論如何都會願意留下來和自由軟體å¾
…在一起;我們會努力設法在缺少專利功能的情況下完成事情
。但那些認為自由軟體在技術上較進步而偏好自由軟體的人,在專利拖住自由軟體發展之時卻會說這是自由軟體的失敗。所以,雖然談論「市集」開發模型在實務上很有效,以及說有些自由軟體很穩定很有力等觀點,對於推動自由軟體很有用處,但我們不該就停在那裡。我們å¿
…須進一步談論自由和原則問題。</p>
+
+<h3>自由文件</h3>
+<p>
+我們的自由作業系統最缺乏的一部分不是軟體——真正缺乏的是能收錄到我們系統中的優質自由手冊。文件是任何軟體åŒ
…必要的一部分;當重要的自由軟體包
沒有隨附良好的自由手冊時,那是一塊大缺陷。我們今日還有許多這樣子的缺陷。</p>
+<p>
+自由文件,好比自由軟體,同樣關乎自由,而非價æ 
¼ã€‚自由文件的判斷準則約略與自由軟體相同:給予所有使用è€
…特定的自由。必須允許再次散布(包
含商業銷售),無論媒體採用線上或紙本,如此手冊便得以伴隨程式副本。</p>
+<p>
+å…
è¨±ä¿®æ”¹ä¹Ÿå¾ˆé—œéµã€‚至於常理,我認為人們不一定得以有權修改所有種類的文ç«
 å’Œæ›¸ç±ã€‚例如,我認為你
或我都不應當有權利修改和本文相同類型的文章,因
為本篇文章描述的是我們的動作行為和我們的想法觀點。</p>
+<p>
+但自由軟體的文件必須可以自由修改有個特別原因
。當人們行使其權利修改軟體,加å…
¥æˆ–更動軟體功能,如果他們一併對手冊的刪改ç…
žè²»è‹¦å¿ƒâ€”—就能為修改後的程式提供準確且有用的文件。若是非自由的手冊,便不å
…
è¨±ç¨‹å¼è¨­è¨ˆå¸«è²»æ­¤ç”¨å¿ƒå®Œæˆä½œæ¥­ï¼Œä¹Ÿå°±ç„¡æ³•æ»¿è¶³æˆ‘們社群所需。</p>
+<p>
+有些禁止修改的限制不會造
成什麼問題。例如,要求保留原始作者
的著作權聲明、散布條款、或是作者
名單,這些都合理。要求修改後版本納å…
¥è²æ˜Žè¡¨ç¤ºè©²ä½œå“æœ‰ç¶“過修改一樣沒有問題,甚至是要求不可以刪除或修改某整個段落也相同,只要這些段落講的是非技術相關主題就行。這些限制不成問題,å›
 
為它們無法阻止用心的程式設計師把手冊編修得更符合修改後的程式版本。換句話說,這些限制無法阻止自由軟體社群完å
…¨åˆ©ç”¨é€™ä»½æ‰‹å†Šã€‚</p>
+<p>
+然而,必須要可以修改手冊中所有 <em>關於技術</em>
+的å…
§å®¹ï¼Œä¸¦ä¸”能接著將成果載於所有常見媒體、透過所有尋常管道散布;否則,這類限制確實會阻礙社群,這樣一來這份手冊就不自由,我們需要撰寫å
…¶ä»–手冊。</p>
+<p>
+自由軟體開發者是否能覺知到自由手冊,並有決心製作出å…
¨é¢çš„自由手冊呢?再一次,我們的未來取決於我們的思想理念。</p>
+
+<h3>我們必須談論自由</h3>
+<p>
+今日估計約有上千萬人使用 GNU/Linux 系統,例如 Debian 
GNU/Linux 和 Red
+Hat「Linux」。自由軟體已發展出實務上的優勢,讓使用者
們純粹基於實務因素群集至此。</p>
+<p>
+這件事帶來的好處很明顯:有越多人對開發自由軟體有興趣,就有越多顧客會尋求自由軟體業務,也更能鼓勵å
…¬å¸é–‹ç™¼å•†æ¥­çš„自由軟體而非專有軟體產品。</p>
+<p>
+但是對自由軟體產生興趣的速度,遠
比體認到自由軟體的理念思想還快,而這會招致禍害。我們達成上述挑戰與威è„
…的能力,取決於我們願為自由挺身而出的堅
定意志。要確使我們的社群能有這樣的意志,我們需要將理念散播給新來到社群中的使用è€
…知道。</p>
+<p>
+但是我們越來越難辦到:吸引新使用者進å…
¥æˆ‘們社群所下的功夫,遠勝於向他們教導我們社群的å…
¬æ°‘學所費的苦工。我們需要兩者兼為,而且我們要在兩者
所做的努力間維持平衡。</p>
+
+<h3>「開源」</h3>
+<p>
+1998年,要教育新使用者有關自由之事變得更為困難,因
為社群有一部分決定停止使用「自由軟體」這個詞語,並且改說成「開源軟體」。</p>
+<p>
+有些人喜歡用這個詞,主要是因為英文中的「free」也有「å…
è²»ã€çš„含意,所以想避免混淆——很有道理。å…
¶ä»–人,不一樣,他們希望把驅使自由軟體和 GNU
+專案發展的原則精神丟在一旁,然後用這個詞語去吸引執行長、企業用戶等,而這群人大多有:利益高於自由、高於社群、高於原則的想法。所以,「開源」這個巧辯詞聚焦在產出高品質、強大軟體的可能性上,但是迴避自由、社群、原則這些概念。</p>
+<p>
+各種「Linux」雜誌就是明確的範例——書中充斥著能在 
GNU/Linux 上運作的專有軟體廣告。如果有下一個 Motif 或是 Qt
+出現,這些雜誌難道會警告程式設計師該遠
離它嗎?還是會幫它打廣告?</p>
+<p>
+商業支持確實對社群有各種貢獻;商業以外的å…
¶é¤˜è²¢ç»ä¹Ÿç›¸åŒï¼Œéƒ½å¾ˆæœ‰ç”¨ã€‚但如果要讓我們減少談論自由與原則來贏得商業支持會是個災難;這使得å
…ˆå‰çš„拓展與公民學教育之間的不平衡變得更為傾斜。</p>
+<p>
+「自由軟體」和「開源軟體」描述的是差不多相同類別的軟體,但講的是軟體的不同特點、和不同的價值觀。GNU
+專案持續使用「自由軟體」一詞來傳達自由的概念,不只是技術上的作法,這很重要。</p>
+
+<h3>嘗試!</h3>
+<p>
+尤達大師的æ 
¼è¨€ï¼ˆã€Œæ²’有所謂『嘗試』」)聽起來乾淨俐落,但對我來說不太管用。我大部分在做事的時候都還對我到底能不能完成這é
 …工作而焦æ…
®ï¼Œè€Œä¸”也不確定是否由我來做的話成果足不足以達成目標。但不管怎樣我都還是嘗試了,å›
 ç‚ºæ²’有人站在敵人和我的城市之間,å…
¶ä¸­å°±åªæœ‰æˆ‘而已。我自己也很驚訝,有的時候我成功了。</p>
+<p>
+而有時候我失敗了,我有的城市淪陷了。接著我發現另一座城市遭受威è„
…,所以得趕快準備下一å 
´æˆ°é¬¥ã€‚隨著時間過去,我學會尋找威脅
,並挺身走到敵人與我的城市之間,呼叫å…
¶ä»–黑客前來和我一起聯手。</p>
+<p>
+時至今日,我常不是唯一的那一位。每當我看見一群黑客挖掘壕溝嚴守陣線之時,我便鬆了一口氣並有股喜æ‚
…油然而生,我於是é 
˜æ‚Ÿï¼Œé€™åº§åŸŽå¸‚保得住——此時此刻。但一年一年過去危險也越來越大,現在微軟已明確鎖定我們社群。我們不能將未來的自由視為理所當然。別視為理所當然!如果ä½
 æƒ³è¦ä¿ä½ä½ çš„自由,你必須準備抵抗。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-tw.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>請來信到 <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> 
詢問有關自由軟體基金會 (FSF)
+和 GNU 的一般問題;或者<a href="/contact/">以å…
¶ä»–方式</a>聯絡自由軟體基金會。至於損毀的連結及å…
¶ä»–修正和建議,可以將之寄給
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+
+<p>
+<!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我們努力盡所能提供貼切、品質良善的翻譯。然而,我們無法十å
…¨åç¾Žï¼Œé‚„請將你的意見評述與一般建議寄給 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a></p><p>請參照
+<a href="/server/standards/README.translations.html">翻譯讀我 README</a>
+來瞭解協調和提交我們的網頁翻譯相關事宜。</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright &copy; 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010, 2014, 2015,
+2017 Richard Stallman</p>
+
+<p>本頁面採用<a rel="license"
+href="https://creativecommons.org/licenses/by-nd/4.0/deed.zh_TW";>創用 CC
+姓名標示-禁止改作 4.0 國際</a>條款給予授權。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-tw.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻譯</b>:曾政嘉 <a href="mailto:zerngjia (at) member (dot) fsf (dot)
+org">zerngjia (at) member (dot) fsf (dot) org</a>, 2017.</div>
 
-<H3>GNU ­pµe</H3>
+<p class="unprintable"><!-- timestamp start -->
+更新時間︰
 
-<P><A HREF="http://www.stallman.org/";><STRONG>Richard 
Stallman</STRONG></A><P>³Ìªìµoªí¦b "Open Sources" ³o¥»®Ñ
+$Date: 2017/12/05 07:29:14 $
 
-<P>
-<A HREF="/graphics/whatsgnu.html"><IMG SRC="/graphics/whats-gnu-sm.jpg"
-   ALT=" [image of What's GNU] "
-   WIDTH="125" HEIGHT="120"></A>
-
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-  <A HREF="/gnu/thegnuproject.cs.html">±¶§J¤å</A>
-| <A HREF="/gnu/thegnuproject.zh-cn.html">²Å餤¤å</A>
-| <A HREF="/gnu/thegnuproject.zh-tw.html">ÁcÅ餤¤å</A>
-| <A HREF="/gnu/thegnuproject.en.html">­^¤å</A>
-| <A HREF="/gnu/thegnuproject.fr.html">ªk¤å</A>
-| <A HREF="/gnu/thegnuproject.id.html">¦L«×¥§¦è¨È¤å</A>
-| <A HREF="/gnu/thegnuproject.it.html">¸q¤j§Q¤å</A>
-| <A HREF="/gnu/thegnuproject.ko.html">Áú¤å</A>
-| <A HREF="/gnu/thegnuproject.ru.html">«Xù´µ¤å</A>
-| <A HREF="/gnu/thegnuproject.es.html">¦è¯Z¤ú¤å</A>
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P>
-
-<H3>address@hidden@¨ÉªÀ¸s</H3>
-
-<P>address@hidden@¦~¶}©l¬°³Â¬Ù²z¤u¾Ç°|address@hidden@address@hidden@address@hidden@¼Ë¡C¦ý¬O§Ú­Ì¤ñ¤j¦h¼Æ¤H°µªº§ó¦h¡C</P>
-
-<P>address@hidden address@hidden (1) address@hidden PDP-1 
address@hidden@address@hidden@¬O¨Ó§ï¶i³o­Ó¨t²Î¡C</P>
-
-<P>address@hidden@­Ó·sªºµ{¦¡¡C</P>
-
-</P>(1) address@hidden@address@hidden</P>
-
-<H3>ªÀ¸sªº±Y¼ì</H3>
-
-<P>address@hidden Digital ¤½¥q¤£¦AÄ~Äò¨ä PDP-10 
¨t¦C®É¹ý©³¦a§ïÅܤF¡C¦¹¨t¦Cªº¬[ºc¦b¤»¡³¦~¥NµÛ¹êÀu¶®¥B¦³¤O¡A¦ý«oµLªk¦ÛµM¦aÂX¥R¨ì¦b¤K¡³¦~¥N¦¨¬°¥i¯àªº¸û¤jªº©w§}ªÅ¶¡¡C³o·N¨ýµÛ´X¥G©Ò¦³ºc¦¨
 ITS ªºµ{¦¡³£¤w¸g³Q²^¨O¤F¡C</P>
-
-<P>address@hidden@¦~¡A©â¸ê²æÂ÷ªº Symbolics 
¤½¥q¤w¸g±q¤H¤u´¼¼z¹êÅç«Ç¶±¶Ä¨«¤F´X¥G©Ò¦³ªºÀb«È¡A¤H¤f´î¤ÖªºªÀ¸s¤w¤£¯àºû«ù¨ä¦Û¨­¡C¡]Steve
 Levy address@hidden@¥x·sªº PDP-10 ®É¡A¨äºÞ²z¼h¨M©w¨Ï¥Î Digital 
ªº«D¦Û¥Ñ¤À®É¨t²Î¦Ó¤£¬O ITS ¡C</P>
-
-<P>VAX ©Î 68020 address@hidden@address@hidden</P>
-
-<P>address@hidden@address@hidden@­Ó«I¥Çª©ÅvªÌ¡C¦pªG§A»Ý­n¥ô¦ó§ó§ï¡A¨D§Ú­Ì¨Ó°µ¡C¡v</P>
-
-<P>»{¬°¨p¦³³nÅéªÀ·|Åé¨î -- address@hidden -- 
¬O¤ÏªÀ·|address@hidden|address@hidden|address@hidden</P>
-
-<P>·í³nÅé¥Xª©ªÌ½Í¨ì¡u°í«ù¡v¥L­Ìªº¡uÅv§Q¡v©Î¡uªý¤î«I¥Çª©Åv¡v®É¡A¥L­Ì¹ê»Ú©Ò¡u»¡¡vªº¬O¦¸­nªº¡C³o¨ÇÁn©ú¯u¥¿ªº°T®§¬O¥L­Ì±N¥¼ÄÄ©úªº°²³]µø¬°²z©Ò·íµM¡F¤½²³³Q»{¬°À³·íµL²§Ä³¦a±µ¨ü³o¨Ç¡CÁÙ¬OÅý§Ú­Ì¨Ó¥J²ÓÀˬd³o¨Ç§a¡C</P>
-
-<P>address@hidden@address@hidden@address@hidden</P>
-
-<P>address@hidden@address@hidden@ -- 
§Ú­Ì­pºâ¾÷¥Î¤á¤£À³¸Ó¦b·N§Ú­Ì³Q¤¹³\¥h¾Ö¦³­þºØªÀ·|¡C</P>
-
-<P>²Ä¤T­Ó°²³]¬O¡A¦pªG§Ú­Ì¤£´£¨Ñ³nÅ餽¥q¦b¥Î¤á¤§¤Wªºµ{¦¡ªºÅv§Q¡A§Ú­Ì±N¨S¦³¥i¥H¨Ï¥Îªº³nÅé¡]©Î¡A±N¨M¤£·|address@hidden@¡^¡C³o­Ó°²³]¦b¦Û¥Ñ³nÅé¹B°ÊÃÒ©ú§Ú­Ì¯à°÷¤£¥²¨ü¨ä§ô¿£¦Ó»s³yÂ×´Iªº¦³¥Î³nÅ餧«e¡A¤]³\¬Ý°_¨Ó¹³¬O¦³²zªº¡C</P>
-
-<P>address@hidden|ªº°ò¦¡C</P>
-
-<P>³o¨à¨S¦³¸Óµ²½×­I«á¼sªx±À²zªºªÅ¶¡¡A¦]¦¹ÅªªÌ¥i°Ñ¾\¤UÃäºô­¶¡A <A 
HREF="http://www.gnu.org/philosophy/why-free.html";>http://www.gnu.org/philosophy/why-free.html</A>
 ¡C</P>
-
-<H3>address@hidden</H3>
-
-<P>address@hidden</P>
-
-<P>address@hidden</P>
-
-<P>«ö¦¹¤è¦¡¡A§Ú¥i¯à¤w¸g±Ã¤F¿ú¡A¨Ã©Î³\¦Û¤v¶}¤ß¦a¼g¥N½X¡C¦ý¬O§Úª¾¹D¦b§Úªº¨Æ·~²×ÂI¡A§Ú±N¦^±æ¿vÀð¹j¶}¤H­Ìªº³o¨Ç¦~¡A·|address@hidden</P>
-
-<P>·í¦³¤H©Úµ´µ¹§Ú©M MIT 
¤H¤u´¼¼z¹êÅç«Ç¦³Ãöªº§Ú­Ì¦Lªí¾÷ªº±±¨îµ{¦¡·½½X®É¡A§Ú¤w¸g¸g¾ú¤F³B¦b«O±K¨óijªº±µ¨üºÝ¡C¡]¸Óµ{¦¡¬Y¨Ç¯S¦âªº¯Ê¤Ö¨Ï±o¦Lªí¾÷ªº¨Ï¥Î·¥¨ä§xÃø¡C¡^¦]¦¹§Ú¤£¯à§i¶D§Ú¦Û¤v«O±K¨óij¬OµL®`ªº¡C·í¥L©Úµ´Åý§Ú­Ì¤À¨É¨ä¥N½X®É¡A§Ú«D±`¥Í®ð¡F§Ú¤£¯à°÷Âà¹L¨­¨Ó¡AµM«á¦Û¤v¤]¹ï¨C­Ó¤H°µ³o¦P¼Ëªº¨Æ±¡¡C</P>
-
-<P>address@hidden|³QÀݥΡA¦ý¤´·|³Q®ö¶O¡C§Ú±N¤£·|¦]¹jÂ÷©M­­¨î­pºâ¾÷¥Î¤á¦Ó³Q«ü³d¡AÁöµM¦p¦¹¡A³oºØ±¡§Î¤´µM·|Ä~Äòµo¥Í¡C</P>
-
-<P>address@hidden@address@hidden@address@hidden</P>
-
-<P>address@hidden@address@hidden@address@hidden@address@hidden -- 
¨ÃÁܽХô¦ó¤H°Ñ¥[¡C¥ô¦ó¤H³£¯à°÷¨Ï¥Î­pºâ¾÷¦Ó¤£¥²±q¹Ï¿Ñ­é¹Ü¥L©Î¦oªºªB¤Í¶}©l¡C</P>
-
-<P>address@hidden@address@hidden@address@hidden@¡C§Ú¿ï¾Ü±N¸Ó¨t²Î°µ¦¨»P Unix 
¬Û®e¦]¦Ó¥¦¥i³Q²¾´Ó¡A¨Ã¨Ï Unix ¥Î¤á¥i¥H®e©ö¦aÂà´«¨ì¥¦¡C GNU 
address@hidden@­Ó»¼°jªº¡uGNU's Not Unix¡v­º¦r¥ÀÁY¼g¡C</P>
-
-<P>address@hidden@address@hidden@address@hidden@·~¨t²Îªº¨t²Î¥]¬A©R¥O³B²z¾¹¡A²ÕĶµ{¦¡¡A½sĶ¾¹¡A¸ÑÄÀµ{¦¡¡A½Õ¸Õ°£¿ù¾¹¡A¤å¦r½s¿è¾¹¡A¶l¥óµ{¦¡¡A¥H¤Î¨ä¥¦³\¦hµ{¦¡¡C
 ITS ¡B Multics ¡B VMS ©M Unix ³£¦³³o¨Ç¡C GNU address@hidden</P>
-
-<P>«á¨Ó§ÚÅ¥¨ì§Æ°Çº¸ªº³o¨Ç¸Ü (1)¡G</P>
-
-<BLOCKQUOTE>
-     §Ú¤£¬°§Ú½Ö¬°§Ú¡H
-     §Ú¥u¬°§Ú§Ú¬°¦ó¡H
-     ­Y«D²{¦b­n¦ó®É¡H
-</BLOCKQUOTE>
-
-<P>¨M©w¶}©l GNU address@hidden</P>
-
-<P>(1) address@hidden@address@hidden@­Ó»¡¹Lªº¸Ü¡C</P>
-
-<H3>¦Û¥Ñ¦Û¦b¯ëªº¦Û¥Ñ</H3>
-
-<P>¡u¦Û¥Ñ³nÅé¡v³o­Ó³N»y¦³®É³Q¿ù»~¦a²z¸Ñ -- address@hidden@address@hidden</P>
-
-<UL>
-  <LI>§A¦³¦Û¥Ñ¬°¥ô¦ó¥Øªº¥h¹B¦æ¸Óµ{¦¡¡C
-  <LI>address@hidden
-  <LI>address@hidden
-  <LI>§A¦³´²§G¸Óµ{¦¡­×§ï¹Lªºª©¥»¡A±q¦ÓÅýªÀ·|±o¥H¨ü¯q©ó§Aªº§ï¶iªº¦Û¥Ñ¡C
-</UL>
-
-<P>¥Ñ©ó "free" address@hidden</P>
-
-<P>address@hidden@­Ó²³æªº¡B©ú½Tªº³æµü¥Î¨Óªí¥Ü¡u¦Û¥Ñ¡v¡A´N¹³¦Û¥Ñ¦Û¦b -- 
address@hidden@¨Ç¨ä¥¦¯ÊÂI¡C</P>
-
-<H3>GNU ³nÅé©M GNU ¨t²Î</H3>
-
-<P>address@hidden@­Ó«Ü¤jªº­pµe¡C¬°¤F¨Ï¨ä¹F¦¨¡A§Ú¨M©w¥u­n¦³¥i¯à´N¥h§ï¼g¨Ã¨Ï¥Î²{¦³ªº¦Û¥Ñ³nÅé¡C¨Ò¦p¡A¦b³Ìªì§Ú¨M©w¥Î
 TeX address@hidden@¨Ç¦~«á¡A§Ú¨M©w¥Î X Window ¨t²Î¦Ó¤£¬O¬° GNU 
address@hidden</P>
-
-<P>¥Ñ©ó³o¶µ¨M©w¡A GNU ¨t²Î»P©Ò¦³ GNU ³nÅ骺°ï¿n¤£¦P¡C GNU ¨t²Î¥]¬A«D GNU 
³nÅéµ{¦¡¡A³o¨Çµ{¦¡¬O¥Ñ¨ä¥L¤H©Î­pµe¬°¤F¥L­Ì¦Û¤vªº¥Øªº¦Ó¶}µoªº¡C§Ú­Ì¤§©Ò¥H¯à¥Î¥¦­Ì¬O¦]¬°¥¦­Ì¬O¦Û¥Ñ³nÅé¡C</P>
-
-<H3>¶}©l¸Ó­pµe</H3>
-
-<P>address@hidden|address@hidden MIT address@hidden GNU ³nÅé¡CÂ÷¶} MIT 
¬O¥²­nªº¡A³o¼Ë¥i¥H¨Ï MIT µLªk¤z¯A±N GNU address@hidden MIT 
address@hidden@address@hidden@¨É³nÅéªÀ¸s¡C</P>
-
-<P>¾¨ºÞ¦p¦¹¡A Winston ±Ð±Â¡A«á¨Óªº MIT 
¤H¤u´¼¼z¹êÅç«Ç»â¾É¤H¡A¤Íµ½¦aÁܽЧÚÄ~Äò¨Ï¥Î¹êÅç«Çªº³]¬I¡C</P>
-
-<H3>ªì´Áªº¸}¨B</H3>
-
-<P>¶}©l GNU ­pµeªº¤£¤[¤§«e¡A§ÚÅ¥»¡¤F¥s°µ VUCK address@hidden@­Ó¦r¥À 
address@hidden C ©M Pascal address@hidden GNU ¬O§_¥i¥H¨Ï¥Î¥¦¡C</P>
-
-<P>address@hidden GNU address@hidden</P>
-
-<P>¦]¬°§Æ±æÁקK¦Û¤v½s¼g¾ã­Ó½sĶ¾¹ªº¥²­n¡A§Ú±o¨ì¤F¦b Lawrence Livermore 
¹êÅç«Ç¶}µoªº¦h¥­¥x½sĶµ{¦¡ Pascal address@hidden@­Ó¨t²Î½sµ{»y¨¥ªº Pascal 
address@hidden C ªº«eºÝ¡A¨Ã¶}©l±N¥¦²¾´Ó¨ì Motorola 68000 
­pºâ¾÷¡C¦ý¬O·í§Úµo²{¸Ó½sĶ¾¹»Ý­n¦Ê¸U¦r¸`ªº°ïÅ|ªÅ¶¡®É¡A§Ú¤£±o¤£©ñ±ó¡C¥i¥Îªº 
68000 Unix ¨t²Î¶È¶È¤¹³\ 64k ¦r¸`¡C</P>
-
-<P>§ÚÀH«á¤F¸Ñ¨ì Pascal address@hidden@address@hidden address@hidden Pascal 
½sĶ¾¹ªº¤º®e¡A¤£¹L§Ú¤´³]ªk§ï½s©M¨Ï¥Î§Ú¤w¼g¦nªº C 
«eºÝ¡C¦ý¨º¬O´X¦~«áªº¨Æ¤F¡F­º¥ý¡A§Ú¶}µo GNU Emacs ¡C</P>
-
-<H3>GNU Emacs</H3>
-
-<P>address@hidden|¦~¤E¤ë¶}©lµÛ¤â GNU Emacs address@hidden Unix address@hidden 
vi ©Î ed ¡Aª½¨ì¨º®É§Ú¬O¦b¨ä¥¦Ãþ«¬¾÷¾¹¤W°µ§Úªº½s¿èªº¡C</P>
-
-<P>³o®É­Ô¡A¤H­Ì¶}©l·Q¥Î GNU 
Emacs¡A¦]¦¹¥X²{¤F¸Ó¦p¦óµo¦æ¥¦ªº°ÝÃD¡C·íµM¡A§Ú±N¥¦©ñ¦b§Ú¥Îªº MIT ­pºâ¾÷ªº°Î¦W 
FTP ¦øªA¾¹¤W¡C¡]³o¥x­pºâ¾÷¡A prep.ai.mit.edu ¡A¦]¦¹¦¨¬°¥D­nªº GNU FTP 
address@hidden FTP address@hidden Internet ¤W¡A¤£¯à³q¹L FTP 
Àò±o«þ¨©¡C©Ò¥H°ÝÃD¬O¡A§Ú¸Ó¹ï¥L­Ì»¡¤°»ò¡H</P>
-
-<P>§Ú¿³³\·|address@hidden@­Ó«þ¨©µ¹§A¡C¡v©ÎªÌ§Ú¿³³\·|¹³§Ú¬°­ì¨Óªº PDP-10 Emacs 
address@hidden@­Ó¶K¨¬¶l¸êªº¦^«H«Ê¡A§Ú·|±N Emacs address@hidden|address@hidden 
$150 ¡C¥Î³oºØ¤èªk¡A§Ú¶}©l¤F¦Û¥Ñ³nÅéµo¦æªº¨Æ·~¡A¥¦¬O²{¤µµo¦æ¾ã­Ó°ò©ó Linux ªº 
GNU ¨t²Îªº¤½¥qªº¥ýÅX¡C</P>
-
-<H3>address@hidden</H3>
-
-<P>address@hidden@address@hidden@address@hidden@address@hidden@¦ý¬O°ò©ó²³æ³\¥iÃÒ¥[¥Hµo¦æ¡A¤¹³\¨p¦³ªº­×§ïª©¥»¡C</P>
-
-<P>³o­Ó°ÝÃDªº¨å«¬¨ÒÃÒ¬O X Window ¨t²Î¡C¥Ñ MIT 
address@hidden@¬°¦Û¥Ñ³nÅéµoªí¡A¥¦«Ü§Ö§Y³Q¤£¦Pªº­pºâ¾÷¤½¥q©Ò±Ä¥Î¡C¥L­Ì±N X 
¥H¶È¤G¶i¨î§Î¦¡ªº¤è¦¡¥[¨ì¥L­Ìªº¨p¦³ Unix ¨t²Î¤¤¡A¨Ã³Q¦P¼Ëªº«O±K¨óij±±¨îµÛ¡C³o¨Ç 
X ªº«þ¨©¡A´N¹³ Unix address@hidden</P>
-
-<P>X Window address@hidden -- 
¥L­Ì´Á±æ¨Ã¦³·N¨Ï¨äµo¥Í¡C¥L­Ìªº¥Ø¼Ð¤£¬O¦Û¥Ñ¡A¦Ó¶È¶È¬O¡u¦¨¥\¡v¡A¨ººØ©w¸q¬°¡u¦³³\¦h¥Î¤á¡vªº¦¨¥\¡C¥L­Ì¤£¦b·N³o¨Ç¥Î¤á¬O§_¾Ö¦³¦Û¥Ñ¡A¥u¬O§Æ±æ¥L­Ì¤H¼Æ²³¦h¡C</P>
-
-<P>address@hidden@­Ó°ÝÃD¡u³o¬O¦Û¥Ñµ{¦¡¶Ü¡H¡vµ¹¥X¤£¦Pªº¦^µª¡C¦pªG§A°ò©ó MIT 
address@hidden|»¡ X ¬O¦Û¥Ñ³nÅé¡C¦ý¬O¦pªG§A¥H X address@hidden X 
¥Î¤á·í®É¥¿¦b¨Ï¥Îªº¬OÀH Unix ¨t²Î¦Ó¨Óªº¨p¦³ª©¥»¡A¦Ó¤£¬O¦Û¥Ñª©¥»¡C</P>
-
-<H3>Copyleft ©M GNU GPL</H3>
-
-<P>GNU ªº¥Ø¼Ð¬Oµ¹¥Î¤á¦Û¥Ñ¡A¦Ó¤£¬O¶È¶È¦¨¬°¬y¦æ¡C©Ò¥H§Ú­Ì»Ý­n¨Ï¥Î¥i¥Hªý¤î GNU 
³nÅé³QÂàÅܦ¨¨p¦³³nÅ骺µo¦æ±ø´Ú¡C§Ú­Ì©Ò¥Îªº¤èªk³QºÙ¤§¬°¡ucopyleft¡v¡C(1)</P>
-
-<P>Copyleft address@hidden@ºØ«O«ù³nÅé¦Û¥Ñªº¤â¬q¡A¦Ó¤£¬O±N³nÅé¨p¦³¤Æªº¤èªk¡C</P>
-
-<P>Copyleft 
ªº¤¤¤ß«ä·Q¬O§Ú­Ìµ¹¤©¨C­Ó¤H¹B¦æ¸Óµ{¦¡¡A«þ¨©µ{¦¡¡A­×§ïµ{¦¡©M´²§G¨ä­×§ïª©¥»ªº³\¥i 
-- address@hidden</P>
-
-<P>address@hidden copyleft address@hidden@address@hidden@address@hidden GNU 
³nÅé®É¡A copyleft address@hidden@¸Óµ{¦¡ªº§Ú­Ìªº¨p¦³ª©¥»¡C¡v</P>
-
-<P>¦pªG§Ú­Ì­n½T«Oµ{¦¡¨C­Ó¥Î¤áªº¦Û¥Ñ¡A­×§ï¥²¶·¬O¦Û¥Ñªº³o­Ó»Ý¨D¬O¥²­nªº¡C¨º¨Ç¨p¦³¤Æ
 X Window address@hidden@¨Ç­×§ï¥H±N¨ä²¾´Ó¨ì¥¦­Ìªº¨t²Î©MµwÅé¡C³o¨Ç§ï°Ê»P X 
address@hidden</P>
-
-<P>address@hidden@address@hidden@¿´²îªº¬}¡C¦]¦¹¡A copyleft address@hidden@­Ó 
copyleft ªºµ{¦¡©Ò²Õ¦X¦Ó¦¨ªºµ{¦¡¥²¶·¤]¨Ï§ó¤jªº²Õ¦Xª©¥»¤]¬O¦Û¥Ñªº©M copyleft 
ªº¡C</P>
-
-<P>§Ú­Ì¬°¤j¦h¼Æ GNU ³nÅé¨Ï¥Îªº copyleft ªº©ú½T¹ê²{¬O GNU address@hidden GNU 
GPL ¡C§Ú­Ì¦b¯S©w³õ¦X¤U¦³¨ä¥¦ºØÃþ copyleft ¥i¥H¨Ï¥Î¡C GNU ¤â¥U¤]¬O copyleft 
address@hidden copyleft Ãþ«¬¡A¦]¬° GNU GPL ªº½ÆÂø©Ê¹ï¨ä¤â¥U¬O¤£»Ý­nªº¡C</P>
-
-<P>(1) address@hidden|address@hidden Don Hopkins 
address@hidden@address@hidden@Åv¨S¦³¡GºM¦^©Ò¦³Åv§Q¡v¡]Copyleft: all rights 
address@hidden Hacker Ethic, and the spirit of information 
address@hidden@µü¡C¬O¹ï¡uª©Åv©Ò¦³ ½¦L¥²¨s¡v¡]Copyright: all rights 
address@hidden</P>
-
-<H3>¦Û¥Ñ³nÅé°òª÷·|</H3>
-
-<P>ÀHµÛ¨Ï¥Î Emacs ¿³½ìªº¼Wªø¡A¨ä¥L¤H¥[¤J¤F GNU 
address@hidden|address@hidden|ªº¬°¦Û¥Ñ³nÅéµo®iªº·Oµ½¹ÎÅé¡C FSF ¤]±µ¤â¤F Emacs 
address@hidden GNU ¤]¦³«D GNU ¡^¡A¤]³q¹L¥X°â¦Û¥Ñ¤â¥UÂX®i¤F¸Ó·~°È¡C</P>
-
-<P>FSF ±µ¨ü®½´Ú¡A¦ý¬O¨ä¤j³¡¤À¦¬¤J±`±`¨Ó¦Û¾P°â -- 
¦Û¥Ñ³nÅ骺«þ¨©¡A©M¨ä¥¦¬ÛÃöªºªA°È¡C¤µ¤Ñ¥¦½æ·½½Xªº CD-ROMs ¡A¤G¶i¨î¥N½Xªº CD-ROMs 
address@hidden</P>
-
-<P>¦Û¥Ñ³nÅé°òª÷·|address@hidden@¨t¦Cªº GNU ³nÅé¥]¡C¨â­Ó­È±oª`·Nªº¬O C 
®w©M¥~´ß(shell)¡C GNU C ®w¬O¨C­Ó¹B¦æ©ó GNU/Linux ¨t²Îªºµ{¦¡¨Ï¥Î¨Ó»P Linux 
³q«Hªº¡C¥¦¬O¥Ñ¦Û¥Ñ³nÅé°òª÷·|address@hidden Roland McGrath ¶}µoªº¡C³Q¤j¦h¼Æ 
GNU/Linux ¨t²Î¨Ï¥Îªº¥~´ßµ{¦¡¬O BASH ¡A the Bourne Again Shell (1) ¡A¥¦­Ì¬O¥Ñ 
FSF ­û¤u Brian Fox ¶}µoªº¡C</P>
-
-<P>§Ú­Ì¸ê§U¤F³o¨Çµ{¦¡ªº¶}µo¦]¬° GNU 
address@hidden@·~¨t²Î¡A¦Ó³o¨Ç¤u¨ã¹ï©ó³o­Ó¥Ø¼Ð¬O»Ý­nªº¡C</P>
-
-<P>(1) ¡uBourne again address@hidden Shell¡vªº Unix ±`¥Î shell ªºª±¯º¡C</P>
-
-<H3>¦Û¥Ñ³nÅé¤ä«ù</H3>
-
-<P>address@hidden@¥¦­Ì¦¨¥\¡C</P>
-
-<P>¾P°â Emacs address@hidden FSF 
address@hidden@ºØ¿Ñ¥Í¤èªk¡C§Ú¦b¾P°â§Ú©Ò¶}µoªº¦Û¥Ñ³nÅé¬ÛÃöªA°È¤¤§ä¨ì¤F¥¦¡C¥¦¥]¬A±Ð¾Ç¡A¥DÃD½Ñ¦p¦p¦ó¹ï
 GNU Emacs ½sµ{¡A¦p¦ó¦Û­q GCC¡A©M³q±`¬O²¾´Ó GCC ¨ì·s¥­¥xªº³nÅé¶}µo¡C</P>
-
-<P>address@hidden 
ªº¦Û¥Ñ³nÅ馬ÂáF¨ä¥¦ªº«h³c½æ±q¦^µª¥Î¤á°ÝÃD¨ì§ï¥¿µ{¦¡¿ù»~¡A¨ì¼W¥[¤jªº·s¥\¯àµ¥¤£¦P¼h¦¸¤WªºªA°È¡C§Ú­Ì¬Æ¦Ü¶}©l¬Ý¨ì°ò©óµo°_·sªº¦Û¥Ñ³nÅé²£«~ªº¦Û¥Ñ³nÅ餽¥q¡C</P>
-
-<P>­È±o¯S§Oª`·Nªº¬O¡A³\¦h¤½¥q¾¨ºÞ±N¥¦­Ì¦Û¤v»P¡uopen address@hidden</P>
-
-<H3>§Þ³N¥Ø¼Ð</H3>
-
-<P>GNU address@hidden GNU ¤£¤ñ Unix address@hidden@ªºªÀ·|address@hidden</P>
-
-<P>address@hidden -- 
¨Ò¦p¡A°ÊºA¦a¤À°t¼Æ¾Úµ²ºc¥HÁקKªZÂ_ªº©T©w¤j¤p­­¨î¡A¨Ã¦b¥ô¦ó¦³·N¸q¤§³B³B²z©Ò¦³¥i¯àªº
 8 ¦ì¤¸¥N½X¡C</P>
-
-<P>¥t¥~¡A§Ú­Ì©ñ±ó¤F¤p¤º¦s¤j¤pªº Unix ³]­p¡A¨M©w¤£¤ä«ù 16 ¦ì¤¸¾÷¾¹¡] 32 
¦ì¤¸¾÷¾¹¦b GNU address@hidden</P>
-
-<P>³o¨Ç¨M©w¨Ï±o³\¦h GNU µ{¦¡¦b¥i¾a©Ê©M³t«×¤W¶W¶V¤F¥¦­Ì¦bUnix 
¤W¬Û·íªº¨ä¥¦µ{¦¡¡C</P>
-
-<H3>®½Ãتº­pºâ¾÷</H3>
-
-<P>ÀHµÛ GNU ­pµe¦WÁnªº¼Wªø¡A¤H­Ì¶}©l´£¨Ñ®½ÃعB¦æ Unix 
ªº­pºâ¾÷µ¹¦¹­pµe¡C³o¨Ç¬O«D±`¦³¥Îªº¡A¦]¬°¶}µo GNU address@hidden Unix 
address@hidden@address@hidden@­Ó¹D¼w°ÝÃD¡G§Ú­Ì¾Ö¦³ Unix 
«þ¨©±q®Ú¥»¤W¨Ó»¡¬O§_¥¿½T¡C</P>
-
-<P>Unix ±q¥H«e¨ì²{¦b³£¬O¨p¦³³nÅé¡A¦Ó GNU 
­pµeªº­õ¾Ç«h»¡§Ú­Ì¤£¸Ó¨Ï¥Î¨p¦³³nÅé¡C¦ý¬O¡AÀ³¥Î»P±À½×¥X 
¡u¦Û§Ú¨¾½Ã¤¤ªº¼É¤O¬O¥¿·íªº¡v 
¬Û¦Pªº½×²z¡A§Úªºµ²½×¬O¡G¦b¶}µo±N¥Î¨ÓÀ°§U¨ä¥L¤H°±¤î¨Ï¥Î¨p¦³³nÅé¥]ªº¦Û¥Ñ³nÅé¥N´À«~ªºÃöÁä®É¨è¡A¨Ï¥Î¨p¦³³nÅé¥]¬O¦X²zªº¡C</P>
-
-<P>address@hidden Unix 
address@hidden@address@hidden@·~¨t²Î¡A§Ú­Ì«h´À´«¸Ó­pºâ¾÷¡C</P>
-
-<H3>GNU ¥ô°È¦Cªí</H3>
-
-<P>ÀHµÛ GNU 
address@hidden@¥ó¦³·N¸qªº¨Æ±¡¡C§Ú­Ì¥Î¥¦¨Ó©Û¸u¶}µoªÌ½s¼g¿òº|ªº³¡¤À¡C³o­Ó¦Cªí¦¨¬°²³©Ò©Pª¾ªº
 GNU ¥ô°È¦Cªí¡C°£¤F¿òº|ªº Unix address@hidden</P>
-
-<P>¤µ¤Ñ¡A´X¥G¤w¸g¨S¦³¤°»ò Unix ³¡¥óÁÙ¯d¦b GNU ¥ô°È¦Cªí¤¤ -- 
address@hidden@address@hidden@·~¨t²Îªº¦³¯q¤§ª«¡C</P>
-
-<P>§Y«K¬O´åÀ¸¤]³Q¥]¬A¦b¥ô°È¦Cªí¤W -- ¦Ó¥B¬O±q³Ìªì´N¶}©l¤F¡CUnix ¥]¬A´åÀ¸¡A©Ò¥H 
GNU address@hidden Unix address@hidden@¨t¦C¤£¦PºØÃþªº¥Î¤á¥i¯à·|³ßÅwªº´åÀ¸¡C</P>
-
-<H3>GNU ®w GPL</H3>
-
-<P>GNU C address@hidden GNU address@hidden 
copyleft¡A¥¦¤¹³\¨p¦³³nÅé¥i¥HÃì±µ¨ì¸Ó®w¡C¬°¤°»òÅý¦¹¦¨¬°¨Ò¥~¡H</P>
-
-<P>address@hidden@address@hidden@address@hidden C ®w©Î¥ô¦ó®w¨Ï¥Î 
address@hidden</P>
-
-<P>C address@hidden C ®w¡C¦]¦¹¡A¥u±N§Ú­Ìªº C 
®wµ¹¦Û¥Ñ³nÅé¥Î¨Ã¤£·|µ¹¦Û¥Ñ³nÅé±a¨Ó¥ô¦ó¦n³B -- ³o±N¥u·|ªý¤î¨Ï¥Î§Ú­Ìªº®w¡C</P>
-
-<P>address@hidden GNU ¨t²Î¤¤¡]³o¥]¬A GNU/Linux¡^¡AGNU C address@hidden C 
®w¡C©Ò¥H GNU C ®wªºµo¦æ±ø´Ú¨M©w¤F¥¦¬O§_¥i¥H¥Î¨Ó¬° GNU address@hidden GNU 
¨t²Î¤W¹B¦æ¨S¦³»P¹D¼w¬ÛÃöªº²z¥Ñ¡A¦ý¬O±q¾Ô²¤¤W¬Ý¡A¤£±µ¨ü¥¦­Ì¦ü¥G¬O§ó¦h¦aªýê¨Ï¥Î 
GNU ¨t²Î¡A¦Ó¤£¬O¹ªÀy¦Û¥ÑÀ³¥Îªº¶}µo¡C</P>
-
-<P>³o´N¬O¬°¤°»ò¨Ï¥Î LGPL ¹ï©ó C 
address@hidden@address@hidden@address@hidden@®É¡A¨º»ò±N¨ä¥Î GPL 
address@hidden@­ÓÀu¶Õ¡C</P>
-
-<P>address@hidden GNU Readline address@hidden BASH ´£¨Ñ©R¥O¦æ½s¿èªº®w¡C 
Readline ¬O¥Î´¶³qªº GNU GPL µo¦æªº¡A¦Ó¤£¬O LGPL¡C³o¥i¯à¯uªº´î¤Ö¤F Readline 
address@hidden Readline¡A¨º¬O¹ï©óªÀ¸sªº¯u¥¿¦¬Àò¡C</P>
-
-<P>address@hidden GPL address@hidden@address@hidden</P>
-
-<H3>§ìÄo¡H</H3>
-
-<P>Eric Raymond address@hidden@­Ó¶}µoªÌªº­Ó¤HÄo¡C¡v¤]³\¨º¦³®É·|µo¥Í¡A¦ý¬O³\¦h 
GNU address@hidden@address@hidden@address@hidden</P>
-
-<P>¨Ò¦p¡A§Ú­Ì¶}µo¤F GNU C address@hidden Unix address@hidden C 
®w¡A¶}µo¤FBourne-Again Shell¡]bash) address@hidden Unix address@hidden GNU tar 
address@hidden Unix address@hidden tar µ{¦¡¡C¹ï§Ú¦Û¤vªºµ{¦¡¤]¦P¼Ë¬O¦p¦¹ -- GNU 
C ½sĶ¾¹¡AGNU Emacs¡AGDB ©M GNU Make¡C</P>
-
-<P>address@hidden GNU µ{¦¡³Q¶}µo¨ÓÀ³¥I¹ï§Ú­Ì¦Û¥Ñªº¯S©w«Â¯Ù¡C¦]¦Ó¡A§Ú­Ì¶}µo¤F 
gzip ¨Ó¥N´À¦] LZW ±M§Q¦Ó¨ÏªÀ¸s¥¢¥hªº Compress µ{¦¡¡C§Ú­Ìµo²{¤H­Ì¶}µo 
LessTif¡Aªñ´Á§ó¶}©l¤F GNOME ©M address@hidden GNU Privacy Guard 
¥H¥N´À¬y¦æªº«D¦Û¥Ñ¥[±K³nÅé¡C</P>
-
-<P>address@hidden</P>
-
-<H3>¥¼¹w®Æªº¶}µo</H3>
-
-<P>¦b GNU ­pµe­è¶}©l®É¡A§Ú³]·Q§Ú­Ì±N¶}µo¾ã­Ó GNU 
¨t²Î¡AµM«á§¹¾ã¦a´²§G¡C¦ý¨º¨Ã¤£¬O¥¦¦p¦óµo¥Íªº¡C</P>
-
-<P>¥Ñ©ó GNU ¨t²Îªº¨C­Ó³¡¥ó³£¬O¦b Unix address@hidden@­Ó§¹³Æªº GNU 
¨t²Î¹ê»Ú¦s¦b¤§«e¡A¨C­Ó³¡¥ó³£¥i¥H¦b Unix 
¨t²Î¤W¹B¦æ¡C³o¨Çµ{¦¡¦³ªºÅܱo¬y¦æ¡A¨Ï¥ÎªÌ¶}©lÂX¥R¨Ã¥B²¾´Ó¥¦­Ì¨ì³\¦h¤£¬Û®eªº Unix 
ª©¥»¡A¦³®É¤]·|²¾´Ó¨ì¨ä¥¦ªº¨t²Î¡C</P>
-
-<P>³o­Ó¹Lµ{¨Ï±o³o¨Çµ{¦¡§ó¥[±j¦Ó¦³¤O¡A¨Ã¥B§l¤Þ¤F GNU address@hidden GNU 
address@hidden@address@hidden|ªº³¡¥ó¤W¡C</P>
-
-<H3>GNU Hurd</H3>
-
-<P>address@hidden GNU 
address@hidden|ªº³¡¥ó¬O¨ä¤º®Ö¡C§Ú­Ì¤w¸g¨M©w±N¤º®Ö¹ê²{¦¨¦b Mach 
¤§¤W¹B¦æªº¦øªA¾¹¶iµ{¶°¦X¡C Mach ¬O¦b Carnegie Melon 
¤j¾Ç¡A«á¦bµS¥L¤j¾Ç¶}µoªº·L®Ö¡F GNU HURD address@hidden Mach 
¤§¤Wªº¦øªA¾¹¶°¦X¡]©ÎºÙ¬°¡u¨¤°¨Ã~¸s¡v¡^¡A¨Ã¥B­t³d Unix 
¤º®Öªº¦UºØ¥ô°È¡C¶}µoªº±Ò°Ê¥Ñ©ó§Ú­Ìµ¥«Ý Mach address@hidden</P>
-
-<P>address@hidden@address@hidden@­Ó·½½X¼h¦¸ªº½Õ¸Õ°£¿ù¾¹ªº±ø¥ó¤U½Õ¸Õ°£¿ù¤º®Öµ{¦¡¡C¦b
 Mach address@hidden GDB ¨Ó½Õ¸Õ°£¿ù HURD 
¦øªA¾¹¡C¦ý¬O³oªá¤F«Üªø®É¶¡¤~¦¨¬°¥i¯à¡A¦Ó¬Û¤¬µo°e°T®§ªº¦h½uµ{¦øªA¾¹³Ì«á¤´ÂÂÃø¥H¶i¦æ½Õ¸Õ°£¿ù¡C³o¨Ï±oÅý
 HURD address@hidden</P>
-
-<H3>Alix</H3>
-
-<P>GNU ¤º®Ö­ì¥»¨Ã¤£³]·Q³QºÙ§@ HURD¡C¥¦ªº­ì¦W¬O Alix -- address@hidden Unix 
address@hidden Unix address@hidden@address@hidden@­Ó¦W¥s Alix 
ªº¤º®Ö¨Ï¦oÅå©_¡C</P>
-
-<P>¨Æ±¡¨Ã¨S¦³«O«ù¤£ÅÜ¡C Michael Bushnell ¡]²{¦bªº 
Thomas¡^¡A¤º®Öªº¥D­n¶}µoªÌ¡AÄÝ·N HURD ³o­Ó¦W¦r¡A¨Ã­«·s©w¸q Alix 
¨Ó«ü¤º®Ö¤¤ªº¬Y­Ó¯S©w³¡¤À -- ¸Ó³¡¤À´N¬O®·Àò¨t²Î©I¥s¨Ã¥Hµo°e°T®§µ¹ HURD 
¦øªA¾¹¨Ó³B²z¥¦­Ì¡C</P>
-
-<P>³Ì²×¡A Alix ©M§Ú¤À¤â¤F¡A¦o§ï¤F¦W¦r¡F»P¦¹µLÃö¦a¡A HURD ³]­p³Q§ïÅܦ]¦Ó¨Ï±o C 
®w±o¥Hª½±µµo°e®ø®§µ¹¦øªA¾¹¡A³o¾É­P Alix ³¡¥ó±q³]­p¤¤®ø¥¢¡C</P>
-
-<P>address@hidden HURD ·½½X¤¤°¸µM¨£¨ì Alix address@hidden</P>
-
-<H3>Linux ©M GNU/Linux</H3>
-
-<P>GNU Hurd address@hidden@­Ó¤º®Ö¤w¸g¥i¥H¨ú±o¡C¦b address@hidden@¦~¡ALinus 
Torvalds address@hidden Unix ¬Û®eªº¤º®Ö¨ÃºÙ¤§¬° Linux address@hidden Linux 
»P¤£¬O«D±`§¹¾ãªº GNU address@hidden@address@hidden@¡C¡^¥Ñ©ó Linux 
address@hidden GNU ¨t²Îªºª©¥»¡C</P>
-
-<P>§Ú­ÌºÙ¦¹ª©¥»ªº¨t²Î¬° GNU/Linux ¡A¥Hªí¹F¥¦¬O GNU ¨t²Î©M¥H Linux 
address@hidden</P>
-
-<H3>§Ú­Ì±N¨Óªº¬D¾Ô</H3>
-
-<P>address@hidden|address@hidden|»Ý­n¨ººØ¤H­Ì¦b·í¥L­Ì¬Ã±¤¥L­Ìªº¦Û¥Ñ¡A¨Ã¥B¤£Åý¥ô¦ó¤H±N¨ä¹Ü¨«®É©ÒÅã¥Üªº¨M¤ß¡C</P>
-
-<P>¤UÃä¥|­Ó¬q¸¨°Q½×³o¨Ç¬D¾Ô¡C</P>
-
-<H3>¯µ±KªºµwÅé</H3>
-
-<P>µwÅé¼t°Ó·U¥[¶É¦V©ó¹ïµwÅé³W½d«O±K¡C³o¨Ï±o½s¼gÅý Linux ©M XFree86 
address@hidden|¦b©ú¤Ñ¥¢¥h¥¦­Ì¡C</P>
-
-<P>address@hidden</P>
-
-<P>address@hidden|address@hidden -- 
address@hidden@­Ó­ì«h°ÝÃDªº°í©T«H©À¡A«h«D¦Û¥ÑÅX°Êµ{¦¡´N¬OµLªk§Ô¨üªº¡C§Ú­Ì¤¤ªº¤j¦h¼Æ¤H·|address@hidden</P>
-
-<H3>«D¦Û¥Ñ®w</H3>
-
-<P>address@hidden@address@hidden@address@hidden <STRONG>¹B¦æ</STRONG> 
¡C¡^§óÁV¿|address@hidden</P>
-
-<P>address@hidden Motif address@hidden Motif ¥H«á·|address@hidden GNU 
­pµe¥H¨âºØ¤è¦¡°µ¤F¦^À³¡G³q¹L½Ð¨D­Ó§Oªº¦Û¥Ñ³nÅé­pµe¦b¤ä«ù Motif ªº¦P®É¤]¤ä«ù¦Û¥Ñ 
X address@hidden Motif address@hidden Hungry µ{¦¡­û­Ì¶}µoªº address@hidden 
Motif À³¥Îµ{¦¡¡C</P>
-
-<P>address@hidden@address@hidden GUI ¤u¨ã½c®w¡A¥s°µ Qt ¡A³Q¥Î¦b KDE 
address@hidden</P>
-
-<P>¦Û¥Ñ GNU/Linux ¨t²ÎµLªk§Q¥Î address@hidden GNU/Linux ¨t²Îµo¦æ°Ó±N KDE 
¥[¤J¨ì¥L­Ìªº¨t²Î¤¤ -- address@hidden KDE ¤p²Õ¿n·¥¦a¹ªÀy§ó¦hªºµ{¦¡­û­Ì¨Ï¥Î Qt 
¡A¦¨¦Ê¸Uªº·s¡uLinux address@hidden|¡C</P>
-
-<P>address@hidden GNOME ©M Harmony ¡C</P>
-
-<P>GNOME §Y GNU ºô¸ôª«¥ó¼Ò«¬Àô¹Ò¡]Network Object Model Environment¡^¡A¬O GNU 
address@hidden Miguel de Icaza ¦b Red Hat Software ¤ä«ù¤U¶}µo¡AGNOME 
¶}©l´£¨ÑÃþ¦üªº®à­±¤u¨ã¡A±Æ¥~¦a¥u¨Ï¥Î¦Û¥Ñ³nÅé¡C¥¦¤]¦³§Þ³N¤WªºÀu¶Õ¡A¦p¤ä«ù¦hºØ»y¨¥¡A¦Ó¤£¶È¶È¬O
 C++¡C¦ý¬O¥¦ªº¥D­n¥Øªº¬O¦Û¥Ñ¡G¤£»Ý­n¨Ï¥Î¥ô¦ó«D¦Û¥Ñ³nÅé¡C</P>
-
-<P>Harmony address@hidden Qt ªº±¡ªp¤U¤]¦³¥i¯à¹B¦æ KDE ³nÅé¡C</P>
-
-<P>address@hidden@¤ë¡A Qt address@hidden|¨Ï±o Qt 
¦¨¬°¦Û¥Ñ³nÅé¡CÁöµM¨S¿ìªk½T«H¡A¦ý¬O§Ú·Q³oÀ³¸Ó³¡¤ÀÂk¥\©óªÀ¸s¹ï©ó Qt 
¬O«D¦Û¥Ñ³nÅé®É©Ò³y¦¨ªº°ÝÃDªº°í©w¦^À³¡C¡]·sªº³\¥iÃÒ¬J¤£¤è«K¤]¤£¤½¥¿¡A©Ò¥H¤´Â­ȱo¥hÁקK¨Ï¥Î
 Qt ¡C¡^</P>
-
-<P>[«á°O¡G¦b¤G¡³¡³¡³¦~¤E¤ë¡A Qt ¥H GNU GPL 
¥[¥Hµo¦æ¡A¦]¦¹¹ê»Ú¤W¸Ñ¨M¤F³o­Ó°ÝÃD]</P>
-
-<P>address@hidden|address@hidden</P>
-
-<H3>³nÅé±M§Q</H3>
-
-<P>§Ú­Ì­±Á{ªº³ÌÃa«Â¯Ù¨Ó¦Û©ó³nÅé±M§Q¡A¥¦¥i¥H¹ï¦Û¥Ñ³nÅ骺ºtºâªk©M¥\¯à¥[¥H­­¨î¦h¹F¤G¤Q¦~¡C
 LZW address@hidden GIFs address@hidden@­Ó¥Î¨Ó²£¥Í MP3 
À£ÁY­µ®Äªº¦Û¥Ñ³nÅéµ{¦¡¥Ñ©ó¾á¤ß±M§Q©x¥q«Â¯Ù¦Ó³Q±qµo¦æ¤¤®³±¼¡C</P>
-
-<P>address@hidden@address@hidden@address@hidden|­¢¨Ï©Ò¦³ªº¦Û¥Ñ³nÅé¯Ê¤Ö¬Y¨Ç¥Î¤á·Q­nªº¥\¯à¡C·í³oµo¥Í®É§Ú­Ì¥i¥H°µ¨Ç¤°»ò©O¡H</P>
-
-<P>address@hidden@address@hidden@¨Ç¦Û¥Ñ³nÅ骺¥i¾a©Ê©M¯à¤O¬O¦³¥Îªº¡A¦ý§Ú­Ì¥²©w¤£¯à°±¦b¨º¨à¡C§Ú­Ì¥²¶·±´°Q¦Û¥Ñ©M­ì«h¡C</P>
-
-<H3>¦Û¥Ñ¤åÀÉ</H3>
-
-<P>address@hidden -- address@hidden@address@hidden</P>
-
-<P>¦Û¥Ñ¤åÀɸê®Æ¡A¦p¦P¦Û¥Ñ³nÅé¡A¬O¦Û¥Ñ°ÝÃD¡A¤£¬O»ù®æ°ÝÃD¡C¦Û¥Ñ¤â¥Uªº¼Ð·Ç´X¥G»P¦Û¥Ñ³nÅ駹¥þ¬Û¦P¡G¥¦¬O¬°¤Fµ¹¤©©Ò¦³¥Î¤á½T©wªº¦Û¥Ñ¡C­«·sµo¦æ¡]¥]¬A°Ó·~¾P°â¡^¥²¶·³Q³\¥i¡A¤£½×¬O½u¤WÁÙ¬O®Ñ­±§Î¦¡¡A¦]¦Ó¤â¥U¯à°÷¦ñÀH¨C­Óµ{¦¡ªº¨C­Ó«þ¨©¡C</P>
-
-<P>address@hidden@­Ó´¶³q³W«h¡A§Ú¤£¬Û«H¤H­Ì¾Ö¦³­×§ï©Ò¦³ºØÃþ¤å³¹©M®ÑÄyªº³\¥i¬O¦ÜÃöºò­nªº¡C¨Ò¦p¡A§Ú¤£»{¬°§A©Î§ÚÀ³¸Ó³Q­¢µ¹¤©­×§ï¹³¥»¤å³o¼Ë´y­z§Ú­Ì¦æ¬°©M§Ú­ÌÆ[ÂI¤å³¹ªº³\¥iÅv¡C</P>
-
-<P>address@hidden -- address@hidden@address@hidden</P>
-
-<P>¥[½Ñ¦b­×§ïÀ³¸Ó¦p¦ó§¹¦¨ªº¬Y¨Ç­­¨î¨Ã¤£·|address@hidden@ªÌ¦Cªíªº­n¨D¬O¥i¥Hªº¡C­n¨D­×§ï«áªºª©¥»¥]¬A¥¦­Ì­×§ïª©¥»ªºÁn©ú¤]¬O¨S¦³°ÝÃDªº¡A§Y¨Ï¦³¾ã¸`¨S¦³§R°£©Î­×§ï¡A¥u­n³o¨Ç¸`¯A¤Î«D§Þ³N¥DÃD¡C³o¨ÇÃþ«¬ªº­­¨î¤£¬O°ÝÃD¡A¦]¬°¥¦­Ì¤£ªý¤îºÉ¾µ{¦¡­û­×§ï¤â¥U¥H¾AÀ³­×§ï¹Lªºµ{¦¡¡C´«ºØ»¡ªk¡A¥¦­Ì¤£§«Ãª¦Û¥Ñ³nÅéªÀ¸s§¹¥þ§Q¥Î¸Ó¤â¥U¡C</P>
-
-<P>¾¨ºÞ¦p¦¹¡A¥²¶·¦³¥i¯à­×§ï¤â¥Uªº©Ò¦³ *§Þ³N* address@hidden</P>
-
-<P>address@hidden</P>
-
-<H3>§Ú­Ì¥²¶·½Í½×¦Û¥Ñ</H3>
-
-<P>¦ô­p·í¤µ¦³¼Æ¤d¸Uªº¥Î¤á¨Ï¥Î½Ñ¦p Debian GNU/Linux ©M Red Hat Linux ªº 
GNU/Linux 
¨t²Î¡C¦Û¥Ñ³nÅé¤w¸gµo®i¨ì¤F³o¼Ë¹ê¥ÎªºÀu¶Õ¡A¨Ï±o¥Î¤á¯Âºé¬°¤F¹ê¥Î­ì¦]¦Ó»E¶°¨ì¥¦¨­Ãä¡C</P>
-
-<P>³oºØ²{¶Hªº¦nµ²ªG¬O©úÅ㪺¡G§ó¦h¶}µo¦Û¥Ñ³nÅ骺¿³½ì¡A§ó¦h¦Û¥Ñ³nÅé°Ó·~ªº¥Î¤á¡A¥H¤Î§ó¦h¹ªÀy¤½¥q¶}µo°Ó·~¦Û¥Ñ³nÅé¦Ó¤£¬O¨p¦³³nÅé²£«~ªº¯à¤O¡C</P>
-
-<P>¦ý¬O¹ï³nÅ骺¿³½ì¼Wªø§Ö©ó¹ï¨ä©Ò°ò©óªº­õ¾Çªº¤F¸Ñ¡A³o±a¨Ó¤F³Â·Ð¡C§Ú­Ì­±¹ï¤WÃä´y­zªº¬D¾Ô©M«Â¯Ùªº¯à¤O¨Ì¿à©ó°í¨M¥D±i¦Û¥Ñªº·N§Ó¡C¬°¤F½T©w§Ú­ÌªºªÀ¸s¾Ö¦³³o­Ó·N§Ó¡A§Ú­Ì»Ý­n¦b·sªº¥Î¤á¨Ó¨ìªÀ¸s®É¦V¥L­Ì¶Ç¼½³o¼Ëªº«ä·Q¡C</P>
-
-<P>¦ý¬O§Ú­Ì¥¿¦b³oÂI¤W¥¢±Ñ¡G§l¤Þ·s¥Î¤á¥[¤JªÀ¸sªº§V¤O¤j¤j¶W¶V¤F±Ð¨|¥L­Ì¦¨¬°§Ú­ÌªÀ¸sªº¦n¤½¥Áªº§V¤O¡C§Ú­Ì»Ý­n°µ³o¨â¥ó¨Æ¡A¦Ó¥B§Ú­Ì¤]»Ý­n«O«ù³o¨â­Ó§V¤Oªº¥­¿Å¡C</P>
-
-<H3>"¶}©ñ·½½X"</H3>
-
-<P>address@hidden@³¡¤À¨M©w°±¤î¨Ï¥Î³N»y¡u¦Û¥Ñ³nÅé¡v¨Ã§ï¬°»¡¡u¶}©ñ·½½X³nÅé¡v®É¡A±Ð¾É·s¥Î¤á¦³Ãö¦Û¥ÑªºÆ[©ÀÅܱo§ó¥[§xÃø¡C</P>
-
-<P>address@hidden -- address@hidden GNU address@hidden@address@hidden</P>
-
-<P>address@hidden -- ¥¦­Ì³Q»P GNU/Linux address@hidden@­Ó Motif ©Î Qt 
¥X²{®É¡A³o¨ÇÂø»x±Nĵ§iµ{¦¡­û­Ì»·Â÷¥¦ÁÙ¬O¬°¥¦­Ìµn¸ü¼s§i©O¡H</P>
-
-<P>address@hidden@¼Ë¡A¥¦¬O¦³¯qªº¡C¦ý¬O¬°¤Fűo¥L­Ìªº¤ä«ù¦Ó¤Ö»¡¦Û¥Ñ©M­ì«h¥i¯à·l¥¢ºG­«¡F¥¦¨Ï±o«e­z¡u¶W¶V©M¤½¥Á·NÃѱШ|¡v¤§¶¡ªº¥¢¿ÅÅܱo·U¥[ÁV¿|¡C</P>
-
-<P>address@hidden 
­pµeÄ~Äò¨Ï¥Î¡u¦Û¥Ñ³nÅé¡v³o­Ó³N»y¡A¨Óªí¹F¤£¶È¶È¬O§Þ³N¡A¦Û¥Ñ¤]¬O­«­nªº«ä·Q¡C</P>
-
-<H3>¹Á¸Õ¡I</H3>
-
-<P>Yoda ¤j®vªº­õ¾Ç¡u¨S¦³¡y¹Á¸Õ¡z¡v¡]There is no 
address@hidden@¡C¦ý¬OµL½×¦p¦ó§Ú¹Á¸Õ¤F¡A¦]¬°¦b¼Ä¤H©M§Úªº«°¥«¤§¶¡°£¤F§Ú¤§¥~¨S¦³§O¤H¡C¥O§Ú¦Û¤vÅå³Yªº¬O¡A¦³®É§Ú¦¨¥\¤F¡C</P>
-
-<P>address@hidden@³õ¾Ô°«°µ¦n·Ç³Æ¡CÀHµÛ®É¶¡ªº®ø³u¡A§Ú¤w¸g¾Ç·|´M§ä«Â¯Ù¨Ã§â§Ú¦Û¤v©ñ¦b¥¦­Ì©M§Úªº«°¥«¤§¶¡¡A¥l³ê¨ä¥LÀb«È¨Ó¥[¤J§Ú¡C</P>
-
-<P>address@hidden@address@hidden@ºØ¦w¼¢©M¼Ö½ì¡A§Ú·NÃѨì¡A¥Ø«e¡A³o­Ó«°¥«¤]³\¯à­Æ¦s¡C¦ý¬O¦MÀI¨C¦~³£Åܱo§ó¤j¡A¨Ã¥B²{¦b
 Microsoft address@hidden</P>
-
-<HR>
-[
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-  <A HREF="/gnu/thegnuproject.cs.html">±¶§J¤å</A>
-| <A HREF="/gnu/thegnuproject.zh-cn.html">²Å餤¤å</A>
-| <A HREF="/gnu/thegnuproject.zh-tw.html">ÁcÅ餤¤å</A>
-| <A HREF="/gnu/thegnuproject.en.html">­^¤å</A>
-| <A HREF="/gnu/thegnuproject.fr.html">ªk¤å</A>
-| <A HREF="/gnu/thegnuproject.id.html">¦L«×¥§¦è¨È¤å</A>
-| <A HREF="/gnu/thegnuproject.it.html">¸q¤j§Q¤å</A>
-| <A HREF="/gnu/thegnuproject.ko.html">Áú¤å</A>
-| <A HREF="/gnu/thegnuproject.ru.html">«Xù´µ¤å</A>
-| <A HREF="/gnu/thegnuproject.es.html">¦è¯Z¤ú¤å</A>
-<!-- Please keep this list alphabetical -->
-<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
-]
-
-<P><a href="/home.html">ªð¦^ GNU ­º­¶</a> ¡C
-<P>½Ð±N¦³Ãö ¦Û¥Ñ³nÅé°òª÷·| »P GNU ªº ¬d¸ß »P °ÝÃD¡]¥H­^¤å¡^°e¨ì <a 
href="mailto:address@hidden";><em>address@hidden</em></a> ¡F<BR>
-©Î¡]¥H¤¤¤å¡^°e¨ì <a href="mailto:address@hidden";><em>address@hidden</em></a> 
¡A<BR>
-±z¤]¥i¥H¨Ï¥Î <a href="/contact/">¨ä¥¦¤èªkÁpô</a> ¦Û¥Ñ³nÅé°òª÷·|¡C
-<P>½Ð±N¦³Ãö GNU ¤¤¤å½Ķ¤p²Õ ªº·N¨£¡]¥H­^¤å©Î¤¤¤å¡^°e¨ì <a 
href="mailto:address@hidden";><em>address@hidden</em></a> ¡A <BR>
-¦³Ãö GNU ¤¤¤åºô­¶ ªº·N¨£¡]¥H­^¤å©Î¤¤¤å¡^°e¨ì <a 
href="mailto:address@hidden";><em>address@hidden</em></a> ¡A<BR>
-¦³Ãö ­ì©l­^¤åºô­¶ ªº·N¨£¡]¥H­^¤å¡^°e¨ì 
-<a href="mailto:address@hidden";><em>address@hidden</em></a>
- ¡A<BR>¨ä¥¦°ÝÃD«h¡]¥H¤¤¤å¡^°e¨ì <a 
href="mailto:address@hidden";><em>address@hidden</em></a> ¡C
-<P>Copyright (C) 1998, 2001 Richard Stallman.
-<P>Permission is granted to make and distribute verbatim copies of this 
<P>transcript as long as the copyright and this permission notice appear.
-¤¹³\¦b¤£ÅܧóÀɮפº®eªº«e´£¤U¥Zµn¥»¤å°Æ¥»¦b¥ô¦ó§Î¦¡ªº´CÅ餤¡A¦ý»Ý«O¯dª©Åv«Å§i©M¦¹Án©ú¡C
-<P>½Ķ¡G¦¶ ¼y¤E ³Õ¤h¡C
-<BR>ÅçÃÒ¡G°¨ ³·µÓ¡B¼B ¬L§»¡C
-<P>address@hidden|address@hidden@ªÌ¡C
-<!--
-<P>address@hidden ¼y¤E¡B§õ ·¥¥ú¡]«ö©m¤óµ§¹º±Æ¦C¡^¡C
-<BR>ÅçÃÒŪªÌ¡G¸ë ¬P«È¡B°¨ ³·µÓ¡B¼B ¬L§»¡C
--->
-<P>
-Updated:
-<!-- timestamp start -->
-$Date: 2013/10/24 11:32:27 $ $Author: ineiev $
 <!-- timestamp end -->
-<HR>
-</BODY>
-</HTML>
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/thegnuproject.zh-tw.po
===================================================================
RCS file: /web/www/www/gnu/po/thegnuproject.zh-tw.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/thegnuproject.zh-tw.po   5 Dec 2017 07:07:30 -0000       1.1
+++ po/thegnuproject.zh-tw.po   5 Dec 2017 07:29:15 -0000       1.2
@@ -8,14 +8,14 @@
 "Project-Id-Version: thegnuproject.html\n"
 "POT-Creation-Date: 2017-06-25 13:26+0000\n"
 "PO-Revision-Date: 2017-12-05 15:04+0800\n"
+"Last-Translator: Cheng-Chia Tseng <address@hidden>\n"
 "Language-Team: Chinese <address@hidden>\n"
+"Language: zh_TW\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 "X-Generator: Poedit 2.0.3\n"
-"Last-Translator: Cheng-Chia Tseng <address@hidden>\n"
 "Plural-Forms: nplurals=1; plural=0;\n"
-"Language: zh_TW\n"
 
 #. type: Content of: <title>
 msgid "About the GNU Project - GNU Project - Free Software Foundation"
@@ -46,10 +46,10 @@
 "that the ideas of the free software movement would not be entirely absent "
 "from that book."
 msgstr ""
-"文章原載於 <em>Open Sources</em> 一書中。理查・史托曼先生 
(Richard "
-"Stallman)<a href=\"/philosophy/open-source-misses-the-point.html\"> 永遠
不是"
-"「開源」或「Open Source」的支持者
</a>,但基於不願讓自由軟體運動的想法在該書中"
-"完全缺席之故而寫下本文。"
+"文章原載於 <em>Open Sources</em> 一書中。理查・史托曼先生 
(Richard Stallman)"
+"<a href=\"/philosophy/open-source-misses-the-point.html\"> 永遠
不是「開源」或"
+"「Open Source」的支持者
</a>,但基於不願讓自由軟體運動的想法在該書中完全缺席之"
+"故而寫下本文。"
 
 #. type: Content of: <blockquote><p>
 msgid ""
@@ -1781,9 +1781,8 @@
 "developed such practical advantages that users are flocking to it for purely "
 "practical reasons."
 msgstr ""
-"今日估計約有上千萬人使用 GNU/Linux 系統,例如 Debian 
GNU/Linux 和 Red "
-"Hat「Linux」。自由軟體已發展出實務上的優勢,讓使用者
們純粹基於實務因素群集至"
-"此。"
+"今日估計約有上千萬人使用 GNU/Linux 系統,例如 Debian 
GNU/Linux 和 Red Hat"
+"「Linux」。自由軟體已發展出實務上的優勢,讓使用者
們純粹基於實務因素群集至此。"
 
 #. type: Content of: <p>
 msgid ""

Index: po/thegnuproject.zh-tw-en.html
===================================================================
RCS file: po/thegnuproject.zh-tw-en.html
diff -N po/thegnuproject.zh-tw-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/thegnuproject.zh-tw-en.html      5 Dec 2017 07:29:15 -0000       1.1
@@ -0,0 +1,1067 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>About the GNU Project
+- GNU Project - Free Software Foundation</title>
+<meta http-equiv="Keywords" content="GNU, GNU Project, FSF, Free Software, 
Free Software Foundation, History" />
+<!--#include virtual="/gnu/po/thegnuproject.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>The GNU Project</h2>
+
+<p>
+by <a href="http://www.stallman.org/";><strong>Richard Stallman</strong></a></p>
+
+<blockquote>
+<p>
+Originally published in the book <em>Open Sources</em>.  Richard
+Stallman was <a href="/philosophy/open-source-misses-the-point.html">
+never a supporter of &ldquo;open source&rdquo;</a>, but contributed
+this article so that the ideas of the free software movement would not
+be entirely absent from that book.
+</p>
+<p>
+Why it is even more important than ever
+<a href="/philosophy/free-software-even-more-important.html">to insist
+that the software we use be free</a>.
+</p>
+</blockquote>
+
+<h3>The first software-sharing community</h3>
+<p>
+When I started working at the 
+<acronym title="Massachusetts Institute of Technology">MIT</acronym>
+Artificial Intelligence Lab in 1971, I became part of a
+software-sharing community that had existed for many years.  Sharing
+of software was not limited to our particular community; it is as old
+as computers, just as sharing of recipes is as old as cooking.  But we
+did it more than most.</p>
+<p>
+The AI Lab used a timesharing operating system called
+<acronym title="Incompatible Timesharing System">ITS</acronym> (the
+Incompatible Timesharing System) that the lab's staff hackers (1) had
+designed and written in assembler language for the Digital
+<acronym title="Programmed Data Processor">PDP</acronym>-10, one of
+the large computers of the era.  As a member of this community, an AI
+Lab staff system hacker, my job was to improve this system.</p>
+<p>
+We did not call our software &ldquo;free software&rdquo;, because that
+term did not yet exist; but that is what it was.  Whenever people from
+another university or a company wanted to port and use a program, we
+gladly let them.  If you saw someone using an unfamiliar and
+interesting program, you could always ask to see the source code, so
+that you could read it, change it, or cannibalize parts of it to make
+a new program.</p>
+<p>
+(1) The use of &ldquo;hacker&rdquo; to mean &ldquo;security
+breaker&rdquo; is a confusion on the part of the mass media.  We
+hackers refuse to recognize that meaning, and continue using the word
+to mean someone who loves to program, someone who enjoys playful
+cleverness, or the combination of the two.  See my
+article, <a href="http://stallman.org/articles/on-hacking.html";>On
+Hacking</a>.</p>
+
+<h3>The collapse of the community</h3>
+<p>
+The situation changed drastically in the early 1980s when Digital
+discontinued the PDP-10 series.  Its architecture, elegant and
+powerful in the 60s, could not extend naturally to the larger address
+spaces that were becoming feasible in the 80s.  This meant that nearly
+all of the programs composing ITS were obsolete.</p>
+<p>
+The AI Lab hacker community had already collapsed, not long before.
+In 1981, the spin-off company Symbolics had hired away nearly all of
+the hackers from the AI Lab, and the depopulated community was unable
+to maintain itself.  (The book Hackers, by Steve Levy, describes these
+events, as well as giving a clear picture of this community in its
+prime.)  When the AI Lab bought a new PDP-10 in 1982, its
+administrators decided to use Digital's nonfree timesharing system
+instead of ITS.</p>
+<p>
+The modern computers of the era, such as the VAX or the 68020, had
+their own operating systems, but none of them were free software: you
+had to sign a nondisclosure agreement even to get an executable copy.</p>
+<p>
+This meant that the first step in using a computer was to promise not
+to help your neighbor.  A cooperating community was forbidden.  The
+rule made by the owners of proprietary software was, &ldquo;If you
+share with your neighbor, you are a pirate.  If you want any changes,
+beg us to make them.&rdquo;</p>
+<p>
+The idea that the proprietary software social system&mdash;the system
+that says you are not allowed to share or change software&mdash;is
+antisocial, that it is unethical, that it is simply wrong, may come as
+a surprise to some readers.  But what else could we say about a system
+based on dividing the public and keeping users helpless?  Readers who
+find the idea surprising may have taken the proprietary software
+social system as a given, or judged it on the terms suggested by
+proprietary software businesses.  Software publishers have worked long
+and hard to convince people that there is only one way to look at the
+issue.</p>
+<p>
+When software publishers talk about &ldquo;enforcing&rdquo; their
+&ldquo;rights&rdquo; or &ldquo;stopping <a 
href="/philosophy/words-to-avoid.html#Piracy">piracy</a>&rdquo;, what they
+actually <em>say</em> is secondary.  The real message of these statements is
+in the unstated assumptions they take for granted, which the public is
+asked to accept without examination.  Let's therefore examine them.</p>
+<p>
+One assumption is that software companies have an unquestionable natural
+right to own software and thus have power over all its users.  (If
+this were a natural right, then no matter how much harm it does to the
+public, we could not object.)  Interestingly, the US Constitution and
+legal tradition reject this view; copyright is not a natural right,
+but an artificial government-imposed monopoly that limits the users'
+natural right to copy.</p>
+<p>
+Another unstated assumption is that the only important thing about
+software is what jobs it allows you to do&mdash;that we computer users
+should not care what kind of society we are allowed to have.</p>
+<p>
+A third assumption is that we would have no usable software (or would
+never have a program to do this or that particular job) if we did not
+offer a company power over the users of the program.  This assumption
+may have seemed plausible, before the free software movement
+demonstrated that we can make plenty of useful software without
+putting chains on it.</p>
+<p>
+If we decline to accept these assumptions, and judge these issues
+based on ordinary commonsense morality while placing the users first,
+we arrive at very different conclusions.  Computer users should be
+free to modify programs to fit their needs, and free to share
+software, because helping other people is the basis of society.</p>
+<p>
+There is no room here for an extensive statement of the reasoning
+behind this conclusion, so I refer the reader to the web pages
+<a href="/philosophy/why-free.html">
+http://www.gnu.org/philosophy/why-free.html</a> and
+<a href="/philosophy/free-software-even-more-important.html">
+http://www.gnu.org/philosophy/free-software-even-more-important.html</a>.
+</p>
+
+<h3>A stark moral choice</h3>
+<p>
+With my community gone, to continue as before was impossible.
+Instead, I faced a stark moral choice.</p>
+<p>
+The easy choice was to join the proprietary software world, signing
+nondisclosure agreements and promising not to help my fellow hacker.
+Most likely I would also be developing software that was released
+under nondisclosure agreements, thus adding to the pressure on other
+people to betray their fellows too.</p>
+<p>
+I could have made money this way, and perhaps amused myself writing
+code.  But I knew that at the end of my career, I would look back on
+years of building walls to divide people, and feel I had spent my life
+making the world a worse place.</p>
+<p>
+I had already experienced being on the receiving end of a
+nondisclosure agreement, when someone refused to give me and the MIT
+AI Lab the source code for the control program for our printer.  (The
+lack of certain features in this program made use of the printer
+extremely frustrating.)  So I could not tell myself that nondisclosure
+agreements were innocent.  I was very angry when he refused to share
+with us; I could not turn around and do the same thing to everyone
+else.</p>
+<p>
+Another choice, straightforward but unpleasant, was to leave the
+computer field.  That way my skills would not be misused, but they
+would still be wasted.  I would not be culpable for dividing and
+restricting computer users, but it would happen nonetheless.</p>
+<p>
+So I looked for a way that a programmer could do something for the
+good.  I asked myself, was there a program or programs that I could
+write, so as to make a community possible once again?</p>
+<p>
+The answer was clear: what was needed first was an operating system.
+That is the crucial software for starting to use a computer.  With an
+operating system, you can do many things; without one, you cannot run
+the computer at all.  With a free operating system, we could again
+have a community of cooperating hackers&mdash;and invite anyone to join.
+And anyone would be able to use a computer without starting out by
+conspiring to deprive his or her friends.</p>
+<p>
+As an operating system developer, I had the right skills for this job.
+So even though I could not take success for granted, I realized that I
+was elected to do the job.  I chose to make the system compatible with
+Unix so that it would be portable, and so that Unix users could easily
+switch to it.  The name GNU was chosen, following a hacker tradition, as
+a recursive acronym for &ldquo;GNU's Not Unix.&rdquo; It is pronounced
+as <a href="/gnu/pronunciation.html">one syllable with a hard g</a>.</p>
+<p>
+An operating system does not mean just a kernel, barely enough to run
+other programs.  In the 1970s, every operating system worthy of the
+name included command processors, assemblers, compilers, interpreters,
+debuggers, text editors, mailers, and much more.  ITS had them,
+Multics had them, VMS had them, and Unix had them.  The GNU operating
+system would include them too.</p>
+<p>
+Later I heard these words, attributed to Hillel (1):</p>
+
+<blockquote><p>
+     If I am not for myself, who will be for me?<br />
+     If I am only for myself, what am I?<br />
+     If not now, when?
+</p></blockquote>
+<p>
+The decision to start the GNU Project was based on a similar spirit.</p>
+<p>
+(1) As an Atheist, I don't follow any religious leaders, but I
+sometimes find I admire something one of them has said.</p>
+
+<h3>Free as in freedom</h3>
+<p>
+The term &ldquo;free software&rdquo; is sometimes misunderstood&mdash;it
+has nothing to do with price.  It is about freedom.  Here, therefore,
+is the definition of free software.</p>
+
+<p>A program is free software, for you, a particular user, if:</p>
+
+<ul>
+  <li>You have the freedom to run the program as you wish, for any 
purpose.</li>
+
+  <li>You have the freedom to modify the program to suit your needs.
+     (To make this freedom effective in practice, you must have access
+     to the source code, since making changes in a program without
+     having the source code is exceedingly difficult.)</li>
+
+  <li>You have the freedom to redistribute copies, either gratis
+     or for a fee.</li>
+
+  <li>You have the freedom to distribute modified versions of the program,
+     so that the community can benefit from your improvements.</li>
+</ul>
+<p>
+Since &ldquo;free&rdquo; refers to freedom, not to price, there is no
+contradiction between selling copies and free software.  In fact, the
+freedom to sell copies is crucial: collections of free software sold
+on CD-ROMs are important for the community, and selling them is an
+important way to raise funds for free software development.
+Therefore, a program which people are not free to include on these
+collections is not free software.</p>
+<p>
+Because of the ambiguity of &ldquo;free&rdquo;, people have long
+looked for alternatives, but no one has found a better term.
+The English language has more words and nuances than any other, but it
+lacks a simple, unambiguous, word that means &ldquo;free&rdquo;, as in
+freedom&mdash;&ldquo;unfettered&rdquo; being the word that comes closest in
+meaning.  Such alternatives as &ldquo;liberated&rdquo;,
+&ldquo;freedom&rdquo;, and &ldquo;open&rdquo; have either the wrong
+meaning or some other disadvantage.</p>
+
+<h3>GNU software and the GNU system</h3>
+<p>
+Developing a whole system is a very large project.  To bring it into
+reach, I decided to adapt and use existing pieces of free software
+wherever that was possible.  For example, I decided at the very
+beginning to use TeX as the principal text formatter; a few years
+later, I decided to use the X Window System rather than writing
+another window system for GNU.</p>
+<p>
+Because of these decisions, and others like them,
+the GNU system is not the same as the collection of all
+GNU software.  The GNU system includes programs that are not GNU
+software, programs that were developed by other people and projects
+for their own purposes, but which we can use because they are free
+software.</p>
+
+<h3>Commencing the project</h3>
+<p>
+In January 1984 I quit my job at MIT and began writing GNU software.
+Leaving MIT was necessary so that MIT would not be able to interfere
+with distributing GNU as free software.  If I had remained on the
+staff, MIT could have claimed to own the work, and could have imposed
+their own distribution terms, or even turned the work into a
+proprietary software package.  I had no intention of doing a large
+amount of work only to see it become useless for its intended purpose:
+creating a new software-sharing community.</p>
+<p>
+However, Professor Winston, then the head of the MIT AI Lab, kindly
+invited me to keep using the lab's facilities.</p>
+
+<h3>The first steps</h3>
+<p>
+Shortly before beginning the GNU Project, I heard about the Free
+University Compiler Kit, also known as VUCK.  (The Dutch word for
+&ldquo;free&rdquo; is written with a <em>v</em>.)  This was a compiler
+designed to handle multiple languages, including C and Pascal, and to
+support multiple target machines.  I wrote to its author asking if GNU
+could use it.</p>
+<p>
+He responded derisively, stating that the university was free but the
+compiler was not.  I therefore decided that my first program for the
+GNU Project would be a multilanguage, multiplatform compiler.</p>
+<p>
+Hoping to avoid the need to write the whole compiler myself, I
+obtained the source code for the Pastel compiler, which was a
+multiplatform compiler developed at Lawrence Livermore Lab.  It
+supported, and was written in, an extended version of Pascal, designed
+to be a system-programming language.  I added a C front end, and began
+porting it to the Motorola 68000 computer.  But I had to give that
+up when I discovered that the compiler needed many megabytes of stack
+space, and the available 68000 Unix system would only allow 64k.</p>
+<p>
+I then realized that the Pastel compiler functioned by parsing the
+entire input file into a syntax tree, converting the whole syntax tree
+into a chain of &ldquo;instructions&rdquo;, and then generating the
+whole output file, without ever freeing any storage.  At this point, I
+concluded I would have to write a new compiler from scratch.  That new
+compiler is now known as <acronym title="GNU Compiler 
Collection">GCC</acronym>;
+none of the Pastel compiler is used in it, but I managed to adapt and
+use the C front end that I had written.  But that was some years
+later; first, I worked on GNU Emacs.</p>
+
+<h3>GNU Emacs</h3>
+<p>
+I began work on GNU Emacs in September 1984, and in early 1985 it was
+beginning to be usable.  This enabled me to begin using Unix systems
+to do editing; having no interest in learning to use vi or ed, I had
+done my editing on other kinds of machines until then.</p>
+<p>
+At this point, people began wanting to use GNU Emacs, which raised the
+question of how to distribute it.  Of course, I put it on the
+anonymous ftp server on the MIT computer that I used.  (This computer,
+prep.ai.mit.edu, thus became the principal GNU ftp distribution site;
+when it was decommissioned a few years later, we transferred the name
+to our new ftp server.)  But at that time, many of the interested
+people were not on the Internet and could not get a copy by ftp.  So
+the question was, what would I say to them?</p>
+<p>
+I could have said, &ldquo;Find a friend who is on the net and who will make
+a copy for you.&rdquo;  Or I could have done what I did with the original
+PDP-10 Emacs: tell them, &ldquo;Mail me a tape and a
+<acronym title="Self-addressed Stamped Envelope">SASE</acronym>, and I
+will mail it back with Emacs on it.&rdquo; But I had no job, and I was
+looking for ways to make money from free software.  So I announced
+that I would mail a tape to whoever wanted one, for a fee of $150.  In
+this way, I started a free software distribution business, the
+precursor of the companies that today distribute entire GNU/Linux
+system distributions.</p>
+
+<h3>Is a program free for every user?</h3>
+<p>
+If a program is free software when it leaves the hands of its author,
+this does not necessarily mean it will be free software for everyone
+who has a copy of it.  For example,
+<a href="/philosophy/categories.html#PublicDomainSoftware"> public domain
+software</a> (software that is not copyrighted) is free software; but
+anyone can make a proprietary modified version of it.  Likewise, many
+free programs are copyrighted but distributed under simple permissive
+licenses which allow proprietary modified versions.</p>
+<p>
+The paradigmatic example of this problem is the X Window System.
+Developed at MIT, and released as free software with a permissive
+license, it was soon adopted by various computer companies.  They
+added X to their proprietary Unix systems, in binary form only, and
+covered by the same nondisclosure agreement.  These copies of X were
+no more free software than Unix was.</p>
+<p>
+The developers of the X Window System did not consider this a
+problem&mdash;they expected and intended this to happen.  Their goal was
+not freedom, just &ldquo;success&rdquo;, defined as &ldquo;having many
+users.&rdquo; They did not care whether these users had freedom, only
+that they should be numerous.</p>
+<p>
+This led to a paradoxical situation where two different ways of
+counting the amount of freedom gave different answers to the question,
+&ldquo;Is this program free?&rdquo; If you judged based on the freedom
+provided by the distribution terms of the MIT release, you would say
+that X was free software.  But if you measured the freedom of the
+average user of X, you would have to say it was proprietary software.
+Most X users were running the proprietary versions that came with Unix
+systems, not the free version.</p>
+
+<h3>Copyleft and the GNU GPL</h3>
+<p>
+The goal of GNU was to give users freedom, not just to be popular.  So
+we needed to use distribution terms that would prevent GNU software
+from being turned into proprietary software.  The method we use is
+called &ldquo;copyleft&rdquo;.(1)</p>
+<p>
+Copyleft uses copyright law, but flips it over to serve the opposite
+of its usual purpose: instead of a means for restricting a program, it
+becomes a means for keeping the program free.</p>
+<p>
+The central idea of copyleft is that we give everyone permission to
+run the program, copy the program, modify the program, and distribute
+modified versions&mdash;but not permission to add restrictions of their
+own.  Thus, the crucial freedoms that define &ldquo;free
+software&rdquo; are guaranteed to everyone who has a copy; they become
+inalienable rights.</p>
+<p>
+For an effective copyleft, modified versions must also be free.  This
+ensures that work based on ours becomes available to our community if
+it is published.  When programmers who have jobs as programmers
+volunteer to improve GNU software, it is copyleft that prevents their
+employers from saying, &ldquo;You can't share those changes, because
+we are going to use them to make our proprietary version of the
+program.&rdquo;</p>
+<p>
+The requirement that changes must be free is essential if we want to
+ensure freedom for every user of the program.  The companies that
+privatized the X Window System usually made some changes to port it to
+their systems and hardware.  These changes were small compared with
+the great extent of X, but they were not trivial.  If making changes
+were an excuse to deny the users freedom, it would be easy for anyone
+to take advantage of the excuse.</p>
+<p>
+A related issue concerns combining a free program with nonfree code.
+Such a combination would inevitably be nonfree; whichever freedoms
+are lacking for the nonfree part would be lacking for the whole as
+well.  To permit such combinations would open a hole big enough to
+sink a ship.  Therefore, a crucial requirement for copyleft is to plug
+this hole: anything added to or combined with a copylefted program
+must be such that the larger combined version is also free and
+copylefted.</p>
+<p>
+The specific implementation of copyleft that we use for most GNU
+software is the GNU General Public License, or GNU GPL for short.  We
+have other kinds of copyleft that are used in specific circumstances.
+GNU manuals are copylefted also, but use a much simpler kind of
+copyleft, because the complexity of the GNU GPL is not necessary
+for manuals.(2)</p>
+<p>
+(1) In 1984 or 1985, Don Hopkins (a very imaginative fellow) mailed me
+a letter.  On the envelope he had written several amusing sayings,
+including this one: &ldquo;Copyleft&mdash;all rights reversed.&rdquo; I
+used the word &ldquo;copyleft&rdquo; to name the distribution concept
+I was developing at the time.</p>
+
+<p>
+(2) We now use the <a href="/licenses/fdl.html">GNU Free
+Documentation License</a> for documentation.</p>
+
+<h3>The Free Software Foundation</h3>
+
+<p>As interest in using Emacs was growing, other people became
+involved in the GNU project, and we decided that it was time to seek
+funding once again.  So in 1985 we created
+the <a href="http://www.fsf.org/";>Free Software Foundation</a> (FSF),
+a tax-exempt charity for free software development.  The
+<acronym title="Free Software Foundation">FSF</acronym> also took over
+the Emacs tape distribution business; later it extended this by adding
+other free software (both GNU and non-GNU) to the tape, and by selling
+free manuals as well.</p>
+
+<p>Most of the FSF's income used to come from sales of copies of free
+software and of other related services (CD-ROMs of source code,
+CD-ROMs with binaries, nicely printed manuals, all with the freedom to
+redistribute and modify), and Deluxe Distributions (distributions for
+which we built the whole collection of software for the customer's
+choice of platform).  Today the FSF
+still <a href="http://shop.fsf.org/";> sells manuals and other
+gear</a>, but it gets the bulk of its funding from members' dues.  You
+can join the FSF at <a href="http://fsf.org/join";>fsf.org</a>.</p>
+
+<p>Free Software Foundation employees have written and maintained a
+number of GNU software packages.  Two notable ones are the C library
+and the shell.  The GNU C library is what every program running on a
+GNU/Linux system uses to communicate with Linux.  It was developed by
+a member of the Free Software Foundation staff, Roland McGrath.  The
+shell used on most GNU/Linux systems is
+<acronym title="Bourne Again Shell">BASH</acronym>, the Bourne Again
+Shell(1), which was developed by FSF employee Brian Fox.</p>
+
+<p>We funded development of these programs because the GNU Project was
+not just about tools or a development environment.  Our goal was a
+complete operating system, and these programs were needed for that
+goal.</p>
+
+<p>(1) &ldquo;Bourne Again Shell&rdquo; is a play on the name
+&ldquo;Bourne Shell&rdquo;, which was the usual shell on Unix.</p>
+
+<h3>Free software support</h3>
+
+<p>The free software philosophy rejects a specific widespread business
+practice, but it is not against business.  When businesses respect the
+users' freedom, we wish them success.</p>
+
+<p>Selling copies of Emacs demonstrates one kind of free software
+business.  When the FSF took over that business, I needed another way
+to make a living.  I found it in selling services relating to the free
+software I had developed.  This included teaching, for subjects such
+as how to program GNU Emacs and how to customize GCC, and software
+development, mostly porting GCC to new platforms.</p>
+
+<p>Today each of these kinds of free software business is practiced by a
+number of corporations.  Some distribute free software collections on
+CD-ROM; others sell support at levels ranging from answering user
+questions, to fixing bugs, to adding major new features.  We are even
+beginning to see free software companies based on launching new free
+software products.</p>
+
+<p>Watch out, though&mdash;a number of companies that associate themselves
+with the term &ldquo;open source&rdquo; actually base their business
+on nonfree software that works with free software.  These are not
+free software companies, they are proprietary software companies whose
+products tempt users away from freedom.  They call these programs
+&ldquo;value-added packages&rdquo;, which shows the values they
+would like us to adopt: convenience above freedom.  If we value freedom
+more, we should call them &ldquo;freedom-subtracted&rdquo; packages.</p>
+
+<h3>Technical goals</h3>
+
+<p>The principal goal of GNU is to be free software.  Even if GNU had no
+technical advantage over Unix, it would have a social advantage,
+allowing users to cooperate, and an ethical advantage, respecting the
+user's freedom.</p>
+
+<p>But it was natural to apply the known standards of good practice to
+the work&mdash;for example, dynamically allocating data structures to avoid
+arbitrary fixed size limits, and handling all the possible 8-bit codes
+wherever that made sense.</p>
+
+<p>In addition, we rejected the Unix focus on small memory size, by
+deciding not to support 16-bit machines (it was clear that 32-bit
+machines would be the norm by the time the GNU system was finished),
+and to make no effort to reduce memory usage unless it exceeded a
+megabyte.  In programs for which handling very large files was not
+crucial, we encouraged programmers to read an entire input file into
+core, then scan its contents without having to worry about I/O.</p>
+
+<p>These decisions enabled many GNU programs to surpass their Unix
+counterparts in reliability and speed.</p>
+
+<h3>Donated computers</h3>
+
+<p>As the GNU Project's reputation grew, people began offering to donate
+machines running Unix to the project.  These were very useful, because
+the easiest way to develop components of GNU was to do it on a Unix
+system, and replace the components of that system one by one.  But
+they raised an ethical issue: whether it was right for us to have a
+copy of Unix at all.</p>
+
+<p>Unix was (and is) proprietary software, and the GNU Project's
+philosophy said that we should not use proprietary software.  But,
+applying the same reasoning that leads to the conclusion that violence
+in self defense is justified, I concluded that it was legitimate to
+use a proprietary package when that was crucial for developing a free
+replacement that would help others stop using the proprietary package.</p>
+
+<p>But, even if this was a justifiable evil, it was still an evil.  Today
+we no longer have any copies of Unix, because we have replaced them
+with free operating systems.  If we could not replace a machine's
+operating system with a free one, we replaced the machine instead.</p>
+
+<h3>The GNU Task List</h3>
+
+<p>As the GNU Project proceeded, and increasing numbers of system
+components were found or developed, eventually it became useful to
+make a list of the remaining gaps.  We used it to recruit developers
+to write the missing pieces.  This list became known as the GNU Task
+List.  In addition to missing Unix components, we listed various
+other useful software and documentation projects that, we thought, a
+truly complete system ought to have.</p>
+
+<p>Today (1), hardly any Unix components are left in the GNU Task
+List&mdash;those jobs had been done, aside from a few inessential
+ones.  But the list is full of projects that some might call
+&ldquo;applications&rdquo;.  Any program that appeals to more than a
+narrow class of users would be a useful thing to add to an operating
+system.</p>
+
+<p>Even games are included in the task list&mdash;and have been since the
+beginning.  Unix included games, so naturally GNU should too.  But
+compatibility was not an issue for games, so we did not follow the
+list of games that Unix had.  Instead, we listed a spectrum of
+different kinds of games that users might like.</p>
+
+<p>(1) That was written in 1998.  In 2009 we no longer maintain a long
+task list.  The community develops free software so fast that we can't
+even keep track of it all.  Instead, we have a list of High Priority
+Projects, a much shorter list of projects we really want to encourage
+people to write.</p>
+
+<h3>The GNU Library GPL</h3>
+
+<p>The GNU C library uses a special kind of copyleft called the GNU
+Library General Public License(1), which gives permission to link
+proprietary software with the library.  Why make this exception?</p>
+
+<p>It is not a matter of principle; there is no principle that says
+proprietary software products are entitled to include our code.  (Why
+contribute to a project predicated on refusing to share with us?)
+Using the LGPL for the C library, or for any library, is a matter of
+strategy.</p>
+
+<p>The C library does a generic job; every proprietary system or compiler
+comes with a C library.  Therefore, to make our C library available
+only to free software would not have given free software any
+advantage&mdash;it would only have discouraged use of our library.</p>
+
+<p>One system is an exception to this: on the GNU system (and this
+includes GNU/Linux), the GNU C library is the only C library.  So the
+distribution terms of the GNU C library determine whether it is
+possible to compile a proprietary program for the GNU system.  There
+is no ethical reason to allow proprietary applications on the GNU
+system, but strategically it seems that disallowing them would do more
+to discourage use of the GNU system than to encourage development of
+free applications.  That is why using the Library GPL is a good
+strategy for the C library.</p>
+
+<p>For other libraries, the strategic decision needs to be
+considered on a case-by-case basis.  When a library does a special job
+that can help write certain kinds of programs, then releasing it under
+the GPL, limiting it to free programs only, is a way of helping other
+free software developers, giving them an advantage against proprietary
+software.</p>
+
+<p>Consider GNU Readline, a library that was developed to provide
+command-line editing for BASH.  Readline is released under the
+ordinary GNU GPL, not the Library GPL.  This probably does reduce the
+amount Readline is used, but that is no loss for us.  Meanwhile, at
+least one useful application has been made free software specifically
+so it could use Readline, and that is a real gain for the
+community.</p>
+
+<p>Proprietary software developers have the advantages money provides;
+free software developers need to make advantages for each other.  I
+hope some day we will have a large collection of GPL-covered libraries
+that have no parallel available to proprietary software, providing
+useful modules to serve as building blocks in new free software, and
+adding up to a major advantage for further free software development.</p>
+
+<p>(1) This license is now called the GNU Lesser General Public License,
+to avoid giving the idea that all libraries ought to use it. 
+See <a href="/philosophy/why-not-lgpl.html">Why you shouldn't use the
+Lesser GPL for your next library</a> for more information.</p>
+
+<h3>Scratching an itch?</h3>
+<p>
+Eric Raymond says that &ldquo;Every good work of software starts by
+scratching a developer's personal itch.&rdquo;  Maybe that happens
+sometimes, but many essential pieces of GNU software were developed in
+order to have a complete free operating system.  They come from a
+vision and a plan, not from impulse.</p>
+<p>
+For example, we developed the GNU C library because a Unix-like system
+needs a C library, BASH because a Unix-like
+system needs a shell, and GNU tar because a Unix-like system needs a
+tar program.  The same is true for my own programs&mdash;the GNU C
+compiler, GNU Emacs, GDB and GNU Make.</p>
+<p>
+Some GNU programs were developed to cope with specific threats to our
+freedom.  Thus, we developed gzip to replace the Compress program,
+which had been lost to the community because of
+the <acronym title="Lempel-Ziv-Welch">LZW</acronym> patents.  We found
+people to develop LessTif, and more recently started
+<acronym title="GNU Network Object Model Environment">GNOME</acronym>
+and Harmony, to address the problems caused by certain proprietary
+libraries (see below).  We are developing the GNU Privacy Guard to
+replace popular nonfree encryption software, because users should not
+have to choose between privacy and freedom.</p>
+<p>
+Of course, the people writing these programs became interested in the
+work, and many features were added to them by various people for the
+sake of their own needs and interests.  But that is not why the
+programs exist.</p>
+
+<h3>Unexpected developments</h3>
+<p>
+At the beginning of the GNU Project, I imagined that we would develop
+the whole GNU system, then release it as a whole.  That is not how it
+happened.</p>
+<p>
+Since each component of the GNU system was implemented on a Unix
+system, each component could run on Unix systems long before a
+complete GNU system existed.  Some of these programs became popular,
+and users began extending them and porting them&mdash;to the various
+incompatible versions of Unix, and sometimes to other systems as well.</p>
+<p>
+The process made these programs much more powerful, and attracted both
+funds and contributors to the GNU Project.  But it probably also
+delayed completion of a minimal working system by several years, as
+GNU developers' time was put into maintaining these ports and adding
+features to the existing components, rather than moving on to write
+one missing component after another.</p>
+
+<h3>The GNU Hurd</h3>
+<p>
+By 1990, the GNU system was almost complete; the only major missing
+component was the kernel.  We had decided to implement our kernel as a
+collection of server processes running on top of Mach.  Mach is a
+microkernel developed at Carnegie Mellon University and then at the
+University of Utah; the GNU Hurd is a collection of servers (i.e., a
+herd of GNUs) that run on top of Mach, and do the
+various jobs of the Unix kernel.  The start of development was delayed
+as we waited for Mach to be released as free software, as had been
+promised.</p>
+<p>
+One reason for choosing this design was to avoid what seemed to be the
+hardest part of the job: debugging a kernel program without a
+source-level debugger to do it with.  This part of the job had been
+done already, in Mach, and we expected to debug the Hurd servers as
+user programs, with GDB.  But it took a long time to make that possible,
+and the multithreaded servers that send messages to each other have
+turned out to be very hard to debug.  Making the Hurd work solidly has
+stretched on for many years.</p>
+
+<h3>Alix</h3>
+<p>
+The GNU kernel was not originally supposed to be called the Hurd.  Its
+original name was Alix&mdash;named after the woman who was my sweetheart at
+the time.  She, a Unix system administrator, had pointed out how her
+name would fit a common naming pattern for Unix system versions; as a
+joke, she told her friends, &ldquo;Someone should name a kernel after
+me.&rdquo; I said nothing, but decided to surprise her with a kernel
+named Alix.</p>
+<p>
+It did not stay that way.  Michael (now Thomas) Bushnell, the main
+developer of the kernel, preferred the name Hurd, and redefined Alix
+to refer to a certain part of the kernel&mdash;the part that would trap
+system calls and handle them by sending messages to Hurd servers.</p>
+<p>
+Later, Alix and I broke up, and she changed her name;
+independently, the Hurd design was changed so that the C library would
+send messages directly to servers, and this made the Alix component
+disappear from the design.</p>
+<p>
+But before these things happened, a friend of hers came across the
+name Alix in the Hurd source code, and mentioned it to her.  So
+she did have the chance to find a kernel named after her.</p>
+
+<h3>Linux and GNU/Linux</h3>
+<p>
+The GNU Hurd is not suitable for production use, and we don't know
+if it ever will be.  The capability-based design has problems that
+result directly from the flexibility of the design, and it is not
+clear whether solutions exist.</p>
+
+<p>
+Fortunately, another kernel is available.  In 1991, Linus Torvalds
+developed a Unix-compatible kernel and called it Linux.  It was
+proprietary at first, but in 1992, he made it free software; combining
+Linux with the not-quite-complete GNU system resulted in a complete
+free operating system.  (Combining them was a substantial job in
+itself, of course.)  It is due to Linux that we can actually run a
+version of the GNU system today.</p>
+<p>
+We call this system version <a href="/gnu/linux-and-gnu.html">
+GNU/Linux</a>, to express its composition as a combination of the GNU
+system with Linux as the kernel.  Please don't fall into the practice
+of calling the whole system &ldquo;Linux&rdquo;, since that means
+attributing our work to someone else.
+Please <a href="/gnu/gnu-linux-faq.html"> give us equal
+mention</a>.</p>
+
+<h3>Challenges in our future</h3>
+<p>
+We have proved our ability to develop a broad spectrum of free
+software.  This does not mean we are invincible and unstoppable.
+Several challenges make the future of free software uncertain; meeting
+them will require steadfast effort and endurance, sometimes lasting
+for years.  It will require the kind of determination that people
+display when they value their freedom and will not let anyone take it
+away.</p>
+<p>
+The following four sections discuss these challenges.</p>
+
+<h3>Secret hardware</h3>
+<p>
+Hardware manufacturers increasingly tend to keep hardware
+specifications secret.  This makes it difficult to write free drivers
+so that Linux and XFree86 can support new hardware.  We have complete
+free systems today, but we will not have them tomorrow if we cannot
+support tomorrow's computers.</p>
+<p>
+There are two ways to cope with this problem.  Programmers can do
+reverse engineering to figure out how to support the hardware.  The
+rest of us can choose the hardware that is supported by free software;
+as our numbers increase, secrecy of specifications will become a
+self-defeating policy.</p>
+<p>
+Reverse engineering is a big job; will we have programmers with
+sufficient determination to undertake it?  Yes&mdash;if we have built up a
+strong feeling that free software is a matter of principle, and
+nonfree drivers are intolerable.  And will large numbers of us spend
+extra money, or even a little extra time, so we can use free drivers?
+Yes, if the determination to have freedom is widespread.</p>
+<p>
+(2008 note: this issue extends to the BIOS as well.  There is a free
+BIOS, <a href="http://www.libreboot.org/";>LibreBoot</a> (a distribution of 
coreboot); the problem is getting specs for machines so that
+LibreBoot can support them without nonfree &ldquo;blobs&rdquo;.)</p>
+
+<h3>Nonfree libraries</h3>
+<p>
+A nonfree library that runs on free operating systems acts as a trap
+for free software developers.  The library's attractive features are
+the bait; if you use the library, you fall into the trap, because your
+program cannot usefully be part of a free operating system.  (Strictly
+speaking, we could include your program, but it
+won't <em>run</em> with the library missing.)  Even worse, if
+a program that uses the proprietary library becomes popular, it can
+lure other unsuspecting programmers into the trap.</p>
+<p>
+The first instance of this problem was the Motif toolkit, back in the
+80s.  Although there were as yet no free operating systems, it was
+clear what problem Motif would cause for them later on.  The GNU
+Project responded in two ways: by asking individual free software
+projects to support the free X Toolkit widgets as well as Motif, and
+by asking for someone to write a free replacement for Motif.  The job
+took many years; LessTif, developed by the Hungry Programmers, became
+powerful enough to support most Motif applications only in 1997.</p>
+<p>
+Between 1996 and 1998, another nonfree 
+<acronym title="Graphical User Interface">GUI</acronym> toolkit
+library, called Qt, was used in a substantial collection of free
+software, the desktop
+<acronym title="K Desktop Environment">KDE</acronym>.</p>
+<p>
+Free GNU/Linux systems were unable to use KDE, because we could not
+use the library.  However, some commercial distributors of GNU/Linux
+systems who were not strict about sticking with free software added
+KDE to their systems&mdash;producing a system with more capabilities,
+but less freedom.  The KDE group was actively encouraging more
+programmers to use Qt, and millions of new &ldquo;Linux users&rdquo;
+had never been exposed to the idea that there was a problem in this.
+The situation appeared grim.</p>
+<p>
+The free software community responded to the problem in two ways:
+GNOME and Harmony.</p>
+<p>
+GNOME, the GNU Network Object Model Environment, is GNU's desktop
+project.  Started in 1997 by Miguel de Icaza, and developed with the
+support of Red Hat Software, GNOME set out to provide similar desktop
+facilities, but using free software exclusively.  It has technical
+advantages as well, such as supporting a variety of languages, not
+just C++.  But its main purpose was freedom: not to require the use of
+any nonfree software.</p>
+<p>
+Harmony is a compatible replacement library, designed to make it
+possible to run KDE software without using Qt.</p>
+<p>
+In November 1998, the developers of Qt announced a change of license
+which, when carried out, should make Qt free software.  There is no
+way to be sure, but I think that this was partly due to the
+community's firm response to the problem that Qt posed when it was
+nonfree.  (The new license is inconvenient and inequitable, so it
+remains desirable to avoid using Qt.)</p>
+<p>
+[Subsequent note: in September 2000, Qt was rereleased under the GNU GPL,
+which essentially solved this problem.]</p>
+<p>
+How will we respond to the next tempting nonfree library?  Will the
+whole community understand the need to stay out of the trap?  Or will
+many of us give up freedom for convenience, and produce a major
+problem?  Our future depends on our philosophy.</p>
+
+<h3>Software patents</h3>
+<p>
+The worst threat we face comes from software patents, which can put
+algorithms and features off limits to free software for up to twenty
+years.  The LZW compression algorithm patents were applied for in
+1983, and we still cannot release free software to produce proper
+compressed <acronym title="Graphics Interchange Format">GIF</acronym>s.
+[As of 2009 they have expired.]  In 1998, a free program to produce
+<acronym title="MPEG-1 Audio Layer 3">MP3</acronym> compressed audio
+was removed from distribution under threat of a patent suit.</p>
+<p>
+There are ways to cope with patents: we can search for evidence that a
+patent is invalid, and we can look for alternative ways to do a job.
+But each of these methods works only sometimes; when both fail, a
+patent may force all free software to lack some feature that users
+want.  After a long wait, the patents expire (the MP3 patents are
+expected to have expired by 2018), but what will we do until then?</p>
+<p>
+Those of us who value free software for freedom's sake will stay with
+free software anyway.  We will manage to get work done without the
+patented features.  But those who value free software because they
+expect it to be technically superior are likely to call it a failure
+when a patent holds it back.  Thus, while it is useful to talk about
+the practical effectiveness of the &ldquo;bazaar&rdquo; model of
+development, and the reliability and power of some free software,
+we must not stop there.  We must talk about freedom and principle.</p>
+
+<h3>Free documentation</h3>
+<p>
+The biggest deficiency in our free operating systems is not in the
+software&mdash;it is the lack of good free manuals that we can include in
+our systems.  Documentation is an essential part of any software
+package; when an important free software package does not come with a
+good free manual, that is a major gap.  We have many such gaps today.</p>
+<p>
+Free documentation, like free software, is a matter of freedom, not
+price.  The criterion for a free manual is pretty much the same as for
+free software: it is a matter of giving all users certain freedoms.
+Redistribution (including commercial sale) must be permitted, online
+and on paper, so that the manual can accompany every copy of the
+program.</p>
+<p>
+Permission for modification is crucial too.  As a general rule, I
+don't believe that it is essential for people to have permission to
+modify all sorts of articles and books.  For example, I don't think
+you or I are obliged to give permission to modify articles like this
+one, which describe our actions and our views.</p>
+<p>
+But there is a particular reason why the freedom to modify is crucial
+for documentation for free software.  When people exercise their right
+to modify the software, and add or change its features, if they are
+conscientious they will change the manual, too&mdash;so they can
+provide accurate and usable documentation with the modified program.
+A nonfree manual, which does not allow programmers to be conscientious
+and finish the job, does not fill our community's needs.</p>
+<p>
+Some kinds of limits on how modifications are done pose no problem.
+For example, requirements to preserve the original author's copyright
+notice, the distribution terms, or the list of authors, are OK.  It is
+also no problem to require modified versions to include notice that
+they were modified, even to have entire sections that may not be
+deleted or changed, as long as these sections deal with nontechnical
+topics.  These kinds of restrictions are not a problem because they
+don't stop the conscientious programmer from adapting the manual to
+fit the modified program.  In other words, they don't block the free
+software community from making full use of the manual.</p>
+<p>
+However, it must be possible to modify all the <em>technical</em> content of
+the manual, and then distribute the result in all the usual media,
+through all the usual channels; otherwise, the restrictions do
+obstruct the community, the manual is not free, and we need another
+manual.</p>
+<p>
+Will free software developers have the awareness and determination to
+produce a full spectrum of free manuals?  Once again, our future
+depends on philosophy.</p>
+
+<h3>We must talk about freedom</h3>
+<p>
+Estimates today are that there are ten million users of GNU/Linux
+systems such as Debian GNU/Linux and Red Hat &ldquo;Linux&rdquo;.
+Free software has developed such practical advantages that users are
+flocking to it for purely practical reasons.</p>
+<p>
+The good consequences of this are evident: more interest in developing
+free software, more customers for free software businesses, and more
+ability to encourage companies to develop commercial free software
+instead of proprietary software products.</p>
+<p>
+But interest in the software is growing faster than awareness of the
+philosophy it is based on, and this leads to trouble.  Our ability to
+meet the challenges and threats described above depends on the will to
+stand firm for freedom.  To make sure our community has this will, we
+need to spread the idea to the new users as they come into the
+community.</p>
+<p>
+But we are failing to do so: the efforts to attract new users into our
+community are far outstripping the efforts to teach them the civics of
+our community.  We need to do both, and we need to keep the two
+efforts in balance.</p>
+
+<h3>&ldquo;Open Source&rdquo;</h3>
+<p>
+Teaching new users about freedom became more difficult in 1998, when a
+part of the community decided to stop using the term &ldquo;free
+software&rdquo; and say &ldquo;open source software&rdquo;
+instead.</p>
+<p>
+Some who favored this term aimed to avoid the confusion of
+&ldquo;free&rdquo; with &ldquo;gratis&rdquo;&mdash;a valid goal.  Others,
+however, aimed to set aside the spirit of principle that had motivated
+the free software movement and the GNU Project, and to appeal instead
+to executives and business users, many of whom hold an ideology that
+places profit above freedom, above community, above principle.  Thus,
+the rhetoric of &ldquo;open source&rdquo; focuses on the potential to
+make high-quality, powerful software, but shuns the ideas of freedom,
+community, and principle.</p>
+<p>
+The &ldquo;Linux&rdquo; magazines are a clear example of this&mdash;they
+are filled with advertisements for proprietary software that works
+with GNU/Linux.  When the next Motif or Qt appears, will these
+magazines warn programmers to stay away from it, or will they run ads
+for it?</p>
+<p>
+The support of business can contribute to the community in many ways;
+all else being equal, it is useful.  But winning their support by
+speaking even less about freedom and principle can be disastrous; it
+makes the previous imbalance between outreach and civics education
+even worse.</p>
+<p>
+&ldquo;Free software&rdquo; and &ldquo;open source&rdquo; describe the
+same category of software, more or less, but say different things
+about the software, and about values.  The GNU Project continues to
+use the term &ldquo;free software&rdquo;, to express the idea that
+freedom, not just technology, is important.</p>
+
+<h3>Try!</h3>
+<p>
+Yoda's aphorism (&ldquo;There is no &lsquo;try&rsquo;&rdquo;) sounds
+neat, but it doesn't work for me.  I have done most of my work while
+anxious about whether I could do the job, and unsure that it would be
+enough to achieve the goal if I did.  But I tried anyway, because
+there was no one but me between the enemy and my city.  Surprising
+myself, I have sometimes succeeded.</p>
+<p>
+Sometimes I failed; some of my cities have fallen.  Then I found
+another threatened city, and got ready for another battle.  Over time,
+I've learned to look for threats and put myself between them and my
+city, calling on other hackers to come and join me.</p>
+<p>
+Nowadays, often I'm not the only one.  It is a relief and a joy when I
+see a regiment of hackers digging in to hold the line, and I realize,
+this city may survive&mdash;for now.  But the dangers are greater each
+year, and now Microsoft has explicitly targeted our community.  We
+can't take the future of freedom for granted.  Don't take it for
+granted!  If you want to keep your freedom, you must be prepared to
+defend it.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.  Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+        replace it with the translation of these two:
+
+        We work hard and do our best to provide accurate, good quality
+        translations.  However, we are not exempt from imperfection.
+        Please send your comments and general suggestions in this regard
+        to <a href="mailto:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+     files generated as part of manuals) on the GNU web server should
+     be under CC BY-ND 4.0.  Please do NOT change or remove this
+     without talking with the webmasters or licensing team first.
+     Please make sure the copyright date is consistent with the
+     document.  For web pages, it is ok to list just the latest year the
+     document was modified, or published.
+     
+     If you wish to list earlier years, that is ok too.
+     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+     years, as long as each year in the range is in fact a copyrightable
+     year, i.e., a year in which the document was published (including
+     being publicly visible on the web or in a revision control system).
+     
+     There is more detail about copyright years in the GNU Maintainers
+     Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright &copy; 1998, 2001, 2002, 2005, 2006, 2007, 2008, 2010, 2014, 
2015, 2017
+Richard Stallman</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative
+Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/12/05 07:29:15 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]