[GNUnet-SVN] [gnunet-texinfo] branch master updated: 'user.texi': include fdl + gpl as files in appendix, clean up @settitle imports. '.gitignore': Add *.cp, *.cps

[gnunet]

This is an automated email from the git hooks/post-receive script.

ng0 pushed a commit to branch master
in repository gnunet-texinfo.

The following commit(s) were added to refs/heads/master by this push:
     new 9ef18b3  'user.texi': include fdl + gpl as files in appendix, clean up 
@settitle imports. '.gitignore': Add *.cp, *.cps
9ef18b3 is described below

commit 9ef18b3bcda1194ce60d30db052a3077b8859fbf
Author: ng0 <address@hidden>
AuthorDate: Fri Feb 17 16:57:59 2017 +0000

    'user.texi': include fdl + gpl as files in appendix,
    clean up @settitle imports.
    '.gitignore': Add *.cp, *.cps
---
 .gitignore   |   2 +
 fdl-1.3.texi | 505 +++++++++++++++++++++++++++++++++++++++++
 gpl-3.0.texi | 717 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 user.texi    | 318 +++++++++++++-------------
 4 files changed, 1373 insertions(+), 169 deletions(-)

diff --git a/.gitignore b/.gitignore
index c541888..fa476e1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,5 @@
 *.aux
 *.pdf
 *.toc
