275 lines
11 KiB
HTML
275 lines
11 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
|
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>Appendix: How to Apply These Terms to Your New Programs</TITLE>
|
|
</HEAD>
|
|
<BODY LANG="EN">
|
|
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node290.html"> About this document </A>
|
|
<B>Up:</B> <A HREF="node286.html">The GNU General Public </A>
|
|
<B> Previous:</B> <A HREF="node288.html">Terms and Conditions for </A>
|
|
<BR> <P>
|
|
<H1><A NAME="SECTION0024300000">Appendix: How to Apply These Terms to Your New Programs</A></H1>
|
|
<P>
|
|
If you develop a new program, and you want it to be of the greatest
|
|
possible use to the public, the best way to achieve this is to make it
|
|
free software which everyone can redistribute and change under these terms.
|
|
<P>
|
|
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.
|
|
<P>
|
|
<BLOCKQUOTE> one line to give the program's name and a brief idea of
|
|
what it does.
|
|
Copyright ©19yy name of author
|
|
<P>
|
|
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 2 of the License, or
|
|
(at your option) any later version.
|
|
<P>
|
|
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.
|
|
<P>
|
|
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.
|
|
</BLOCKQUOTE>
|
|
<P>
|
|
Also add information on how to contact you by electronic and paper mail.
|
|
<P>
|
|
If the program is interactive, make it output a short notice like this
|
|
when it starts in an interactive mode:
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
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.
|
|
<P>
|
|
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 is a sample; alter the names:
|
|
<P>
|
|
<BLOCKQUOTE> Yoyodyne, Inc., hereby disclaims all copyright interest in the program
|
|
`Gnomovision' (which makes passes at compilers) written by James Hacker.
|
|
<P>
|
|
signature of Ty Coon, 1 April 1989
|
|
Ty Coon, President of Vice
|
|
</BLOCKQUOTE>
|
|
<P>
|
|
This General Public License does not permit incorporating your program into
|
|
proprietary programs. If your program is a subroutine library, you may
|
|
consider it more useful to permit linking proprietary applications with the
|
|
library. If this is what you want to do, use the GNU Library General
|
|
Public License instead of this License.
|
|
<P>
|
|
%
|
|
<P>
|
|
Glossary
|
|
<A NAME="glossary"></A>
|
|
<P>
|
|
<B>[Meta: This could use more entries, and a little polishing.
|
|
Feel free to make suggestions.]</B>
|
|
<P>
|
|
An enormous difficulty in networking is to remember what all the
|
|
abbreviations and terms one encounters really mean. Here's a list of
|
|
those used frequently throughout the guide, along with a short
|
|
explanation.
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
%
|
|
<P>
|
|
Annotated Bibliography
|
|
Books
|
|
<P>
|
|
The following is a list of books you might want to read to if you want
|
|
to know more about some of the topics covered in the Networking Guide.
|
|
It is not very complete or systematic, I just happen to have read them
|
|
and find them quite useful. Any additions to, and enhancement of
|
|
this list are welcome.
|
|
<P>
|
|
General Books on the Internet
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
Administration Issues
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
The Background
|
|
<P>
|
|
The following is a list of books that might be of interest to
|
|
people who want to know more about <em>how</em> TCP/IP and its
|
|
applications work, but don't want to read RFCs.
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
HOWTOs
|
|
The following is an excerpt of the HOWTO-INDEX, version-2.0
|
|
(17-March 1994), written by Matt Welsh.
|
|
<P>
|
|
What are HOWTOs?
|
|
<P>
|
|
HOWTOs are short online documents which describe in detail a
|
|
certain aspect of configuring or using the system. For example,
|
|
there is the Installation HOWTO, which gives instructions on
|
|
installing , and the Mail HOWTO, which describes how to set up
|
|
and configure mail under . Other examples include the
|
|
NET-2-HOWTO (previously the NET-2-FAQ) and the Printing HOWTO.
|
|
<P>
|
|
Information in HOWTOs is generally more detailed and in-depth than
|
|
what can be squeezed into the FAQ. For this reason, the
|
|
FAQ is being rewritten. A large amount of the information contained
|
|
therein will be relegated to various HOWTO documents. The FAQ will be
|
|
a shorter list of frequently asked questions about , covering
|
|
small specific topics. Most of the ``useful'' information in the FAQ
|
|
will now be covered in the HOWTOs.
|
|
<P>
|
|
HOWTOs are comprehensive documents--much like an FAQ but generally
|
|
not in question-and-answer format. However, many HOWTOs contain an FAQ
|
|
section at the end. For example, the NET-2-FAQ has been renamed to the
|
|
NET-2-HOWTO, because it wasn't in question-and-answer format. However,
|
|
you will see the NET-2-HOWTO named as the NET-2-FAQ in many places.
|
|
The two docs are one and the same.
|
|
<P>
|
|
Where to get HOWTOs
|
|
<P>
|
|
HOWTOs can be retrieved via anonymous FTP from the following sites:
|
|
<P>
|
|
<UL><LI>
|
|
sunsite.unc.edu:/pub//docs/HOWTO<LI>
|
|
tsx-11.mit.edu:/pub/linux/docs/HOWTO
|
|
</UL>
|
|
<P>
|
|
as well as the many mirror sites, which are listed in the
|
|
META-FAQ (see below).
|
|
<P>
|
|
The Index, printed below, lists the currently available HOWTOs.
|
|
<P>
|
|
HOWTOs are also posted regularly to the newsgroups comp.os.linux and
|
|
comp.os.linux.announce. In addition, a number of the HOWTOs will be
|
|
cross-posted to news.answers. Therefore, you can find the
|
|
HOWTOs on the news.answers archive site rtfm.mit.edu.
|
|
<P>
|
|
HOWTO Index
|
|
<P>
|
|
The following HOWTOs are currently available.
|
|
<P>
|
|
<UL><LI>
|
|
Busmouse HOWTO, by mike@starbug.apana.org.au (Mike
|
|
Battersby). Information on bus mouse compatibility with .<LI>
|
|
CDROM HOWTO, by tranter@software.mitel.com (Jeff Tranter).
|
|
Information on CD-ROM drive compatibility for .<LI>
|
|
DOSEMU HOWTO, by deisher@enws125.EAS.ASU.EDU (Michael E.
|
|
Deisher). HOWTO about the MS-DOS Emulator, DOSEMU.<LI>
|
|
Distribution HOWTO, by mdw@sunsite.unc.edu (Matt Welsh). A
|
|
list of mail order distributions and other commercial services.<LI>
|
|
Ethernet HOWTO, by Paul Gortmaker
|
|
gpg109@rsphysse.anu.edu.au. Information on Ethernet hardware
|
|
compatibility for .<LI>
|
|
Ftape HOWTO, by ftape@mic.dth.dk ( ftape-HOWTO
|
|
maintainer). Information on ftape drive compatibility with .<LI>
|
|
HOWTO Index, by mdw@sunsite.unc.edu (Matt Welsh). Index of
|
|
HOWTO documents about .<LI>
|
|
Hardware Compatibility HOWTO, by erc@apple.com (Ed Carp). A
|
|
near-extensive list of hardware known to work with .<LI>
|
|
Installation HOWTO, by mdw@sunsite.unc.edu (Matt Welsh). How
|
|
to obtain and install the software.<LI>
|
|
JE-HOWTO, by Yasuhiro Yamazaki
|
|
hiro@rainbow.physics.utoronto.ca. Information on JE, a set of
|
|
Japanese language extensions for .<LI>
|
|
Keystroke HOWTO, by Zenon Fortuna (zenon@netcom.com).
|
|
HOWTO bind macro actions to keystrokes under .<LI>
|
|
MGR HOWTO, by broman@Np.nosc.mil (Vincent Broman).
|
|
Information on the MGR graphics interface for .<LI>
|
|
Electronic Mail HOWTO, by vince@victrola.wa.com (Vince
|
|
Skahan). Information on -based mail servers and clients.<LI>
|
|
NET-2 HOWTO, by terryd@extro.ucc.su.oz.au (Terry Dawson).
|
|
HOWTO configure TCP/IP networking, SLIP, PLIP, and PPP under .<LI>
|
|
News HOWTO, by vince@victrola.wa.com (Vince Skahan).
|
|
Information on USENET news server and client software for .<LI>
|
|
PCI-HOWTO, by Michael Will
|
|
michaelw@desaster.student.uni-tuebingen.de. Information on
|
|
PCI-architecture compatibility with .<LI>
|
|
Printing HOWTO, by gtaylor@cs.tufts.edu (Grant Taylor).
|
|
HOWTO on printing software for .<LI>
|
|
SCSI HOWTO, by Drew Eckhardt drew@kinglear.cs.Colorado.EDU.
|
|
Information on SCSI driver compatibility with .<LI>
|
|
Serial HOWTO, by gregh@cc.gatech.edu (Greg Hankins).
|
|
Information on use of serial devices and communications software.<LI>
|
|
Sound HOWTO, by tranter@software.mitel.com (Jeff Tranter).
|
|
Sound hardware and software for the operating system.<LI>
|
|
Term HOWTO, by Bill Reynolds bill@goshawk.lanl.gov. HOWTO
|
|
use the `term' communications package on systems.<LI>
|
|
Tips HOWTO, by Vince Reed reedv@rpi.edu. HOWTO on
|
|
miscellaneous tips and tricks for .<LI>
|
|
UUCP HOWTO, by vince@victrola.wa.com (Vince Skahan).
|
|
Information on UUCP software for .<LI>
|
|
XFree86 HOWTO, by geyer@polyhymnia.iwr.uni-heidelberg.de
|
|
(Helmut Geyer). HOWTO on installation of XFree86 (X11R5) for .
|
|
</UL>
|
|
<P>
|
|
Miscellaneous and Legalese
|
|
<P>
|
|
If you have questions, please feel free to mail
|
|
mdw@sunsite.unc.edu. The FAQ rewrite is being coordinated by
|
|
Ian Jackson, ijackson@nyx.cs.du.edu, with help from others.
|
|
<P>
|
|
Unless otherwise stated, HOWTO documents are copyrighted by their
|
|
respective authors. HOWTO documents may be reproduced and distributed
|
|
in whole or in part, in any medium physical or electronic, without
|
|
permission of the author. Translations and derivative works are similarly
|
|
permitted without express permission. Commercial redistribution is allowed
|
|
and encouraged; however, the author would like to be notified of any such
|
|
distributions.
|
|
<P>
|
|
In short, we wish to promote dissemination of this information through as
|
|
many channels as possible. However, we do wish to retain copyright on the
|
|
HOWTO documents, and would like to be notified of any plans to redistribute
|
|
the HOWTOs. If you have questions, please contact Matt Welsh, the
|
|
HOWTO coordinator, at mdw@sunsite.unc.edu.
|
|
<P>
|
|
RFCs
|
|
<P>
|
|
The following is a list of RFCs mentioned throughout this book. All
|
|
RFCs are available via anonymous FTP from nic.ddn.mil,
|
|
ftp.uu.net. To obtain an RFC via email, send a message to
|
|
service@nic.ddn.mil, putting the request send
|
|
RFC-number.TXT in the subject header line.
|
|
<P>
|
|
<P><P>
|
|
<P>
|
|
%
|
|
<P>
|
|
<HR><A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
|
|
<B> Next:</B> <A HREF="node290.html"> About this document </A>
|
|
<B>Up:</B> <A HREF="node286.html">The GNU General Public </A>
|
|
<B> Previous:</B> <A HREF="node288.html">Terms and Conditions for </A>
|
|
<P><ADDRESS>
|
|
<I>Andrew Anderson <BR>
|
|
Thu Mar 7 23:22:06 EST 1996</I>
|
|
</ADDRESS>
|
|
</BODY>
|
|
</HTML>
|