new

Article View: gnu.misc.discuss

Article #74960

#74960

From: Leonard H. Tower Jr.
Date: Tue, 08 Jan 1991 19:21

2105 lines
96975 bytes

id AA15641; Mon, 7 Jan 91 20:40:33 -0500
Errors-To: gnu-misc-discuss-request@cis.ohio-state.edu
Sender: gnu-misc-discuss-request@cis.ohio-state.edu
Received: by tut.cis.ohio-state.edu (5.61-kk/5.910105)
id AA15573; Mon, 7 Jan 91 20:37:45 -0500
Received: from USENET by tut.cis.ohio-state.edu with netnews
for gnu-misc-discuss@tut.cis.ohio-state.edu
(gnu-misc-discuss@tut.cis.ohio-state.edu) (contact
usenet@tut.cis.ohio-state.edu if you have questions)
Date: 7 Jan 91 23:11:03 GMT
From: inuy@vax5.cit.cornell.edu
Subject: new
Message-Id: <1991Jan7.191103.1904@vax5.cit.cornell.edu>
To: gnu-misc-discuss@cis.ohio-state.edu

Please forgive me if this is not the best place for this, but can
someone pleas fill me in on exactley what the GNU project and the
free software foundation are? All of this sounds interesting to
me.

--Matthew

PS: Please email your reply as I do not regularley read this area..Thanks!

enjoy -len

PS: By the way, what do you think of look-and-feel lawsuits?
----------------------------------------------------------------------
Trust you won't be bothered by the canned reply. Individual requests
have a lower priority than work that benefits everybody. Consider it
a contribution on your part to the GNU Project. The following are
appended:

GNU Manifesto
GNU General Public License
Description of GNU Mailing Lists
Getting GNU Software
FTPing/UUCPing GNU Software and Documentation
Mail Ordering GNU Software and Documentation

Each section is separated by a row of hyphens.
----------------------------------------------------------------------
The GNU Manifesto

What's GNU? Gnu's Not Unix!

GNU, which stands for Gnu's Not Unix, is the name for the complete
Unix-compatible software system which I am writing so that I can give it
away free to everyone who can use it. Several other volunteers are helping
me. Contributions of time, money, programs and equipment are greatly
needed.

So far we have an Emacs text editor with Lisp for writing editor commands,
a source level debugger, a yacc-compatible parser generator, a linker, and
around 35 utilities. A shell (command interpreter) is nearly completed. A
new portable optimizing C compiler has compiled itself and may be released
this year. An initial kernel exists but many more features are needed to
emulate Unix. When the kernel and compiler are finished, it will be
possible to distribute a GNU system suitable for program development. We
will use @TeX{} as our text formatter, but an nroff is being worked on. We
will use the free, portable X window system as well. After this we will
add a portable Common Lisp, an Empire game, a spreadsheet, and hundreds of
other things, plus on-line documentation. We hope to supply, eventually,
everything useful that normally comes with a Unix system, and more.

GNU will be able to run Unix programs, but will not be identical to Unix.
We will make all improvements that are convenient, based on our experience
with other operating systems. In particular, we plan to have longer
filenames, file version numbers, a crashproof file system, filename
completion perhaps, terminal-independent display support, and perhaps
eventually a Lisp-based window system through which several Lisp programs
and ordinary Unix programs can share a screen. Both C and Lisp will be
available as system programming languages. We will try to support UUCP,
MIT Chaosnet, and Internet protocols for communication.

GNU is aimed initially at machines in the 68000/16000 class with virtual
memory, because they are the easiest machines to make it run on. The extra
effort to make it run on smaller machines will be left to someone who wants
to use it on them.

To avoid horrible confusion, please pronounce the `G' in the word `GNU'
when it is the name of this project.

Who Am I?

I am Richard Stallman, inventor of the original much-imitated EMACS editor,
formerly at the Artificial Intelligence Lab at MIT. I have worked
extensively on compilers, editors, debuggers, command interpreters, the
Incompatible Timesharing System and the Lisp Machine operating system. I
pioneered terminal-independent display support in ITS. Since then I have
implemented one crashproof file system and two window systems for Lisp
machines, and designed a third window system now being implemented; this
one will be ported to many systems including use in GNU. [Historical note:
The window system project was not completed; GNU now plans to use the
X window system.]

Why I Must Write GNU

I consider that the golden rule requires that if I like a program I must
share it with other people who like it. Software sellers want to divide
the users and conquer them, making each user agree not to share with
others. I refuse to break solidarity with other users in this way. I
cannot in good conscience sign a nondisclosure agreement or a software
license agreement. For years I worked within the Artificial Intelligence
Lab to resist such tendencies and other inhospitalities, but eventually
they had gone too far: I could not remain in an institution where such
things are done for me against my will.

So that I can continue to use computers without dishonor, I have decided to
put together a sufficient body of free software so that I will be able to
get along without any software that is not free. I have resigned from the
AI lab to deny MIT any legal excuse to prevent me from giving GNU away.

Why GNU Will Be Compatible with Unix

Unix is not my ideal system, but it is not too bad. The essential features
of Unix seem to be good ones, and I think I can fill in what Unix lacks
without spoiling them. And a system compatible with Unix would be
convenient for many other people to adopt.

How GNU Will Be Available

GNU is not in the public domain. Everyone will be permitted to modify and
redistribute GNU, but no distributor will be allowed to restrict its
further redistribution. That is to say, proprietary modifications will not
be allowed. I want to make sure that all versions of GNU remain free.

Why Many Other Programmers Want to Help

I have found many other programmers who are excited about GNU and want to
help.

Many programmers are unhappy about the commercialization of system
software. It may enable them to make more money, but it requires them to
feel in conflict with other programmers in general rather than feel as
comrades. The fundamental act of friendship among programmers is the
sharing of programs; marketing arrangements now typically used essentially
forbid programmers to treat others as friends. The purchaser of software
must choose between friendship and obeying the law. Naturally, many decide
that friendship is more important. But those who believe in law often do
not feel at ease with either choice. They become cynical and think that
programming is just a way of making money.

By working on and using GNU rather than proprietary programs, we can be
hospitable to everyone and obey the law. In addition, GNU serves as an
example to inspire and a banner to rally others to join us in sharing.
This can give us a feeling of harmony which is impossible if we use
software that is not free. For about half the programmers I talk to, this
is an important happiness that money cannot replace.

How You Can Contribute

I am asking computer manufacturers for donations of machines and money.
I'm asking individuals for donations of programs and work.

One consequence you can expect if you donate machines is that GNU will run
on them at an early date. The machines should be complete, ready to use
systems, approved for use in a residential area, and not in need of
sophisticated cooling or power.

I have found very many programmers eager to contribute part-time work for
GNU. For most projects, such part-time distributed work would be very hard
to coordinate; the independently-written parts would not work together.
But for the particular task of replacing Unix, this problem is absent. A
complete Unix system contains hundreds of utility programs, each of which
is documented separately. Most interface specifications are fixed by Unix
compatibility. If each contributor can write a compatible replacement for
a single Unix utility, and make it work properly in place of the original
on a Unix system, then these utilities will work right when put together.
Even allowing for Murphy to create a few unexpected problems, assembling
these components will be a feasible task. (The kernel will require closer
communication and will be worked on by a small, tight group.)

If I get donations of money, I may be able to hire a few people full or
part time. The salary won't be high by programmers' standards, but I'm
looking for people for whom building community spirit is as important as
making money. I view this as a way of enabling dedicated people to devote
their full energies to working on GNU by sparing them the need to make a
living in another way.

Why All Computer Users Will Benefit

Once GNU is written, everyone will be able to obtain good system software
free, just like air.

This means much more than just saving everyone the price of a Unix license.
It means that much wasteful duplication of system programming effort will
be avoided. This effort can go instead into advancing the state of the
art.

Complete system sources will be available to everyone. As a result, a user
who needs changes in the system will always be free to make them himself,
or hire any available programmer or company to make them for him. Users
will no longer be at the mercy of one programmer or company which owns the
sources and is in sole position to make changes.

Schools will be able to provide a much more educational environment by
encouraging all students to study and improve the system code. Harvard's
computer lab used to have the policy that no program could be installed on
the system if its sources were not on public display, and upheld it by
actually refusing to install certain programs. I was very much inspired by
this.

Finally, the overhead of considering who owns the system software and what
one is or is not entitled to do with it will be lifted.

Arrangements to make people pay for using a program, including licensing of
copies, always incur a tremendous cost to society through the cumbersome
mechanisms necessary to figure out how much (that is, which programs) a
person must pay for. And only a police state can force everyone to obey
them. Consider a space station where air must be manufactured at great
cost: charging each breather per liter of air may be fair, but wearing the
metered gas mask all day and all night is intolerable even if everyone can
afford to pay the air bill. And the TV cameras everywhere to see if you
ever take the mask off are outrageous. It's better to support the air
plant with a head tax and chuck the masks.

Copying all or parts of a program is as natural to a programmer as
breathing, and as productive. It ought to be as free.

Some Easily Rebutted Objections to GNU's Goals

"Nobody will use it if it is free, because that means
they can't rely on any support."
"You have to charge for the program
to pay for providing the support."

If people would rather pay for GNU plus service than get GNU free without
service, a company to provide just service to people who have obtained GNU
free ought to be profitable.

We must distinguish between support in the form of real programming work
and mere handholding. The former is something one cannot rely on from a
software vendor. If your problem is not shared by enough people, the
vendor will tell you to get lost.

