bull8.html 57 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096109710981099110011011102110311041105110611071108110911101111111211131114111511161117111811191120112111221123112411251126112711281129113011311132113311341135113611371138113911401141114211431144114511461147
  1. <!-- This HTML file has been created by texi2html 1.30
  2. from bull8.texi on 28 January 1995 -->
  3. <TITLE>GNU's Bulletin, vol. 1 no. 8</TITLE>
  4. <H1>GNU's Bulletin, vol. 1 no. 8</H1>
  5. <P>
  6. <HR>
  7. <P>
  8. The GNU's Bulletin is the semi-annual newsletter of the Free Software
  9. Foundation, bringing you news about the GNU Project.
  10. <P>
  11. Free Software Foundation, Inc. Telephone: (617) 876-3296 <BR> 675
  12. Massachusetts Avenue Electronic mail: gnu@prep.ai.mit.edu <BR>
  13. Cambridge, MA 02139 USA
  14. <P>
  15. <HR>
  16. <P>
  17. <H1><A NAME="SEC3" HREF="bull8_toc.html#SEC3">GNU's Who</A></H1>
  18. <P>
  19. <B>Joseph Arceneaux</B> is working on Emacs version 19. <B>Jim Kingdon</B> is
  20. working on GDB. <B>Kathy Hargreaves</B> is working on the
  21. regular-expression routines <CODE>regex.c</CODE>, <B>Karl Berry</B> is working on
  22. Ghostscript, and both Kathy and Karl have been working on transforming
  23. character bitmaps into cubic splines, so that GNU can include
  24. high-quality typefaces. <B>Roland McGrath</B> and <B>Joy Kendall</B> spent
  25. last summer programming various GNU software. <B>Mike Rowan</B> has just
  26. been hired as a programmer.<P>
  27. <B>Mike Haertel</B> is working on finishing the C interpreter started by
  28. Nobuyuki Hikichi, in addition to continuing to maintain and improve
  29. various utilities and library routines. <B>David Lawrence</B> is currently
  30. expanding the GNU Emacs Lisp libraries. He is working for us at the
  31. Rensselaer Polytechnic Institute.<P>
  32. <B>Brian Fox</B> is now working for us at Caltech. He has released the
  33. beta version of Bash, the `Bourne Again SHell', and is now working on
  34. GNU's daemon-based Finger. <B>Jay Fenlason</B> is writing the GNU
  35. spreadsheet program Oleo, and maintaining <CODE>tar</CODE>, <CODE>sed</CODE> and the
  36. GNU assembler. Jay also takes care of our backups and creating
  37. distribution tapes.<P>
  38. <B>Diane Barlow Close</B> has written initial drafts of the documentation
  39. for all of the small Unix utilities that have been completed for us and
  40. is now working on a shell programming manual. Diane is the primary
  41. author of the GAWK Manual. <B>Mona Cosmos</B> is working on an
  42. introductory user manual (shell commands, files, etc.) and <B>Grace Sylvan</B>
  43. is working on a C manual.<P>
  44. <B>S. Opus Goldstein</B> is still running our office. She now has an
  45. assistant, <B>Erica Brigid ni Judith</B>, who answers the phone machine,
  46. handles correspondence, and packs the orders. <B>Robert J. Chassell</B> is
  47. our Treasurer. Besides dealing with foundation issues not related to
  48. programming, he is working on an elementary introduction to programming
  49. in Emacs Lisp.<P>
  50. <B>Richard Stallman</B> continues as a volunteer to do countless tasks,
  51. including refining the C compiler, GNU Emacs, etc. and their
  52. documentation. Finally, volunteer <B>Len Tower</B> continues as our
  53. electronic JOAT (jack-of-all-trades), handling mailing lists and
  54. gnUSENET, information requests, etc.<P>
  55. <HR>
  56. <P>
  57. <H3><A NAME="SEC4" HREF="bull8_toc.html#SEC4">GNU's Bulletin</A></H3>
  58. <P>
  59. Copyright (C) 1990 Free Software Foundation, Inc.
  60. <P>
  61. Written by: Jim Kingdon, Robert J. Chassell, Michael Bloom, Barry Shein,
  62. <P>
  63. <BLOCKQUOTE>
  64. Micheal Tiemann, Richard Stallman, and Leonard H. Tower Jr.
  65. </BLOCKQUOTE>
  66. <P>
  67. Illustrations: Etienne Suvasa
  68. <P>
  69. Japanese Translator: Mieko Hikichi
  70. <P>
  71. <BLOCKQUOTE>
  72. Permission is granted to anyone to make or distribute verbatim copies of
  73. this document as received, in any medium, provided that the copyright
  74. notice and permission notice are preserved, and that the distributor
  75. grants the recipient permission for further redistribution as permitted
  76. by this notice.
  77. </BLOCKQUOTE>
  78. <P>
  79. <H1><A NAME="SEC5" HREF="bull8_toc.html#SEC5">What Is the Free Software Foundation?</A></H1>
  80. <P>
  81. The Free Software Foundation is dedicated to eliminating restrictions on
  82. copying, redistribution, understanding and modification of computer
  83. programs. We do this by promoting the development and use of free
  84. software in all areas of computer use. Specifically, we are putting
  85. together a complete integrated software system named "GNU" (GNU's Not
  86. Unix) that will be upwardly compatible with Unix. Some large parts of
  87. this system are already working and we are distributing them now.<P>
  88. The word "free" in our name refers to two specific freedoms: first,
  89. the freedom to copy a program and give it away to your friends and
  90. co-workers; second, the freedom to change a program as you wish, by
  91. having full access to source code. Furthermore, you can study the
  92. source and learn how such programs are written. You may then be able to
  93. port it, improve it, and share your changes with others.<P>
  94. Other organizations distribute whatever free software happens to be
  95. available. By contrast, FSF concentrates on development of new free
  96. software, building toward a GNU system complete enough to eliminate the
  97. need to purchase a proprietary system.<P>
  98. Besides developing GNU, the Foundation has secondary functions:
  99. producing tapes and printed manuals of GNU software, carrying out
  100. distribution, and accepting gifts to support GNU development. We are
  101. tax exempt; you can deduct donations to us on your tax returns. Our
  102. development effort is funded partly from donations and partly from
  103. distribution fees. Note that the distribution fees purchase just the
  104. service of distribution: you never have to pay anyone license fees to
  105. use GNU software, and you always have the freedom to make your copy from
  106. a friend's computer at no charge (provided your friend is
  107. willing).<P>
  108. The Foundation also maintains a Service Directory: a list of people who
  109. offer service for pay to users of GNU programs and systems. The Service
  110. Directory is located in file <TT>`etc/SERVICE'</TT> in the GNU Emacs
  111. distribution. Service can mean answering questions for new users,
  112. customizing programs, porting to new systems, or anything else. Contact
  113. us if you want to be listed or wish a copy.<P>
  114. After we create our programs, we continually update and improve them.
  115. We release between 2 and 20 updates a year for each program. Doing this
  116. while developing new programs takes a lot of work, so any donations of
  117. pertinent source code and documentation, machines, labor or money are
  118. always appreciated.<P>
  119. The board of the Foundation is: Richard Stallman, President; Robert J.
  120. Chassell, Treasurer; Gerald J. Sussman, Harold Abelson and Leonard H.
  121. Tower Jr., Directors.<P>
  122. <H1><A NAME="SEC6" HREF="bull8_toc.html#SEC6">What Is Copyleft?</A></H1>
  123. <P>
  124. In the section entitled "What Is the Free Software Foundation?" we
  125. state that "you never have to pay anyone license fees to use GNU
  126. software, and you always have the freedom to make your copy from a
  127. friend's computer at no charge." What exactly do we mean by this, and
  128. how do we make sure that it stays true?<P>
  129. The simplest way to make a program free is to put it in the public
  130. domain. Then people who get it from sharers can share it with others.
  131. But bad citizens can also do what they like to do: sell binary-only
  132. versions under typical don't-share-with-your-neighbor licenses. They
  133. would thus enjoy the benefits of the freeness of the original program
  134. while withholding these benefits from the users. It could easily come
  135. about that most users get the program this way, and our goal of making
  136. the program free for <EM>all</EM> users would have been undermined.<P>
  137. To prevent this from happening, we don't normally place GNU programs in
  138. the public domain. Instead, we protect them by what we call
  139. <DFN>copylefts</DFN>. A copyleft is a legal instrument that makes everybody
  140. free to copy a program as long as the person getting the copy gets with
  141. it the freedom to distribute further copies, and the freedom to modify
  142. their copy (which means that they must get access to the source code).
  143. Typical software companies use copyrights to take away these freedoms;
  144. now we software sharers use copylefts to preserve these freedoms.<P>
  145. The copyleft used by the GNU project is made from a combination of a
  146. copyright notice and the <DFN>GNU General Public License</DFN>. The
  147. copyright notice is the usual kind. The General Public License is a
  148. copying license which basically says that you have the freedoms we want
  149. you to have and that you can't take these freedoms away from anyone
  150. else. (The actual document consists of several pages of rather
  151. complicated legalbol that our lawyer said we needed.) The complete
  152. license is included in all GNU source code distributions and many
  153. manuals, and we will send you a copy on request.<P>
  154. We encourage others to copyleft their programs using the General Public
  155. License; basically programs only need to include a few sentences stating
  156. that the license applies to them. Specifics on using the License
  157. accompany it, so refer there for details.<P>
  158. <BLOCKQUOTE>
  159. <EM>"As we enjoy great advantages from the inventions of others, we
  160. should be glad of an opportunity to serve others by any invention of
  161. ours."</EM>
  162. </BLOCKQUOTE>
  163. <P>
  164. --Benjamin Franklin
  165. <P>
  166. <H1><A NAME="SEC7" HREF="bull8_toc.html#SEC7">GNUs Flashes</A></H1>
  167. <P>
  168. <UL>
  169. <P>
  170. <LI>
  171. <B>Donation from Japan Unix Society</B>
  172. <P>
  173. The Japan Unix Society has given us $10,000. They have also been
  174. distributing Nobuyuki and Mieko Hikichi's translation of the GNU's
  175. bulletin and have plans to distribute GNU software. We want to say
  176. "Thank You," and encourage other user groups to support the
  177. development of high quality free software.<P>
  178. <LI>
  179. <B>Emacs Lisp Reference Manual</B>
  180. <P>
  181. We will publish the long awaited, and very long, <CITE>GNU Emacs Lisp
  182. Reference Manual</CITE> in March 1990. The manual describes the GNU Emacs
  183. Lisp programming language in detail.
  184. <P>
  185. <LI>
  186. <B>Long-named options</B>
  187. <P>
  188. We have started adding long-named options to many of our utilities. For
  189. example, instead of remembering whether to use <CODE>-v</CODE> or <CODE>-V</CODE>,
  190. you can use <CODE>+verbose</CODE> (or any unambiguous abbreviation) in all
  191. programs. Eventually we hope to provide command-line completion for
  192. long option names.<P>
  193. <LI>
  194. <B><CODE>indent</CODE></B>
  195. <P>
  196. We have added some enhancements to the <CODE>indent</CODE> prettyprinter from
  197. the 4.3BSD-tahoe free software release. GNU indent improvements include
  198. removal of arbitrary limits, GNU coding style support, and bug
  199. fixes.<P>
  200. <LI>
  201. <B>GNU compiler gaining acceptance</B>
  202. <P>
  203. Many people are now using our C compiler, including the Open Software
  204. Foundation (as part of their operating system); Data General (for their
  205. Aviion 88000 based workstation); and Intel (for their 960
  206. microprocessor).<P>
  207. <LI>
  208. <B>GNU Chess defeats Fidelity Mach 3</B>
  209. <P>
  210. A 10 game match was conducted between GNU Chess 1.55 running on a Sun
  211. Sparcstation-1 and the strong commercial chess machine Fidelity Mach 3.
  212. Fidelity Mach 3 is officially rated USCF 2265 (2200 is master). Most
  213. observers acknowledge it is a true master. The match result was 7-3 in
  214. GNU's favor. After various corrections, we arrive at a putative rating
  215. of around 2330 (strong master) for GNU Chess 1.55 on this
  216. machine.<P>
  217. This result was most unexpected since prior versions of GNU Chess had
  218. scored no more than 3 points out of 10 against the Mach 3. The big leap
  219. appears to come from: (1) the inclusion of Hans Eric Sandstrom's fast
  220. move generator and (2) the Sparcstation-1, which is (apparently)
  221. particularly suited to speedy chess processing. Minor modifications to
  222. the book, draw factor, and thinking on opponent's time have also
  223. helped.<P>
  224. Please remember this rating is based on a short match result. Certain
  225. moves GNU Chess plays are clearly non-master in quality. Computer
  226. masters generally achieve their strength through accuracy of tactics,
  227. not subtle positional moves.<P>
  228. </UL>
  229. <P>
  230. <H1><A NAME="SEC8" HREF="bull8_toc.html#SEC8">Boycott Apple; Defend Apple</A></H1>
  231. <P>
  232. by Richard Stallman
  233. <P>
  234. Most of the people I know in the computer field are disgusted with
  235. Apple for its look-and-feel lawsuit. So, when they hear that Xerox
  236. has sued Apple in the same way, they are usually delighted: now
  237. Sculley may get what he deserves.<P>
  238. There is only one dark cloud in this inviting landscape: if Xerox
  239. wins, the rest of us will also get what Sculley deserves.<P>
  240. In practical terms, a Xerox victory would have the same kind of effect
  241. as a victory by Apple in its lawsuit against HP and Microsoft. If we
  242. lose the freedom to develop and distribute window systems, it little
  243. matters precisely who has taken it away. The dangerous precedent for
  244. future cases on other kinds of software would likewise be the
  245. same.<P>
  246. However, Xerox as a monopolist could be worse in degree. Xerox was
  247. involved in an earlier stage of window system development, so a Xerox
  248. monopoly might cover a wider range of window systems than an Apple
  249. monopoly.<P>
  250. For the GNU project, the practical result might be that we cannot have
  251. a window system. We have been planning to use the X window system,
  252. but if Xerox wins the suit, this could become illegal.<P>
  253. An additional danger in the Xerox suit is that public sympathy for
  254. Xerox, due to resentment of Apple's own lawsuit and to Xerox's early
  255. role in developing window system ideas, may help Xerox win.<P>
  256. This sympathy is misplaced. Xerox entered a competitive market
  257. functioning under well-known rules: no one could copyright a user
  258. interface. (As for ideas and techniques, copyright has never applied to
  259. those.) They developed an interesting product that failed in the market
  260. due to various mistakes--an event which is not unusual in business. Now
  261. they wish to escape the consequences of their errors by changing the
  262. rules retroactively. This is hardly fair.<P>
  263. In order for us to keep our freedom to write software, we must now
  264. defeat Xerox as well as Apple. This means our task is now harder.
  265. However, the Xerox lawsuit may aid us indirectly: the absurdity of
  266. this mess of lawsuits may help convince the public that the whole idea
  267. of look-and-feel copyright must be firmly rejected.<P>
  268. But being convinced is not enough; to end the danger of look-and-feel
  269. suits, we must convince the courts and Congress. By expressing our
  270. views in public, writing to the House Subcommittee on Intellectual
  271. Property, or joining the League for Programming Freedom, we can put an
  272. end to this wasteful legal contentiousness.<P>
  273. <BLOCKQUOTE>
  274. You can write to the subcomittee at:<BR>
  275. House Subcommittee on Intellectual Property,<BR>
  276. U.S. House of Representatives,<BR>
  277. Washington, DC 20515
  278. </BLOCKQUOTE>
  279. <P>
  280. <H1><A NAME="SEC9" HREF="bull8_toc.html#SEC9">League for Programming Freedom</A></H1>
  281. <P>
  282. by Michael Bloom and Richard Stallman
  283. <P>
  284. The League for Programming Freedom is an organization of people who
  285. oppose the attempt to monopolize common user interfaces through "look
  286. and feel" copyright lawsuits. Some of us are programmers, who worry
  287. that such monopolies will obstruct our work. Some of us are users,
  288. who want new computer systems to be compatible with the interfaces we
  289. know.
  290. <P>
  291. "Look and feel" lawsuits aim to create a new class of
  292. government-enforced monopolies broader in scope than ever before.
  293. Such a system of user-interface copyright would impose gratuitous
  294. incompatibility, reduce competition, and stifle innovation.
  295. <P>
  296. We in the League hope to prevent these problems by preventing
  297. user-interface copyright. The League is not opposed to copyright law as
  298. it was understood until 1986--copyright on particular programs. Our
  299. aim is to stop changes in the copyright system which would take away
  300. programmers' traditional freedom to write new programs compatible with
  301. existing programs and practices.
  302. <P>
  303. The League for Programming Freedom will act against the doctrine behind
  304. look-and-feel suits by any means consistent with the law and
  305. intellectual liberty. We will write editorials, talk with public
  306. officials, file amicus curiae briefs with the courts, and boycott
  307. egregious offenders. On May 24th, 1989, we picketed Lotus headquarters
  308. on account of their lawsuits against competitors, stimulating widespread
  309. media coverage for the issue. If you have other ideas, please suggest
  310. them.
  311. <P>
  312. In the future, the League may also fight other restrictive practices,
  313. such as software patents, which threaten to make every design decision
  314. in software development a chance for a lawsuit. The League's founders
  315. consider software patents potentially even more dangerous than
  316. look-and-feel copyright, but it will be up to the members to decide
  317. whether the League should campaign against them.
  318. <P>
  319. The League needs both activist members and members who only pay their
  320. dues.<P>
  321. To join, write to:
  322. <P>
  323. <PRE>
  324. League for Programming Freedom, 1 Kendall Square #143,
  325. P.O.Box 9171, Cambridge, MA 02139, USA. Phone: (617) 492--0023.
  326. </PRE>
  327. <P>
  328. Note that the League for Programming Freedom is a separate organization
  329. from the Free Software Foundation; please direct all League inquiries to
  330. the above address, not to the Foundation.<P>
  331. <H1><A NAME="SEC10" HREF="bull8_toc.html#SEC10">Online Book Initiative</A></H1>
  332. <P>
  333. by Barry Shein
  334. <P>
  335. The Online Book Initiative has been formed to make available freely
  336. redistributable collections of information. There exist huge
  337. collections of books, conference proceedings, reference material,
  338. catalogues, etc., which can be freely shared. Some of it is in
  339. machine-readable form, much of it isn't.<P>
  340. The purpose of the Online Book Initiative is to create a publicly
  341. accessible repository for this information, a net-worker's
  342. library.<P>
  343. Information in the Online Book Repository will be available for free
  344. redistribution. On-line access, magnetic media and other methods of
  345. distribution will involve reasonable charges for the services provided,
  346. not the information.<P>
  347. There are other organizations with similar overall goals (e.g. Project
  348. Gutenberg, Common Knowledge); in some cases the details of their goals
  349. or approaches are quite different. We are in contact with most of them
  350. and in general our conversations are very positive. Anyone putting
  351. textual information on-line soon develops an attitude of "the more, the
  352. merrier;" it's a massive area of endeavor.<P>
  353. What We Wish to Archive
  354. <P>
  355. All on-line materials (other than software collections) such as books,
  356. journals, catalogues, conference proceedings, magazines, manuals, maps,
  357. images, technical documentation, reference works, etc. The only
  358. software we are interested in is software specific to the viewing,
  359. manipulation, searching and maintenance of information in the
  360. repository.<P>
  361. Materials must be free of copyrights limiting redistribution by us or
  362. any individual or organization who receives them. The Online Book
  363. Initiative is dealing only with materials free of restrictive copyrights
  364. because we don't want to be distracted by the complications they
  365. demand.<P>
  366. We also need pointers to collections of materials that may be
  367. available. For example, there are government collections of interesting
  368. data which are available at reasonable costs and do not limit further
  369. redistribution of copies obtained.<P>
  370. What We Need from You
  371. <P>
  372. Beyond machine-readable material there are huge collections of printed
  373. material which could be redistributed if put on-line. We need people
  374. willing to organize informal projects to scan, type or otherwise get
  375. this material on-line for inclusion in the Online Book
  376. Repository.<P>
  377. We need to get in touch with Library and Information Scientists
  378. interested in helping us create formats and structures for organizing
  379. the repository.<P>
  380. We need international participation to help ensure that our efforts are
  381. useful to people everywhere.<P>
  382. We need people willing to participate in a Technical Advisory Board to
  383. help us guide our efforts.<P>
  384. We need involvement from academia, industry and governments to help us
  385. enrich this effort without bounds and make available a first-rate,
  386. freely available information utility.<P>
  387. We need involvement from publishers who have materials that can be
  388. included in the Online Book Repository. Many books and reference
  389. works have become unprofitable to publish by ordinary paper means.
  390. It's time to make these materials available!<P>
  391. We need involvement from the technical community to choose and implement
  392. multi-media software standards such as hypertext, mark-up languages,
  393. index and catalogue software, text retrieval, network access methods and
  394. more. Standards are critical to our efforts.<P>
  395. What We Are Offering
  396. <P>
  397. <CODE>world.std.com</CODE> is a public access UNIX system which will serve as
  398. the initial repository. It is a Sun4/280 system and will be expanded as
  399. needed.<P>
  400. Anyone can dial into the system and set up an account if they wish
  401. direct access (617-739-WRLD). Accounts are charged and proceeds will be
  402. used to build the Online Book Repository.<P>
  403. UUCP and other links will be available for the redistribution of
  404. collections. We will also make collections available on magnetic media
  405. for reasonable copying charges.<P>
  406. How to Get Involved
  407. <P>
  408. If you think you can help or want more information send electronic mail
  409. to <CODE>obi@world.std.com</CODE>. There are two mailing lists, one for
  410. general discussion about Online Book Initiative issues and another which
  411. receives announcements only (the general discussion list will see all
  412. announcements so you only need to be on one). To subscribe to either,
  413. mail a request to <CODE>obi-request@world.std.com</CODE>.<P>
  414. Or call us at Software Tool &#38; Die, 617-739-0202.<P>
  415. Or drop by our office and chat if you're in the area: 1330 Beacon
  416. Street, Brookline, MA 02146.<P>
  417. Postscript
  418. <P>
  419. This started as an informal discussion group that called themselves
  420. "The KiloMonkeys Project" ("Strong Typing For Weak Minds") who
  421. wanted to figure out how to get useful materials on-line and generally
  422. available. I have decided to make Software Tool &#38; Die a home for this
  423. activity and formalize the project under the new name "The Online Book
  424. Initiative." My thanks to that original group from Monkey
  425. Shein.<P>
  426. <H1><A NAME="SEC11" HREF="bull8_toc.html#SEC11">Common Knowledge's Universal Index</A></H1>
  427. <P>
  428. There is an international group called Common Knowledge working to
  429. compile public domain, copyright free and machine-readable information.
  430. The group, consisting of journalists, scientists, librarians and others,
  431. is amassing a database of non-copyrighted information which they call
  432. the "Universal Index". They are doing this to provide an alternative
  433. to the information merchants, who are increasingly successful at
  434. reducing the amount of material available to traditional libraries.
  435. Their address is:<P>
  436. <PRE>
  437. Common Knowledge, Jefferson, MD 21755, USA. Phone: (301) 695--3100
  438. </PRE>
  439. <P>
  440. <H1><A NAME="SEC12" HREF="bull8_toc.html#SEC12">New Support Company</A></H1>
  441. <P>
  442. Cygnus Support has been organized as the first for-profit corporation
  443. that provides commercial support <EM>only</EM> for free software, that we
  444. are aware of. Their initial support package is for GNU program
  445. development tools at sites with 50 -- 150 seats. Contact
  446. <CODE>tiemann@ai.mit.edu</CODE> or Cygnus Support, 814 University Ave.,
  447. Palo Alto, CA 94301. (FSF is not affiliated with Cygnus Support; note
  448. that numerous individual consultants are listed in the GNU Service
  449. Directory in file <TT>`etc/SERVICE'</TT> in the GNU Emacs
  450. distribution.)<P>
  451. <H1><A NAME="SEC13" HREF="bull8_toc.html#SEC13">GNU Wish List</A></H1>
  452. <P>
  453. Wishes for this issue are for:<P>
  454. <UL>
  455. <LI>
  456. Someone skilled in compiler maintenance who could take over GCC
  457. maintenance for RMS. This would probably be a full-time job.<P>
  458. <LI>
  459. We are hiring both programmers and technical writers to work on Project
  460. GNU. We want people who can do a good job and who are willing to work
  461. for less money than most employers pay. You must either be in
  462. Cambridge, Mass., or be able to maintain good electronic communication
  463. with us. Contact <CODE>rms@ai.mit.edu</CODE> or send mail to Richard
  464. Stallman c/o the Free Software Foundation if you are interested.<P>
  465. <LI>
  466. Volunteers to help write utilities and documentation. Send mail to
  467. <CODE>gnu@prep.ai.mit.edu</CODE> for the task list.<P>
  468. <LI>
  469. Professors who might be interested in sponsoring or hosting research
  470. assistants to do GNU development, with full or partial FSF support.
  471. Several schools have done this and we welcome others to join in.<P>
  472. <LI>
  473. Speech generation, speech recognition, and character recognition
  474. software (if the devices aren't too weird), with the device drivers if
  475. possible. This would help at least one partially disabled programmer we
  476. know to be productive.<P>
  477. <LI>
  478. Grammar checking software for English and other natural
  479. languages.<P>
  480. <LI>
  481. Copies of newspaper and journal articles mentioning the GNU Project.
  482. Send these to the address on the front cover, or send a citation to
  483. <CODE>gnu@prep.ai.mit.edu</CODE>.<P>
  484. <LI>
  485. Money, as always. Please remember, donations are tax-deductible. With
  486. the latest donations, we have again been able to expand our
  487. staff.<P>
  488. One way to give us a small amount of money is to order a distribution
  489. tape or two. This may not count as a donation for tax purposes, but it
  490. can qualify as a business expense.<P>
  491. </UL>
  492. <P>
  493. <H1><A NAME="SEC14" HREF="bull8_toc.html#SEC14">GNU Project Status Report</A></H1>
  494. <P>
  495. <UL>
  496. <LI>
  497. <B>GNU Emacs</B>
  498. <P>
  499. Except for bug fixes, work on Emacs version 18 has ceased. Emacs 19 is
  500. advancing and the new features we have added include multiple X window
  501. capability, support for European character sets and multiple fonts,
  502. enhanced visual aspects including scrollbars, floating point numbers, a
  503. relocating memory allocator for buffers, more sophisticated mouse
  504. support and use of function keys, and many changes to the Lisp
  505. libraries.<P>
  506. Other features we are considering are associating property lists and
  507. actions with regions of text, incremental syntax analysis for
  508. programming languages, source-level debugging for Emacs Lisp, hooks to
  509. be run if point moves outside a certain range, a more hyper-text
  510. oriented Info mode, a mouse-help X window application, menu bars, and
  511. possibly a new and improved pop-up menu system.<P>
  512. We don't know how much of this we will do before we make a release, or
  513. when that release will be, so please don't ask. We will announce
  514. it.<P>
  515. We will publish the <CITE>GNU Emacs Lisp Reference Manual</CITE> in March
  516. 1990.<P>
  517. <LI>
  518. <B>Kernel</B>
  519. <P>
  520. We hope to use the Mach message-passing kernel being developed at CMU.
  521. The current distributed version of Mach is not free because it contains
  522. code from BSD of AT&#38;T origin. However, the Mach developers have been
  523. working to separate this code from the kernel and they now say they have
  524. a first version of this running in alpha test. Prof. Rashid assures us
  525. that when this version is stable, it will be free.<P>
  526. Should Mach not become available, then we will start the kernel with
  527. either MIT's TRIX kernel or Berkeley's Sprite system.<P>
  528. Right now, we aren't doing any kernel work. It does not make sense for
  529. us to start a kernel project now, when we still hope to use Mach.<P>
  530. <LI>
  531. <B>GNU Debugger</B>
  532. <P>
  533. The GNU source-level C debugger, GDB, is now being distributed along
  534. with Emacs version 18 as GDB version 2.8. GDB version 3.4 is
  535. distributed on the beta-test (compiler) tape, and as soon as it is
  536. stable it will replace version 2.8 on the Emacs tape.<P>
  537. When we have a stable release of GDB 3.x we will start work on GDB 4.
  538. We plan to add over-the-ethernet debugging, remote cross-debugging, and
  539. Dalek extensions such as <CODE>if</CODE>, <CODE>while</CODE>, and event-based
  540. debugging (see Crawford, Richard H., Ho, W. Wilson, and Olsson, Ronald
  541. A., <CITE>A Dataflow Approach to Event-Based Debugging</CITE>, University of
  542. California at Davis, Davis, CA, CSE-89-7, May, 1989), and other
  543. features.<P>
  544. Other features that we may add sometime are watchpoints, and the ability
  545. to debug multi-threaded parallel programs.<P>
  546. <LI>
  547. <B>C Compiler</B>
  548. <P>
  549. The GNU C Compiler, GCC, is now fairly reliable. People are still
  550. reporting bugs, but they also say they think there are fewer bugs than
  551. in commercial compilers. NeXT builds their entire system, including
  552. their port of the MACH kernel and NFS, with GCC. Someone has also told
  553. us that GCC successfully compiled a System V.3 kernel. Much of the BSD
  554. source tree has been compiled with GCC.<P>
  555. We are now working to stabilize GCC version 1 while incorporating new
  556. improvements into version 2. Version 2 now has support for nested
  557. functions, a certain amount of common subexpression elimination between
  558. basic blocks, and a new feature for classifying instructions that can
  559. be used to choose between long and short branches, or to provide raw
  560. data for instruction scheduling.<P>
  561. Version 2 will support C<CODE>++</CODE> on the same basis as C itself. Also,
  562. we expect to have instruction scheduling and perhaps global common
  563. subexpression elimination. Ron Guilmette's Protoize, which generates
  564. ANSI C prototypes, will be merged in.<P>
  565. We are currently implementing delayed-branch fill and pipeline
  566. scheduling (experimentally). We may add facilities for precompilation
  567. of header files to save time when they are large and the source files
  568. are small.<P>
  569. We might also do other language front ends, but there seem to be enough
  570. volunteer GNUers willing to do this job. Jukka Virtanen is now working
  571. on the Pascal front-end. It is running, but before it will be ready for
  572. alpha testing it needs some new features and the ability to detect
  573. errors more gracefully. Other volunteers are working on FORTRAN and
  574. Modula. So far, no one has volunteered to write Ada or Cobol.<P>
  575. GCC has recently been ported to the Motorola 88000, Intel 860, and
  576. Pyramid processors. Volunteers may be working on ports to the IBM 370,
  577. IBM PC/RT, 3B2, HP Spectrum, some sort of Gould machine, and the AMD
  578. 29000.<P>
  579. <LI>
  580. <B>C Library</B>
  581. <P>
  582. Roland McGrath and some others continue to work on the C Library. The C
  583. library currently contains all of the ANSI C and POSIX.1 functions, and
  584. work is in progress on POSIX.2 and Unix features.<P>
  585. Doug Schmidt has provided an improved <CODE>qsort</CODE> which is faster than
  586. Berkeley's and is also reentrant.<P>
  587. The C library is using a new <CODE>malloc</CODE> written by Mike Haertel.<P>
  588. <LI>
  589. <B>Preliminary Ghostscript</B>
  590. <P>
  591. We are distributing Ghostscript, the free GNU software that provides
  592. nearly all the facilities of a Postscript interpreter, on our beta
  593. tape.<P>
  594. Karl Berry and Kathy Hargreaves are working on adding typefaces. Beside
  595. typefaces, Ghostscript needs these enhancements: to serve as a previewer
  596. for multi-page files; to serve other X clients by drawing on their
  597. windows; to improve both its performance and visual quality. Other
  598. suggestions for enhancements are welcome.<P>
  599. <LI>
  600. <B>Finger and Send</B>
  601. <P>
  602. We soon will have a daemon-based Finger program. It polls a selection
  603. of hosts and is thus able to tell you where each person is logged
  604. in.<P>
  605. We are also testing a Send program for sending immediate messages to
  606. other users across the net.<P>
  607. <LI>
  608. <B>Oleo</B>
  609. <P>
  610. Jay Fenlason is writing a spreadsheet named Oleo (better for you than
  611. the more expensive spreadsheet).<P>
  612. <LI>
  613. <B>GNU Mailer</B>
  614. <P>
  615. We may use <CODE>smail</CODE>, written by Landon Noll and Ronald Karr of
  616. Amdahl, or <CODE>zmailer</CODE>, which Rayan Zachariasen is writing, or
  617. perhaps both.<P>
  618. <LI>
  619. <B>File Manipulation Utilities</B>
  620. <P>
  621. We have a collection of utilities for file manipulation, including
  622. <CODE>ls</CODE>, <CODE>mv</CODE>, <CODE>cp</CODE>, <CODE>cat</CODE>, <CODE>rm</CODE>, <CODE>du</CODE>,
  623. <CODE>head</CODE>, <CODE>tail</CODE> and <CODE>cmp</CODE>. We use these on our own
  624. machines and plan to release them soon.<P>
  625. <LI>
  626. <B>Possible Target Machines</B>
  627. <P>
  628. GNU will require a CPU that uses 32-bit addresses and integers and
  629. addresses to the 8-bit byte. Virtual memory will probably be
  630. required.<P>
  631. GNU Emacs and GNU C require more than a meg of addressable memory in the
  632. system, although a meg of physical memory may be enough if there is
  633. virtual memory. 2 meg would make a noticeable improvement in
  634. performance. Many source files need more than 1 meg of virtual memory
  635. to compile.<P>
  636. A hard disk will be essential; at least 30 or 40 meg will be needed to
  637. hold a minimal system. Plus more space for the user's files, of course.
  638. We recommend at least 80meg for a personal GNU system, and that would be
  639. fairly cramped.<P>
  640. Not that it will be impossible to adapt some or all of GNU for other
  641. architectures; but we don't currently consider it part of our
  642. job.<P>
  643. <LI>
  644. <B>Distribution of 80386 Floppies Still Planned</B>
  645. <P>
  646. We are still considering distribution of 1.2 megabyte 5.25 inch
  647. diskettes.<P>
  648. </UL>
  649. <P>
  650. <H3><A NAME="SEC15" HREF="bull8_toc.html#SEC15">Freemacs, an Extensible Editor for MS-DOS</A></H3>
  651. <P>
  652. Russ Nelson has a copylefted editor for MS-DOS called Freemacs. It is
  653. one of the few editors that has a full extension language yet runs on
  654. small machines. It is the only such editor that tries to be compatible
  655. with GNU Emacs. For more information contact Russ via electronic mail
  656. (<CODE>nelson@clutx.clarkson.edu</CODE>) or paper mail (Russell Nelson,
  657. 11 Grant St., Potsdam, NY, 13676).<P>
  658. Note that the Free Software Foundation does not distribute Freemacs;
  659. please don't ask us about it.<P>
  660. <P>
  661. <H1><A NAME="SEC16" HREF="bull8_toc.html#SEC16">GNU Documentation</A></H1>
  662. <P>
  663. GNU is dedicated to having quality easy-to-use on-line and printed
  664. documentation. GNU manuals explain the underlying concepts, describe
  665. how to use all the features of each program, and give examples of
  666. command use.<P>
  667. GNU documentation is distributed as Texinfo source files. Texinfo
  668. source yields both a typeset hardcopy and on-line presentations,
  669. accessed by a menu-driven system.<P>
  670. The following manuals, provided with our software, are also available in
  671. hardcopy; see the order form on the inside back cover.<P>
  672. The <B>Emacs Manual</B> describes how to use GNU Emacs. It also explains
  673. advanced features, such as outline mode and regular expression search.
  674. The manual tells how to use the special modes for programming in
  675. languages such as C and Lisp, how to use the tags utility, and how to
  676. compile and correct code. It also describes how to make your own
  677. keybindings and make other elementary customizations.<P>
  678. The <B>Emacs Lisp Reference Manual</B>, which will be released in March
  679. 1990, describes the GNU Emacs Lisp programming language. An
  680. introductory Emacs Lisp programming manual is also being written.<P>
  681. The <B>Texinfo Manual</B> describes how to write documents in Texinfo
  682. source code. It describes the markup language used to create both an
  683. Info file and a printed document from the same source file: how to make
  684. tables, lists, chapters, nodes, indices and cross references. It also
  685. describes how to use Texinfo mode in GNU Emacs and how to catch
  686. mistakes.<P>
  687. The <B>Termcap Manual</B> is often described as "Twice as much as you ever
  688. wanted to know about Termcap." It describes the format of the Termcap
  689. database, the definitions of terminal capabilities, and how to
  690. interrogate a terminal description. This manual is primarily for
  691. programmers.<P>
  692. The <B>Bison Manual</B> describes how to write a grammar description that
  693. Bison can convert into a C program that can parse that grammar. This
  694. manual assumes no prior knowledge of parser generators. It describes
  695. the concepts and then provides a series of increasingly complex examples
  696. before describing what goes on in considerable detail.<P>
  697. The <B>GAWK Manual</B> describes how to use the GNU implementation of AWK.
  698. It is written for someone who has never used AWK before, and describes
  699. all the features of this powerful string manipulating language.<P>
  700. The <B>Make Manual</B> describes the GNU Make utility, a program used to
  701. rebuild parts of other programs when and as needed. The manual tells
  702. how to write a makefile, which specifies how to recompile the parts of
  703. your program and how they depend on each other.<P>
  704. The <B>GDB Manual</B> explains how to use GDB, the GNU Debugger. It
  705. describes how to run your program under control of the debugger, how to
  706. examine and alter data within the program, and how to modify the flow of
  707. control within the program. It also explains how to use GDB through GNU
  708. Emacs, with auto-display of source lines.<P>
  709. <H1><A NAME="SEC17" HREF="bull8_toc.html#SEC17">GNU Software Available Now</A></H1>
  710. <P>
  711. We now offer four Unix software source distribution tapes, plus VMS
  712. tapes for GNU Emacs and GNU C that include sources and VMS executables.
  713. The first Unix tape (called the "Release" or "Emacs" tape) contains
  714. GNU Emacs as well as various other well-tested programs that we consider
  715. reliable. The second Unix tape (called the "Beta test" or
  716. "Compiler" tape) contains the GNU C compiler and related utilities,
  717. and other new programs that are less thoroughly tested. The third and
  718. fourth Unix tapes (called the "X11" tapes) contain the X11
  719. distribution from the MIT X consortium. See the order form, on the
  720. inside back cover, for details about media, etc.<P>
  721. Note that the contents of the 1600bpi 9-track tapes and the QIC-24
  722. DC300XLP 1/4 inch cartridge tapes are the same. It is only the media
  723. that are different.<P>
  724. <H3><A NAME="SEC18" HREF="bull8_toc.html#SEC18">Contents of the Release Tape</A></H3>
  725. <P>
  726. The software on this tape is considered to be fairly stable, but as
  727. always, we welcome your bug reports.<P>
  728. <UL>
  729. <LI>
  730. <B>GNU Emacs</B>
  731. <P>
  732. In 1975, Richard Stallman developed the first Emacs: the extensible,
  733. customizable real-time display editor. GNU Emacs is his second
  734. implementation of Emacs. It's the first Emacs available on Unix systems
  735. that offers true Lisp, smoothly integrated into the editor, for writing
  736. extensions. It also provides a special interface to MIT's free X window
  737. system, versions 10 and 11, which makes redisplay very fast. The
  738. current version is 18.55.<P>
  739. GNU Emacs has been in widespread use since 1985 and often displaces
  740. proprietary implementations of Emacs because of its greater reliability
  741. as well as its good features and easier extensibility. DEC, Berkeley,
  742. and NeXT are all distributing Emacs with their systems. When Isaac
  743. Salzman set out to review various versions of Emacs, only one company
  744. wanted their product to be compared with GNU Emacs. In his review, which
  745. appeared in the July, 1989 issue of <I>Unix Review</I>, Salzman concluded,
  746. "When it comes to Emacs, GNU is the way to go."<P>
  747. GNU Emacs (as of version 18.55) runs on many kinds of Unix systems:
  748. those made by Alliant, Altos 3068, Amdahl (UTS), Apollo, AT&#38;T (3B
  749. machines and 7300 pc), CCI 5/32 and 6/32, Celerity, Convex, Digital
  750. (DECstation 3100; Vax running BSD or SysV), Dual, Elxsi 6400, Encore
  751. (DPC, APC, and XPC), Gould, HP (9000 series 200, 300 or 800 (Spectrum)
  752. but not series 500), HLH Orion 1/05, IBM (RT/PC running 4.2 and AIX;
  753. PS2 running AIX), Integrated Solutions (Optimum V with 68020 and
  754. VMEbus), Intel 80386 (BSD, SysV, and Xenix; not MS-DOS), Iris (2500,
  755. 2500 Turbo, and 4D), LMI (Nu), Masscomp, Megatest, MIPS, NCR (Tower
  756. 32), Nixdorf Targon 31, Plexus, Prime, Pyramid, Sequent (Balance and
  757. Symmetry), SONY News, Stride (system release 2), Sun (1, 2, 3, 4,
  758. SparcStation, and 386i), Tahoe, Tektronix (NS32000 system &#38; 4300),
  759. Texas Instruments (Nu), and Whitechapel (MG1).<P>
  760. GNU Emacs is described by the <CITE>GNU Emacs Manual</CITE>, which comes with
  761. the software in Texinfo form. See "GNU Documentation" above.<P>
  762. <LI>
  763. <B>GNU Emacs Lisp Reference Manual</B>
  764. <P>
  765. We will publish the <CITE>GNU Emacs Lisp Reference Manual</CITE> and put the
  766. Texinfo source on the release tape in March 1990. The manual
  767. describes the GNU Emacs Lisp programming language in detail and is for
  768. those interested in programming in GNU Emacs Lisp.
  769. <P>
  770. <LI>
  771. <B>Debugger</B>
  772. <P>
  773. GDB 2.8 (GNU's Debugger) is the source-level C debugger written in 1986.
  774. It offers many features not usually found in debuggers on Unix, such as
  775. Emacs-style command history and substitution, a history that records all
  776. values examined within the debugger for concise later reference,
  777. multi-line user-defined commands, and good self-documentation.<P>
  778. GDB 2.8 currently runs on Vaxes under 4.2 and 4.3bsd, on Sun 3 under
  779. systems version 2, 3 and 4, on the SPARC (Sun 4) under systems version
  780. 3.2 and 4.0, HP9K320, ISI, Merlin, SONY News, Gould NPL and PN, i386,
  781. and on some 32000 systems. GDB 3.<CODE>*</CODE> supports more systems and has
  782. some additional features; see "Contents of the Beta Test Tape"
  783. below.<P>
  784. On-line help and a Texinfo manual for GDB comes with the software (see
  785. "GNU Documentation" above).<P>
  786. <LI>
  787. <B>Bison</B>
  788. <P>
  789. Bison is an upwardly compatible replacement parser generator for Yacc,
  790. with additional features. It has been in use for several years. Bison
  791. is used for compiling GNU C, so it is included on the GNU beta tape as
  792. well. The <CITE>Bison Manual</CITE> comes with the software in Texinfo form
  793. (see "GNU Documentation" above).<P>
  794. <LI>
  795. <B>X Window System, V10R4</B>
  796. <P>
  797. Version 10 of X Windows is distributed on the GNU Emacs tape; version 11
  798. (which is totally incompatible) is distributed on the two X11 tapes.
  799. GNU Emacs version 18.55 supports both versions 10 and 11.<P>
  800. <LI>
  801. <B>MIT Scheme</B>
  802. <P>
  803. <LI>
  804. <B>Yale T</B>
  805. <P>
  806. A variant of Scheme developed at Yale University, T is intended for
  807. production use in program development. T contains a native-code
  808. optimizing compiler that produces code that runs at speeds comparable to
  809. the running speeds of programs written in conventional languages. It
  810. runs on BSD Vaxes and a few types of 68020 systems. T is written in
  811. itself and cannot be bootstrapped without a binary (included), but it is
  812. great if you can use it. Some documentation is included.<P>
  813. <LI>
  814. <B><CODE>texi2roff</CODE></B>
  815. <P>
  816. <CODE>texi2roff</CODE> translates GNU Texinfo files into a format that can be
  817. printed by the Unix [nt]roff programs utilizing the mm, ms or me macro
  818. packages. It is included on both tapes so that people who don't have a
  819. copy of TeX can print out GNU documentation.<P>
  820. <LI>
  821. <B>GNU Chess and NetHack</B>
  822. <P>
  823. GNU chess is a chess program, now in its second major version. The
  824. first was written by Stuart Cracraft. The second was written and donated
  825. by John Stanback. If a successor is found that is significantly
  826. stronger, it could become the new GNU Chess. GNU chess has text-only
  827. and X display interfaces.<P>
  828. Hack is a display oriented adventure game similar to Rogue.<P>
  829. </UL>
  830. <P>
  831. <H3><A NAME="SEC19" HREF="bull8_toc.html#SEC19">Contents of the Beta Test Tape</A></H3>
  832. <P>
  833. The programs on this tape are all recent releases and can be considered
  834. to be at various stages of user testing. As always, we solicit your
  835. comments and bug reports. This tape is also known as the Compiler
  836. tape.<P>
  837. <UL>
  838. <LI>
  839. <B>GNU CC</B>
  840. <P>
  841. The GNU C compiler is a fairly portable optimizing compiler. It
  842. generates good code for the 32000, 680x0 (optionally with 68881/2),
  843. 80386, 860, 88000, Alliant, Convex, Tahoe, and Vax CPUs, and for these
  844. RISC CPUs: Pyramid, SPARC, and SPUR. The MIPS RISC CPU is also
  845. supported. Machines using these CPUs include 386 running AIX, Alliant
  846. FX/8, Altos 3068, Apollo 68000/68020 running Aegis, AT&#38;T 3B1, Convex C1
  847. and C2, DECstation 3100, DEC VAX, Encore MultiMax (NS32000), Genix
  848. NS32000, Harris HCX-7 and HCX-9, HP-UX 68000/68020, HP running BSD, IBM
  849. PS/2 running AIX, Intel 386, Iris MIPS machine, ISI 68000/68020, MIPS,
  850. NeXT, Pyramid, Sequent Balance (NS32000), Sequent Symmetry (i386), SONY
  851. News, Sun 2, Sun 3 (optionally with FPA), Sun 4, SparcStation, and
  852. Sun386i. The current version is 1.37. It supports full ANSI C as of
  853. the latest proposed standard.<P>
  854. Optimizations include automatic register allocation, common
  855. subexpression elimination, invariant code motion from loops, induction
  856. variable optimizations, constant propagation and copy propagation,
  857. delaying popping of function call arguments, tail recursion elimination,
  858. plus many local optimizations that are automatically deduced from the
  859. machine description.<P>
  860. Included with the compiler are Bison (also on the Emacs release tape),
  861. and the perfect hash-table generating utility (Gperf), plus the Texinfo
  862. source of the <CITE>GCC Manual</CITE>. This manual describes how to run and
  863. install the GNU C compiler, and how to port it to new processors. It
  864. describes new features and incompatibilities of the compiler, but people
  865. not familiar with C will also need a good book on C.<P>
  866. <LI>
  867. <B>Assembler and Object File Utilities</B>
  868. <P>
  869. The GNU assembler (GAS) is a fairly portable, one pass assembler that is
  870. almost twice as fast as Unix <CODE>as</CODE>. It now works for 32x32, 680x0,
  871. 80386, Sparc (Sun 4), and Vax.<P>
  872. We have free versions of <CODE>ar</CODE>, <CODE>ld</CODE>, <CODE>nm</CODE>, <CODE>size</CODE>,
  873. <CODE>gprof</CODE>, <CODE>strip</CODE>, and <CODE>ranlib</CODE>.<P>
  874. The GNU linker <CODE>ld</CODE> runs significantly faster than the BSD version.
  875. Our <CODE>ld</CODE> is the only one that will give you source-line numbered
  876. error messages for multiply-defined symbols and undefined
  877. references.<P>
  878. <LI>
  879. <B>COFF Support</B>
  880. <P>
  881. It is possible to run the entire suite of GNU software tools on
  882. System V, replacing COFF entirely. First you install the GNU compiler,
  883. assembler, linker and other utilities. Then you use the program
  884. <CODE>robotussin</CODE>---COFF medicine for your computer--to convert the
  885. system libraries from COFF format to GNU (i.e. BSD) format.<P>
  886. When you compile programs, you will get ordinary GNU/BSD object files.
  887. Linking these with the GNU linker will produce GNU/BSD executables with
  888. a COFF header that the kernel will accept. The other GNU utilities such
  889. as <CODE>size</CODE>, <CODE>nm</CODE> and <CODE>strip</CODE> know how to operate on these
  890. encapsulated files.<P>
  891. As true COFF support is peripheral to the GNU project, please don't ask
  892. us to expend effort on it.<P>
  893. <LI>
  894. <B><CODE>make</CODE></B>
  895. <P>
  896. GNU make includes almost all the features from the BSD, System V, and
  897. POSIX makes, as well many of our own extensions, such as parallelism,
  898. conditional execution, and text manipulation. Texinfo source for a
  899. manual is provided; see "GNU documentation" above.<P>
  900. <LI>
  901. <B>Debugger</B>
  902. <P>
  903. Version 3.<CODE>*</CODE> of GDB, the GNU debugger, runs under BSD 4.2 and 4.3
  904. on Vaxes and Suns (2, 3, and 4), Convex, HP 9000/300's under BSD, HP
  905. 9000/320's under HPUX, System V 386 machines (with either GNU or native
  906. object file format), ISI Optimum V, Merlin under Utek 2.1, SONY News,
  907. Gould NPL and PN machines, Sequent Symmetry (a 386 based machine),
  908. Altos, and Encores under Umax 4.2.<P>
  909. GDB features incremental reading of symbol tables (for fast startup and
  910. less memory use), command-line editing, the ability to call functions in
  911. the program being debugged, a value history, and user-defined commands.
  912. It can be used to debug C, C<CODE>++</CODE>, and FORTRAN programs.<P>
  913. GDB also provides for remote debugging over a serial line. Remote
  914. debugging is the most convenient way to develop software for systems
  915. which are too small to run a debugger; it allows you to have the
  916. features of GDB at your disposal even on such systems.<P>
  917. <LI>
  918. <B>GAWK, FLEX and <CODE>tar</CODE></B>
  919. <P>
  920. GAWK is GNU's version of the Unix AWK utility; it comes with a Texinfo
  921. manual (see "GNU Documentation" above). FLEX is a mostly-compatible
  922. replacement for the Unix <CODE>lex</CODE> scanner generator written by Vern
  923. Paxson of the Lawrence Berkeley Laboratory. FLEX generates far more
  924. efficient scanners than <CODE>lex</CODE> does. GNU <CODE>tar</CODE> includes
  925. multivolume support, the ability to archive sparse files, automatic
  926. compression and decompression of archives, remote archives, and special
  927. features to allow <CODE>tar</CODE> to be used for incremental and full backups
  928. of file systems.<P>
  929. <LI>
  930. <B>Freed Files from the U.C. Berkeley 4.3-tahoe Release</B>
  931. <P>
  932. These files have been declared by Berkeley to be free of AT&#38;T code, and
  933. may be freely redistributed. They include complete sources for some
  934. utility programs, games, library routines and partial sources for many
  935. others.<P>
  936. <LI>
  937. <B>RCS</B>
  938. <P>
  939. The latest version of the Revision Control System for version control
  940. and management of large software projects.<P>
  941. <LI>
  942. <B>CVS</B>
  943. <P>
  944. CVS, the Concurrent Version System written by Brian Berliner, manages
  945. software revision and release control in a multi-developer,
  946. multi-directory, multi-group environment. It is designed to work on top
  947. of RCS Version 4, but will parse older RCS formats with the loss of
  948. CVS's fancier features. For further details, see Berliner, Brian,
  949. <CITE>CVS-II: Parallelizing Software Development,</CITE> Proceedings of the
  950. Winter 1990 USENIX Association Conference.<P>
  951. <LI>
  952. <B>BASH</B>
  953. <P>
  954. The GNU Shell, Bash (for Bourne Again SHell), provides compatibility
  955. with the Unix <CODE>sh</CODE> and provides many extensions found in <CODE>csh</CODE>
  956. and <CODE>ksh</CODE>. It has job control, <CODE>csh</CODE>-style command history,
  957. command-line editing (with Emacs and vi modes built-in and the ability
  958. to rebind keys).<P>
  959. <LI>
  960. <B><CODE>diff</CODE> and <CODE>grep</CODE></B>
  961. <P>
  962. These programs are GNU's versions of the Unix programs of the same name.
  963. They are much faster than their Unix counterparts.<P>
  964. <LI>
  965. <B>Ghostscript and <CODE>gnuplot</CODE></B>
  966. <P>
  967. Ghostscript is GNU's graphics language. It is almost fully compatible
  968. with the PostScript language. It supports X version 11. Right now,
  969. Ghostscript will accept commands in Postscript and execute them by
  970. drawing on an X window.<P>
  971. Ghostscript also includes a C-callable graphics library (for client
  972. programs that don't want to deal with the Postscript language), and also
  973. supports IBM PCs and compatibles with EGA graphics (but please don't ask
  974. the FSF staff any questions about this; we don't use PCs and don't have
  975. time to learn anything about them).<P>
  976. <CODE>gnuplot</CODE> is an interactive program for plotting mathematical
  977. expressions and data. Oddly enough, the program was neither done for
  978. nor named for the GNU Project--the name is a coincidence. However, we
  979. are distributing it anyway. If you can put us in contact with the
  980. author of this program, please do!<P>
  981. <LI>
  982. <B><CODE>g++</CODE>, <CODE>libg++</CODE>, NIH Class Library, and InterViews</B>
  983. <P>
  984. G<CODE>++</CODE> is a set of changes for GCC that compiles C<CODE>++</CODE>, the
  985. well-known object-oriented language. This was the first compiler to
  986. compile C<CODE>++</CODE> directly instead of preprocessing it into C, with
  987. great benefits for debugging and efficiency. G<CODE>++</CODE> also was first
  988. with multiple inheritance and other new features later released by AT&#38;T
  989. in <CODE>cfront 2.0</CODE>. Since G<CODE>++</CODE> depends on GCC, it must be used
  990. with the correspondingly numbered version of GCC. GDB version
  991. 3.<CODE>*</CODE> includes support for debugging C<CODE>++</CODE> code, which merges
  992. in the functionality of the old program GDB<CODE>+</CODE>.<P>
  993. <CODE>libg++</CODE> (the GNU C<CODE>++</CODE> library) is an extensive and
  994. documented collection of C<CODE>++</CODE> classes and support tools for
  995. use with G<CODE>++</CODE>.<P>
  996. The NIH Class Library (formerly known as OOPS (Object-Oriented Program
  997. Support)) is a portable collection of classes similar to those in
  998. Smalltalk-80 that has been developed by Keith Gorlen of NIH, using the
  999. C<CODE>++</CODE> programming language.<P>
  1000. InterViews is an object-oriented, C<CODE>++</CODE> library to support the
  1001. design and implementation of window-based user interfaces for X11.<P>
  1002. <LI>
  1003. <B>GnuGo</B>
  1004. <P>
  1005. GnuGo allows the user to play the machine in a game of Go (Wei-Chi). It
  1006. is an updated version of the program called Hugo.<P>
  1007. </UL>
  1008. <P>
  1009. <H3><A NAME="SEC20" HREF="bull8_toc.html#SEC20">Contents of the X11 Tapes</A></H3>
  1010. <P>
  1011. The two X11 tapes contain Version 11, Release 4 of the MIT X window
  1012. system. X11 is more powerful than, but incompatible with, the
  1013. no-longer-supported Version 10.<P>
  1014. The first FSF tape contains the contents of both tape one and tape two
  1015. from the MIT X Consortium: the core software and documentation, and the
  1016. contributed clients. FSF refers to its first tape as the `required' X
  1017. tape since it is necessary for running X or GNU Emacs under X. (The
  1018. Consortium refers to its first two tapes as the `required/recommended'
  1019. tapes.)
  1020. <P>
  1021. The second, `optional' FSF tape contains the contents of tapes three and
  1022. four from the MIT X Consortium: contributed libraries and other
  1023. toolkits, the Andrew software, games, etc. (The Consortium refers to
  1024. its last two tapes as `optional' tapes.)<P>
  1025. <H3><A NAME="SEC21" HREF="bull8_toc.html#SEC21">VMS Emacs and Compiler Tapes</A></H3>
  1026. <P>
  1027. We offer a VMS tape of the GNU Emacs editor, and a separate VMS tape
  1028. containing the beta-test GNU C compiler. The VMS compiler tape also
  1029. contains Bison (needed to compile GCC), GAS (needed to assemble GCC's
  1030. output) and some library and include files. Both VMS tapes include
  1031. executables that you can bootstrap from.<P>
  1032. Note that the DEC VMS C compiler has bugs and thus cannot compile GNU
  1033. C.<P>
  1034. Please don't ask us to devote effort to additional VMS support, because
  1035. it is peripheral to the GNU project.<P>
  1036. <H1><A NAME="SEC22" HREF="bull8_toc.html#SEC22">How to Get GNU Software</A></H1>
  1037. <P>
  1038. All the software and publications from the Free Software Foundation are
  1039. distributed with permission to copy and redistribute. The easiest way
  1040. to get GNU software is to copy it from someone else who has it.<P>
  1041. If you have access to the Internet, you can get the latest software from
  1042. the host <TT>`prep.ai.mit.edu'</TT>. For more information, read the file
  1043. <TT>`/u/emacs/GETTING.GNU.SOFTWARE'</TT> on that host. Please note that the
  1044. internet address of <TT>`prep'</TT> has changed to <CODE>18.71.0.38</CODE>.<P>
  1045. If you cannot get the software from a friend or over the net, or if you
  1046. would like to contribute some funds to our efforts and receive the
  1047. latest versions, the Free Software Foundation distributes tapes for a
  1048. copying and distribution fee. See the order form on the inside back
  1049. cover.<P>
  1050. There are also third party groups that distribute our software: people
  1051. and organizations that do not work with us, but have our software in
  1052. other forms. For your convenience, some of them are listed below.
  1053. Please note that the Free Software Foundation is <I>not</I> affiliated with
  1054. them in any way, and is not responsible for either the currency of their
  1055. versions or the swiftness of their responses.<P>
  1056. These Internet sites provide GNU software for anonymous FTP:<P>
  1057. <PRE>
  1058. scam.berkeley.edu, itstd.sri.com, wuarchive.wustl.edu,
  1059. wsmr-simtel20.army.mil (under <TT>`PD:&#60;UNIX.GNU&#62;'</TT>), bu.edu,
  1060. bu-it.bu.edu, louie.udel.edu, nic.nyser.net, sauna.hut.fi,
  1061. sunic.sunet.se, freja.diku.dk, ftp.cs.titech.ac.jp,
  1062. cc.utah.edu (VMS GNU Emacs), and uunet.uu.net.
  1063. </PRE>
  1064. <P>
  1065. Those on the SPAN network can ask <TT>rdss::corbet</TT>.<P>
  1066. Information on how to obtain some GNU programs using UUCP is available via
  1067. electronic mail from:<P>
  1068. <PRE>
  1069. hao!scicom!qetzal!upba!ugn!nepa!denny, acornrc!bob,
  1070. hqda-ai!merlin, ames!killer!wisner, uunet!hutch!barber,
  1071. mit-eddie!bloom-beacon!ht!spt!gz, sun!nosun!illian!darylm,
  1072. oli-stl!root, or info@uunet.uu.net.
  1073. </PRE>
  1074. <P>
  1075. Ohio State also makes GNU programs available via UUCP. They post their
  1076. instructions monthly to newsgroup <CODE>comp.sources.d</CODE> on USENET.
  1077. Current details from Karl Kleinpaste <CODE>karl@tut.cis.ohio-state.edu</CODE>
  1078. or <CODE>...!osu-cis!karl</CODE>.<P>
  1079. Information on getting floppy disks of GNU Emacs for the AT&#38;T Unix PC
  1080. (aka 3B1 or PC7300) is available from: <CODE>brant@manta.pha.pa.us</CODE> or
  1081. <CODE>...!bpa!manta!brant</CODE>.<P>
  1082. <H1><A NAME="SEC23" HREF="bull8_toc.html#SEC23">Thank GNUs</A></H1>
  1083. <P>
  1084. Thanks to the <B>Japanese Unix Society</B> for their donation of
  1085. $10,000.<P>
  1086. Thanks to our <B>Anonymous Contributor</B>, and thanks to
  1087. <B>Hewlett-Packard</B> for their donations of a $100,000 each.<P>
  1088. Thanks to <B>Hewlett-Packard</B> for their donation of six 68030
  1089. machines.<P>
  1090. Thanks to all those mentioned in GNUs Flashes and the GNU Project Status
  1091. Report.<P>
  1092. Thanks to <B>Bil Lewis</B>, <B>Dan LaLiberte</B>, and the volunteers who
  1093. have proofread drafts and suggested improvements to the <CITE>Emacs
  1094. Lisp Reference Manual</CITE>; and thanks to <B>Warren Hunt</B> of <B>Computer
  1095. Logic Inc.</B> for support.
  1096. <P>
  1097. Thanks to the <B>MIT Laboratory for Computer Science</B>, and its director,
  1098. <B>Professor Michael Dertouzos</B>. LCS has provided FSF with the loan of
  1099. a Microvax for program development.<P>
  1100. Thanks to the <B>MIT Artificial Intelligence Laboratory</B> for invaluable
  1101. assistance of many kinds.<P>
  1102. Thanks to <B>Arnold Robbins</B> and <B>Dave Trueman</B> for their continued
  1103. work on <CODE>gawk</CODE> and the <CODE>gawk</CODE> manual.<P>
  1104. Thanks to <B>Brian Kernighan</B> of <B>AT&#38;T Bell Labs</B> for invaluable assistance
  1105. during the testing and debugging of <CODE>gawk</CODE>, and for help in
  1106. clarifying several points about the language.<P>
  1107. Thanks to <B>Chris Welty</B> and the <B>Computer Science Department</B> at
  1108. <B>Rensselaer Polytechnic Institute</B> for splitting Dave Lawrence's salary
  1109. with FSF and providing him computing facilities.<P>
  1110. Thanks to <B>Prof. Christof Koch</B> and the <B>CNS Lab</B> at <B>Caltech</B> for
  1111. their support of Brian Fox and the use of their facilities.<P>
  1112. Thanks to the <B>University of Minnesota Department of Computer Science</B>
  1113. for allowing Mike Haertel to use their computers.<P>
  1114. Thanks to <B>Information Systems</B> and the <B>Whitaker College Computing
  1115. Facility</B> at <B>MIT</B> for use of their machines for making our VMS master
  1116. tapes.<P>
  1117. Thanks go out to all those who have either lent or donated us machines,
  1118. including <B>Brewster Kahle</B> of Thinking Machines Corp. (TMC) for the
  1119. Sun 4/110, <B>K. Richard Magill</B> for the AT&#38;T Unix PC, <B>Doug Blewett</B>
  1120. of AT&#38;T Bell Labs for two Convergent Miniframes, CMU's <B>Mach Project</B>
  1121. for the Sun 3/60, <B>Intel Corp.</B> for their 386 workstation, <B>NeXT</B>
  1122. for a NeXT workstation, the <B>MIT Media Laboratory</B> for the
  1123. Hewlett-Packard 68020 machine, and <B>SONY Corp.</B> and <B>Software
  1124. Research Associates</B>, Inc., both of Tokyo, for the SONY News
  1125. workstations.<P>
  1126. Thanks to all those who have contributed ports and extensions, as well as
  1127. those who have contributed other source code, documentation, and good bug
  1128. reports.<P>
  1129. Thanks to those who sent money and offered help. Thanks also to those
  1130. who support us by ordering manuals and distribution tapes.<P>
  1131. <HR>
  1132. <P>
  1133. <PRE>
  1134. -------
  1135. | |
  1136. Free Software Foundation, Inc. | stamp |
  1137. 675 Massachusetts Avenue | |
  1138. Cambridge, MA 02139 USA | here |
  1139. | |
  1140. -------
  1141. </PRE>
  1142. <P>
  1143. <HR>
  1144. <P>