In the preface, answer #2, mark up references to the GPL, LGPL and FreeBSD

license with <ulink>s to the appropriate file in
http://www.FreeBSD.org/copyright/.
This commit is contained in:
Chris Costello 2001-06-17 21:42:51 +00:00
parent 274eb68ac6
commit 05489d9ec5
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9635

View file

@ -14,7 +14,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.217 2001/06/17 21:17:53 chris Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.218 2001/06/17 21:22:40 chris Exp $</pubdate>
<copyright>
<year>1995</year>
@ -112,14 +112,14 @@
This is, we believe, one of the most fundamental goals of Free
Software and one that we enthusiastically support.</para>
<para>That code in our source tree which falls under the GNU
General Public License (GPL) or GNU Library General Public
License (LGPL) comes with slightly more strings attached,
<para>That code in our source tree which falls under the <ulink url="http://www.FreeBSD.org/copyright/COPYING">GNU
General Public License (GPL)</ulink> or <ulink url="http://www.FreeBSD.org/copyright/COPYING.LIB">GNU Library General Public
License (LGPL)</ulink> comes with slightly more strings attached,
though at least on the side of enforced access rather than the
usual opposite. Due to the additional complexities that can
evolve in the commercial use of GPL software, we do, however,
endeavor to replace such software with submissions under the
more relaxed BSD copyright whenever possible.</para>
more relaxed <ulink url="http://www.FreeBSD.org/copyright/freebsd-license.html">BSD copyright</ulink> whenever possible.</para>
</answer>
</qandaentry>