If your business needs to be able to rely on support, the only way is to
have all the necessary sources and tools. Then you can hire any available
person to fix your problem; you are not at the mercy of any individual.
With Unix, the price of sources puts this out of consideration for most
businesses. With GNU this will be easy. It is still possible for there to
be no available competent person, but this problem cannot be blamed on
distibution arrangements. GNU does not eliminate all the world's problems,
only some of them.

Meanwhile, the users who know nothing about computers need handholding:
doing things for them which they could easily do themselves but don't know
how.

Such services could be provided by companies that sell just hand-holding
and repair service. If it is true that users would rather spend money and
get a product with service, they will also be willing to buy the service
having got the product free. The service companies will compete in quality
and price; users will not be tied to any particular one. Meanwhile, those
of us who don't need the service should be able to use the program without
paying for the service.

"You cannot reach many people without advertising,
and you must charge for the program to support that."
"It's no use advertising a program people can get free."

There are various forms of free or very cheap publicity that can be used to
inform numbers of computer users about something like GNU. But it may be
true that one can reach more microcomputer users with advertising. If this
is really so, a business which advertises the service of copying and
mailing GNU for a fee ought to be successful enough to pay for its
advertising and more. This way, only the users who benefit from the
advertising pay for it.

On the other hand, if many people get GNU from their friends, and such
companies don't succeed, this will show that advertising was not really
necessary to spread GNU. Why is it that free market advocates don't want
to let the free market decide this?

"My company needs a proprietary operating system
to get a competitive edge."

GNU will remove operating system software from the realm of competition.
You will not be able to get an edge in this area, but neither will your
competitors be able to get an edge over you. You and they will compete in
other areas, while benefitting mutually in this one. If your business is
selling an operating system, you will not like GNU, but that's tough on
you. If your business is something else, GNU can save you from being
pushed into the expensive business of selling operating systems.

I would like to see GNU development supported by gifts from many
manufacturers and users, reducing the cost to each.

"Don't programmers deserve a reward for their creativity?"

If anything deserves a reward, it is social contribution. Creativity can
be a social contribution, but only in so far as society is free to use the
results. If programmers deserve to be rewarded for creating innovative
programs, by the same token they deserve to be punished if they restrict
the use of these programs.

"Shouldn't a programmer be able to ask for a reward for his creativity?"

There is nothing wrong with wanting pay for work, or seeking to maximize
one's income, as long as one does not use means that are destructive. But
the means customary in the field of software today are based on
destruction.

Extracting money from users of a program by restricting their use of it is
destructive because the restrictions reduce the amount and the ways that
the program can be used. This reduces the amount of wealth that humanity
derives from the program. When there is a deliberate choice to restrict,
the harmful consequences are deliberate destruction.

The reason a good citizen does not use such destructive means to become
wealthier is that, if everyone did so, we would all become poorer from the
mutual destructiveness. This is Kantian ethics; or, the Golden Rule.
Since I do not like the consequences that result if everyone hoards
information, I am required to consider it wrong for one to do so.
Specifically, the desire to be rewarded for one's creativity does not
justify depriving the world in general of all or part of that creativity.

"Won't programmers starve?"

I could answer that nobody is forced to be a programmer. Most of us cannot
manage to get any money for standing on the street and making faces. But
we are not, as a result, condemned to spend our lives standing on the
street making faces, and starving. We do something else.

But that is the wrong answer because it accepts the questioner's implicit
assumption: that without ownership of software, programmers cannot possibly
be paid a cent. Supposedly it is all or nothing.

The real reason programmers will not starve is that it will still be
possible for them to get paid for programming; just not paid as much as
now.

Restricting copying is not the only basis for business in software. It is
the most common basis because it brings in the most money. If it were
prohibited, or rejected by the customer, software business would move to
other bases of organization which are now used less often. There are
always numerous ways to organize any kind of business.

Probably programming will not be as lucrative on the new basis as it is
now. But that is not an argument against the change. It is not considered
an injustice that sales clerks make the salaries that they now do. If
programmers made the same, that would not be an injustice either. (In
practice they would still make considerably more than that.)

"Don't people have a right to control how their creativity is used?"

"Control over the use of one's ideas" really constitutes control over other
people's lives; and it is usually used to make their lives more difficult.

People who have studied the issue of intellectual property rights carefully
(such as lawyers) say that there is no intrinsic right to intellectual
property. The kinds of supposed intellectual property rights that the
government recognizes were created by specific acts of legislation for
specific purposes.

For example, the patent system was established to encourage inventors to
disclose the details of their inventions. Its purpose was to help society
rather than to help inventors. At the time, the life span of 17 years for
a patent was short compared with the rate of advance of the state of the
art. Since patents are an issue only among manufacturers, for whom the
cost and effort of a license agreement are small compared with setting up
production, the patents often do not do much harm. They do not obstruct
most individuals who use patented products.

The idea of copyright did not exist in ancient times, when authors
frequently copied other authors at length in works of non-fiction. This
practice was useful, and is the only way many authors' works have survived
even in part. The copyright system was created expressly for the purpose
of encouraging authorship. In the domain for which it was invented--books,
which could be copied economically only on a printing press--it did little
harm, and did not obstruct most of the individuals who read the books.

All intellectual property rights are just licenses granted by society
because it was thought, rightly or wrongly, that society as a whole would
benefit by granting them. But in any particular situation, we have to ask:
are we really better off granting such license? What kind of act are we
licensing a person to do?

The case of programs today is very different from that of books a hundred
years ago. The fact that the easiest way to copy a program is from one
neighbor to another, the fact that a program has both source code and
object code which are distinct, and the fact that a program is used rather
than read and enjoyed, combine to create a situation in which a person who
enforces a copyright is harming society as a whole both materially and
spiritually; in which a person should not do so regardless of whether the
law enables him to.

"Competition makes things get done better."

The paradigm of competition is a race: by rewarding the winner, we
encourage everyone to run faster. When capitalism really works this way,
it does a good job; but its defenders are wrong in assuming it always works
this way. If the runners forget why the reward is offered and become
intent on winning, no matter how, they may find other strategies--such as,
attacking other runners. If the runners get into a fist fight, they will
all finish late.

Proprietary and secret software is the moral equivalent of runners in a
fist fight. Sad to say, the only referee we've got does not seem to
object to fights; he just regulates them ("For every ten yards you run, you
are allowed one kick."). He really ought to break them up, and penalize
runners for even trying to fight.

"Won't everyone stop programming without a monetary incentive?"

Actually, many people will program with absolutely no monetary incentive.
Programming has an irresistible fascination for some people, usually the
people who are best at it. There is no shortage of professional musicians
who keep at it even though they have no hope of making a living that way.

But really this question, though commonly asked, is not appropriate to the
situation. Pay for programmers will not disappear, only become less. So
the right question is, will anyone program with a reduced monetary
incentive? My experience shows that they will.

For more than ten years, many of the world's best programmers worked at the
Artificial Intelligence Lab for far less money than they could have had
anywhere else. They got many kinds of non-monetary rewards: fame and
appreciation, for example. And creativity is also fun, a reward in itself.

Then most of them left when offered a chance to do the same interesting
work for a lot of money.

What the facts show is that people will program for reasons other than
riches; but if given a chance to make a lot of money as well, they will
come to expect and demand it. Low-paying organizations do poorly in
competition with high-paying ones, but they do not have to do badly if the
high-paying ones are banned.

"We need the programmers desperately. If they demand that we
stop helping our neighbors, we have to obey."

You're never so desperate that you have to obey this sort of demand.
Remember: millions for defense, but not a cent for tribute!

"Programmers need to make a living somehow."

In the short run, this is true. However, there are plenty of ways that
programmers could make a living without selling the right to use a program.
This way is customary now because it brings programmers and businessmen the
most money, not because it is the only way to make a living. It is easy to
find other ways if you want to find them. Here are a number of examples.

A manufacturer introducing a new computer will pay for the porting of
operating systems onto the new hardware.

The sale of teaching, hand-holding and maintenance services could also
employ programmers.

People with new ideas could distribute programs as freeware, asking for
donations from satisfied users, or selling hand-holding services. I have
met people who are already working this way successfully.

Users with related needs can form users' groups, and pay dues. A group
would contract with programming companies to write programs that the
group's members would like to use.

All sorts of development can be funded with a Software Tax:

Suppose everyone who buys a computer has to pay x percent of
the price as a software tax. The government gives this to
an agency like the NSF to spend on software development.

But if the computer buyer makes a donation to software development
himself, he can take a credit against the tax. He can donate to
the project of his own choosing--often, chosen because he hopes to
use the results when it is done. He can take a credit for any amount
of donation up to the total tax he had to pay.

The total tax rate could be decided by a vote of the payers of
the tax, weighted according to the amount they will be taxed on.

The consequences:
* the computer-using community supports software development.
* this community decides what level of support is needed.
* users who care which projects their share is spent on
can choose this for themselves.

In the long run, making programs free is a step toward the post-scarcity
world, where nobody will have to work very hard just to make a living.
People will be free to devote themselves to activities that are fun,
such as programming, after spending the necessary ten hours a week
on required tasks such as legislation, family counseling, robot
repair and asteroid prospecting. There will be no need to be able
to make a living from programming.

We have already greatly reduced the amount of work that the whole
society must do for its actual productivity, but only a little of this
has translated itself into leisure for workers because much
nonproductive activity is required to accompany productive activity.
The main causes of this are bureaucracy and isometric struggles
against competition. Free software will greatly reduce these
drains in the area of software production. We must do this,
in order for technical gains in productivity to translate into
less work for us.

Permission is granted to anyone to make or distribute verbatim copies
of this document as received, in any medium, provided that the
copyright notice and permission notice are preserved,
and that the distributor grants the recipient permission
for further redistribution as permitted by this notice.

Modified versions may not be made.

----------------------------------------------------------------------

GNU GENERAL PUBLIC LICENSE
Version 1, February 1989

Copyright (C) 1989 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.

Preamble

The license agreements of most software companies try to keep users
at the mercy of those companies. By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.

When we speak of free software, we are referring to freedom, not
price. Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.

For example, if you distribute copies of a such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must tell them their rights.

We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.

The precise terms and conditions for copying, distribution and
modification follow.

GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any program or other work which
contains a notice placed by the copyright holder saying it may be
distributed under the terms of this General Public License. The
"Program", below, refers to any such program or work, and a "work based
on the Program" means either the Program or any work containing the
Program or a portion of it, either verbatim or with modifications. Each
licensee is addressed as "you".

1. You may copy and distribute verbatim copies of the Program's source
code as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this
General Public License and to the absence of any warranty; and give any
other recipients of the Program a copy of this General Public License
along with the Program. You may charge a fee for the physical act of
transferring a copy.

2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:

a) cause the modified files to carry prominent notices stating that
you changed the files and the date of any change; and

