begin.txt 5.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138
  1. Message-Id: <9204131416.AA28109@cs.kun.nl>
  2. To: usenet.hist@weber.ucsd.edu
  3. Cc: lwj@cs.kun.nl
  4. From: Luc Rooijakkers <lwj@cs.kun.nl>
  5. Subject: GNU announcement
  6. Date: Mon, 13 Apr 92 16:16:30 +0200
  7. Sender: lwj@cs.kun.nl
  8. Is someone interested in this? I didn't get anything else from Rich, so
  9. presumably he hasn't got more. Didn't rms get flamed for this? One would
  10. expect so, but perhaps usenet was a nicer place in those days (I wasn't
  11. there yet by a long shot).
  12. ------- Forwarded Message
  13. From: rsk@gynko.circ.upenn.edu (Rich Kulawiec)
  14. Message-Id: <9203041402.AA10807@gynko.circ.upenn.edu>
  15. Subject: Re: Gnu/OS (was Re: UP)
  16. To: lwj@cs.kun.nl
  17. Date: Wed, 4 Mar 92 9:02:31 EST
  18. Organization: Cardiothoracic Imaging Research Center
  19. >Could you possible send me the complete message? I would like to read it
  20. >in its entirety. If you have additional discussion (responses etc) on
  21. >that subject I would like to read those too.
  22. Sure, no problem. I knew there was a reason I kept this all these years! :-)
  23. I'll also check through the archives to see if I have any of the contemporary
  24. comments on it -- a quick scan this morning over coffee didn't reveal anything,
  25. but I was barely awake, so perhaps I should try again when I'm more alive.
  26. Cheers,
  27. Rich
  28. > From CSvax:pur-ee:inuxc!ixn5c!ihnp4!houxm!mhuxi!eagle!mit-vax!mit-eddie!RMS@MIT-OZ
  29. > From: RMS%MIT-OZ@mit-eddie
  30. > Newsgroups: net.unix-wizards,net.usoft
  31. > Subject: new UNIX implementation
  32. > Date: Tue, 27-Sep-83 12:35:59 EST
  33. > Organization: MIT AI Lab, Cambridge, MA
  34. >
  35. > Free Unix!
  36. >
  37. > Starting this Thanksgiving I am going to write a complete
  38. > Unix-compatible software system called GNU (for Gnu's Not Unix), and
  39. > give it away free to everyone who can use it. Contributions of time,
  40. > money, programs and equipment are greatly needed.
  41. >
  42. > To begin with, GNU will be a kernel plus all the utilities needed to
  43. > write and run C programs: editor, shell, C compiler, linker,
  44. > assembler, and a few other things. After this we will add a text
  45. > formatter, a YACC, an Empire game, a spreadsheet, and hundreds of
  46. > other things. We hope to supply, eventually, everything useful that
  47. > normally comes with a Unix system, and anything else useful, including
  48. > on-line and hardcopy documentation.
  49. >
  50. > GNU will be able to run Unix programs, but will not be identical
  51. > to Unix. We will make all improvements that are convenient, based
  52. > on our experience with other operating systems. In particular,
  53. > we plan to have longer filenames, file version numbers, a crashproof
  54. > file system, filename completion perhaps, terminal-independent
  55. > display support, and eventually a Lisp-based window system through
  56. > which several Lisp programs and ordinary Unix programs can share a screen.
  57. > Both C and Lisp will be available as system programming languages.
  58. > We will have network software based on MIT's chaosnet protocol,
  59. > far superior to UUCP. We may also have something compatible
  60. > with UUCP.
  61. >
  62. >
  63. > Who Am I?
  64. >
  65. > I am Richard Stallman, inventor of the original much-imitated EMACS
  66. > editor, now at the Artificial Intelligence Lab at MIT. I have worked
  67. > extensively on compilers, editors, debuggers, command interpreters, the
  68. > Incompatible Timesharing System and the Lisp Machine operating system.
  69. > I pioneered terminal-independent display support in ITS. In addition I
  70. > have implemented one crashproof file system and two window systems for
  71. > Lisp machines.
  72. >
  73. >
  74. > Why I Must Write GNU
  75. >
  76. > I consider that the golden rule requires that if I like a program I
  77. > must share it with other people who like it. I cannot in good
  78. > conscience sign a nondisclosure agreement or a software license
  79. > agreement.
  80. >
  81. > So that I can continue to use computers without violating my principles,
  82. > I have decided to put together a sufficient body of free software so that
  83. > I will be able to get along without any software that is not free.
  84. >
  85. >
  86. > How You Can Contribute
  87. >
  88. > I am asking computer manufacturers for donations of machines and money.
  89. > I'm asking individuals for donations of programs and work.
  90. >
  91. > One computer manufacturer has already offered to provide a machine. But
  92. > we could use more. One consequence you can expect if you donate
  93. > machines is that GNU will run on them at an early date. The machine had
  94. > better be able to operate in a residential area, and not require
  95. > sophisticated cooling or power.
  96. >
  97. > Individual programmers can contribute by writing a compatible duplicate
  98. > of some Unix utility and giving it to me. For most projects, such
  99. > part-time distributed work would be very hard to coordinate; the
  100. > independently-written parts would not work together. But for the
  101. > particular task of replacing Unix, this problem is absent. Most
  102. > interface specifications are fixed by Unix compatibility. If each
  103. > contribution works with the rest of Unix, it will probably work
  104. > with the rest of GNU.
  105. >
  106. > If I get donations of money, I may be able to hire a few people full or
  107. > part time. The salary won't be high, but I'm looking for people for
  108. > whom knowing they are helping humanity is as important as money. I view
  109. > this as a way of enabling dedicated people to devote their full energies to
  110. > working on GNU by sparing them the need to make a living in another way.
  111. >
  112. >
  113. > For more information, contact me.
  114. > Arpanet mail:
  115. > RMS@MIT-MC.ARPA
  116. >
  117. > Usenet:
  118. > ...!mit-eddie!RMS@OZ
  119. > ...!mit-vax!RMS@OZ
  120. >
  121. > US Snail:
  122. > Richard Stallman
  123. > 166 Prospect St
  124. > Cambridge, MA 02139
  125. >
  126. >
  127. ------- End of Forwarded Message