+*.cp
+*.cps
diff --git a/fdl-1.3.texi b/fdl-1.3.texi
new file mode 100644
index 0000000..cb71f05
--- /dev/null
+++ b/fdl-1.3.texi
@@ -0,0 +1,505 @@
address@hidden The GNU Free Documentation License.
address@hidden Version 1.3, 3 November 2008
+
address@hidden This file is intended to be included within another document,
address@hidden hence no sectioning command or @node.
+
address@hidden
+Copyright @copyright{} 2000, 2001, 2002, 2007, 2008 Free Software Foundation, 
Inc.
address@hidden://fsf.org/}
+
+Everyone is permitted to copy and distribute verbatim copies
+of this license document, but changing it is not allowed.
address@hidden display
+
address@hidden 0
address@hidden
+PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document @dfn{free} in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+This License is a kind of ``copyleft'', which means that derivative
+works of the document must themselves be free in the same sense.  It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does.  But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book.  We recommend this License
+principally for works whose purpose is instruction or reference.
+
address@hidden
+APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License.  Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein.  The ``Document'', below,
+refers to any such manual or work.  Any member of the public is a
+licensee, and is addressed as ``you''.  You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A ``Modified Version'' of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A ``Secondary Section'' is a named appendix or a front-matter section
+of the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject.  (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.)  The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The ``Invariant Sections'' are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License.  If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant.  The Document may contain zero
+Invariant Sections.  If the Document does not identify any Invariant
+Sections then there are none.
+
+The ``Cover Texts'' are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License.  A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+A ``Transparent'' copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters.  A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text.  A copy that is not ``Transparent'' is called ``Opaque''.
+
+Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, address@hidden input
+format, SGML or XML using a publicly available
+DTD, and standard-conforming simple HTML,
+PostScript or PDF designed for human modification.  Examples
+of transparent image formats include PNG, XCF and
+JPG.  Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, SGML or
+XML for which the DTD and/or processing tools are
+not generally available, and the machine-generated HTML,
+PostScript or PDF produced by some word processors for
+output purposes only.
+
+The ``Title Page'' means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page.  For works in
+formats which do not have any title page as such, ``Title Page'' means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+The ``publisher'' means any person or entity that distributes copies
+of the Document to the public.
+
+A section ``Entitled XYZ'' means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language.  (Here XYZ stands for a
+specific section name mentioned below, such as ``Acknowledgements'',
+``Dedications'', ``Endorsements'', or ``History''.)  To ``Preserve the Title''
+of such a section when you modify the Document means that it remains a
+section ``Entitled XYZ'' according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document.  These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
address@hidden
+VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License.  You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute.  However, you may accept
+compensation in exchange for copies.  If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
address@hidden
+COPYING IN QUANTITY
+
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover.  Both covers must also clearly and legibly identify
+you as the publisher of these copies.  The front cover must present
+the full title with all words of the title equally prominent and
+visible.  You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
address@hidden
+MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it.  In addition, you must do these things in the Modified Version:
+
address@hidden A
address@hidden
+Use in the Title Page (and on the covers, if any) a title distinct
+from that of the Document, and from those of previous versions
+(which should, if there were any, be listed in the History section
+of the Document).  You may use the same title as a previous version
+if the original publisher of that version gives permission.
+
address@hidden
+List on the Title Page, as authors, one or more persons or entities
+responsible for authorship of the modifications in the Modified
+Version, together with at least five of the principal authors of the
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
+
address@hidden
+State on the Title page the name of the publisher of the
+Modified Version, as the publisher.
+
address@hidden
+Preserve all the copyright notices of the Document.
+
address@hidden
+Add an appropriate copyright notice for your modifications
+adjacent to the other copyright notices.
+
address@hidden
+Include, immediately after the copyright notices, a license notice
+giving the public permission to use the Modified Version under the
+terms of this License, in the form shown in the Addendum below.
+
address@hidden
+Preserve in that license notice the full lists of Invariant Sections
+and required Cover Texts given in the Document's license notice.
+
address@hidden
+Include an unaltered copy of this License.
+
address@hidden
+Preserve the section Entitled ``History'', Preserve its Title, and add
+to it an item stating at least the title, year, new authors, and
+publisher of the Modified Version as given on the Title Page.  If
+there is no section Entitled ``History'' in the Document, create one
+stating the title, year, authors, and publisher of the Document as
+given on its Title Page, then add an item describing the Modified
+Version as stated in the previous sentence.
+
address@hidden
+Preserve the network location, if any, given in the Document for
+public access to a Transparent copy of the Document, and likewise
+the network locations given in the Document for previous versions
+it was based on.  These may be placed in the ``History'' section.
+You may omit a network location for a work that was published at
+least four years before the Document itself, or if the original
+publisher of the version it refers to gives permission.
+
address@hidden
+For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
+
address@hidden
+Preserve all the Invariant Sections of the Document,
+unaltered in their text and in their titles.  Section numbers
+or the equivalent are not considered part of the section titles.
+
address@hidden
+Delete any section Entitled ``Endorsements''.  Such a section
+may not be included in the Modified Version.
+
address@hidden
+Do not retitle any existing section to be Entitled ``Endorsements'' or
+to conflict in title with any Invariant Section.
+
address@hidden
+Preserve any Warranty Disclaimers.
address@hidden enumerate
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant.  To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section Entitled ``Endorsements'', provided it contains
+nothing but endorsements of your Modified Version by various
+parties---for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version.  Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity.  If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
address@hidden
+COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy.  If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections Entitled ``History''
+in the various original documents, forming one section Entitled
+``History''; likewise combine any sections Entitled ``Acknowledgements'',
+and any sections Entitled ``Dedications''.  You must delete all
+sections Entitled ``Endorsements.''
+
address@hidden
+COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
address@hidden
+AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an ``aggregate'' if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
address@hidden
+TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections.  You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers.  In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled ``Acknowledgements'',
+``Dedications'', or ``History'', the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
address@hidden
+TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense, or distribute it is void, and
+will automatically terminate your rights under this License.
+
+However, if you cease all violation of this License, then your license
+from a particular copyright holder is reinstated (a) provisionally,
+unless and until the copyright holder explicitly and finally
+terminates your license, and (b) permanently, if the copyright holder
+fails to notify you of the violation by some reasonable means prior to
+60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, receipt of a copy of some or all of the same material does
+not give you any rights to use it.
+
address@hidden
+FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation 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.  See
address@hidden://www.gnu.org/copyleft/}.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License ``or any later version'' applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation.  If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.  If the Document
+specifies that a proxy can decide which future versions of this
+License can be used, that proxy's public statement of acceptance of a
+version permanently authorizes you to choose that version for the
+Document.
+
address@hidden
+RELICENSING
+
+``Massive Multiauthor Collaboration Site'' (or ``MMC Site'') means any
+World Wide Web server that publishes copyrightable works and also
+provides prominent facilities for anybody to edit those works.  A
+public wiki that anybody can edit is an example of such a server.  A
+``Massive Multiauthor Collaboration'' (or ``MMC'') contained in the
+site means any set of copyrightable works thus published on the MMC
+site.
+
+``CC-BY-SA'' means the Creative Commons Attribution-Share Alike 3.0
+license published by Creative Commons Corporation, a not-for-profit
+corporation with a principal place of business in San Francisco,
+California, as well as future copyleft versions of that license
+published by that same organization.
+
+``Incorporate'' means to publish or republish a Document, in whole or
+in part, as part of another Document.
+
+An MMC is ``eligible for relicensing'' if it is licensed under this
+License, and if all works that were first published under this License
+somewhere other than this MMC, and subsequently incorporated in whole
+or in part into the MMC, (1) had no cover texts or invariant sections,
+and (2) were thus incorporated prior to November 1, 2008.
+
+The operator of an MMC Site may republish an MMC contained in the site
+under CC-BY-SA on the same site at any time before August 1, 2009,
+provided the MMC is eligible for relicensing.
+
address@hidden enumerate
+
address@hidden
address@hidden ADDENDUM: How to use this License for your documents
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
address@hidden
address@hidden
+  Copyright (C)  @var{year}  @var{your name}.
+  Permission is granted to copy, distribute and/or modify this document
+  under the terms of the GNU Free Documentation License, Version 1.3
+  or any later version published by the Free Software Foundation;
+  with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+  Texts.  A copy of the license is included in the section entitled ``GNU
+  Free Documentation License''.
address@hidden group
address@hidden smallexample
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the address@hidden''@: line with this:
+
address@hidden
address@hidden
+    with the Invariant Sections being @var{list their titles}, with
+    the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
+    being @var{list}.
address@hidden group
address@hidden smallexample
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.
+
address@hidden Local Variables:
address@hidden ispell-local-pdict: "ispell-dict"
address@hidden End:
diff --git a/gpl-3.0.texi b/gpl-3.0.texi
new file mode 100644
index 0000000..0e2e212
--- /dev/null
+++ b/gpl-3.0.texi
@@ -0,0 +1,717 @@
address@hidden The GNU General Public License.
address@hidden Version 3, 29 June 2007
+
address@hidden This file is intended to be included within another document,
address@hidden hence no sectioning command or @node.
+
address@hidden
+Copyright @copyright{} 2007 Free Software Foundation, Inc. 
@url{http://fsf.org/}
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
address@hidden display
+
address@hidden Preamble
+
+The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom
+to share and change all versions of a program---to make sure it remains
+free software for all its users.  We, the Free Software Foundation,
+use the GNU General Public License for most of our software; it
+applies also to any other work released this way by its authors.  You
+can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), 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 prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you
+have certain responsibilities if you distribute copies of the
+software, or if you modify it: responsibilities to respect the freedom
+of others.
+
+For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too,
+receive or can get the source code.  And you must show them these
+terms so they know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the
+manufacturer can do so.  This is fundamentally incompatible with the
+aim of protecting users' freedom to change the software.  The
+systematic pattern of such abuse occurs in the area of products for
+individuals to use, which is precisely where it is most unacceptable.
+Therefore, we have designed this version of the GPL to prohibit the
+practice for those products.  If such problems arise substantially in
+other domains, we stand ready to extend this provision to those
+domains in future versions of the GPL, as needed to protect the
+freedom of users.
+
+Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish
+to avoid the special danger that patents applied to a free program
+could make it effectively proprietary.  To prevent this, the GPL
+assures that patents cannot be used to render the program non-free.
+
+The precise terms and conditions for copying, distribution and
+modification follow.
+
address@hidden TERMS AND CONDITIONS
+
address@hidden 0
address@hidden Definitions.
+
+``This License'' refers to version 3 of the GNU General Public License.
+
+``Copyright'' also means copyright-like laws that apply to other kinds
+of works, such as semiconductor masks.
+
+``The Program'' refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as ``you''.  ``Licensees'' and
+``recipients'' may be individuals or organizations.
+
+To ``modify'' a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of
+an exact copy.  The resulting work is called a ``modified version'' of
+the earlier work or a work ``based on'' the earlier work.
+
+A ``covered work'' means either the unmodified Program or a work based
+on the Program.
+
+To ``propagate'' a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+To ``convey'' a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user
+through a computer network, with no transfer of a copy, is not
+conveying.
+
+An interactive user interface displays ``Appropriate Legal Notices'' to
+the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
address@hidden Source Code.
+
+The ``source code'' for a work means the preferred form of the work for
+making modifications to it.  ``Object code'' means any non-source form
+of a work.
+
+A ``Standard Interface'' means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+The ``System Libraries'' of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+``Major Component'', in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+The ``Corresponding Source'' for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can
+regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same
+work.
+
address@hidden Basic Permissions.
+
+All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey,
+without conditions so long as your license otherwise remains in force.
+You may convey covered works to others for the sole purpose of having
+them make modifications exclusively for you, or provide you with
+facilities for running those works, provided that you comply with the
+terms of this License in conveying all material for which you do not
+control copyright.  Those thus making or running the covered works for
+you must do so exclusively on your behalf, under your direction and
+control, on terms that prohibit them from making any copies of your
+copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the
+conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
address@hidden Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such
+circumvention is effected by exercising rights under this License with
+respect to the covered work, and you disclaim any intention to limit
+operation or modification of the work as a means of enforcing, against
+the work's users, your or third parties' legal rights to forbid
+circumvention of technological measures.
+
address@hidden Conveying Verbatim Copies.
+
+You may convey 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;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
address@hidden Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these
+conditions:
+
address@hidden a
address@hidden
+The work must carry prominent notices stating that you modified it,
+and giving a relevant date.
+
address@hidden
+The work must carry prominent notices stating that it is released
+under this License and any conditions added under section 7.  This
+requirement modifies the requirement in section 4 to ``keep intact all
+notices''.
+
address@hidden
+You must license the entire work, as a whole, under this License to
+anyone who comes into possession of a copy.  This License will
+therefore apply, along with any applicable section 7 additional terms,
+to the whole of the work, and all its parts, regardless of how they
+are packaged.  This License gives no permission to license the work in
+any other way, but it does not invalidate such permission if you have
+separately received it.
+
address@hidden
+If the work has interactive user interfaces, each must display
+Appropriate Legal Notices; however, if the Program has interactive
+interfaces that do not display Appropriate Legal Notices, your work
+need not make them do so.
address@hidden enumerate
+
+A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+``aggregate'' if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
address@hidden  Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms of
+sections 4 and 5, provided that you also convey the machine-readable
+Corresponding Source under the terms of this License, in one of these
+ways:
+
address@hidden a
address@hidden
+Convey the object code in, or embodied in, a physical product
+(including a physical distribution medium), accompanied by the
+Corresponding Source fixed on a durable physical medium customarily
+used for software interchange.
+
address@hidden
+Convey the object code in, or embodied in, a physical product
+(including a physical distribution medium), accompanied by a written
+offer, valid for at least three years and valid for as long as you
+offer spare parts or customer support for that product model, to give
+anyone who possesses the object code either (1) a copy of the
+Corresponding Source for all the software in the product that is
+covered by this License, on a durable physical medium customarily used
+for software interchange, for a price no more than your reasonable
+cost of physically performing this conveying of source, or (2) access
+to copy the Corresponding Source from a network server at no charge.
+
address@hidden
+Convey individual copies of the object code with a copy of the written
+offer to provide the Corresponding Source.  This alternative is
+allowed only occasionally and noncommercially, and only if you
+received the object code with such an offer, in accord with subsection
+6b.
+
address@hidden
+Convey the object code by offering access from a designated place
+(gratis or for a charge), and offer equivalent access to the
+Corresponding Source in the same way through the same place at no
+further charge.  You need not require recipients to copy the
+Corresponding Source along with the object code.  If the place to copy
+the object code is a network server, the Corresponding Source may be
+on a different server (operated by you or a third party) that supports
+equivalent copying facilities, provided you maintain clear directions
+next to the object code saying where to find the Corresponding Source.
+Regardless of what server hosts the Corresponding Source, you remain
+obligated to ensure that it is available for as long as needed to
+satisfy these requirements.
+
address@hidden
+Convey the object code using peer-to-peer transmission, provided you
+inform other peers where the object code and Corresponding Source of
+the work are being offered to the general public at no charge under
+subsection 6d.
+
address@hidden enumerate
+
+A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+A ``User Product'' is either (1) a ``consumer product'', which means any
+tangible personal property which is normally used for personal,
+family, or household purposes, or (2) anything designed or sold for
+incorporation into a dwelling.  In determining whether a product is a
+consumer product, doubtful cases shall be resolved in favor of
+coverage.  For a particular product received by a particular user,
+``normally used'' refers to a typical or common use of that class of
+product, regardless of the status of the particular user or of the way
+in which the particular user actually uses, or expects or is expected
+to use, the product.  A product is a consumer product regardless of
+whether the product has substantial commercial, industrial or
+non-consumer uses, unless such uses represent the only significant
+mode of use of the product.
+
+``Installation Information'' for a User Product means any methods,
+procedures, authorization keys, or other information required to
+install and execute modified versions of a covered work in that User
+Product from a modified version of its Corresponding Source.  The
+information must suffice to ensure that the continued functioning of
+the modified object code is in no case prevented or interfered with
+solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or
+updates for a work that has been modified or installed by the
+recipient, or for the User Product in which it has been modified or
+installed.  Access to a network may be denied when the modification
+itself materially and adversely affects the operation of the network
+or violates the rules and protocols for communication across the
+network.
+
+Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
address@hidden Additional Terms.
+
+``Additional permissions'' are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders
+of that material) supplement the terms of this License with terms:
+
address@hidden a
address@hidden
+Disclaiming warranty or limiting liability differently from the terms
+of sections 15 and 16 of this License; or
+
address@hidden
+Requiring preservation of specified reasonable legal notices or author
+attributions in that material or in the Appropriate Legal Notices
+displayed by works containing it; or
+
address@hidden
+Prohibiting misrepresentation of the origin of that material, or
+requiring that modified versions of such material be marked in
+reasonable ways as different from the original version; or
+
address@hidden
+Limiting the use for publicity purposes of names of licensors or
+authors of the material; or
+
address@hidden
+Declining to grant rights under trademark law for use of some trade
+names, trademarks, or service marks; or
+
address@hidden
+Requiring indemnification of licensors and authors of that material by
+anyone who conveys the material (or modified versions of it) with
+contractual assumptions of liability to the recipient, for any
+liability that these contractual assumptions directly impose on those
+licensors and authors.
address@hidden enumerate
+
+All other non-permissive additional terms are considered ``further
+restrictions'' within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions; the
+above requirements apply either way.
+
address@hidden Termination.
+
+You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+However, if you cease all violation of this License, then your license
+from a particular copyright holder is reinstated (a) provisionally,
+unless and until the copyright holder explicitly and finally
+terminates your license, and (b) permanently, if the copyright holder
+fails to notify you of the violation by some reasonable means prior to
+60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
address@hidden Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run
+a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
address@hidden Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+An ``entity transaction'' is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
address@hidden Patents.
+
+A ``contributor'' is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's ``contributor version''.
+
+A contributor's ``essential patent claims'' are all patent claims owned
+or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, ``control'' includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+In the following three paragraphs, a ``patent license'' is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To ``grant'' such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  ``Knowingly relying'' means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+A patent license is ``discriminatory'' if it does not include within the
+scope of its coverage, prohibits the exercise of, or is conditioned on
+the non-exercise of one or more of the rights that are specifically
+granted under this License.  You may not convey a covered work if you
+are a party to an arrangement with a third party that is in the
+business of distributing software, under which you make payment to the
+third party based on the extent of your activity of conveying the
+work, and under which the third party grants, to any of the parties
+who would receive the covered work from you, a discriminatory patent
+license (a) in connection with copies of the covered work conveyed by
+you (or copies made from those copies), or (b) primarily for and in
+connection with specific products or compilations that contain the
+covered work, unless you entered into that arrangement, or that patent
+license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
address@hidden No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey
+a covered work so as to satisfy simultaneously your obligations under
+this License and any other pertinent obligations, then as a
+consequence you may not convey it at all.  For example, if you agree
+to terms that obligate you to collect a royalty for further conveying
+from those to whom you convey the Program, the only way you could
+satisfy both those terms and this License would be to refrain entirely
+from conveying the Program.
+
address@hidden Use with the GNU Affero General Public License.
+
+Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
address@hidden Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions
+of the GNU 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 that a certain numbered version of the GNU General Public
+License ``or any later version'' applies to it, you have the option of
+following the terms and conditions either of that numbered version or
+of any later version published by the Free Software Foundation.  If
+the Program does not specify a version number of the GNU General
+Public License, you may choose any version ever published by the Free
+Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions
+of the GNU General Public License can be used, that proxy's public
+statement of acceptance of a version permanently authorizes you to
+choose that version for the Program.
+
+Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
address@hidden Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE address@hidden  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 address@hidden  THE ENTIRE RISK AS TO THE QUALITY AND
+PERFORMANCE OF THE PROGRAM IS WITH address@hidden  SHOULD THE PROGRAM PROVE
+DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
+CORRECTION.
+
address@hidden Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
+CONVEYS 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.
+
address@hidden Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
address@hidden enumerate
+
address@hidden END OF TERMS AND CONDITIONS
+
address@hidden 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 the public, 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
+state the exclusion of warranty; and each file should have at least
+the ``copyright'' line and a pointer to where the full notice is found.
+
address@hidden
address@hidden line to give the program's name and a brief idea of what it 
does.}
+Copyright (C) @var{year} @var{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 3 of the License, 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 address@hidden  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, see @url{http://www.gnu.org/licenses/}.
address@hidden smallexample
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
address@hidden
address@hidden Copyright (C) @var{year} @var{name of author}
+This program comes with ABSOLUTELY NO WARRANTY; for details type @samp{show w}.
+This is free software, and you are welcome to redistribute it
+under certain conditions; type @samp{show c} for details.
address@hidden smallexample
+
+The hypothetical commands @samp{show w} and @samp{show c} should show
+the appropriate parts of the General Public License.  Of course, your
+program's commands might be different; for a GUI interface, you would
+use an ``about box''.
+
+You should also get your employer (if you work as a programmer) or school,
+if any, to sign a ``copyright disclaimer'' for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
address@hidden://www.gnu.org/licenses/}.
+
+The GNU 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 Lesser General Public License instead of this License.  But
+first, please read @url{http://www.gnu.org/philosophy/why-not-lgpl.html}.
diff --git a/user.texi b/user.texi
index 4e640a7..c9d5431 100644
--- a/user.texi
+++ b/user.texi
@@ -27,7 +27,12 @@ Foundation Web site at 
@url{http://www.gnu.org/licenses/gpl.html}.
 
 @dircategory User Handbook of GNUnet
 @direntry
-* foo
+* Introduction
+* Tutorial: using GNUnet
+  * Checking the Installation
+  * gnunet-gtk
+  * Statistics
+  * Peer Information
 @end direntry
 
 @titlepage
@@ -37,7 +42,7 @@ Foundation Web site at 
@url{http://www.gnu.org/licenses/gpl.html}.
 @page
 @vskip 0pt plus 1filll
 Edition @value{EDITION} @*
address@hidden @*
address@hidden @*
 
 @insertcopying
 @end titlepage
@@ -66,9 +71,9 @@ profile ID number included. We will then relax these 
restrictions on your
 account. We're sorry for this inconvenience; however, few people would want to
 read this site if 99% of it was advertisements for bogus websites.
 
address@hidden Tutorial: Using GNUnet
address@hidden Tutorial: Using GNUnet
address@hidden Tutorial: Using GNUnet
 @c %**end of header
address@hidden Top
 
 This tutorial is supposed to give a first introduction for end-users trying to
 do something "real" with GNUnet. Installation and configuration are 
specifically
@@ -76,51 +81,41 @@ outside of the scope of this tutorial. Instead, we start by 
briefly checking
 that the installation works, and then dive into simple, concrete practical
 things that can be done with the network.
 
address@hidden Checking the Installation
address@hidden Checking the Installation
address@hidden Checking the Installation
 @c %**end of header
address@hidden Top
 
 This chapter describes a quick casual way to check if your GNUnet installation
 works. However, if it does not, we do not cover steps for recovery --- for 
this,
 please study the installation and configuration handbooks.
 
address@hidden gnunet-gtk
address@hidden gnunet-gtk
address@hidden gnunet-gtk
 @c %**end of header
address@hidden Top
 
 First, you should launch @code{gnunet-gtk}, the graphical user interface for
 GNUnet which will be used for most of the tutorial. You can do this from the
 command-line by typing@
address@hidden@ $ address@hidden@
address@hidden@ $ gnunet-gtk}@
 (note that @code{$} represents the prompt of the shell for a normal user).
 Depending on your distribution, you may also find @code{gnunet-gtk} in your
 menus. After starting @code{gnunet-gtk}, you should see the following window:
 
address@hidden/gnunet-gtk-0-10.png,5in,, picture of gnunet-gtk application}
address@hidden/gnunet-gtk-0-10,5in,, picture of gnunet-gtk application}
 
 The five images on top represent the five different graphical applications that
 you can use within @code{gnunet-gtk}. They are (from left to right):
 @itemize @bullet
-
address@hidden
-Statistics
-
address@hidden
-Peer Information
-
address@hidden
-GNU Name System
-
address@hidden
-File Sharing
-
address@hidden
-Identity Management
address@hidden Statistics
address@hidden Peer Information
address@hidden GNU Name System
address@hidden File Sharing
address@hidden Identity Management
 @end itemize
 
address@hidden Statistics
address@hidden Statistics
address@hidden Statistics
 @c %**end of header
address@hidden Top
 
 When @code{gnunet-gtk} is started, the statistics area should be selected at
 first. If your peer is running correctly, you should see a bunch of lines, all
@@ -135,9 +130,9 @@ peer has consumed, and on "Storage" to check the amount of 
storage available and
 used by your peer. Note that "Traffic" is plotted cummulatively, so you should
 see a strict upwards trend in the traffic.
 
address@hidden Peer Information
address@hidden Peer Information
address@hidden Peer Information
 @c %**end of header
address@hidden Top
 
 You should now click on the Australian Aboriginal Flag. Once you have done 
this,
 you will see a list of known peers (by the first four characters of their 
public
@@ -150,9 +145,10 @@ connectivity, there is likely a problem with your network 
configuration.
 
 @multitable @columnfractions 0.333333333333333 0.333333333333333 
0.333333333333333
 @end multitable
address@hidden First steps: File-sharing
+
address@hidden First steps: File-sharing
address@hidden First steps: File-sharing
 @c %**end of header
address@hidden Top
 
 This chapter describes first steps for file-sharing with GNUnet. To start, you
 should launch @code{gnunet-gtk} and select the file-sharing tab (the one with
@@ -161,9 +157,9 @@ the arrows between the three circles).
 As we want to be sure that the network contains the data that we are looking 
for
 for testing, we need to begin by publishing a file.
 
address@hidden Publishing
address@hidden Publishing
address@hidden Publishing
 @c %**end of header
address@hidden Top
 
 To publish a file, select "File Sharing" in the menu bar just below the
 "Statistics" icon, and then select "Publish" from the menu. 
@@ -210,9 +206,9 @@ GNUnet! Afterwards, you should see the main dialog with a 
new area showing the
 list of published files (or ongoing publishing operations with progress
 indicators):
 
address@hidden Searching
address@hidden Searching
address@hidden Searching
 @c %**end of header
address@hidden Top
 
 Below the menu bar, there are four entry widges labeled "Namespace", 
"Keywords",
 "Anonymity" and "Mime-type" (from left to right). These widgets are used to
@@ -233,9 +229,9 @@ be listed at the bottom right.
 Once a file is selected, at the bottom of the search result list a little area
 for downloading appears.
 
address@hidden Downloading
address@hidden Downloading
address@hidden Downloading
 @c %**end of header
address@hidden Top
 
 In the downloading area, you can select the target directory (default is
 "Downloads") and specify the desired filename (by default the filename it taken
@@ -260,13 +256,13 @@ That's it, you now know the basics for file-sharing with 
GNUnet!
 @multitable @columnfractions 0.0833333333333333 0.0833333333333333 
0.0833333333333333 0.0833333333333333 0.0833333333333333 0.0833333333333333 
0.0833333333333333 0.0833333333333333 0.0833333333333333 0.0833333333333333 
0.0833333333333333 0.0833333333333333
 @end multitable
 
address@hidden First steps: Using the GNU Name System
address@hidden First steps: Using the GNU Name System
address@hidden First steps: Using the GNU Name System
 @c %**end of header
address@hidden Top
 
address@hidden Preliminaries
address@hidden Preliminaries
address@hidden Preliminaries
 @c %**end of header
address@hidden Top
 
 First, we will check if the GNU Name System installation was completed 
normally.
 For this, we first start @code{gnunet-gtk} and switch to the Identity 
Management
@@ -287,9 +283,9 @@ shared with the world, and the "shorten" zone is for 
records that the system
 learns automatically. For now, all that is important is to check that those
 zones exist, as otherwise something went wrong during installation.
 
address@hidden The GNS Tab
address@hidden The GNS Tab
address@hidden The GNS Tab
 @c %**end of header
address@hidden Top
 
 Next, we switch to the GNS tab, which is the tab in the middle with the letters
 "GNS" connected by a graph. The tab shows on top the public key of the zone
@@ -310,9 +306,9 @@ entries (for the master-zone):@
 and "private" are pointers from your master zone to your shorten and private
 zones respectively.
 
address@hidden Creating a Record
address@hidden Creating a Record
address@hidden Creating a Record
 @c %**end of header
address@hidden Top
 
 We will begin by creating a simple record in your master zone. To do this, 
click
 on the text "<new name>" in the table. The field is editable, allowing you to
@@ -336,9 +332,9 @@ Once finished, press the "Save" button. Back in the main 
dialog, select the tiny
 triangle left of the "test" label. By doing so, you get to see all of the
 records under "test". Note that you can right-click a record to edit it later.
 
address@hidden Creating a Business Card
address@hidden Creating a Business Card
address@hidden Creating a Business Card
 @c %**end of header
address@hidden Top
 
 Before we can really use GNS, you should create a business card. Note that this
 requires having @code{LaTeX} installed on your system (@code{apt-get install
@@ -364,9 +360,9 @@ and a GNUnet logo. We'll explain how to use those a bit 
later. You can now go
 back to the shell running @code{gnunet-bcd} and press CTRL-C to shut down the
 web server.
 
address@hidden Resolving GNS records
address@hidden Resolving GNS records
address@hidden Resolving GNS records
 @c %**end of header
address@hidden Top
 
 Next, you should try resolving your own GNS records. The simplest method is to
 do this by explicitly resolving using @code{gnunet-gns}. In the shell, type:@
@@ -377,9 +373,9 @@ do this by explicitly resolving using @code{gnunet-gns}. In 
the shell, type:@
 }@
 That shows that resolution works, once GNS is integrated with the application.
 
address@hidden Integration with Browsers
address@hidden Integration with Browsers
address@hidden Integration with Browsers
 @c %**end of header
address@hidden Top
 
 While we recommend integrating GNS using the NSS module in the GNU libc Name
 Service Switch, you can also integrate GNS directly with your browser via the
@@ -434,9 +430,9 @@ Note that while you can use GNS to access ordinary 
websites, this is more an
 experimental feature and not really our primary goal at this time. Still, it is
 a possible use-case and we welcome help with testing and development.
 
address@hidden Be Social
address@hidden Be Social
address@hidden Be Social
 @c %**end of header
address@hidden Top
 
 Next, you should print out your business card and be social. Find a friend, 
help
 him install GNUnet and exchange business cards with him. Or, if you're a
@@ -459,9 +455,9 @@ nickname is "Bob". Then, type@
 }@
 to check if your friend was as good at following instructions as you were.
 
address@hidden What's Next?
address@hidden What's Next?
address@hidden What's Next?
 @c %**end of header
address@hidden Top
 
 This may seem not like much of an application yet, but you have just been one 
of
 the first to perform a decentralized secure name lookup (where nobody could 
have
@@ -478,9 +474,9 @@ public key infrastructure.
 @multitable @columnfractions 0.166666666666667 0.166666666666667 
0.166666666666667 0.166666666666667 0.166666666666667 0.166666666666667
 @end multitable
 
address@hidden First steps: Using GNUnet Conversation
address@hidden First steps: Using GNUnet Conversation
address@hidden First steps: Using GNUnet Conversation
 @c %**end of header
address@hidden Top
 
 Before starting the tutorial, you should be aware that
 @code{gnunet-conversation} is currently only available as an interactive shell
@@ -488,9 +484,9 @@ tool and that the call quality tends to be abysmal. There 
are also some awkward
 steps necessary to use it. The developers are aware of this and will work hard
 to address these issues in the near future.
 
address@hidden Testing your Audio Equipment
address@hidden Testing your Audio Equipment
address@hidden Testing your Audio Equipment
 @c %**end of header
address@hidden Top
 
 First, you should use @code{gnunet-conversation-test} to check that your
 microphone and speaker are working correctly. You will be prompted to speak for
@@ -500,17 +496,17 @@ configuration tool to check that microphone and speaker 
are not muted and, if
 you have multiple input/output devices, that the correct device is being
 associated with GNUnet's audio tools.
 
address@hidden GNS Zones
address@hidden GNS Zones
address@hidden GNS Zones
 @c %**end of header
address@hidden Top
 
 @code{gnunet-conversation} uses GNS for addressing. This means that you need to
 have a GNS zone created before using it. Information about how to create GNS
 zones can be found here.
 
address@hidden Picking an Identity
address@hidden Picking an Identity
address@hidden Picking an Identity
 @c %**end of header
address@hidden Top
 
 To make a call with @code{gnunet-conversation}, you first need to choose an
 identity. This identity is both the caller ID that will show up when you call
@@ -549,9 +545,9 @@ option to make the record public. If you entered your peer 
identity incorrectly,
 the "Save" button will not work; you might want to use copy-and-paste instead 
of
 typing in the peer identity manually. Save the record.
 
address@hidden Calling somebody
address@hidden Calling somebody
address@hidden Calling somebody
 @c %**end of header
address@hidden Top
 
 Now you can call a buddy. Obviously, your buddy will have to have GNUnet
 installed and must have performed the same steps. Also, you must have your 
buddy
@@ -573,21 +569,21 @@ Your buddy then can answer the call using the "/accept" 
command. After that,
 can end the call using "/cancel". You can exit @code{gnunet-converation} using
 "/quit".
 
address@hidden Future Directions
address@hidden Future Directions
address@hidden Future Directions
 @c %**end of header
address@hidden Top
 
 Note that we do not envision people to use gnunet-conversation like this
 forever. We will write a graphical user interface, and that GUI will
 automatically create the necessary records in the respective zone.
 
address@hidden First steps: Using the GNUnet VPN
address@hidden First steps: Using the GNUnet VPN
address@hidden First steps: Using the GNUnet VPN
 @c %**end of header
address@hidden Top
 
address@hidden Preliminaries
address@hidden Preliminaries
address@hidden Preliminaries
 @c %**end of header
address@hidden Top
 
 To test the GNUnet VPN, we should first run a web server. The easiest way to do
 this is to just start @code{gnunet-bcd}, which will run a webserver on port
@@ -617,9 +613,9 @@ $ cd src/gns/nss; sudo make install
 
 to install the NSS plugins in the proper location.
 
address@hidden Exit configuration
address@hidden Exit configuration
address@hidden Exit configuration
 @c %**end of header
address@hidden Top
 
 Stop your peer (as user @code{gnunet}, run @code{gnunet-arm -e}) and run
 @code{gnunet-setup}. In @code{gnunet-setup}, make sure to activate the
@@ -632,9 +628,9 @@ the 8888 port accordingly).
 
 Now exit @code{gnunet-setup} and restart your peer (@code{gnunet-arm -s}).
 
address@hidden GNS configuration
address@hidden GNS configuration
address@hidden GNS configuration
 @c %**end of header
address@hidden Top
 
 Now, using your normal user (not the @code{gnunet} system user), run
 @code{gnunet-gtk}. Select the GNS icon and add a new label www in your master
@@ -652,9 +648,9 @@ want others to be able to use the service, you should 
probably make the record
 public. For non-public services, you should use a passphrase instead of the
 string "bcd". Save the record and exit @code{gnunet-gtk}.
 
address@hidden Accessing the service
address@hidden Accessing the service
address@hidden Accessing the service
 @c %**end of header
address@hidden Top
 
 You should now be able to access your webserver. Type in:@
 @code{@
@@ -670,9 +666,9 @@ the local machine, it should also work with other peers --- 
naturally, they will
 need a way to access your GNS zone first, for example by learning your public
 key from a QR code on your business card.
 
address@hidden Using a Browser
address@hidden Using a Browser
address@hidden Using a Browser
 @c %**end of header
address@hidden Top
 
 Sadly, modern browsers tend to bypass the Name Services Switch and attempt DNS
 resolution directly. You can either run a @code{gnunet-dns2gns} DNS proxy, or
@@ -681,9 +677,9 @@ connect to the socks proxy for @code{.gnu} TLDs, even if we 
disabled its
 autoblunder of changing @code{.gnu} to ".gnu.com". Still, using the HTTP proxy
 with Chrome does work.
 
address@hidden File-sharing
address@hidden File-sharing
address@hidden File-sharing
 @c %**end of header
address@hidden Top
 
 This chapter documents the GNUnet file-sharing application. The original
 file-sharing implementation for GNUnet was designed to provide
@@ -701,9 +697,9 @@ In this chapter, we will first look at the various concepts 
in GNUnet's
 file-sharing implementation. Then, we will discuss specifics as to how they
 impact users that publish, search or download files.
 
address@hidden File-sharing: Concepts
address@hidden File-sharing: Concepts
address@hidden File-sharing: Concepts
 @c %**end of header
address@hidden Top
 
 Sharing files in GNUnet is not quite as simple as in traditional file sharing
 systems. For example, it is not sufficient to just place files into a specific
@@ -717,9 +713,9 @@ reputation. Furthermore, GNUnet allows updates to certain 
content to be made
 available. This section is supposed to introduce users to the concepts that are
 used to achive these goals.
 
address@hidden Files
address@hidden Files
address@hidden Files
 @c %**end of header
address@hidden Top
 
 A file in GNUnet is just a sequence of bytes. Any file-format is allowed and 
the
 maximum file size is theoretically 264 bytes, except that it would take an
@@ -727,9 +723,9 @@ impractical amount of time to share such a file. GNUnet 
itself never interprets
 the contents of shared files, except when using GNU libextractor to obtain
 keywords.
 
address@hidden Keywords
address@hidden Keywords
address@hidden Keywords
 @c %**end of header
address@hidden Top
 
 Keywords are the most simple mechanism to find files on GNUnet. Keywords are
 @strong{case-sensitive} and the search string must always match 
@strong{exactly}
@@ -742,9 +738,9 @@ process. Starting a keyword search on a slow machine can 
take a little while
 since the keyword search involves computing a fresh RSA key to formulate the
 request.
 
address@hidden Directories
address@hidden Directories
address@hidden Directories
 @c %**end of header
address@hidden Top
 
 A directory in GNUnet is a list of file identifiers with meta data. The file
 identifiers provide sufficient information about the files to allow downloading
@@ -753,9 +749,9 @@ is treated just like an ordinary file by the network. Small 
files (of a few
 kilobytes) can be inlined in the directory, so that a separate download becomes
 unnecessary.
 
address@hidden Pseudonyms
address@hidden Pseudonyms
address@hidden Pseudonyms
 @c %**end of header
address@hidden Top
 
 Pseudonyms in GNUnet are essentially public-private (RSA) key pairs that allow 
a
 GNUnet user to maintain an identity (which may or may not be detached from his
@@ -768,9 +764,9 @@ pseudonyms for a single user, and users could 
(theoretically) share the private
 pseudonym keys (currently only out-of-band by knowing which files to copy
 around).
 
address@hidden Namespaces
address@hidden Namespaces
address@hidden Namespaces
 @c %**end of header
address@hidden Top
 
 A namespace is a set of files that were signed by the same pseudonym. Files (or
 directories) that have been signed and placed into a namespace can be updated.
@@ -779,9 +775,9 @@ update. Namespaces are also useful to establish a 
reputation, since all of the
 content in the namespace comes from the same entity (which does not have to be
 the same person).
 
address@hidden Advertisements
address@hidden Advertisements
address@hidden Advertisements
 @c %**end of header
address@hidden Top
 
 Advertisements are used to notify other users about the existence of a
 namespace. Advertisements are propagated using the normal keyword search. When
@@ -799,9 +795,9 @@ namespace and find it using keyword search --- even for 
your own namespaces. The
 pseudonyms and namespaces. This will likely change in the future to reduce the
 potential for confusion.
 
address@hidden Anonymity level
address@hidden Anonymity level
address@hidden Anonymity level
 @c %**end of header
address@hidden Top
 
 The anonymity level determines how hard it should be for an adversary to
 determine the identity of the publisher or the searcher/downloader. An
@@ -813,9 +809,9 @@ Specifying higher anonymity levels increases the amount of 
cover traffic
 required. While this offers better privacy, it can also significantly hurt
 performance.
 
address@hidden Content Priority
address@hidden Content Priority
address@hidden Content Priority
 @c %**end of header
address@hidden Top
 
 Depending on the peer's configuration, GNUnet peers migrate content between
 peers. Content in this sense are individual blocks of a file, not necessarily
@@ -829,9 +825,9 @@ of requests from peers we trust) and, in case of blocks 
published locally, the
 base-priority that was specified by the user when the block was published
 initially.
 
address@hidden Replication
address@hidden Replication
address@hidden Replication
 @c %**end of header
address@hidden Top
 
 When peers migrate content to other systems, the replication level of a block 
is
 used to decide which blocks need to be migrated most urgently. GNUnet will
@@ -839,9 +835,9 @@ always push the block with the highest replication level 
into the network, and
 then decrement the replication level by one. If all blocks reach replication
 level zero, the selection is simply random.
 
address@hidden File-sharing: Publishing
address@hidden File-sharing: Publishing
address@hidden File-sharing: Publishing
 @c %**end of header
address@hidden Top
 
 The command @code{gnunet-publish} can be used to add content to the network.
 The basic format of the command is
@@ -849,9 +845,9 @@ The basic format of the command is
 $ gnunet-publish [-n] [-k KEYWORDS]* [-m TYPE:VALUE] FILENAME 
 @end example
 
address@hidden Important command-line options
address@hidden Important command-line options
address@hidden Important command-line options
 @c %**end of header
address@hidden Top
 
 The option -k is used to specify keywords for the file that should be inserted.
 You can supply any number of keywords, and each of the keywords will be
@@ -869,9 +865,9 @@ gnunet-publish has a few additional options to handle 
namespaces and
 directories.
 See the man-page for details.
 
address@hidden Indexing vs. Inserting
address@hidden Indexing vs. Inserting
address@hidden Indexing vs Inserting
 @c %**end of header
address@hidden Top
 
 By default, GNUnet indexes a file instead of making a full copy. This is much
 more efficient, but requries the file to stay unaltered at the location where 
it
@@ -903,9 +899,9 @@ knowledge of the existence of the file, even if it is still 
(encrypted) on the
 drive and the adversary is able to crack the encryption (e.g. by guessing the
 keyword. 
 
address@hidden File-sharing: Searching
address@hidden File-sharing: Searching
address@hidden File-sharing: Searching
 @c %**end of header
address@hidden Top
 
 The command @code{gnunet-search} can be used to search for content on GNUnet.
 The format is: 
@@ -951,9 +947,9 @@ The second line contains the description of the file; here 
this is
 "The GNU Public License" and the mime-type (see the options for gnunet-publish
 on how to specify these). 
 
address@hidden File-sharing: Downloading
address@hidden File-sharing: Downloading
address@hidden File-sharing: Downloading
 @c %**end of header
address@hidden Top
 
 In order to download a file, you need the three values returned by
 @code{gnunet-search}.
@@ -983,9 +979,9 @@ You may want to use the @code{-V} switch (must be added 
before the @code{--}) to
 turn on verbose reporting. In this case, @code{gnunet-download} will print the
 current number of bytes downloaded whenever new data was received. 
 
address@hidden File-sharing: Directories
address@hidden File-sharing: Directories
address@hidden File-sharing: Directories
 @c %**end of header
address@hidden Top
 
 Directories are shared just like ordinary files. If you download a directory
 with @code{gnunet-download}, you can use @code{gnunet-directory} to list its
@@ -997,9 +993,9 @@ retrieve the file. The meta data typically includes the 
mime-type, description,
 a filename and other meta information, and possibly even the full original file
 (if it was small). 
 
address@hidden File-sharing: Namespace Management
address@hidden File-sharing: Namespace Management
address@hidden File-sharing: Namespace Management
 @c %**end of header
address@hidden Top
 
 THIS TEXT IS OUTDATED AND NEEDS TO BE REWRITTEN FOR 0.10!
 
@@ -1007,27 +1003,26 @@ The gnunet-pseudonym tool can be used to create 
pseudonyms and to advertise
 namespaces. By default, gnunet-pseudonym simply lists all locally available
 pseudonyms.
 
address@hidden Creating Pseudonyms
address@hidden Creating Pseudonyms
address@hidden Creating Pseudonyms
 @c %**end of header
address@hidden Top
 
 With the @code{-C NICK} option it can also be used to create a new pseudonym.
 A pseudonym is the virtual identity of the entity in control of a namespace.
 Anyone can create any number of pseudonyms. Note that creating a pseudonym can
 take a few minutes depending on the performance of the machine used.
 
address@hidden Deleting Pseudonyms
address@hidden Deleting Pseudonyms
address@hidden Deleting Pseudonyms
 @c %**end of header
address@hidden Top
 
 With the @code{-D NICK} option pseudonyms can be deleted. Once the pseudonym 
has
 been deleted it is impossible to add content to the corresponding namespace.
 Deleting the pseudonym does not make the namespace or any content in it
 unavailable.
 
address@hidden Advertising namespaces
address@hidden Advertising namespaces
 @c %**end of header
address@hidden Top
 
 Each namespace is associated with meta-data that describes the namespace.
 This meta data is provided by the user at the time that the namespace is
@@ -1039,9 +1034,8 @@ When a keyword-search finds a namespace advertisement, it 
is automatically
 stored in a local list of known namespaces. Users can then associate a rank 
with
 the namespace to remember the quality of the content found in it.
 
address@hidden Namespace names
address@hidden Namespace names
 @c %**end of header
address@hidden Top
 
 While the namespace is uniquely identified by its ID, another way to refer to
 the namespace is to use the NICKNAME. The NICKNAME can be freely chosen by the
@@ -1049,33 +1043,29 @@ creator of the namespace and hence conflicts are 
possible. If a GNUnet client
 learns about more than one namespace using the same NICKNAME, the ID is 
appended
 to the NICKNAME to get a unique identifier.
 
address@hidden Namespace root
address@hidden Namespace root
 @c %**end of header
address@hidden Top
 
 An item of particular interest in the namespace advertisement is the ROOT.
 The ROOT is the identifier of a designated entry in the namespace. The idea is
 that the ROOT can be used to advertise an entry point to the content of the
 namespace. 
 
address@hidden File-Sharing URIs
address@hidden File-Sharing URIs
 @c %**end of header
address@hidden Top
 
 GNUnet (currently) uses four different types of URIs for file-sharing. They all
 begin with "gnunet://fs/". This section describes the four different URI types
 in detail.
 
address@hidden Encoding of hash values in URIs
address@hidden Encoding of hash values in URIs
 @c %**end of header
address@hidden Top
 
 Most URIs include some hash values. Hashes are encoded using base32hex
 (RFC 2938).
 
address@hidden Content Hash Key (chk)
address@hidden Content Hash Key (chk)
 @c %**end of header
address@hidden Top
 
 A chk-URI is used to (uniquely) identify a file or directory and to allow peers
 to download the file. Files are stored in GNUnet as a tree of encrypted blocks.
@@ -1086,9 +1076,8 @@ tree), KEYHASH is the key used to decrypt the file (also 
the hash of the
 plaintext of the top block) and QUERYHASH is the query used to request the
 top-level block (also the hash of the encrypted block).
 
address@hidden Location identifiers (loc)
address@hidden Location identifiers (loc)
 @c %**end of header
address@hidden Top
 
 For non-anonymous file-sharing, loc-URIs are used to specify which peer is
 offering the data (in addition to specifying all of the data from a chk-URI).
@@ -1099,9 +1088,8 @@ public key of the peer (in GNUnet format in base32hex), 
SIG is the RSA signature
 (in GNUnet format in base32hex) and EXPTIME specifies when the signature 
expires
 (in milliseconds after 1970).
 
address@hidden Keyword queries (ksk)
address@hidden Keyword queries (ksk)
 @c %**end of header
address@hidden Top
 
 A keyword-URI is used to specify that the desired operation is the search using
 a particular keyword. The format is simply "gnunet://fs/ksk/KEYWORD". Non-ASCII
@@ -1110,9 +1098,8 @@ from HTTP. "+" can be used to specify multiple keywords 
(which are then
 logically "OR"-ed in the search, results matching both keywords are given a
 higher rank): "gnunet://fs/ksk/KEYWORD1+KEYWORD2".
 
address@hidden Namespace content (sks)
address@hidden Namespace content (sks)
 @c %**end of header
address@hidden Top
 
 Namespaces are sets of files that have been approved by some (usually
 pseudonymous) user --- typically by that user publishing all of the files
@@ -1125,13 +1112,11 @@ is the public key for the namespace. "IDENTIFIER" is a 
freely chosen keyword
 (or password!). A commonly used identifier is "root" which by convention refers
 to some kind of index or other entry point into the namespace.
 
address@hidden GNS Configuration
address@hidden GNS Configuration
 @c %**end of header
address@hidden Top
 
address@hidden DNS Services Configuration
address@hidden DNS Services Configuration
 @c %**end of header
address@hidden Top
 
 This creates new hostnames in the form "example.gnu". The "example" is filled 
in
 the first column, the others describe a mapping to a service.
@@ -1139,9 +1124,8 @@ the first column, the others describe a mapping to a 
service.
 The special strings "localhost4" and "localhost6" are expanded to the IPv4 and
 IPv6 address of the exit interface respectively.
 
address@hidden The GNU Name System
address@hidden The GNU Name System
 @c %**end of header
address@hidden Top
 
 The GNU Name System (GNS) is secure and decentralized naming system.
 It allows its users to resolve and register names within the @code{.gnu}
@@ -1171,7 +1155,6 @@ freely chosen by the user. This results in non-unique 
name-value mappings as
 
 @settitle Maintaining your own Zones
 @c %**end of header
address@hidden Top
 
 To setup you GNS system you must execute:@
 @code{$ gnunet-gns-import.sh}
@@ -1204,7 +1187,6 @@ editing the zones using the gnunet-setup GUI to be easier.
 
 @settitle Obtaining your Zone Key
 @c %**end of header
address@hidden Top
 
 Each zone in GNS has a public-private key. Usually, gnunet-namestore and
 gnunet-setup will access your private key as necessary, so you do not have to
@@ -1223,7 +1205,6 @@ disk using the Save as button next to the image.
 
 @settitle Adding Links to Other Zones
 @c %**end of header
address@hidden Top
 
 A central operation in GNS is the ability to securely delegate to other zones.
 Basically, by adding a delegation you make all of the names from the other zone
@@ -1249,7 +1230,6 @@ the name of Carol's record you want to access).
 
 @settitle The Three Local Zones of GNS
 @c %**end of header
address@hidden Top
 
 Each user GNS has control over three zones. Each of the zones has a different
 purpose. These zones are the
@@ -1265,7 +1245,6 @@ shorten zone.
 
 @settitle The Master Zone
 @c %**end of header
address@hidden Top
 
 The master zone is your personal TLD. Names within the @code{.gnu} namespace 
are
 resolved relative to this zone. You can arbitrarily add records to this zone 
and
@@ -1273,7 +1252,6 @@ selectively publish those records.
 
 @settitle The Private Zone
 @c %**end of header
address@hidden Top
 
 The private zone is a subzone (or subdomain in DNS terms) of your master zone.
 It should be used for records that you want to keep private. For example
@@ -1283,7 +1261,6 @@ users.
 
 @settitle The Shorten Zone
 @c %**end of header
address@hidden Top
 
 The shorten zone can either be a subzone of the master zone or the private 
zone.
 It is different from the other zones in that GNS will automatically populate
@@ -1303,7 +1280,6 @@ memorable as possible.
 
 @settitle The ZKEY Top Level Domain in GNS
 @c %**end of header
address@hidden Top
 
 GNS also provides a secure and globally unique namespace under the .zkey
 top-level domain. A name in the .zkey TLD corresponds to the (printable) public
@@ -1314,7 +1290,6 @@ systems.
 
 @settitle Resource Records in GNS
 @c %**end of header
address@hidden Top
 
 GNS supports the majority of the DNS records as defined in
 @uref{http://www.ietf.org/rfc/rfc1035.txt, RFC 1035}. Additionally, GNS defines
@@ -1336,7 +1311,6 @@ GNS currently supports the following record types:
 
 @settitle NICK
 @c %**end of header
address@hidden Top
 
 A NICK record is used to give a zone a name. With a NICK record, you can
 essentially specify how you would like to be called. GNS expects this record
@@ -1346,7 +1320,6 @@ separate lookup to discover the NICK record.
 
 @settitle Example
 @c %**end of header
address@hidden Top
 
 Name: +; RRType: NICK; Value: bob
 
@@ -1356,14 +1329,12 @@ their own zones. It can be seen as a recommendation 
("Please call me 'bob'").
 
 @settitle PKEY
 @c %**end of header
address@hidden Top
 
 PKEY records are used to add delegation to other users' zones and give those
 zones a petname.
 
 @settitle Example
 @c %**end of header
address@hidden Top
 
 Let Bob's zone be identified by the hash "ABC012". Bob is your friend so you
 want to give him the petname "friend". Then you add the following record to 
your
@@ -1375,7 +1346,6 @@ This will allow you to resolve records in bob's zone 
under "*.friend.gnu".
 
 @settitle BOX
 @c %**end of header
address@hidden Top
 
 BOX records are there to integrate information from TLSA or SRV records under
 the main label. In DNS, TLSA and SRV records use special names of the form
@@ -1389,7 +1359,6 @@ they internally are BOXed up.
 
 @settitle LEHO
 @c %**end of header
address@hidden Top
 
 The LEgacy HOstname of a server. Some webservers expect a specific hostname to
 provide a service (virtiual hosting). Also SSL certificates usually contain DNS
@@ -1399,7 +1368,6 @@ GNS proxy will use the LEHO information to apply the 
necessary transformations.
 
 @settitle VPN
 @c %**end of header
address@hidden Top
 
 GNS allows easy access to services provided by the GNUnet Virtual Public
 Network. When the GNS resolver encounters a VPN record it will contact the VPN
@@ -1408,7 +1376,6 @@ IP address) that can be used to contact the service.
 
 @settitle Example
 @c %**end of header
address@hidden Top
 
 I want to provide access to the VPN service "web.gnu." on port 80 on peer
 ABC012:@
@@ -1424,13 +1391,11 @@ following lines in the @code{gnunet.conf} configuration 
file:@
 
 @settitle A, AAAA and TXT
 @c %**end of header
address@hidden Top
 
 Those records work in exactly the same fashion as in traditional DNS.
 
 @settitle CNAME
 @c %**end of header
address@hidden Top
 
 As specified in RFC 1035 whenever a CNAME is encountered the query needs to be
 restarted with the specified name. In GNS a CNAME can either be:
@@ -1445,14 +1410,12 @@ A DNS name (in which case resolution will continue 
outside of GNS with the syste
 
 @settitle GNS2DNS
 @c %**end of header
address@hidden Top
 
 GNS can delegate authority to a legacy DNS zone. For this, the name of the DNS
 nameserver and the name of the DNS zone are specified in a GNS2DNS record.
 
 @settitle Example
 @c %**end of header
address@hidden Top
 
 Name: pet; RRType: GNS2DNS; Value: gnunet.org@@a.ns.joker.com
 
@@ -1478,7 +1441,6 @@ be effective.
 
 @settitle SOA, SRV, PTR and MX
 @c %**end of header
address@hidden Top
 
 The domain names in those records can, again, be either
 @itemize @bullet
@@ -1499,7 +1461,6 @@ local users.
 
 @settitle The Virtual Public Network
 @c %**end of header
address@hidden Top
 
 Using the GNUnet Virtual Public Network (VPN) application you can tunnel IP
 traffic over GNUnet. Moreover, the VPN comes with built-in protocol translation
@@ -1530,7 +1491,6 @@ of using the VPN later in this chapter.
 
 @settitle Setting up an Exit node
 @c %**end of header
address@hidden Top
 
 Any useful operation with the VPN requires the existence of an exit node in the
 GNUnet Peer-to-Peer network. Exit functionality can only be enabled on peers
@@ -1588,7 +1548,6 @@ easier.
 
 @settitle Fedora and the Firewall
 @c %**end of header
address@hidden Top
 
 When using an exit node on Fedora 15, the standard firewall can create trouble
 even when not really exiting the local system! For IPv4, the standard rules 
seem
@@ -1610,7 +1569,6 @@ ICMP messages are generated when running some tests that 
should work.
 
 @settitle Setting up VPN node for protocol translation and tunneling
 @c %**end of header
address@hidden Top
 
 The GNUnet VPN/PT subsystem enables you to tunnel IP traffic over the VPN to an
 exit node, from where it can then be forwarded to the Internet. This section
@@ -1660,5 +1618,27 @@ can create an IP tunnel to that peer by specifying the 
peer's identity, service
 name and protocol (--tcp or --udp) and you will again receive an IP address 
that
 will terminate at the respective peer's service.
 
address@hidden 
*****************************************************************************
address@hidden GNU Free Documentation License
address@hidden GNU Free Documentation License
address@hidden license, GNU Free Documentation License
address@hidden fdl-1.3.texi
+
address@hidden 
*****************************************************************************
address@hidden GNU General Public License
address@hidden GNU General Public License
address@hidden license, GNU General Public License
address@hidden gpl-3.0.texi
+
address@hidden 
*****************************************************************************
address@hidden Concept Index
address@hidden Concept Index
address@hidden cp
+
address@hidden 
*****************************************************************************
address@hidden Contents
address@hidden Contents
address@hidden Contents
 @contents
+
 @bye

-- 
To stop receiving notification emails like this one, please contact
address@hidden