b) cause the whole of any work that you distribute or publish, that
in whole or in part contains the Program or any part thereof, either
with or without modifications, to be licensed at no charge to all
third parties under the terms of this General Public License (except
that you may choose to grant warranty protection to some or all
third parties, at your option).

c) If the modified program normally reads commands interactively when
run, you must cause it, when started running for such interactive use
in the simplest and most usual way, to print or display an
announcement including an appropriate copyright notice and a notice
that there is no warranty (or else, saying that you provide a
warranty) and that users may redistribute the program under these
conditions, and telling the user how to view a copy of this General
Public License.

d) You may charge a fee for the physical act of transferring a
copy, and you may at your option offer warranty protection in
exchange for a fee.

Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.

3. You may copy and distribute the Program (or a portion or derivative of
it, under Paragraph 2) in object code or executable form under the terms of
Paragraphs 1 and 2 above provided that you also do one of the following:

a) accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of
Paragraphs 1 and 2 above; or,

b) accompany it with a written offer, valid for at least three
years, to give any third party free (except for a nominal charge
for the cost of distribution) a complete machine-readable copy of the
corresponding source code, to be distributed under the terms of
Paragraphs 1 and 2 above; or,

c) accompany it with the information you received as to where the
corresponding source code may be obtained. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form alone.)

Source code for a work means the preferred form of the work for making
modifications to it. For an executable file, complete source code means
all the source code for all modules it contains; but, as a special
exception, it need not include source code for modules which are standard
libraries that accompany the operating system on which the executable
file runs, or for standard header files or definitions files that
accompany that operating system.

4. You may not copy, modify, sublicense, distribute or transfer the
Program except as expressly provided under this General Public License.
Any attempt otherwise to copy, modify, sublicense, distribute or transfer
the Program is void, and will automatically terminate your rights to use
the Program under this License. However, parties who have received
copies, or rights to use copies, from you under this General Public
License will not have their licenses terminated so long as such parties
remain in full compliance.

5. By copying, distributing or modifying the Program (or any work based
on the Program) you indicate your acceptance of this license to do so,
and all its terms and conditions.

6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the original
licensor to copy, distribute or modify the Program subject to these
terms and conditions. You may not impose any further restrictions on the
recipients' exercise of the rights granted herein.

7. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.

Each version is given a distinguishing version number. If the Program
specifies a version number of the license which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
the license, you may choose any version ever published by the Free Software
Foundation.

8. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.

NO WARRANTY

9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.

10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

Appendix: How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.

To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>

This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 1, or (at your option)
any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) 19xx name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License. Of course, the
commands you use may be called something other than `show w' and `show
c'; they could even be mouse-clicks or menu items--whatever suits your
program.

You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the
program `Gnomovision' (a program to direct compilers to make passes
at assemblers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

That's all there is to it!
----------------------------------------------------------------------
GNU Project Electronic Mailing Lists. Last Updated 9 Nov 90

Please report improvements to: gnu@prep.ai.mit.edu

* GNU mailing lists are also distributed as USENET news groups

The mailing lists are gated both ways with the gnu.all newsgroups at
ohio-state.edu. The one-to-one correspondence is indicated below. If
you don't know if your site is on USENET, ask your system administrator.
If you are a USENET site and don't get the gnu.all newsgroups, please
ask your USENET administrator to get them. If he has your feeds ask
their feeds, you should win. And everyone else wins: newsgroups make
better use of the limited bandwidth of the computer networks and your
home machine than mailing list traffic; and staying off the mailing
lists make better use of the people who maintain the lists and the
machines that the GNU people working with rms use (i.e. we have more
time to produce code!!). Thanx.

* Getting the mailing lists directly

If several users at your site or local network want to read a list and
you aren't a USENET site, Project GNU would prefer that you would set up
one address that redistributes locally. This reduces overhead on our
people and machines, your gateway machine, and the network(s) used to
transport the mail from us to you.

* How to subscribe to and report bugs in mailing lists

Send messages ABOUT these lists, such as reports of mail problems, or
requests to be added or removed, to help-gnu-emacs-request (or
info-gnu-request, bug-gdb-request, etc.), NOT to info-gnu-emacs (or
info-gnu, etc.). These <LIST_NAME>-request addresses go only to the
people who can do something about your requests or problems, and thus
avoids disturbing everyone else.

Note that all GNU mailing lists are maintained by volunteers. They get
behind occasionally. Wait at least 3 or 4 days before asking again.
Thanks!

Many of the GNU mailing lists are very large and are received by many
people. Please don't send them anything that is not seriously important
to all their readers. All GNU mailing lists are unmoderated, mail
reflectors, except info-gnu, info-gnu-emacs, info-gcc and info-g++.

All addresses below are in internet format. Consult the mail guru for
your computer to figure out address syntaxes from other networks. From
UUCP machines:
..!ucbvax!prep.ai.mit.edu!ADDRESS
..!uunet!prep.ai.mit.edu!ADDRESS

If a message you mail to a list is returned from a MAILER-DAEMON (often
with the line:
----- Transcript of session follows -----
don't resend the message to the list. All this return means is that
your original message failed to reach a few addresses on the list. Such
messages are NEVER a reason to resend a piece of mail a 2nd time. This
just bothers all (less the few delivery failures (which will probably
just fail again!)) of the readers of the list with a message they have
already seen. It also wastes computer and network resources.

It is appropriate to send these to the -request address for a list, and
ask them to check the problem out.

* Send Specific Requests for Information to: gnu@prep.ai.mit.edu

Specific requests for information about obtaining GNU software, or GNU
activities in Cambridge and elsewhere can be directed to:
gnu@prep.ai.mit.edu

* General Information about all lists

Please keep each message under 40,000 characters. Some mailers bounce
messages that are longer than this.

Most of the time, when you reply to a message sent to a list, the reply
should not go to the list. But most mail reading programs supply, by
default, all the recipients of the original as recipients of the reply.
Make a point of deleting the list address from the header when it does
not belong. This prevents bothering all readers of a list, and reduces
network congestion.

* General Information about info-* lists

These lists and their newsgroups are meant for important announcements.
Most GNU projects info-* lists (and their corresponding gnu.*.announce
newsgroups) are moderated to keep their content significant and
relevant. If you have a bug to report, send it to the bug-* list. If
you need help on something else and the help-* list exists, ask it.

See section '* General Information about all lists'.

* General Information about help-* lists

These lists (and their newsgroups) exist for anyone to ask questions
about the GNU software that the list deals with. The lists are read by
people who are willing to take the time to help other users.

See section '* General Information about all lists'.

* General Information about bug-* lists and reporting program bugs

If you think something is a bug in a program, it might be one; or, it
might be a misunderstanding or even a feature. Before beginning to
report bugs, please read the section ``Reporting Emacs Bugs'' toward the
end of the GNU Emacs reference manual (or node Emacs/Bugs in Emacs's
built-in Info system) for a discussion of how and when to send in bug
reports. For GNU programs other than GNU Emacs, also consult their
documentation for their bug reporting procedures. Always include the
version number of the GNU program, as well as the operating system and
machine the program was ran on (if the program doesn't have a version
number, send the date of the latest entry in the file ChangeLog). For
GNU Emacs bugs, type "M-x emacs-version". A debugger backtrace of any
core dump, can also be useful. Be careful to separate out hypothesis
from fact! For bugs in GNU Emacs lisp, set variable debug-on-error to
t, and re-enter the command(s) that cause the error message; Emacs will
pop up a debug buffer if something is wrong; please include a copy of
the buffer in your bug report.

Please don't send in a patch without a test case to illustrate the
problem the patch is supposed to fix. Sometimes the patches aren't
correct or aren't the best way to do the job, and without a test case
there is no way to debug an alternate fix.

The purpose of reporting a bug is to enable the bug to be fixed for the
sake of the whole community of users. You may or may not receive a
response; the maintainers will send one if that helps them find or
verify a fix. Most GNU maintainers are volunteers and all are
overworked; they don't have time to help individuals and still fix the
bugs and make the improvements that everyone wants. If you want help
for yourself in particular, you may have to hire someone. The GNU
project maintains a list of people providing such services. It is
distributed with GNU Emacs in file etc/SERVICE, and can be requested
from gnu@prep.ai.mit.edu.

Anything addressed to the implementors and maintainers of a GNU program
via a bug-* list, should NOT be sent to the corresponding info-* or
help-* list.

Please DON'T post your bug reports on the gnu.* newsgroups! Mail them
to bug-*@prep instead! At first sight, it seems to make no difference:
anything sent to one will be propagated to the other; but if you post on
the newsgroup, the information about how to reach you is lost in the
message that goes on the mailing list. It can be very important to know
how to reach you if there is anything in the bug report that we don't
understand. Bug reports also reach the GNU maintainers quickest when
they are sent to the bug-* mailing list submittal address.

And please DON'T post your GNU bug reports to comp.* or other non gnu.*
newsgroups, they never make it to the GNU maintainers at all. Please
mail them to bug-*@prep instead!

See section '* General Information about all lists'.

* info-gnu-request@prep.ai.mit.edu to subscribe to info-gnu
** gnUSENET newsgroup: gnu.announce
** Send announcements to: info-gnu@prep.ai.mit.edu

This list distributes progress reports on the GNU Project. It is also
used by the GNU Project to ask people for various kinds of help. It is
NOT for general discussion.

The list is filtered to remove items meant for info-gnu-request, that
can be answered by the moderator without bothering the list, or should
have been sent to another list.

See section '* General Information about info-* lists'.

* gnu-misc-discuss-request@cis.ohio-state.edu to subscribe to gnu-misc-discuss
** gnUSENET newsgroup: gnu.misc.discuss
** Send contributions to: gnu-misc-discuss@cis.ohio-state.edu

This list is for serious discussion of freed software, the GNU
Project, the GNU Manifesto and their implications. It's THE place for
discussion that is not appropriate in the other GNU mailing lists and
gnUSENET newsgroups.

Flaming is out of place. Tit-for-tat is not welcome. Repetition
should not occur.

Good READING and writing are expected. Before posting, wait a while,
cool off, and think.

Don't trust pronouncements made on gnu-misc-discuss about what GNU is,
what FSF position is, what the GNU General Public License is, etc.,
unless they are made by someone you know is well connected with GNU and
are sure the message is not forged.

USENET and gnUSENET readers are expected to have read ALL the articles
in news.announce.newusers before posting. If news.announce.newusers is
empty at your site, wait (the articles are posted monthly), your posting
isn't that urgent! Readers on the Internet can anonymous ftp these
articles from wsmr-simtel20.army.mil under directory
PD2:<UNIX-C.USENET>.

Someone from the Free Software Foundation will attempt to follow this
group as time and volume permits.

Remember, "GNUs Not Unix" and "gnUSENET is Not USENET". We have
higher standards!

Note that sending technical questions about specific GNU software to
gnu-misc-discuss is likely to be less useful than sending them to the
appropriate mailing list or gnUSENET newsgroup, since more technical
people read those.

* bug-gnu-emacs-request@prep.ai.mit.edu to subscribe to bug-gnu-emacs
** gnUSENET newsgroup: gnu.emacs.bug
** Gnu Emacs bug reports to: bug-gnu-emacs@prep.ai.mit.edu

This list distributes, to the active maintainers of GNU Emacs, bug
reports and fixes for, and suggestions for improvements in GNU Emacs.
It is the place to report GNU Emacs bugs by all users of GNU Emacs.

Send bugs in the GNU Emacs Lisp reference manual to:
lisp-manual-bugs@prep.ai.mit.edu

lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.
It's just a bug-reporting address.

Subscribers to bug-gnu-emacs automatically receive all
info-gnu-emacs messages.

See section '* General Information about bug-* lists and reporting
program bugs'.

* gnu-emacs-sources-request@prep.ai.mit.edu to subscribe to gnu-emacs-sources
** gnUSENET newsgroup: gnu.emacs.sources
** Gnu Emacs source code to: gnu-emacs-sources@prep.ai.mit.edu

This list/newsgroup will be for the posting, by their authors, of lisp
and C sources and patches that improve GNU Emacs. Its contents will
be reviewed by FSF for inclusion in future releases of GNU Emacs.

Please do NOT discuss or request source code here. Use
help-gnu-emacs/gnu.emacs.help for those purposes. This allows the
automatic archiving of sources posted to this list/newsgroup.

Please do NOT post such sources to any other GNU mailing list (e.g
help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). It's up
to each poster to decide whether to cross-post to any non-gnUSENET
newsgroup (e.g. comp.emacs or vmsnet.sources).

Please do NOT announce that you have posted source code to
gnu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) or
gnUSENET newsgroups (e.g. gnu.emacs.help). People who want to keep up
with sources will read this list/newsgroup. It's up to each poster to
decide whether to announce a gnu.emacs.sources article in any
non-gnUSENET newsgroup (e.g comp.emacs or comp.sources.d).

If source or patches that were previously posted or a simple fix is
requested in help-gnu-emacs, please mail it to the requester. Do NOT
repost it. If you also want something that is requested, send mail to
the requester asking him to forward it to you. This kind of traffic is
best handled by e-mail, not by a broadcast medium that reaches thousands
of sites.

If the source is very long (>10k bytes) send mail offering to send it.
This prevents the requester from getting many redundant copies and saves
network bandwidth.

* help-gnu-emacs-request@prep.ai.mit.edu to subscribe to help-gnu-emacs
** gnUSENET newsgroup: gnu.emacs.help (and one-way into comp.emacs)
** Send contributions to: help-gnu-emacs@prep.ai.mit.edu

This list is the place for users and installers of GNU Emacs to ask for
help. Please send bug reports to bug-gnu-emacs instead of posting them
here.

Since help-gnu-emacs a very large list, send it only those items that are
seriously important to many people.

If source or patches that were previously posted or a simple fix is
requested in help-gnu-emacs, please mail it to the requester. Do NOT
repost it. If you also want something that is requested, send mail to
the requester asking him to forward it to you. This kind of traffic is
best handled by e-mail, not a broadcast medium that reaches thousands of
sites.

This list is also gated one way to USENET's newsgroup comp.emacs (once
known as net.emacs). This one-way gating is done for users whose sites
get comp.emacs, but not gnu.emacs.help. Users at non-USENET sites may
receive all articles from comp.emacs by making their request to:
unix-emacs-request@bbn.com

If Emacs crashes, or if you build Emacs following the standard procedure
on a system which Emacs is supposed to work on (see etc/MACHINES) and it
does not work at all, or if an editing command does not behave as it is
documented to behave, this is a bug. Don't send bug reports to
help-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them to
bug-gnu-emacs instead.

See section '* General Information about help-* lists'.

* info-gnu-emacs-request@prep.ai.mit.edu to subscribe to info-gnu-emacs
** gnUSENET newsgroup: gnu.emacs.announce (and one-way into comp.emacs)
** Send announcements to: info-gnu-emacs@prep.ai.mit.edu

This list distributes announcements and progress reports on GNU Emacs.
It is NOT for general discussion; please use help-gnu-emacs for that.

The list is filtered to remove items meant for info-gnu-emacs-request,
that can be answered by the moderator without bothering the list, or
should have been sent to another list.

info-gnu-emacs is also gated one way to USENET's newsgroup comp.emacs
(once known as net.emacs). This one-way gating is done for users whose
sites get comp.emacs, but not gnu.emacs.announce. Users at non-USENET
sites may receive all articles from comp.emacs by making their request
to: unix-emacs-request@bbn.com

Do not report GNU Emacs bugs to info-gnu-emacs or comp.emacs, instead
mail them to bug-gnu-emacs@prep.ai.mit.edu.

See section '* General Information about info-* lists'.

* vms-gnu-emacs-request@harvard.harvard.edu to subscribe to vms-gnu-emacs
** gnUSENET newsgroup: gnu.emacs.vms
** Send contributions to: vms-gnu-emacs@harvard.harvard.edu
*** UUCP: ..!uunet!harvard!vms-gnu-emacs-request

This list was a working group who did the initial port of GNU Emacs to
the VMS operating system. It still discusses problems and solutions to
the VMS port and the distribution of it.

* bug-bash-request@prep.ai.mit.edu to subscribe to bug-bash
** gnUSENET newsgroup: gnu.bash.bug
** BASH bug reports to: bug-bash@prep.ai.mit.edu

This list distributes, to the active maintainers of BASH (the Bourne
Again SHell), bug reports and fixes for, and suggestions for
improvements in BASH. It is the place to report BASH bugs by all users
of BASH.

Always report the version number of the operating system, hardware, and
bash (flag -version on startup or check the variable $BASH_VERSION in a
running bash).

There are no other GNU mailing lists or gnUSENET newsgroups for BASH.

See section '* General Information about bug-* lists and reporting
program bugs'.

* bug-gdb-request@prep.ai.mit.edu to subscribe to bug-gdb
** gnUSENET newsgroup: gnu.gdb.bug
** GDB bug reports to: bug-gdb@prep.ai.mit.edu

This list distributes, to the active maintainers of GDB (Gnu's
DeBugger), bug reports and fixes for, and suggestions for improvements
in GDB. It is the place to report GDB bugs by all users of GDB.

There are no other GNU mailing lists or gnUSENET newsgroups for GDB.

See section '* General Information about bug-* lists and reporting
program bugs'.

* bug-gcc-request@prep.ai.mit.edu to subscribe to bug-gcc
** gnUSENET newsgroup: gnu.gcc.bug
** GCC bug reports to: bug-gcc@prep.ai.mit.edu

This list distributes bug reports for, fixes for bugs in, and
suggestions for improvements in the GNU C Compiler to its active
developers. It is the place to report GCC bugs by all testers of GCC.
The GNU C Compiler still has bugs in it, and is not quite ready for
everyday use.

The most convenient form of test case is a piece of cpp output that can
be passed directly to cc1. Preferably written in C, not C++.

Subscribers to bug-gcc automatically receive all info-gcc messages.

See section '* General Information about bug-* lists and reporting
program bugs'.

* help-gcc-request@prep.ai.mit.edu to subscribe to help-gcc
** gnUSENET newsgroup: gnu.gcc.help
** Send contributions to: help-gcc@prep.ai.mit.edu

This list is the place for users and installers of the GNU C Compiler to
ask for help.

If gcc crashes, or if you build gcc following the standard procedure on
a system which gcc is supposed to work on (see config.gcc) and it does
not work at all, or if an command line option does not behave as it is
documented to behave, this is a bug. Don't send bug reports to help-gcc
(gnu.gcc.help); mail them to bug-gcc instead.

See section '* General Information about help-* lists'.

* info-gcc-request@prep.ai.mit.edu to subscribe to info-gcc
** gnUSENET newsgroup: gnu.gcc.announce
** Send announcements to: info-gcc@prep.ai.mit.edu

This list distributes announcements and progress reports on the GNU C
Compiler. It is NOT for general discussion; please use help-gcc for
that.

The list is filtered to remove items meant for info-gcc-request, that
can be answered by the moderator without bothering the list, or should
have been sent to another list.

See section '* General Information about info-* lists'.

* bug-g++-request@prep.ai.mit.edu to subscribe to bug-g++
** gnUSENET newsgroup: gnu.g++.bug
** G++ bug reports to: bug-g++@prep.ai.mit.edu

This list distributes bug reports for, fixes for bugs in, and
suggestions for improvements in the GNU C++ Compiler to its active
developers. It is the place to report G++ bugs by all testers of G++.

G++ uses the GNU C-Compiler back end. Active developers may wish to
subscribe to bug-gcc@prep.ai.mit.edu as well.

Subscribers to bug-g++ automatically receive all info-g++ messages.

See section '* General Information about bug-* lists and reporting
program bugs'.

* help-g++-request@prep.ai.mit.edu to subscribe to help-g++
** gnUSENET newsgroup: gnu.g++.help (and one-way into comp.lang.c++)
** Send contributions to: help-g++@prep.ai.mit.edu

This list is the place for users and installers of the GNU C++ Compiler
to ask for help. Please send bug reports to bug-g++ instead of posting
them here.

help-g++ is also gated one way to USENET's newsgroup comp.lang.c++.
This one-way gating is done for users whose sites get comp.lang.c++, but
not gnu.g++.help.

If g++ crashes, or if you build g++ following the standard procedure on
a system which g++ is supposed to work on (see config.g++) and it does
not work at all, or if an command line option does not behave as it is
documented to behave, this is a bug. Don't send bug reports to help-g++
(gnu.g++.help) or post them to comp.lang.c++; mail them to bug-g++
instead.

See section '* General Information about help-* lists'.

* info-g++-request@prep.ai.mit.edu to subscribe to info-g++
** gnUSENET newsgroup: gnu.g++.announce (and one-way into comp.lang.c++)
** Send announcements to: info-g++@prep.ai.mit.edu

This list distributes announcements and progress reports on the GNU C++
Compiler. It is NOT for general discussion; please use help-g++ for
that.

The list is filtered to remove items meant for info-g++-request, that
can be answered by the moderator without bothering the list, or should
have been sent to another list.

It is also gated one way to USENET's newsgroup comp.lang.c++. This
one-way gating is done for users whose sites get comp.lang.c++, but not
gnu.g++.announce.

Do not report g++ bugs to info-g++ or comp.lang.c++, mail them to
bug-g++@prep.ai.mit.edu instead.

See section '* General Information about info-* lists'.

* bug-lib-g++-request@prep.ai.mit.edu to subscribe to bug-lib-g++
** gnUSENET newsgroup: gnu.g++.lib.bug
** lib-g++ bug reports to: bug-lib-g++@prep.ai.mit.edu

This list distributes, to the active maintainers of lib-g++ (GNU's
library for C++), bug reports and fixes for, and suggestions for
improvements in lib-g++. It is the place to report lib-g++ bugs by all
users of lib-g++.

Announcements of new releases of lib-g++ are made on both info-g++ and
bug-lib-g++.

There are no other GNU mailing lists or gnUSENET newsgroups for the G++
Library.

See section '* General Information about bug-* lists and reporting
program bugs'.

* bug-gnu-smalltalk-request@prep.ai.mit.edu to subscribe to bug-gnu-smalltalk
** gnUSENET newsgroup: gnu.smalltalk.bug
** GNU Smalltalk bug reports to: bug-gnu-smalltalk@prep.ai.mit.edu

GNU Smalltalk is the GNU project implementation of the Smalltalk language.

This list distributes, to the active maintainers of GNU Smalltalk, bug
reports and fixes for, and suggestions for improvements to GNU
Smalltalk. It is the place to report bugs in GNU Smalltalk by all users
of the program.

For now, new releases of GNU Smalltalk will also be announced on this list.

There are no other GNU mailing lists or gnUSENET newsgroups for GNU
Smalltalk.

See section '* General Information about bug-* lists and reporting
program bugs'.

* bug-groff-request@prep.ai.mit.edu to subscribe to bug-groff
** gnUSENET newsgroup: gnu.groff.bug
** GNU groff bug reports to: bug-groff@prep.ai.mit.edu

groff is the GNU project implementation, in C++, of the traditional
Unix document formatting tools. As of June 1990 it includes troff,
pic, tbl, eqn, man macros, a PostScript driver, a driver which
produces TeX dvi format and a driver for typewriter-like devices. A
modified version of the Berkeley me macros and an enhanced version of
the X11R4 xditview are also included.

This list distributes, to the active maintainers of groff, bug reports
and fixes for, and suggestions for improvements to groff (and it
component programs). It is the place for all users of groff to report
bugs.

For now, new releases of groff will also be announced on this list.

There are no other GNU mailing lists or gnUSENET newsgroups for groff.

See section '* General Information about bug-* lists and reporting
program bugs'.

* bug-ghostscript-request@prep.ai.mit.edu to subscribe to bug-ghostscript
** gnUSENET newsgroup: gnu.ghostscript.bug
** Ghostscript bug reports to: bug-ghostscript@prep.ai.mit.edu

GhostScript is the GNU project implementation of a language and graphics
library with a remarkable similarity to PostScript.

This list distributes, to the active maintainers of Ghostscript, bug
reports and fixes for, and suggestions for improvements in Ghostscript. It
is the place to report bugs in Ghostscript by all users of them.

For now, new releases of Ghostscript will also be announced on this list.

There are no other GNU mailing lists or gnUSENET newsgroups for
GhostScript.

See section '* General Information about bug-* lists and reporting
program bugs'.

* info-gnu-chess-request@prep.ai.mit.edu to subscribe to info-gnu-chess
** gnUSENET newsgroup: gnu.chess
** Send contributions to: info-gnu-chess@prep.ai.mit.edu

This list reports new releases and information about the program GNU
Chess.

See section '* General Information about info-* lists'.

* bug-gnu-utils-request@prep.ai.mit.edu to subscribe to bug-gnu-utils
** gnUSENET newsgroup: gnu.utils.bug
** GNU Utilities bug reports to: bug-gnu-utils@prep.ai.mit.edu

This list distributes, to the active maintainers of these programs, bug
reports and fixes for, and suggestions for improvements in GNU programs
not covered by other bug-* mailing lists/gnu.*.bug newsgroups. It is
the place to report bugs in these GNU programs by all users of them.

There are no other GNU mailing lists or gnUSENET newsgroups for these
GNU utilities.

See section '* General Information about bug-* lists and reporting
program bugs'.

* info-gnus-request%flab.Fujitsu.JUNET@uunet.UU.NET to subscribe
** gnUSENET newsgroup: NONE YET
** Send contributions to: info-gnus%flab.Fujitsu.JUNET@uunet.UU.NET

The list is intended to exchange useful information about GNUS, such as
bug reports, useful hooks, and extensions of GNUS. GNUS is an NNTP-base
network news reader for GNU Emacs (which also works with a news spool).
English and Japanese are the official languages of the list. GNUS is
quite different than gnews.

* info-gnus-english-request@cis.ohio-state.edu to subscribe
** gnUSENET newsgroup: gnu.emacs.gnus
** Send contributions to: info-gnus-english@cis.ohio-state.edu

The list has the same charter as info-gnus. The difference is that
English is the only official language of the list.

info-gnus-english/gnu.emacs.gnus is forward to info-gnus, but NOT
vice-versa.

* info-gnews-request@ics.uci.edu to subscribe to info-gnews
** gnUSENET newsgroup: gnu.emacs.gnews
** Send contributions to: info-gnews@ics.uci.edu

This newsgroup is intended to exchange useful information about gnews,
such as bug reports, useful hooks, and extensions of gnews. gnews is an
NNTP-base network news reader for GNU Emacs (which also works a news
spool). It is quite different than GNUS.

* gnu-emacs-ada-request@grebyn.com to subscribe to gnu-emacs-ada
** gnUSENET newsgroup: NONE PLANNED
** Gnu Emacs Ada support bug reports to: gnu-emacs-ada@grebyn.com

This list distributes bug reports for, fixes for bugs in, and
suggestions for improvements in GNU Emacs' editing support of the Ada
programming language.

There are no other GNU mailing lists or gnUSENET newsgroups for GNU
Emacs' editing support of Ada.

See section '* General Information about bug-* lists and reporting
program bugs'.

* bug-vm-request@uunet.uu.net to subscribe to bug-vm
** gnUSENET newsgroup: NONE
** VM mail reader bug reports to: bug-vm@uunet.uu.net

This list discusses bugs in View Mail mode for GNU Emacs, with an
emphasis on beta and prerelease versions. It is the place to report
bugs in VM.

Always report the version number of VM you are using, as well as the
version of Emacs you're running. If you believe it is significant,
report the operating system used and the hardware.

Subscribers to bug-vm automatically receive all info-vm messages.

* info-vm-request@uunet.uu.net to subscribe to info-vm
** gnUSENET newsgroup: NONE
** Send contributions to: info-vm@uunet.uu.net

This list dicusses the View Mail mode for GNU Emacs, an alternative to
rmail mode.

* supercite-request@warsaw.nlm.nih.gov to subscribe to supercite
** gnUSENET newsgroup: NONE PLANNED
** Send articles to: supercite@warsaw.nlm.nih.gov
*** UUCP: ..!uunet!warsaw.nlm.nih.gov!supercite-request

The supercite mailing list covers issues related to the advanced
mail/news citation package called Supercite for GNU Emacs.

* bug-gnu960-request@mipon2.intel.com to subscribe to bug-gnu960
** gnUSENET newsgroup: NONE PLANNED
** Intel 960 Port bug reports to: bug-gnu960@mipon2.intel.com

This list distributes bug reports for, fixes for bugs in, and
suggestions for improvements in Intel's port of GNU software to the
Intel 960 microprocessor.

You can also fax to: GNU/960 - 1-503-696-4930.

There are no other GNU mailing lists or gnUSENET newsgroups for Intel's
port of GNU software to the Intel 960 microprocessor.

See section '* General Information about bug-* lists and reporting
program bugs'.

* gnu-manual-request@a.cs.uiuc.edu IS NOW DEFUNCT
** DEAD: Gnusenet newsgroup: gnu.emacs.lisp.manual
** DEAD address: gnu-manual@a.cs.uiuc.edu
*** DEAD UUCP address: ..!uunet!uiucdcs!gnu-manual-request

This list and newsgroup is dead. It was a working group whose
volunteers wrote, proofread and commented on the developing GNU Emacs
Lisp programmers manual.

Send bugs in the GNU Emacs Lisp reference manual to:
lisp-manual-bugs@prep.ai.mit.edu

lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.
It's just a bug-reporting address.

* no mailing list request
** gnUSENET newsgroup: gnu.gnusenet.config
** no mailing list

This newsgroup has nothing to do with GNU software, especially its
configuration. It's exists to distribute information about the
administration and configuration of gnUSENET: the gnu.all alternative
USENET hierarchy that carry the GNU mailing lists.

Administrators of gnUSENET hosts receiving the gnu.all newsgroups are
welcome to ask questions here or via e-mail of gnu@prep.ai.mit.edu.

* no mailing list request
** gnUSENET newsgroup: gnu.gnusenet.test
** no mailing list

This newsgroup has nothing to do with GNU software, especially its
testing. It's exists to allow test messages to be made in gnUSENET: the
gnu.all alternative USENET hierarchy that carry the GNU mailing lists.

Local variables:
mode: outline
fill-column: 72
End:
----------------------------------------------------------------------
-*- text -*-
Getting GNU Software, 19 Sep 90
Copyright (C) 1986, 1987, 1988, 1989, 1990 Free Software Foundation, Inc.

Permission is granted to anyone to make or distribute
verbatim copies of this document provided that the
copyright notice and this permission notice are preserved.

* GNU and the Free Software Foundation

Project GNU is organized as part of the Free Software Foundation, Inc.
The Free Software Foundation has the following goals:
1) to create GNU as a full development/operating system.
2) to distribute GNU and other useful software with source code and
permission to copy and redistribute.

Further information on the rationale for GNU is in file
/pub/gnu/etc/GNU (All files referred to are on the Internet host
prep.ai.mit.edu.

Information on GNU Internet mailing lists and gnUSENET newsgroupscan
be found in file /pub/gnu/etc/MAILINGLISTS.

* How To Get The Software

The easiest way to get a copy of the distribution is from someone else
who has it. You need not ask for permission to do so, or tell any one
else; just copy it. The second easiest is to ftp it over the
Internet. The third easiest way is to uucp it. Ftp and uucp
information is in file /pub/gnu/etc/FTP.

If you cannot get a copy any of these ways, or if you would feel more
confident getting copies straight from us, or if you would like to get
some funds to us to help in our efforts, you can order one from the
Free Software Foundation. See file /pub/gnu/etc/DISTRIB.

* Available Software

** GNU Emacs

The GNU Emacs distribution includes:
- manual source in TeX format.
- an enhanced regex (regular expression) library.

See file /pub/gnu/etc/MACHINES for the status of porting Emacs to
various machines and operating systems.

** C Scheme - a block structured dialect of LISP.

The Free Software Foundation distributes C Scheme for the MIT Scheme
Project on it tapes. A partial ftp distribution can be found on
prep.ai.mit.edu. The full ftp distribution can be found on
zurich.ai.mit.edu.

Problems with the C Scheme distribution and it's ftp distribution
should be referred to: <bug-cscheme@prep.ai.mit.edu>. There are two
general mailing lists: <scheme@mc.lcs.mit.edu> and
<info-cscheme@prep.ai.mit.edu>. Requests to join either list to:
<info-cscheme-request@prep.ai.mit.edu> or
<scheme-request@mc.lcs.mit.edu>.

** Other GNU Software

A fuller list of available software are in the files
/pub/gnu/etc/DISTRIB and /pub/gnu/etc/FTP.

* No Warranties

We distribute software in the hope that it will be useful, but without
any warranty. No author or distributor of this software accepts
responsibility to anyone for the consequences of using it or for
whether it serves any particular purpose or works at all, unless he
says so in writing.

* If You Like The Software

If you like the software developed and distributed by the Free
Software Foundation, please express your satisfaction with a donation.
Your donations will help to support the foundation and make our future
efforts successful, including a complete development and operating
system, called GNU (Gnu's Not Un*x), which will run Un*x user
programs. For more information on GNU and the Foundation, contact us
at Internet address <gnu@prep.ai.mit.edu> or the foundation's US Mail
address found in file /pub/gnu/etc/DISTRIB.
----------------------------------------------------------------------
-*- text -*-
How to get GNU Software by Internet FTP or by UUCP. Last updated 21 Nov 90.

* No Warranties

We distribute software in the hope that it will be useful, but
without any warranty. No author or distributor of this software
accepts responsibility to anyone for the consequences of using it or
for whether it serves any particular purpose or works at all, unless
he says so in writing.

* Updates

If you find this file in the Emacs distribution, there is a chance
it is out of date. If you plan to FTP files from prep.ai.mit.edu,
you might as well start by FTPing the current version of this file,
which is `/pub/gnu/etc/FTP'.

* FTPing GNU Software

** GNU Emacs and How To FTP It

If you are on the Internet (see also "** Alternative Internet FTP
Sources" below), you can at present copy the latest distribution
version of GNU Emacs from the file /pub/gnu/emacs-M.N.tar on host
prep.ai.mit.edu (or the file /pub/gnu/emacs-M.N.tar.Z which has been
run through compress after tar). M and N standard for version
numbers; look at a listing of the directory through ftp to see what
version is available. These files are about 11 and 4 megabytes long,
respectively. After you unpack the distribution, be sure to look at
the files README and INSTALL.

Because of difficulties in transferring large files, sometimes a split
version of the tar file is created. This is a directory named
/pub/gnu/emacs-M.N.tar-split or perhaps
/pub/gnu/emacs-M.N.tar.Z-split, containing files of 100000 characters
each. There is generally no trouble in ftping files of this size.
They can be combined with cat to make a tar file or compressed tar
file.

ALWAYS USE BINARY/IMAGE MODE TO TRANSFER THESE FILES!
Text mode does not work for tar files or compressed files.

Some ftp'ers have found it necessary for successful file transfer:
- to explicitly use prep.ai.mit.edu internet address:
18.71.0.38 (as of 11 April 89)

Files of differences from previous widely distributed GNU Emacs
versions to the present version are also available on prep.ai.mit.edu
under names of the form emacs.diff-OO.OO-NN.NN in directory /pub/gnu.
These are made with diff -rc2. Sometimes there are compressed
versions of these difference files as well; their names have .Z
appended.

The Emacs manual in source form is included in the distribution.
The dvi file produced by TeX is not included, but a copy may be
available for ftp under the name /pub/gnu/emacs.dvi.

The Emacs Lisp Reference Manual is in a separate file:
/pub/gnu/lispref.tar.Z.

** VMS versions of GNU Emacs and How To FTP It.
You can anonymously ftp a VMS version of GNU emacs from:
- ddvax.llnl.gov.
- VMSA.OAC.UCI.EDU or VMSD.OAC.UCI.EDU.
- RIGEL.EFD.LTH.SE [130.235.48.3].
- ctrsci.cc.utah.edu. The 00readme.txt file gives details.
- cc.utah.edu [128.110.8.24]. User anonymous, pass guest. It
has already been compiled and linked so it is ready to run. You will
need to ftp the reblock.for program to reblock the saveset so that the
backup utility can restore that saveset. Do a backup/list on the
ftp'd saveset and catch the header info that backup puts out. It
contains the correct block size to reblock the file to. Remember to
ftp it in binary mode.

** A VMS version of G++ and How To FTP It.

mango.miami.edu has a VMS version of the G++ compiler. Contact
angel@flipper.miami.edu (angel li) for details.

** A VMS version of GCC and How To FTP It.

Jonathan Corbet has made the "bootstrap files" for the GNU C compiler
available for pseudo-anonymous FTP on rdss.ucar.edu. The full gcc
sources are also available, for anybody who wants to start from scratch.

Jonathan Corbet also requests that you please limit your access to
outside the hours of 8-6 (mountain time) on weekdays. RDSS is a
*very* busy machine during the day. Jonathan notes, "I don't think I
have to tell you what will happen if my users feel they are being
slowed down by outside people grabbing software."

The procedure is this: FTP to rdss.ucar.edu (128.117.80.1), and log in
with a username of FTP, password FTP. Cd into the [.gcc] directory,
and grab either or both of these files:
bootstrap.bck The bootstrap files -- not much more than the
.exe files. About 1.3 mb.
gcc.bck The full-blown gcc source code. About 5mb.
Both of these files are backup savesets, and should thus be grabbed
in binary mode.

SPAN people can grab the same files from rdss::du:[ftp.gcc]. If your
node database does not know about rdss, use 9452 instead.

Jonathan Corbet is with the
National Center for Atmospheric Research, Field Observing Facility
Internet: corbet@rdss.ucar.edu
SPAN: rdss::corbet (rdss = 9452)
Usenet: ...!ncar!rdss!corbet

** Other GNU Software and How To FTP It.

This software is available on prep.ai.mit.edu under directory
/pub/gnu. Files containing diff from previous versions are often
available. Compressed versions of the tar or diff files are often
available (indicated by a .Z suffix). Much of this software is in
beta test (probably still buggy), and is being made available for use
by hackers who like to test software. M.N indicates a version number.
diff files to convert between versions (like those used for GNU
Emacs), exist for some of these programs. Some programs have misc
suport files as well. Have a look on prep.ai.mit.edu to see which
ones.

GNU Assembler (gas) gas-M.N.tar.Z Released
GNU Bash bash-M.N.tar.Z BETA TEST
GNU Bison bison-M.N.tar.Z Released
GNU C Compiler (gcc) gcc.tar-M.N.Z Late BETA TEST
GNU C++ Compiler (g++) g++.tar-M.N.Z BETA TEST
GNU C++ Library libg++-M.N.tar.Z BETA TEST
GNU cpio cpio-M.N.tar.Z BETA TEST
GNU Emacs Lisp Reference Manual lispref.tar.Z Released
GNU AWK (gawk) gawk-M.N.tar.Z Released
GNU debugger (gdb) gdb-M.N.tar.Z Released
GNU Make make-M.N.tar.Z Released
GNU ld, ar, gprof, size, nm and strip
binutils.tar.Z Released
GNU cat chmod cmp cp cut dd dir du head install ln ls
mkdir mkfifo mv paste rm rmdir tac tail touch vdir
fileutils-M.N.tar.Z BETA TEST
GNU Diff diff-M.N.tar.Z Released
GNU e?grep grep-M.N.tar.Z Released
GNU fgrep fgrep-M.N.tar.Z BETA TEST
GNU find find-M.N.tar.Z BETA TEST
GNU finger finger-M.N.tar.Z BETA TEST
GNU Ghostscript ghostscript-M.N.tar.Z
& font ghostscript*tar.Z files BETA TEST
GNU gdbm gdbm-M.N.tar.Z BETA TEST
GNU Go gnugo-M.N.tar.Z BETA TEST
GNU groff groff-M.N.tar.Z BETA TEST
GNU indent indent-M.N.tar.Z BETA TEST
GNU malloc malloc.tar.Z BETA TEST
GNU tar (to unpacl .tar files) tar-M.N.tar.Z
and tar-M-N.shar BETA TEST
GNU m4 m4.tar.Z BETA TEST
GNU sed sed-M.N.tar.Z BETA TEST
GNU Smalltalk smalltalk-M.N.tar.Z BETA TEST
GNU Chess gnuchess-M.N.tar.Z Released
GNU Buttons & Designs button.M.N.ps Released

and these packages which are not FSF software but work with
them and are part of GNU:

Concurrent Version System cvs-M.N.tar.Z
compress (to undo .Z files) compress.shar and compress.tar
dirent dirent.tar.Z
(directory reader for sysV 3.2)
elvis (a vi clone) elvis.M.N.O.tar.Z
Flex (a faster lex) flex-M.N.tar.Z
gnuplot gnuplot-M.N.tar.Z
The jargon file jargon.text.Z
(definitions of terms used by hackers)
NIH C++ Class Library nihcl-M.N.tar.Z
Perl perl-M.N.tar.Z
Revision Control System rcs.tar.Z
Texi2roff texi2roff.shar.Z

** TeX and How to FTP It

We don't distribute TeX now, but it is free software.

You can get TeX sources via anonymous FTP from labrea.stanford.edu in
pub/tex. The directory pub/tex/unix3.0 probably contains what you
want, but see pub/tex/README to be sure. The most recent incarnation
of the LaTeX macros are in labrea:pub/tex/latex. If you'd like to
support TUG and/or don't have access to the Internet, then write to
elisabet@max.acs.washington.edu about getting their tape distribution.

** Scheme and How to FTP It

The latest distribution version of C Scheme is on the machine
zurich.ai.mit.edu. To obtain a "tarred" copy of this directory,
telnet to zurich.ai.mit.edu and log in as scheme (password: scheme).
A file called dist.tar will be created (if there isn't one already),
and you will be given a choice of the file transfer program to run (of
all the ones supported by zurich). It should be self-explanatory (ha,
ha! [try ? for help]).

Read the files INSTALL and README in the top level C Scheme directory.

** Alternative Internet FTP Sources

The administrators of wsmr-simtel20.army.mil maintains copies of GNU
distributed software for MILNET/DDN hosts. It is available via
anonymous ftp from PD:<UNIX-C.GNU> in the original tar or tar.Z
format.

The administrators of louie.udel.edu maintains copies of GNU Emacs and
the compress program. The files are available via anonymous ftp under
directory ~ftp/gnu.

Emacs and other GNU programs may be available on nic.nyser.net, in
/usb/gnu/emacs-dist.tar{,.Z}. Anonymous ftp starts you in directory
/usb.

Emacs and other GNU programs may be available on gatekeeper.dec.com,
itstd.sri.com, scam.berkeley.edu, uunet.uu.net, wuarchive.wustl.edu,
and bu.edu via anonymous ftp.

* Getting GNU software in Great Britain

jpo@cs.nott.ac.uk is willing to distribute those GNU sources he has
available. The smaller items are available from the info-server (send
to info-server@cs.nott.ac.uk) the larger items by negotiation. Due to
communication costs this service is only available within the UK.

BattenIG@computer-science.birmingham.ac.uk (aka
I.G.Batten@fulcrum.bt.co.uk) is also willing to distribute those GNU
sources he has available. He can also write tapes in qic-21 and
qic-24 formats.

lmjm@doc.ic.ac.uk is willing to distribute those GNU sources he has
available along with comp.sources.unix, comp.sources.x, X windows et
al. All items are available using uucp, NIFTP over JANET or, via a
suitable gateway, from PSS sites as well. Due to communication costs
this service is only available within the UK. Mail to
info-server@doc.ic.ac.uk for details. He can also write sun cartridge
or exabyte tapes.

* Getting GNU software in Sweden

Site sunic.sunet.se has many of the GNU programs available for anonymous ftp.

* Getting GNU software in Finland

Site funic.funet.fi (Internet address 128.214.6.100) has many of the
GNU programs available for anonymous ftp.

* Getting GNU software in Denmark

Site freja.diku.dk (Internet address 129.142.96.1) has many of the GNU
programs, TeX, and the X window system available for anonymous ftp.

* Getting GNU software in Japan

Site ftp.cs.titech.ac.jp has some of the GNU programs available for
anonymous ftp. nemacs (the japanese port of GNU Emacs) is under
~ftp/JAPAN.

* Getting GNU software via UUCP

OSU is distributing via UUCP: most GNU software, MIT C Scheme,
Compress, News, RN, NNTP, Patch, some Appletalk stuff, some of the
Internet Requests For Comment (RFC) et al.. See their periodic
postings on the Usenet newsgroup comp.sources.d for informational
updates. Current details from Karl Kleinpaste
<karl@tut.cis.ohio-state.edu> or <...!osu-cis!karl>.

Information on how to uucp some GNU programs is available via
electronic mail from: uunet!hutch!barber, hqda-ai!merlin,
sun!nosun!illian!darylm, acornrc!bob,
hao!scicom!qetzal!upba!ugn!nepa!denny, bigtex!james (aka
james@bigtex.cactus.org), ncar!noao!asuvax!hrc!dan, oli-stl!root, and
postmaster@uunet.uu.net.

* If You Like The Software

If you like the software developed and distributed by the Free
Software Foundation, please express your satisfaction with a donation.
Your donations will help to support the Foundation and make our future
efforts successful, including a complete development and operating
system, called GNU (Gnu's Not Un*x), which will run Un*x user
programs. For more information on GNU and the Foundation, contact us
at the above address.

Ordering a distribution tape from the Foundation is often a good
way to bring your company or university to make a donation.
----------------------------------------------------------------------
-*- text -*-
The prices on the order form below EXPIRE in January 1991

GNU Emacs availability information, 18 Sep 1990
Copyright (C) 1986, 1987, 1988, 1989, 1990 Free Software Foundation, Inc.

Permission is granted to anyone to make or distribute
verbatim copies of this document provided that the
copyright notice and this permission notice are preserved.

GNU Emacs is legally owned by the Free Software Foundation, but we
regard the foundation actually as its custodian on behalf of the
public, since all software ought to be the common property of mankind.

The foundation permits everyone to have and run copies of GNU Emacs,
at no charge, and to redistribute copies under certain conditions
which are designed to make sure that that all modified versions of GNU
Emacs remain as free as the versions we distribute. These conditions
are stated in the document "GNU Emacs General Public License", a copy
of which is required to be distributed with every copy of GNU Emacs.
It is usually in a file named COPYING in the same directory as this
file.

If you do not know anyone to get a copy of GNU Emacs from, you can
order a tape from the Free Software Foundation. We distribute Emacs
version 18 on 1600bpi industry standard mag tape in tar format. We
will also ship it on 1/4" Sun cartridge tapes in tar format and on
1600bpi magtape in VMS interchange (aka backup) format. We also
distribute nicely typeset copies of the Emacs manual and the Emacs
reference card. See the order form at the end of this file.

If you have Internet access, you can copy the latest Emacs
distribution from host prep.ai.mit.edu. There are several ways to do
this; see the file `FTP' in the same directory as this file for more
information. Even better, get the latest version of the file from
`/pub/gnu/etc/FTP' on prep.ai.mit.edu for the most current
arrangements. It may also be possible to copy Emacs via uucp; the
file `FTP' contains information on that too.

Emacs has been run on both Berkeley Unix and System V Unix, on a
variety of types of cpu. It also works on VMS and on Apollo
computers, though with some deficiencies that reflect problems in
these operating systems. See the file MACHINES in this directory for
a full list of machines that GNU Emacs has been tested on, with
machine-specific installation notes and warnings.

Note that there is significant variation between Unix systems
supposedly running the same version of Unix; it is possible that what
works in GNU Emacs for me does not work on your system due to such an
incompatibility. Since I must avoid reading Unix source code, I
cannot even guess what such problems may exist.

GNU Emacs is distributed with no warranty (see the General Public
License for full details, in the file COPYING in this directory), and
neither I nor the Free Software Foundation promises any kind of
support or assistance to users. The foundation keeps a list of people
who are willing to offer support and assistance for hire. It is
usually in a file named SERVICE in the same directory as this file.
You get the latest version of the file from `/pub/gnu/etc/SERVICE' on
prep.ai.mit.edu.

However, I plan to continue to improve GNU Emacs and keep it reliable,
so please send me any complaints and suggestions you have. I will
probably fix anything that is clearly (to me) a malfunction. I may
make an improvement if I consider it worth the effort, but you should
not be surprised if I don't think I can spare time for it. I hope to
keep Emacs stable now, and avoid putting much time into it, so I can
work on other parts of the GNU system.

If you are on the Internet, report bugs to
bug-gnu-emacs@prep.ai.mit.edu; on UUCP, use the address
...!uunet!prep.ai.mit.edu!bug-gnu-emacs. Otherwise, phone the
foundation at the number listed below, or write to the address listed
below. General questions about the GNU Project can be asked of
gnu@prep.ai.mit.edu.

If you are a computer manufacturer, I encourage you to ship a copy of
GNU Emacs with every computer you deliver. The same copying
permission terms apply to computer manufacturers as to everyone else.
You should consider making a donation to help support the GNU project;
if you estimate what it would cost to distribute some commercial
product and divide it by five, that is a good amount.

If you like GNU Emacs, please express your satisfaction with a
donation: send me or the Foundation what you feel Emacs has been worth
to you. If you are glad that I developed GNU Emacs and distribute it
as freeware, rather than following the obstructive and antisocial
practices typical of software developers, reward me for doing so!

Your donations will help to support the development of more useful
software to be distributed on the same basis as GNU Emacs. Eventually
we will have a complete imitation of the Unix operating system, called
GNU (Gnu's Not Unix), which will run Unix user programs. For more
information on GNU, see the file GNU in this directory.

Richard M Stallman
Chief GNUisance,
President of the Free Software Foundation

Free Software Foundation Order Form

This form is effective June 1990--January 1991.

Prices and contents of tapes are subject to change without notice.

All software and publications are distributed with permission to copy
and redistribute.

TeX source for each manual is on the appropriate tape; the prices for
tapes do not include printed manuals.

All software from the Free Software Foundation is provided on an "as
is" basis, with no warranty of any kind.

Quantity Price Item

For Unix systems, on 1600 bpi 9-track tape in Unix tar format:

________ $150 GNU Emacs source code and other software.
The tape includes:
* GNU Emacs (the extensible, customizable, self-documenting
real-time display editor)
* The GNU Emacs Lisp Reference Manual, as source code.
* MIT Scheme (a dialect of Lisp)
* T, Yale's implementation of Scheme
* Bison (a free, compatible replacement for yacc)
* Nethack (a rogue-like game)
* GNU Chess (a chess playing program with an interface to X).
* GDB (release version of the GNU source-level C debugger)

________ $150 GNU prerelease software, for Unix systems.
The tape includes:
* GCC (the GNU C Compiler, including COFF support)
* G++ (the C++ front end to GCC)
* lib-g++ (the G++ class library)
* NIH Class Library (formerly known as OOPS)
* Bash (GNUs' Bourne Again SHell)
* Bison (a free, compatible replacement for yacc)
* Flex (Vern Paxson fast rewrite of lex)
* Ghostscript (a Postscript interpreter)
* Gawk (the GNU implementation of the AWK programming language)
* Gas (the GNU Assembler)
* GDB (beta version of the GNU source-level C debugger)
* Gnuplot (an interactive mathematical plotting program)
* Compress (a file compression program)
* Perl (version 3.0; a programming language interpreter)
* RCS (Revision Control System)
* CVS (Concurrent Control System)
* GNU object file utilities (ar, ld, make, gprof, size, nm,
strip, ranlib, et al.)
* other GNU utilities (make, diff, grep, tar, et al.)
* GNU GO (the GNU implementation of the game of GO)
* the freed files from the 4.3BSD-Tahoe distribution

________ $150 GNU Experimental software. Not ready before Nov. 1990.

________ $150 Required MIT X Window System X11R4, core software and
documentation, and contributed client software.

________ $150 Optional MIT X Window System X11R4, contributed software
including libraries, games, Andrew and toolkits.

For Suns and other Unix Systems, on QIC-24 DC300XLP 1/4 inch cartridge
tape, Unix tar format:

________ $175 GNU Emacs and other software, as in the first item.

________ $175 GNU Beta Test tape, for Suns, as in the second item.

________ $175 GNU Experimental software, as in the third item (Nov. 1990).

________ $175 Required MIT X Window System X11R4, as in the fourth item.

________ $175 Optional MIT X Window System X11R4, as in the fifth item.

For VMS systems, on 1600 bpi reel-to-reel 9-track tape in VMS BACKUP
format:

________ $150 GNU Emacs source code and binaries.

________ $150 GNU C compiler source code and binaries.
Includes Bison and GAS.

GNU Emacs manual, ~300 pages, phototypeset, offset printed, spiral
bound, with a reference card.

________ $15 A single GNU Emacs manual. This price may go up in Jan 1991.

________ $60 Box of six GNU Emacs manuals.

The following documentation:

________ $1 One GNU Emacs reference card, without the manual.

________ $5 Packet of ten GNU Emacs reference cards.

________ $50 Gnu Emacs Lisp Reference Manual, ~550 pages.

________ $10 GDB Manual, ~70 pages, side stapled.

________ $10 Texinfo Manual, ~100 pages, side stapled. Texinfo is GNU's
structured documentation system, included with GNU Emacs.
Texinfo is used to produce both on-line and printed documents.
This manual describes how to write Texinfo documents.

________ $10 Termcap Manual, ~60 pages, side stapled. Documents the
termcap library and GNU's extensions to it. The GNU termcap
library is included with GNU Emacs.

________ $10 Bison Manual, ~80 pages, side stapled.

________ $10 Gawk Manual, ~100 pages, side stapled.

________ $10 Make Manual, ~100 pages, side stapled.
--------

________ Sub Total

________ If ordering from Massachusetts: add 5% sales tax.

________ If outside of North America and Hawaii, for shipping costs:
- for tapes or unboxed manuals, please add $15, and then add
$15 more for each tape or unboxed manual in the order:
________ total $ amount for this item = $15 + $15 times number;
- for each box of Emacs manuals,
________ please add $60.

________ Optional tax deductible donation.
--------

________ Total paid

Orders are filled upon receipt of check or money order. We do not have
the staff to handle the billing of unpaid orders. Please help keep
our lives simple by including your payment with your order.

Please make checks payable to Free Software Foundation. Mail orders to:

Free Software Foundation, Inc.
675 Massachusetts Avenue
Cambridge, MA 02139

+1 617-876-3296

EFFECTIVE: June 1990 to January 1991

Name:
----------------------------------------------------------------

Organization:
--------------------------------------------------------

Street Address:
------------------------------------------------------

City / State / Zip:
--------------------------------------------------
----------------------------------------------------------------------
enjoy -len

PS: By the way, what do you think of look-and-feel lawsuits?

Technical Details

Message-ID: <9101081921.AA00736@spiff.ai.mit.edu>

Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!tut.cis.ohio-state.edu!AI.MIT.EDU!tower

References: <1991Jan7.191103.1904@vax5.cit.cornell.edu>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1025b4,3eb9415cefa1229b
X-Google-Attributes: gid1025b4,public
X-Google-ArrivalTime: 1991-01-08 22:55:22 PST
Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!tut.cis.ohio-state.edu!AI.MIT.EDU!tower
From: tower@AI.MIT.EDU (Leonard H. Tower Jr.)
Newsgroups: gnu.misc.discuss
Subject: new
Message-ID: <9101081921.AA00736@spiff.ai.mit.edu>
Date: 8 Jan 91 19:21:09 GMT
References: <1991Jan7.191103.1904@vax5.cit.cornell.edu>
Sender: karl@tut.cis.ohio-state.edu
Reply-To: tower@prep.ai.mit.edu
Distribution: gnu
Organization: Project GNU, Free Software Foundation,
    675 Massachusetts Ave., Cambridge, MA  02139, USA   +1 (617) 876-3296
Lines: 2105

Reply to Parent Message