LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

First re-draft for next major release

This commit is contained in:
binh 2004-05-18 04:44:06 +00:00
parent b697c745e7
commit fe01ebd4b7
34 changed files with 98935 additions and 98659 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
LDP/guide/docbook/Linux-Dictionary/About-the-Author.xml
View File

@ -1,3 +1,4 @@
<?xml version="1.0" encoding="UTF-8"?>
<appendix id="About-the-Author">
<title>About the Author</title>

161
LDP/guide/docbook/Linux-Dictionary/Contributors.xml
View File

@ -1,85 +1,86 @@
<appendix id="Contributors">
<title>Contributors</title>
<itemizedlist>
<listitem>
<para>Martin Wheeler for creating the online database.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<?xml version="1.0" encoding="UTF-8"?>
<appendix id="Contributors">
<title>Contributors</title>
<itemizedlist>
<listitem>
<para>Martin Wheeler for creating the online database.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Dale Rogers for participating in coverage testing.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Anthony E. Greene for writing a program to help sort the
dictionary into alphabetical order.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Machtelt Garrels for writing a template program which allowed me to
write a program to convert the original text file to Docbook.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Chris Karakas for general troubleshooting.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Greg Ferguson for general help in publishing this document.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Andrew Laird for participating in coverage testing.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Jason Hounam for participating in coverage testing.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Ahmed Tanvir for participating in coverage testing.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Dan Richter.</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Emma Jane Hogbin.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Anthony E. Greene for writing a program to help sort the
dictionary into alphabetical order.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Geoff Farrell.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Machtelt Garrels for writing a template program which allowed me to
write a program to convert the original text file to Docbook.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Neil Eagle</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Chris Karakas for general troubleshooting.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Greg Ferguson for general help in publishing this document.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Andrew Laird for participating in coverage testing.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Jason Hounam for participating in coverage testing.</para>
</listitem>
</itemizedlist>
</appendix>
<itemizedlist>
<listitem>
<para>Ahmed Tanvir for participating in coverage testing.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Dan Richter.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Emma Jane Hogbin.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Geoff Farrell.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Neil Eagle.</para>
</listitem>
</itemizedlist>
</appendix>

23
LDP/guide/docbook/Linux-Dictionary/Disclaimer.xml
View File

@ -1,20 +1,21 @@
<appendix id="Disclaimer">
<title>Disclaimer</title>
<?xml version="1.0" encoding="UTF-8"?>
<appendix id="Disclaimer">
<title>Disclaimer</title>
<para>
No liability for the contents of this document can be accepted. Use the concepts,
examples and other content at your own risk. As this is a new edition of this document,
there may be errors and inaccuracies that may of course be damaging to your system.
Proceed with caution, and although this is highly unlikely, the author does not and
can not take any responsibility for any damage to your system that may occur as a
direct or indirect result of information that is contained within this document.
</para>
direct or indirect result of information that is contained within this document.
</para>
<para>
Naming of particular products or brands should not be seen as endorsements.
You are strongly recommended to make a backup of your system before major
installation and adhere to the practice of backing up at regular intervals.
</para>
</appendix>
installation and adhere to the practice of backing up at regular intervals.
</para>
</appendix>

46
LDP/guide/docbook/Linux-Dictionary/Feedback.xml
View File

@ -1,24 +1,24 @@
<appendix id="Feedback">
<title>Feedback</title>
<para>
Further revisions of this document will be dependent upon user response.
Any feedback on the content of this document is welcome. Every attempt has
been made to ensure that the instructions and information herein are
<appendix id="Feedback">
<title>Feedback</title>
<para>
Further revisions of this document will be dependent upon user response.
Any feedback on the content of this document is welcome. Every attempt has
been made to ensure that the instructions and information herein are
accurate and reliable. Please send corrections, comments, suggestions
and questions to the author Binh Nguyen,
linuxfilesystem(at)yahoo(dot)com(dot)au with the subject
heading of Dictionary. There is, however, no guarantee of a response.
</para>
<para>All trademarks and copyrights are the property of their owners, unless
otherwise indicated. Use of a term in this document should not be regarded
as affecting the validity of any trademark or service mark.
</para>
<para>The author would appreciate and consider it courteous, notification of
any and all modifications, translations, and printed versions.
</para>
</appendix>
and questions to the author Binh Nguyen,
linuxfilesystem(at)yahoo(dot)com(dot)au with the subject
heading of Dictionary. There is, however, no guarantee of a response.
</para>
<para>All trademarks and copyrights are the property of their owners, unless
otherwise indicated. Use of a term in this document should not be regarded
as affecting the validity of any trademark or service mark.
</para>
<para>The author would appreciate and consider it courteous, notification of
any and all modifications, translations, and printed versions.
</para>
</appendix>

311
LDP/guide/docbook/Linux-Dictionary/Linux-Dictionary.xml
View File

@ -1,138 +1,183 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd" [
<!ENTITY About-the-Author SYSTEM "About-the-Author.xml">
<!ENTITY Contributors SYSTEM "Contributors.xml">
<!ENTITY Disclaimer SYSTEM "Disclaimer.xml">
<!ENTITY Feedback SYSTEM "Feedback.xml">
<!ENTITY References SYSTEM "References.xml">
<!ENTITY GFDL SYSTEM "fdl.xml">
<!ENTITY edPunctuation SYSTEM "edPunctuation.xml">
<!ENTITY edA SYSTEM "edA.xml">
<!ENTITY edB SYSTEM "edB.xml">
<!ENTITY edC SYSTEM "edC.xml">
<!ENTITY edD SYSTEM "edD.xml">
<!ENTITY edE SYSTEM "edE.xml">
<!ENTITY edF SYSTEM "edF.xml">
<!ENTITY edG SYSTEM "edG.xml">
<!ENTITY edH SYSTEM "edH.xml">
<!ENTITY edI SYSTEM "edI.xml">
<!ENTITY edJ SYSTEM "edJ.xml">
<!ENTITY edK SYSTEM "edK.xml">
<!ENTITY edL SYSTEM "edL.xml">
<!ENTITY edM SYSTEM "edM.xml">
<!ENTITY edN SYSTEM "edN.xml">
<!ENTITY edO SYSTEM "edO.xml">
<!ENTITY edP SYSTEM "edP.xml">
<!ENTITY edQ SYSTEM "edQ.xml">
<!ENTITY edR SYSTEM "edR.xml">
<!ENTITY edS SYSTEM "edS.xml">
<!ENTITY edT SYSTEM "edT.xml">
<!ENTITY edU SYSTEM "edU.xml">
<!ENTITY edV SYSTEM "edV.xml">
<!ENTITY edW SYSTEM "edW.xml">
<!ENTITY edX SYSTEM "edX.xml">
<!ENTITY edY SYSTEM "edY.xml">
<!ENTITY edZ SYSTEM "edZ.xml">
]>
<book>
<bookinfo>
<title>Linux Dictionary</title>
<subtitle>Version 0.12</subtitle>
<pubdate>2003-12-19</pubdate>
<author>
<firstname>Author: Binh</firstname>
<surname>Nguyen</surname>
<affiliation>
<address>
<email>linuxfilesystem(at)yahoo(dot)com(dot)au</email>
</address>
</affiliation>
</author>
<author>
<firstname>Database Creator: Martin</firstname>
<surname>Wheeler</surname>
<affiliation>
<address>
<email>mwheeler(at)startext(dot)co(dot)uk</email>
</address>
</affiliation>
</author>
<abstract>
<para>This document is designed to be a resource for those Linux users wishing to seek clarification on Linux/UNIX/POSIX related terms and jargon. At approximately 9000 definitions and one thousand pages it is one of the largest Linux related dictionaries currently available. Due to the rapid rate at which new terms are being created it has been decided that this will be an active project. We welcome input into the content of this document. At this moment in time half yearly updates are being envisaged.</para>
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd" [
<!ENTITY About-the-Author SYSTEM "About-the-Author.xml">
<!ENTITY Contributors SYSTEM "Contributors.xml">
<!ENTITY Disclaimer SYSTEM "Disclaimer.xml">
<!ENTITY Feedback SYSTEM "Feedback.xml">
<!ENTITY References SYSTEM "References.xml">
<!ENTITY GFDL SYSTEM "fdl.xml">
<!ENTITY edPunctuation SYSTEM "edPunctuation.xml">
<!ENTITY edA SYSTEM "edA.xml">
<!ENTITY edB SYSTEM "edB.xml">
<!ENTITY edC SYSTEM "edC.xml">
<!ENTITY edD SYSTEM "edD.xml">
<!ENTITY edE SYSTEM "edE.xml">
<!ENTITY edF SYSTEM "edF.xml">
<!ENTITY edG SYSTEM "edG.xml">
<!ENTITY edH SYSTEM "edH.xml">
<!ENTITY edI SYSTEM "edI.xml">
<!ENTITY edJ SYSTEM "edJ.xml">
<!ENTITY edK SYSTEM "edK.xml">
<!ENTITY edL SYSTEM "edL.xml">
<!ENTITY edM SYSTEM "edM.xml">
<!ENTITY edN SYSTEM "edN.xml">
<!ENTITY edO SYSTEM "edO.xml">
<!ENTITY edP SYSTEM "edP.xml">
<!ENTITY edQ SYSTEM "edQ.xml">
<!ENTITY edR SYSTEM "edR.xml">
<!ENTITY edS SYSTEM "edS.xml">
<!ENTITY edT SYSTEM "edT.xml">
<!ENTITY edU SYSTEM "edU.xml">
<!ENTITY edV SYSTEM "edV.xml">
<!ENTITY edW SYSTEM "edW.xml">
<!ENTITY edX SYSTEM "edX.xml">
<!ENTITY edY SYSTEM "edY.xml">
<!ENTITY edZ SYSTEM "edZ.xml">
]>
<para>The Linux Dictionary online database may be accessed from its home page at <ulink url="http://startext.demon.co.uk/Linux-Dictionary/">http://startext.demon.co.uk/Linux-Dictionary/</ulink>
<book>
<bookinfo>
<title>Linux Dictionary</title>
<subtitle>Version 0.12</subtitle>
<pubdate>2003-12-19</pubdate>
<author>
<firstname>Author: Binh</firstname>
<surname>Nguyen</surname>
<affiliation>
<address>
<email>linuxfilesystem(at)yahoo(dot)com(dot)au</email>
</address>
</affiliation>
</author>
<author>
<firstname>Database Creator: Martin</firstname>
<surname>Wheeler</surname>
<affiliation>
<address>
<email>mwheeler(at)startext(dot)co(dot)uk</email>
</address>
</affiliation>
</author>
<abstract>
<para>This document is designed to be a resource for those Linux users wishing
to seek clarification on Linux/UNIX/POSIX related terms and jargon. At
approximately 9000 definitions and one thousand pages it is one of the largest
Linux related dictionaries currently available. Due to the rapid rate at which
new terms are being created it has been decided that this will be an active
project. We welcome input into the content of this document. At this moment
in time half yearly updates are being envisaged.</para>
<para>The 'unofficial' official Linux Dictionary online database may be accessed
from its home page at <ulink url="http://startext.demon.co.uk/Linux-Dictionary/">
http://startext.demon.co.uk/Linux-Dictionary/</ulink></para>
<para>Readers may query the dictionary database by keyword, generate a complete
listing of all terms and definitions marked up in HTML, or contribute to the
Linux Dictionary wiki at <ulink url="http://startext.demon.co.uk/distwiki/index.php?LinuxDictionary">
http://startext.demon.co.uk/distwiki/index.php?LinuxDictionary</ulink>
</para>
<para>Readers may query the dictionary database by keyword, generate a complete listing of all terms and definitions marked up in HTML, or contribute to the Linux Dictionary wiki at <ulink url="http://startext.demon.co.uk/distwiki/index.php?LinuxDictionary">http://startext.demon.co.uk/distwiki/index.php?LinuxDictionary</ulink>
</para>
</abstract>
<legalnotice>
<para>Copyright 2003 Binh Nguyen</para>
<para>Trademarks are owned by their owners.</para>
<para>Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.2; with no Invariant Sections, with no Front-Cover Texts,
and with no Back-Cover Texts. A copy of the license is included in
the section entitled "GNU Free Documentation License".</para>
</legalnotice>
</bookinfo>
<preface> <title>Source and pre-formatted versions available</title>
<para>Searchable databases also exist at other locations such as:</para>
<para><ulink url="http://www.swpearl.com/eng/scripts/dictionary/">
http://www.swpearl.com/eng/scripts/dictionary/</ulink></para>
<para>(SWP) Sun Wah-PearL Linux Training and Development Centre
is a centre of the Hong Kong Polytechnic University, established
in 2000. Presently SWP is delivering professional grade Linux
and related Open Source Software (OSS) technology training and
consultant service in Hong Kong. SWP has an ambitious aim to promote
the use of Linux and related Open Source Software (OSS) and Standards.
The vendor independent positioning of SWP has been very well perceived
by the market. Throughout the last couple of years, SWP becomes the Top
Leading OSS training and service provider in Hong Kong.</para>
<para><ulink url="http://www.linuxdig.com/documents/dictionary.php">
http://www.linuxdig.com/documents/dictionary.php</ulink></para>
<para>LINUXDIG.COM, "Yours News and Resource Site"</para>
<para><ulink url="http://www.geona.com/dictionary?b=">
http://www.geona.com/dictionary?b=</ulink></para>
<para><ulink url="http://www.gral.org.br/gral/modules.php?name=Encyclopedia">
http://www.gral.org.br/gral/modules.php?name=Encyclopedia</ulink></para>
<para>Alternative forms of the dictionary are available at:</para>
<para><ulink url="http://linux.about.com/mbiopage.htm">
http://linux.about.com/mbiopage.htm</ulink></para>
<para><ulink url="http://elibrary.fultus.com/covers/technical/linux/guides/Linux-Dictionary/cover.html">
http://elibrary.fultus.com/covers/technical/linux/guides/Linux-Dictionary/cover.html</ulink></para>
<para>Please inform the author as to whether you would like to create alternative form of the dictionary so that he can include you in this list. Also note that the author considers breaches of copyright extremely seriously. He will pursue claims to the fullest extent of the law no matter where the breach may have occured geographically.</para>
</abstract>
<legalnotice>
<para>Copyright 2003 Binh Nguyen</para>
<para>Trademarks are owned by their owners.</para>
<para>Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License,
Version 1.2; with no Invariant Sections, with no Front-Cover Texts,
and with no Back-Cover Texts. A copy of the license is included in
the section entitled "GNU Free Documentation License".</para>
</legalnotice>
</bookinfo>
<preface> <title>Source and pre-formatted versions available</title>
<para>
The source code and other machine readable formats
of this book can be found on the Internet at the
Linux Documentation Project home page <ulink
url="http://www.tldp.org/">http://www.tldp.org/</ulink>
</para>
</preface>
<chapter>
<title>Linux Dictionary</title>
&edPunctuation;
&edA;
&edB;
&edC;
&edD;
&edE;
&edF;
&edG;
&edH;
&edI;
&edJ;
&edK;
&edL;
&edM;
&edN;
&edO;
&edP;
&edQ;
&edR;
&edS;
&edT;
&edU;
&edV;
&edW;
&edX;
&edY;
&edZ;
</chapter>
The source code and other machine readable formats
of this book can be found on the Internet at the
Linux Documentation Project home page <ulink
url="http://www.tldp.org/">http://www.tldp.org/</ulink>
</para>
</preface>
<chapter>
<title>Linux Dictionary</title>
&edPunctuation;
&edA;
&edB;
&edC;
&edD;
&edE;
&edF;
&edG;
&edH;
&edI;
&edJ;
&edK;
&edL;
&edM;
&edN;
&edO;
&edP;
&edQ;
&edR;
&edS;
&edT;
&edU;
&edV;
&edW;
&edX;
&edY;
&edZ;
<para></para>
</chapter>
&About-the-Author;
&Contributors;
&Disclaimer;
&Feedback;
&References;
&GFDL;
</book>
&Contributors;
&Disclaimer;
&Feedback;
&References;
&GFDL;
</book>

797
LDP/guide/docbook/Linux-Dictionary/References.xml
View File

@ -1,399 +1,400 @@
<appendix id="References">
<title>References</title>
<itemizedlist>
<listitem>
<para>http://www.matisse.net/files/glossary.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.hyperdictionary.com/thesaurus/Linux</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://ai.uwaterloo.ca/~jhuang/UnixDictionary.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.firstlinux.com/guide/index.shtml</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.lwn.net/Distributions</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://whatis.techtarget.com/definition/0,,sid9_gci213627,00.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.darpa.mil/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://hostingworks.com/support/dict.phtml?foldoc=Defense%2BAdvanced%2BResearch%2BProjects%2BAgency</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxsa.org.au/meetings/1997-06/fsstnd/fsstnd.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>QUE&#39;s Computer &#38; Internet Dictionary (6th Edition), Bryan
Pfaffenberger, QUE Corporation, USA, 1995.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Rute-Users-Guide, http://rute.sourceforge.net</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Essential System Administration, Aeleen Frisch, O&#39;Reilly &#38;
Associates, Inc., USA, 1995</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://pages.ripco.com:8080/~kadokev/kadokev.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.robertgraham.com/pubs/hacking-dict.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.cusd.claremont.edu/www/computing/doc/intro/netterms_glossary.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.msg.net/kadow/answers/a.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/share/doc/sysvinit/README.runlevels.gz</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/src/linux/Documentation/initrd.txt, Werner Almesberger
&#60;werner.almesberger@epfl.ch&#62; and Hans Lermen
&#60;lermen@fgan.de&#62;, 2000.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.opussoftware.com/tutorial/TutMakefile.htm</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.cc.gatech.edu/people/home/oxblood/Linux_Doc.txt</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>hints.linuxfromscratch.org/hints/grub-howto.txt</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.fifi.org/cgi-bin/man2html?initrd+4</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxsa.org.au/meetings/1997-06/fsstnd/fsstnd.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://public.csusm.edu/public/guests/history/netinfo/arpa.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://whatis.techtarget.com/definition/0,,sid9_gci214635,00.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxjournal.com/article.php?sid=1104</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.mlinux.org/projects/present/filesys/slide01.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.mil.ufl.edu/linuxhelp/linuxfilesystem.pdf</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.nsa.gov/selinux/doc/slinux/node57.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxnow.com/tutorial/fs/fs.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://info.cqu.edu.au/courses/aut2001/85321/resources/study_guide/chapter_4</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://lwn.net/2001/features/ols/pdf/pdf/devfs.pdf</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/src/linux/Documentation/filesystems/proc.txt, Terrehon Bowden
&#60;terrehon@pacbell.net&#62;, Bodo Bauer &#60;bb@ricochet.net&#62;,
Jorge Nerin &#60;comandante@zaralinux.com&#62;</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/share/doc/FAQ/Linux-FAQ/index.html,
ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/comp/os/linux/misc/, David
Merrill, david@lupercalia.net, Robert Kiesling,
rkiesling@mainmatter.com, Linux Frequently Asked Questions with Answers,
2001-12-04.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Linux System Security (The Administrator&#39;s Guide to Open
Source Security Tools), Scott Mann &#38; Ellen L. Mitchell,
Prentice-Hall, New-Jersey, 2000.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>XFree86 For Linux (Uncommon Solutions for the Technical
Professional), Aron Hsiao, QUE Corporation, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Complete Idiot&#39;s Guide to Linux Second Edition, Manuel Alberto
Ricart, QUE Corporation, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Lions&#39; Commentry on UNIX 6th Edition with Source Code, John
Lions, Peer-to-Peer Communications Incorporated, USA, 1996.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>The Linux System Administrators’ Guide Version 0.6.1, Lars
Wirzenius, liw@iki.fi, Finland, 1998.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>SAMS Teach Yourself Shell Progamming in 24 Hours, Sriranga
Veerararaghavan, SAMS Publishing, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>433-252 Software Development: Principles and Tools, Zoltan
Somogyi, Les Kitchen, The University of Melbourne, Department of
Computer Science and Software Engineering, Australia, 2002.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>The Advanced Linux Pocketbook, Ashton Mills,
ashtonmills@bigpond.com, ACP Publishing Pty Ltd, Australia, 2001.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.pathname.com/fhs</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://freeos.com/articles/3102/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://freeos.com/articles/2879/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Magnicomp, http://www.magnicomp.com/rdist/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>ACPI, http://www.acpi.info/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Zapping, http://zapping.sourceforge.net/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>LIRC, http://www.lirc.org/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Mplayer, http://freshmeat.net/releases/119440/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>EGP,
http://whatis.techtarget.com/definition/0,,sid9_gci213930,00.html
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>IGP,
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci214018,00.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>3dwm, http://www.3dwm.org</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>The UNIX programming environment, Brian W. Kernighan, Rob Pike,
Prentice Hall, New Jersey, 1984.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Newnes UNIX Pocket Book, Steve Heath, Butterworth-Heinemann, Great
Britain, 1998.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Suse Linux Installation and Configuration, Nazeeh Amin El-Dirghami
&#38; Youssef A. Abu Kwaik, QUE Corporation, USA, 2000.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Inside Linux, Michael J. Tobler, New Riders Publishing, USA, 2001.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Linux in a Nutshell 2nd Edition, Ellen Siever, O&#39;Reilly &#38;
Associates Inc., CA, USA, 1999</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Using Caldera OpenLinux Special Edition, Allan Smart, Erik
Ratcliffe, Tim Bird, David Bandel, QUE Corporation, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://wiki.org/wiki.cgi?WhatIsWiki</para>
</listitem>
</itemizedlist>
<?xml version="1.0" encoding="UTF-8"?>
<appendix id="References">
<title>References</title>
<para></para>
</appendix>
<itemizedlist>
<listitem>
<para>http://www.matisse.net/files/glossary.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.hyperdictionary.com/thesaurus/Linux</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://ai.uwaterloo.ca/~jhuang/UnixDictionary.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.firstlinux.com/guide/index.shtml</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.lwn.net/Distributions</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://whatis.techtarget.com/definition/0,,sid9_gci213627,00.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.darpa.mil/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://hostingworks.com/support/dict.phtml?foldoc=Defense%2BAdvanced%2BResearch%2BProjects%2BAgency</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxsa.org.au/meetings/1997-06/fsstnd/fsstnd.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>QUE&#39;s Computer &#38; Internet Dictionary (6th Edition), Bryan
Pfaffenberger, QUE Corporation, USA, 1995.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Rute-Users-Guide, http://rute.sourceforge.net</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Essential System Administration, Aeleen Frisch, O&#39;Reilly &#38;
Associates, Inc., USA, 1995</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://pages.ripco.com:8080/~kadokev/kadokev.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.robertgraham.com/pubs/hacking-dict.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.cusd.claremont.edu/www/computing/doc/intro/netterms_glossary.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.msg.net/kadow/answers/a.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/share/doc/sysvinit/README.runlevels.gz</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/src/linux/Documentation/initrd.txt, Werner Almesberger
&#60;werner.almesberger@epfl.ch&#62; and Hans Lermen
&#60;lermen@fgan.de&#62;, 2000.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.opussoftware.com/tutorial/TutMakefile.htm</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.cc.gatech.edu/people/home/oxblood/Linux_Doc.txt</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>hints.linuxfromscratch.org/hints/grub-howto.txt</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.fifi.org/cgi-bin/man2html?initrd+4</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxsa.org.au/meetings/1997-06/fsstnd/fsstnd.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://public.csusm.edu/public/guests/history/netinfo/arpa.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://whatis.techtarget.com/definition/0,,sid9_gci214635,00.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxjournal.com/article.php?sid=1104</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.mlinux.org/projects/present/filesys/slide01.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.mil.ufl.edu/linuxhelp/linuxfilesystem.pdf</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.nsa.gov/selinux/doc/slinux/node57.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.linuxnow.com/tutorial/fs/fs.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://info.cqu.edu.au/courses/aut2001/85321/resources/study_guide/chapter_4</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://lwn.net/2001/features/ols/pdf/pdf/devfs.pdf</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/src/linux/Documentation/filesystems/proc.txt, Terrehon Bowden
&#60;terrehon@pacbell.net&#62;, Bodo Bauer &#60;bb@ricochet.net&#62;,
Jorge Nerin &#60;comandante@zaralinux.com&#62;</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>/usr/share/doc/FAQ/Linux-FAQ/index.html,
ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/comp/os/linux/misc/, David
Merrill, david@lupercalia.net, Robert Kiesling,
rkiesling@mainmatter.com, Linux Frequently Asked Questions with Answers,
2001-12-04.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Linux System Security (The Administrator&#39;s Guide to Open
Source Security Tools), Scott Mann &#38; Ellen L. Mitchell,
Prentice-Hall, New-Jersey, 2000.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>XFree86 For Linux (Uncommon Solutions for the Technical
Professional), Aron Hsiao, QUE Corporation, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Complete Idiot&#39;s Guide to Linux Second Edition, Manuel Alberto
Ricart, QUE Corporation, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Lions&#39; Commentry on UNIX 6th Edition with Source Code, John
Lions, Peer-to-Peer Communications Incorporated, USA, 1996.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>The Linux System Administrators Guide Version 0.6.1, Lars
Wirzenius, liw@iki.fi, Finland, 1998.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>SAMS Teach Yourself Shell Progamming in 24 Hours, Sriranga
Veerararaghavan, SAMS Publishing, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>433-252 Software Development: Principles and Tools, Zoltan
Somogyi, Les Kitchen, The University of Melbourne, Department of
Computer Science and Software Engineering, Australia, 2002.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>The Advanced Linux Pocketbook, Ashton Mills,
ashtonmills@bigpond.com, ACP Publishing Pty Ltd, Australia, 2001.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.pathname.com/fhs</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://www.atnf.csiro.au/people/rgooch/linux/docs/devfs.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://freeos.com/articles/3102/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://freeos.com/articles/2879/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Magnicomp, http://www.magnicomp.com/rdist/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>ACPI, http://www.acpi.info/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Zapping, http://zapping.sourceforge.net/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>LIRC, http://www.lirc.org/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Mplayer, http://freshmeat.net/releases/119440/</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>EGP,
http://whatis.techtarget.com/definition/0,,sid9_gci213930,00.html
</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>IGP,
http://searchsecurity.techtarget.com/sDefinition/0,,sid14_gci214018,00.html</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>3dwm, http://www.3dwm.org</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>The UNIX programming environment, Brian W. Kernighan, Rob Pike,
Prentice Hall, New Jersey, 1984.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Newnes UNIX Pocket Book, Steve Heath, Butterworth-Heinemann, Great
Britain, 1998.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Suse Linux Installation and Configuration, Nazeeh Amin El-Dirghami
&#38; Youssef A. Abu Kwaik, QUE Corporation, USA, 2000.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Inside Linux, Michael J. Tobler, New Riders Publishing, USA, 2001.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Linux in a Nutshell 2nd Edition, Ellen Siever, O&#39;Reilly &#38;
Associates Inc., CA, USA, 1999</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>Using Caldera OpenLinux Special Edition, Allan Smart, Erik
Ratcliffe, Tim Bird, David Bandel, QUE Corporation, USA, 1999.</para>
</listitem>
</itemizedlist>
<itemizedlist>
<listitem>
<para>http://wiki.org/wiki.cgi?WhatIsWiki</para>
</listitem>
</itemizedlist>
<para></para>
</appendix>

8394
LDP/guide/docbook/Linux-Dictionary/edA.xml
View File

File diff suppressed because one or more lines are too long

7052
LDP/guide/docbook/Linux-Dictionary/edB.xml
View File

File diff suppressed because one or more lines are too long

10572
LDP/guide/docbook/Linux-Dictionary/edC.xml
View File

File diff suppressed because it is too large Load Diff

11078
LDP/guide/docbook/Linux-Dictionary/edD.xml
View File

File diff suppressed because it is too large Load Diff

5556
LDP/guide/docbook/Linux-Dictionary/edE.xml
View File

File diff suppressed because it is too large Load Diff

7668
LDP/guide/docbook/Linux-Dictionary/edF.xml
View File

File diff suppressed because it is too large Load Diff

13586
LDP/guide/docbook/Linux-Dictionary/edG.xml
View File

File diff suppressed because it is too large Load Diff

3884
LDP/guide/docbook/Linux-Dictionary/edH.xml
View File

File diff suppressed because it is too large Load Diff

7261
LDP/guide/docbook/Linux-Dictionary/edI.xml
View File

File diff suppressed because it is too large Load Diff

2146
LDP/guide/docbook/Linux-Dictionary/edJ.xml
View File

File diff suppressed because it is too large Load Diff

7116
LDP/guide/docbook/Linux-Dictionary/edK.xml
View File

File diff suppressed because it is too large Load Diff

11782
LDP/guide/docbook/Linux-Dictionary/edL.xml
View File

File diff suppressed because one or more lines are too long

12332
LDP/guide/docbook/Linux-Dictionary/edM.xml
View File

File diff suppressed because it is too large Load Diff

5644
LDP/guide/docbook/Linux-Dictionary/edN.xml
View File

File diff suppressed because it is too large Load Diff

3576
LDP/guide/docbook/Linux-Dictionary/edO.xml
View File

File diff suppressed because it is too large Load Diff

13652
LDP/guide/docbook/Linux-Dictionary/edP.xml
View File

File diff suppressed because one or more lines are too long

2982
LDP/guide/docbook/Linux-Dictionary/edPunctuation.xml
View File

File diff suppressed because it is too large Load Diff

1222
LDP/guide/docbook/Linux-Dictionary/edQ.xml
View File

File diff suppressed because it is too large Load Diff

8724
LDP/guide/docbook/Linux-Dictionary/edR.xml
View File

File diff suppressed because it is too large Load Diff

16820
LDP/guide/docbook/Linux-Dictionary/edS.xml
View File

File diff suppressed because it is too large Load Diff

9582
LDP/guide/docbook/Linux-Dictionary/edT.xml
View File

File diff suppressed because one or more lines are too long

3994
LDP/guide/docbook/Linux-Dictionary/edU.xml
View File

File diff suppressed because it is too large Load Diff

3048
LDP/guide/docbook/Linux-Dictionary/edV.xml
View File

File diff suppressed because it is too large Load Diff

5770
LDP/guide/docbook/Linux-Dictionary/edW.xml
View File

File diff suppressed because it is too large Load Diff

9976
LDP/guide/docbook/Linux-Dictionary/edX.xml
View File

File diff suppressed because it is too large Load Diff

848
LDP/guide/docbook/Linux-Dictionary/edY.xml
View File

@ -1,424 +1,424 @@
<glossary id="Y">
<title>Y</title>
<glossentry>
<glossterm>
YP
</glossterm>
<glossdef>
<para>
Yellow Pages(tm), a registered trademark in the UK of British Telecom plc. From NIS HOWTO
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yacc
</glossterm>
<glossdef>
<para>
a &quot;parser&quot;. YACC stands for &quot;Yet Another Compiler Compiler&quot;. This is because this kind of analysis of text files is normally associated with writing compilers. From Linux Guide @FirstLinux
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yellow Book
</glossterm>
<glossdef>
<para>
An Interntional Standards Organisation (1SO) standard that describes the way data is encoded on CD-ROMs. The Yellow Book standard includes CD-XA specifications. YModem A file transfer protocol is an improved version of XMODEM-IK. YMODEM transfers data in 1,024-byte, blocks and performs a cyclic redundancy check (CRC) on each frame. Also, YMODEM supports sending more than over file in sequence. See YMODEM-g and ZMODEM. From QUECID
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yellow Dog
</glossterm>
<glossdef>
<para>
Yellow Dog Linux is a complete, Red Hat and RPM based operating system for PowerPC computers. YDL may co-exist with Mac OS in a dual-boot environment or replace the Mac OS on &quot;New World ROM&quot; (Blue &amp; White G3s and newer) machines. Simple to install, YDL offers a graphical installer, KDE (an elegant, mature GUI), and over 900 applications to fulfill server, code developer, and home/office needs. YDL 3.0 was released March 19, 2003. From LWN Distribution List
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yet Another
</glossterm>
<glossdef>
<para>
adj. [From Unix&apos;s yacc(1), `Yet Another Compiler-Compiler&apos;, a LALR parser generator] 1. Of your own work: A humorous allusion often used in titles to acknowledge that the topic is not original, though the content is. As in `Yet Another AI Group&apos; or `Yet Another Simulated Annealing Algorithm&apos;. 2. Of others&apos; work: Describes something of which there are already far too many. See also YA-, YABA, YAUN. From Jargon Dictionary
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yoper
</glossterm>
<glossdef>
<para>
Yoper is a high performance operating system which has been carefully optimised for PC&apos;s with either 686 or higher processor types. The binaries that come with Yoper have been built from scratch using the original sources combined with the best features of from the major distros. Yoper is high performance and compact. In fact Yoper is one of the most standardised linux&apos;s that you will find and hardware performance is better than that of any other commercial OS. With Yoper it is possible to import packages from all the other major distributions, including RPM&apos;s, .deb&apos;s, and .tgz packages. Ydesktop-3.2.1 Release Candidate 3 released January 12, 2003. From LWN Distribution List
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yabasic
</glossterm>
<glossdef>
<para>
Yet Another BASIC interpreter Implements the most common (and simple) elements of the language plus some graphics facilities. Anyone who has ever written BASIC programs on a C-64 should feel at home. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yacas
</glossterm>
<glossdef>
<para>
Computer Algebra System Yet Another Computer Algebra System is a small and highly flexible computer algebra language. The syntax is very close to Mathematica. The distribution contains a small library of mathematical functions, but its real strength is in the language in which you can easily write your own symbolic manipulation algorithms. It supports arbitrary precision arithmetic. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yacc
</glossterm>
<glossdef>
<para>
GNU Project parser generator (yacc replacement) From whatis
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yaclc
</glossterm>
<glossdef>
<para>
check the bug closings in a Debian changelog. yaclc (yet another change log check) queries the Bug Tracking System to see if the bugs closed in a package&apos;s changelog belong to that package. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yada
</glossterm>
<glossdef>
<para>
Yet Another Debianisation Aid YADA is a Debian packaging helper. It parses a special file, debian/packages, in a source package, and generates an appropriate debian/rules to control building of the package. WARNING: YADA is still very experimental! Use it at your own risk! (And please run Lintian over anything built with yada before uploading.) From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yadex
</glossterm>
<glossdef>
<para>
WAD file editor for doom-style WADs Yadex is a Doom level (wad) editor for Unix systems running X, including Linux. It supports Doom alpha, Doom beta, Doom, Ultimate Doom, Final Doom, Doom II, Heretic and also, in a more or less limited way, Hexen and Strife. It is available under the terms of the GPL. Yadex is descended from DEU 5.21. Therefore, as you might expect, it&apos;s a rather low-level editor that requires you to take care of a lot of detail but on the flip side allows you to control very precisely what you are doing. In addition, it has many advanced functions that DEU didn&apos;t have, to make certain tedious tasks easy. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yafc
</glossterm>
<glossdef>
<para>
Yet Another FTP Client Yafc is an ftp client intended to be a replacement for the standard ftp(1) program. Features include directory cache, remote filename completion, aliases, colored ls, recursive get/put/ls/rm, nohup mode transfers, tagging (queueing), background downloading, and more. This version is compiled without KTH Kerberos 4/5 authentication. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yank
</glossterm>
<glossdef>
<para>
yet another notekeeper Yank is a simple notekeeper and todo-list manager using the gnome and gtk libraries. It feels stable and usable enough to be released to the public but it surely lacks some (not so important) features which might be added later. Excessive tests have shown that yank is fool-proof, irritating and wasting too much memory. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yaps
</glossterm>
<glossdef>
<para>
Yet Another Pager Software This software is primary designed to send message to so called pager devices including cellular phones which are able to receive textual messages (sometimes called SMS, short message system/service.) From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yard
</glossterm>
<glossdef>
<para>
Perl scripts to build rescue disk(s) to revive a system Yard is a suite of Perl scripts for creating custom boot/rescue disks. Using a compressed filesystem, it can put a standard kernel image plus about 2.4 meg of utilities on a single floppy. Yard is also useful for creating self-contained Linux-on-a-floppy systems. You specify a basic set of files and utilities for inclusion and Yard handles many of the details. Features: - File specs allow absolute and relative filenames, symbolic links, file replacements and full shell-style globbing. - Automatically determines necessary libraries and loaders. - Allows stripping of binaries and libraries during copying. - Automatically regenerates ld.so.cache - Checks for broken symlinks - Checks /etc/{fstab,inittab,termcap,pam.conf} for common errors and inconsistencies. - Checks user directories and files mentioned in /etc/passwd - Checks command files (eg, rc.local and .login) and scripts for missing binaries and command interpreters. - Automatically performs filesystem compression and copying. - Can be used with or without LILO. - Can make single or double disk sets. - Extensive checking of user choices and execution errors. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yardradius
</glossterm>
<glossdef>
<para>
YARD Radius Auth/Acct Server YARD Radius is a Radius authentication/accounting server which is derived from the original Livingston Enterprise Inc. RADIUS daemon release 2.1. It adds a number of useful features to the LE daemon, i.e. Control of simultaneous logins. Support of Ascend, Cisco and USR boxes. Extended daily/monthly/yearly accounting information on a per-user basis MD5 encrypted passwords support (both in passwd file and/or users file) Expirations in shadow file. Checking based on time-of-day, traffic and connection time. Support of PAM authentication and accounting. Binary form of accounting file. GDBM formats for users and user stats databases. Autoconfiguring capabilities of sources. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yasgml
</glossterm>
<glossdef>
<para>
Yet Another Linuxdoc-DTD only SGML mode Yasgml automates typesetting and previewing of SGML and enables completing input of SGML mark-up command such as `&lt;verb&gt;&apos;..`&lt;/verb&gt;&apos;. It is intended to use with LinuxDoc DTD only. You may need linuxdoc-tools package to process Linuxdoc-DTD SGML source. Default is for Japanese text editing. Its keybinding is based on that of YaTeX. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yatex
</glossterm>
<glossdef>
<para>
Yet Another LaTeX mode YaTeX automates typesetting and previewing of LaTeX and enables completing input of LaTeX mark-up command such as `\begin{}&apos;..`\end{}&apos;. YaTeX also supports Demacs which runs on MS-DOS(386), Mule (Multi Language Enhancement to GNU Emacs), and latex on DOS. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yc-el
</glossterm>
<glossdef>
<para>
Yet another Canna client for Emacsen. Canna client for emacs20, emacs21 or xemacs with MULE support. yc.el is implemented in pure elisp, makes it possible to use Canna on emacsen without direct support for Canna. Canna is a Japanese input method. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yelp
</glossterm>
<glossdef>
<para>
Yelp is the Gnome 2 help/documentation browser. It is designed to help you browse all the documentation on your system in one central tool. From Redhat 8.0 RPM
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yencode
</glossterm>
<glossdef>
<para>
Powerful yEnc decoder/encoder Powerful standards-compliant yEnc encoder/decoder for the Usenet yEnc encoding format for modern UNIX systems From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yes
</glossterm>
<glossdef>
<para>
output a string repeatedly until killed From whatis
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yforth
</glossterm>
<glossdef>
<para>
A small freeware Forth environment in ANSI C. yForth? is an interestingly small implementation of Forth for Linux. It suffers several deficiencies. For general Forth programming or learning under Linux, yForth? is not the best choice. From the author&apos;s README: yForth? is a Forth environment written entirely in ANSI C, making it extremely portable. The first thing I want to tell you about yForth? is that it seems a joke compared to other systems such as gForth or PFE. Nevertheless, you could find yForth? nice, in which case you&apos;re invited to explore yForth? It&apos;s yours, you can make anything you want with it. If you want an explanation of the words provided by yForth? please refer to the draft of ANS Forth or something equivalent. The Net will help you. Do not expect the prompt &quot;ok&quot; to come up when you run yForth?, the standard says that &quot;ok&quot; shall be printed AFTER every successful command execution... From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yh
</glossterm>
<glossdef>
<para>
Yan Huang Chinese Platform, a console Chinese environment Yan Huang Chinese Platform provides Chinese/English text input/output environment. Users can choose input methods from &quot;Quwei&quot;, &quot;GbkPinYin&quot; and &quot;BiaoXingMa&quot;. GBK standard Chinese interal encoding and Big5 encoding Chinese text are both supported. Authors: Red Flag Linux Home Page: http://www.redflag-linux.com/ From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yiff-server
</glossterm>
<glossdef>
<para>
Y Sound Server YIFF is a network based and multi client connection system that supports X Window Systems style event and client handling. Internal 3D sound support and client to server IO wrapper code is also available. YIFF is OSS, ALSA, YSound and Y2N compliant. More information can be found at the YIFF web site http://wolfpack.twu.net/YIFF/ . From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yiyantang
</glossterm>
<glossdef>
<para>
Terminal-based Chinese automatic encoding converter yyt is a pseudo-tty program that converts Chinese terminal output encoded in GB/BIG5 to a preset encoding automatically. It is useful for users who have to work with multiple Chinese encoding in console applications. Now it also converts input to the incoming encoding if the incoming encoding is set explicitly. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yodl
</glossterm>
<glossdef>
<para>
Yet oneOther Document Language. Yodl is a package that implements a pre-document language and tools to process it. The idea of Yodl is that you write up a document in a pre-language, then use the tools (e.g. yodl2html) to convert it to some final document language. Current converters are for HTML, ms, man, LaTeX SGML and texinfo, plus a poor-man&apos;s text converter. Main document types are &quot;article&quot;, &quot;report&quot;, &quot;book&quot; and &quot;manpage&quot;. The Yodl document language is designed to be easy to use and extensible. URL: http://www.xs4all.nl/~jantien/yodl/ Authors: Karel Kubat &lt;karel@icce.rug.nl&gt; Frank Brokken &lt;f.b.brokken@rc.rug.nl&gt; Jan Nieuwenhuizen &lt;janneke@gnu.org&gt; From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yorick
</glossterm>
<glossdef>
<para>
interpreted language and scientific graphics Yorick is an interpreted programming language for: * scientific simulations or calculations * postprocessing or steering large simulation codes * interactive scientific graphics * reading, writing, and translating large files of numbers The language features a compact syntax for many common array operations, so it processes large arrays of numbers very quickly and efficiently. Superficially, yorick code resembles C code, but yorick variables are never explicitly declared and have a dynamic scoping similar to many Lisp dialects. The yorick language is designed to be typed interactively at a keyboard, as well as stored in files for later use. This package includes an emacs-based development environment, which you can launch by typing M-x yorick in emacs. ftp://ftp-icf.llnl.gov/pub/Yorick/doc/index.html From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
youbin
</glossterm>
<glossdef>
<para>
The conventional mail arrival notification server. Youbin is a kind of biff in the network age. When youbin is used, the mail spool of a certain, specific machine (mail server) is observed to inform the arrival of mail to a user at an arbitrary machine through the network. On the other hand, the conventional &quot;biff&quot; informs only the user who logs in at the machine with the mail spool. Combining with POP, youbin eliminate a lot of NFS mount of mail spool for mail arrival checking. Since youbin is designed with event driven, the user is promptly informed of status change of mail spool caused by mail arriving and reading. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yp-tools
</glossterm>
<glossdef>
<para>
The Network Information Service (NIS) is a system that provides network information (login names, passwords, home directories, group information) to all of the machines on a network. NIS can allow users to log in on any machine on the network, as long as the machine has the NIS client programs running and the user&apos;s password is recorded in the NIS passwd database. NIS was formerly known as Sun Yellow Pages(YP). This NIS implementation is based on FreeBSD&apos;s YP and is a special port for glibc 2.x and libc versions 5.4.21 and later. This package only provides the NIS client programs. In order to use the clients, you need to have an NIS server running on your network. An NIS server is provided in the ypserv package. Install the yp-tools package if you need NIS client programs for machines on your network. You will also need to install the ypbind package on every machine running NIS client programs. If you need an NIS server, you need to install the ypserv package on one machine on the network. From Redhat 8.0 RPM
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ypbind
</glossterm>
<glossdef>
<para>
The Network Information Service (NIS) is a system that provides network information (login names, passwords, home directories, group information) to all of the machines on a network. NIS can allow users to log in on any machine on the network, as long as the machine has the NIS client programs running and the user&apos;s password is recorded inthe NIS passwd database. NIS was formerly known as Sun Yellow Pages(YP). This package provides the ypbind daemon. The ypbind daemon binds NIS clients to an NIS domain. Ypbind must be running on any machines running NIS client programs. Install the ypbind package on any machines running NIS client programs (included in the yp-tools package). If you need an NIS server, youalso need to install the ypserv package to a machine on your network. From Redhat 8.0 RPM
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ytalk
</glossterm>
<glossdef>
<para>
Enhanced talk program with X support. Ytalk is a multi-user chat program. It works exactly like the UNIX talk program and even communicates with the same talk daemons. Ytalk&apos;s advantages come in it&apos;s ability to allow multiple connections. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ytree
</glossterm>
<glossdef>
<para>
A file manager that looks like Xtree Gold(tm) This is a file manager that looks like xtree gold(tm). it has history, colors, configurable file viewers and much more. It works on terminals. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yudit
</glossterm>
<glossdef>
<para>
unicode text editor yudit is a unicode text editor for the X Window System. It does not need localized environment or unicode fonts. It supports simultaneous processing of many languages, conversions for local character standards, bidirectional input, has its own input methods. The package includes conversion utilities, and it also has support for postscript printing. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yydecode
</glossterm>
<glossdef>
<para>
decode yEnc archives yydecode works almost identically to the infamous uudecode program, but for yEnc encoded archives. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yyextract
</glossterm>
<glossdef>
<para>
extract grammar rules from a yacc grammar From whatis
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yyref
</glossterm>
<glossdef>
<para>
generate cross-reference for yacc input From whatis
</para>
</glossdef>
</glossentry>
</glossary>
<?xml version="1.0" encoding="UTF-8"?>
<glossary id="Y">
<title>Y</title>
<glossentry>
<glossterm>
YP
</glossterm>
<glossdef>
<para>
Yellow Pages(tm), a registered trademark in the UK of British Telecom plc. From NIS HOWTO
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yacc
</glossterm>
<glossdef>
<para>
a &quot;parser&quot;. YACC stands for &quot;Yet Another Compiler Compiler&quot;. This is because this kind of analysis of text files is normally associated with writing compilers. From Linux Guide @FirstLinux
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yellow Book
</glossterm>
<glossdef>
<para>
An Interntional Standards Organisation (1SO) standard that describes the way data is encoded on CD-ROMs. The Yellow Book standard includes CD-XA specifications. YModem A file transfer protocol is an improved version of XMODEM-IK. YMODEM transfers data in 1,024-byte, blocks and performs a cyclic redundancy check (CRC) on each frame. Also, YMODEM supports sending more than over file in sequence. See YMODEM-g and ZMODEM. From QUECID
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yellow Dog
</glossterm>
<glossdef>
<para>
Yellow Dog Linux is a complete, Red Hat and RPM based operating system for PowerPC computers. YDL may co-exist with Mac OS in a dual-boot environment or replace the Mac OS on &quot;New World ROM&quot; (Blue &amp; White G3s and newer) machines. Simple to install, YDL offers a graphical installer, KDE (an elegant, mature GUI), and over 900 applications to fulfill server, code developer, and home/office needs. YDL 3.0 was released March 19, 2003. From LWN Distribution List
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yet Another
</glossterm>
<glossdef>
<para>
adj. [From Unix&apos;s yacc(1), `Yet Another Compiler-Compiler&apos;, a LALR parser generator] 1. Of your own work: A humorous allusion often used in titles to acknowledge that the topic is not original, though the content is. As in `Yet Another AI Group&apos; or `Yet Another Simulated Annealing Algorithm&apos;. 2. Of others&apos; work: Describes something of which there are already far too many. See also YA-, YABA, YAUN. From Jargon Dictionary
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Yoper
</glossterm>
<glossdef>
<para>
Yoper is a high performance operating system which has been carefully optimised for PC&apos;s with either 686 or higher processor types. The binaries that come with Yoper have been built from scratch using the original sources combined with the best features of from the major distros. Yoper is high performance and compact. In fact Yoper is one of the most standardised linux&apos;s that you will find and hardware performance is better than that of any other commercial OS. With Yoper it is possible to import packages from all the other major distributions, including RPM&apos;s, .deb&apos;s, and .tgz packages. Ydesktop-3.2.1 Release Candidate 3 released January 12, 2003. From LWN Distribution List
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yabasic
</glossterm>
<glossdef>
<para>
Yet Another BASIC interpreter Implements the most common (and simple) elements of the language plus some graphics facilities. Anyone who has ever written BASIC programs on a C-64 should feel at home. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yacas
</glossterm>
<glossdef>
<para>
Computer Algebra System Yet Another Computer Algebra System is a small and highly flexible computer algebra language. The syntax is very close to Mathematica. The distribution contains a small library of mathematical functions, but its real strength is in the language in which you can easily write your own symbolic manipulation algorithms. It supports arbitrary precision arithmetic. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yacc
</glossterm>
<glossdef>
<para>
GNU Project parser generator (yacc replacement) From whatis
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yaclc
</glossterm>
<glossdef>
<para>
check the bug closings in a Debian changelog. yaclc (yet another change log check) queries the Bug Tracking System to see if the bugs closed in a package&apos;s changelog belong to that package. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yada
</glossterm>
<glossdef>
<para>
Yet Another Debianisation Aid YADA is a Debian packaging helper. It parses a special file, debian/packages, in a source package, and generates an appropriate debian/rules to control building of the package. WARNING: YADA is still very experimental! Use it at your own risk! (And please run Lintian over anything built with yada before uploading.) From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yadex
</glossterm>
<glossdef>
<para>
WAD file editor for doom-style WADs Yadex is a Doom level (wad) editor for Unix systems running X, including Linux. It supports Doom alpha, Doom beta, Doom, Ultimate Doom, Final Doom, Doom II, Heretic and also, in a more or less limited way, Hexen and Strife. It is available under the terms of the GPL. Yadex is descended from DEU 5.21. Therefore, as you might expect, it&apos;s a rather low-level editor that requires you to take care of a lot of detail but on the flip side allows you to control very precisely what you are doing. In addition, it has many advanced functions that DEU didn&apos;t have, to make certain tedious tasks easy. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yafc
</glossterm>
<glossdef>
<para>
Yet Another FTP Client Yafc is an ftp client intended to be a replacement for the standard ftp(1) program. Features include directory cache, remote filename completion, aliases, colored ls, recursive get/put/ls/rm, nohup mode transfers, tagging (queueing), background downloading, and more. This version is compiled without KTH Kerberos 4/5 authentication. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yank
</glossterm>
<glossdef>
<para>
yet another notekeeper Yank is a simple notekeeper and todo-list manager using the gnome and gtk libraries. It feels stable and usable enough to be released to the public but it surely lacks some (not so important) features which might be added later. Excessive tests have shown that yank is fool-proof, irritating and wasting too much memory. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yaps
</glossterm>
<glossdef>
<para>
Yet Another Pager Software This software is primary designed to send message to so called pager devices including cellular phones which are able to receive textual messages (sometimes called SMS, short message system/service.) From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yard
</glossterm>
<glossdef>
<para>
Perl scripts to build rescue disk(s) to revive a system Yard is a suite of Perl scripts for creating custom boot/rescue disks. Using a compressed filesystem, it can put a standard kernel image plus about 2.4 meg of utilities on a single floppy. Yard is also useful for creating self-contained Linux-on-a-floppy systems. You specify a basic set of files and utilities for inclusion and Yard handles many of the details. Features: - File specs allow absolute and relative filenames, symbolic links, file replacements and full shell-style globbing. - Automatically determines necessary libraries and loaders. - Allows stripping of binaries and libraries during copying. - Automatically regenerates ld.so.cache - Checks for broken symlinks - Checks /etc/{fstab,inittab,termcap,pam.conf} for common errors and inconsistencies. - Checks user directories and files mentioned in /etc/passwd - Checks command files (eg, rc.local and .login) and scripts for missing binaries and command interpreters. - Automatically performs filesystem compression and copying. - Can be used with or without LILO. - Can make single or double disk sets. - Extensive checking of user choices and execution errors. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yardradius
</glossterm>
<glossdef>
<para>
YARD Radius Auth/Acct Server YARD Radius is a Radius authentication/accounting server which is derived from the original Livingston Enterprise Inc. RADIUS daemon release 2.1. It adds a number of useful features to the LE daemon, i.e. Control of simultaneous logins. Support of Ascend, Cisco and USR boxes. Extended daily/monthly/yearly accounting information on a per-user basis MD5 encrypted passwords support (both in passwd file and/or users file) Expirations in shadow file. Checking based on time-of-day, traffic and connection time. Support of PAM authentication and accounting. Binary form of accounting file. GDBM formats for users and user stats databases. Autoconfiguring capabilities of sources. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yasgml
</glossterm>
<glossdef>
<para>
Yet Another Linuxdoc-DTD only SGML mode Yasgml automates typesetting and previewing of SGML and enables completing input of SGML mark-up command such as `&lt;verb&gt;&apos;..`&lt;/verb&gt;&apos;. It is intended to use with LinuxDoc DTD only. You may need linuxdoc-tools package to process Linuxdoc-DTD SGML source. Default is for Japanese text editing. Its keybinding is based on that of YaTeX. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yatex
</glossterm>
<glossdef>
<para>
Yet Another LaTeX mode YaTeX automates typesetting and previewing of LaTeX and enables completing input of LaTeX mark-up command such as `\begin{}&apos;..`\end{}&apos;. YaTeX also supports Demacs which runs on MS-DOS(386), Mule (Multi Language Enhancement to GNU Emacs), and latex on DOS. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yc-el
</glossterm>
<glossdef>
<para>
Yet another Canna client for Emacsen. Canna client for emacs20, emacs21 or xemacs with MULE support. yc.el is implemented in pure elisp, makes it possible to use Canna on emacsen without direct support for Canna. Canna is a Japanese input method. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yelp
</glossterm>
<glossdef>
<para>
Yelp is the Gnome 2 help/documentation browser. It is designed to help you browse all the documentation on your system in one central tool. From Redhat 8.0 RPM
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yencode
</glossterm>
<glossdef>
<para>
Powerful yEnc decoder/encoder Powerful standards-compliant yEnc encoder/decoder for the Usenet yEnc encoding format for modern UNIX systems From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yes
</glossterm>
<glossdef>
<para>
output a string repeatedly until killed From whatis
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yforth
</glossterm>
<glossdef>
<para>
A small freeware Forth environment in ANSI C. yForth? is an interestingly small implementation of Forth for Linux. It suffers several deficiencies. For general Forth programming or learning under Linux, yForth? is not the best choice. From the author&apos;s README: yForth? is a Forth environment written entirely in ANSI C, making it extremely portable. The first thing I want to tell you about yForth? is that it seems a joke compared to other systems such as gForth or PFE. Nevertheless, you could find yForth? nice, in which case you&apos;re invited to explore yForth? It&apos;s yours, you can make anything you want with it. If you want an explanation of the words provided by yForth? please refer to the draft of ANS Forth or something equivalent. The Net will help you. Do not expect the prompt &quot;ok&quot; to come up when you run yForth?, the standard says that &quot;ok&quot; shall be printed AFTER every successful command execution... From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yh
</glossterm>
<glossdef>
<para>
Yan Huang Chinese Platform, a console Chinese environment Yan Huang Chinese Platform provides Chinese/English text input/output environment. Users can choose input methods from &quot;Quwei&quot;, &quot;GbkPinYin&quot; and &quot;BiaoXingMa&quot;. GBK standard Chinese interal encoding and Big5 encoding Chinese text are both supported. Authors: Red Flag Linux Home Page: http://www.redflag-linux.com/ From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yiff-server
</glossterm>
<glossdef>
<para>
Y Sound Server YIFF is a network based and multi client connection system that supports X Window Systems style event and client handling. Internal 3D sound support and client to server IO wrapper code is also available. YIFF is OSS, ALSA, YSound and Y2N compliant. More information can be found at the YIFF web site http://wolfpack.twu.net/YIFF/ . From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yiyantang
</glossterm>
<glossdef>
<para>
Terminal-based Chinese automatic encoding converter yyt is a pseudo-tty program that converts Chinese terminal output encoded in GB/BIG5 to a preset encoding automatically. It is useful for users who have to work with multiple Chinese encoding in console applications. Now it also converts input to the incoming encoding if the incoming encoding is set explicitly. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yodl
</glossterm>
<glossdef>
<para>
Yet oneOther Document Language. Yodl is a package that implements a pre-document language and tools to process it. The idea of Yodl is that you write up a document in a pre-language, then use the tools (e.g. yodl2html) to convert it to some final document language. Current converters are for HTML, ms, man, LaTeX SGML and texinfo, plus a poor-man&apos;s text converter. Main document types are &quot;article&quot;, &quot;report&quot;, &quot;book&quot; and &quot;manpage&quot;. The Yodl document language is designed to be easy to use and extensible. URL: http://www.xs4all.nl/~jantien/yodl/ Authors: Karel Kubat &lt;karel@icce.rug.nl&gt; Frank Brokken &lt;f.b.brokken@rc.rug.nl&gt; Jan Nieuwenhuizen &lt;janneke@gnu.org&gt; From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yorick
</glossterm>
<glossdef>
<para>
interpreted language and scientific graphics Yorick is an interpreted programming language for: * scientific simulations or calculations * postprocessing or steering large simulation codes * interactive scientific graphics * reading, writing, and translating large files of numbers The language features a compact syntax for many common array operations, so it processes large arrays of numbers very quickly and efficiently. Superficially, yorick code resembles C code, but yorick variables are never explicitly declared and have a dynamic scoping similar to many Lisp dialects. The yorick language is designed to be typed interactively at a keyboard, as well as stored in files for later use. This package includes an emacs-based development environment, which you can launch by typing M-x yorick in emacs. ftp://ftp-icf.llnl.gov/pub/Yorick/doc/index.html From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
youbin
</glossterm>
<glossdef>
<para>
The conventional mail arrival notification server. Youbin is a kind of biff in the network age. When youbin is used, the mail spool of a certain, specific machine (mail server) is observed to inform the arrival of mail to a user at an arbitrary machine through the network. On the other hand, the conventional &quot;biff&quot; informs only the user who logs in at the machine with the mail spool. Combining with POP, youbin eliminate a lot of NFS mount of mail spool for mail arrival checking. Since youbin is designed with event driven, the user is promptly informed of status change of mail spool caused by mail arriving and reading. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yp-tools
</glossterm>
<glossdef>
<para>
The Network Information Service (NIS) is a system that provides network information (login names, passwords, home directories, group information) to all of the machines on a network. NIS can allow users to log in on any machine on the network, as long as the machine has the NIS client programs running and the user&apos;s password is recorded in the NIS passwd database. NIS was formerly known as Sun Yellow Pages(YP). This NIS implementation is based on FreeBSD&apos;s YP and is a special port for glibc 2.x and libc versions 5.4.21 and later. This package only provides the NIS client programs. In order to use the clients, you need to have an NIS server running on your network. An NIS server is provided in the ypserv package. Install the yp-tools package if you need NIS client programs for machines on your network. You will also need to install the ypbind package on every machine running NIS client programs. If you need an NIS server, you need to install the ypserv package on one machine on the network. From Redhat 8.0 RPM
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ypbind
</glossterm>
<glossdef>
<para>
The Network Information Service (NIS) is a system that provides network information (login names, passwords, home directories, group information) to all of the machines on a network. NIS can allow users to log in on any machine on the network, as long as the machine has the NIS client programs running and the user&apos;s password is recorded inthe NIS passwd database. NIS was formerly known as Sun Yellow Pages(YP). This package provides the ypbind daemon. The ypbind daemon binds NIS clients to an NIS domain. Ypbind must be running on any machines running NIS client programs. Install the ypbind package on any machines running NIS client programs (included in the yp-tools package). If you need an NIS server, youalso need to install the ypserv package to a machine on your network. From Redhat 8.0 RPM
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ytalk
</glossterm>
<glossdef>
<para>
Enhanced talk program with X support. Ytalk is a multi-user chat program. It works exactly like the UNIX talk program and even communicates with the same talk daemons. Ytalk&apos;s advantages come in it&apos;s ability to allow multiple connections. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ytree
</glossterm>
<glossdef>
<para>
A file manager that looks like Xtree Gold(tm) This is a file manager that looks like xtree gold(tm). it has history, colors, configurable file viewers and much more. It works on terminals. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yudit
</glossterm>
<glossdef>
<para>
unicode text editor yudit is a unicode text editor for the X Window System. It does not need localized environment or unicode fonts. It supports simultaneous processing of many languages, conversions for local character standards, bidirectional input, has its own input methods. The package includes conversion utilities, and it also has support for postscript printing. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yydecode
</glossterm>
<glossdef>
<para>
decode yEnc archives yydecode works almost identically to the infamous uudecode program, but for yEnc encoded archives. From Debian 3.0r0 APT
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yyextract
</glossterm>
<glossdef>
<para>
extract grammar rules from a yacc grammar From whatis
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
yyref
</glossterm>
<glossdef>
<para>
generate cross-reference for yacc input From whatis
</para>
</glossdef>
</glossentry>
</glossary>

1128
LDP/guide/docbook/Linux-Dictionary/edZ.xml
View File

File diff suppressed because it is too large Load Diff

862
LDP/guide/docbook/Linux-Dictionary/fdl.xml
View File

@ -1,431 +1,431 @@
<appendix id="gfdl">
<title>GNU Free Documentation License</title>
<subtitle>Version 1.2, November 2002</subtitle>
<blockquote id="fsf-copyright">
<para>Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.</para>
</blockquote>
<section id="gfdl-0"><title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook, or
other functional and useful document "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.</para>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-1"><title>APPLICABILITY AND DEFINITIONS</title>
<para id="gfdl-doc">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.</para>
<para id="gfdl-mod-ver">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.</para>
<para id="gfdl-secnd-sect">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.</para>
<para id="gfdl-inv-sect">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.</para>
<para id="gfdl-cov-text">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.</para>
<para id="gfdl-transparent">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".</para>
<para>Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX 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.</para>
<para id="gfdl-title-page">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.</para>
<para id="gfdl-entitled">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.</para>
<para>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.</para>
</section>
<section id="gfdl-2"><title>VERBATIM COPYING</title>
<para>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.
</para>
<para>You may also lend copies, under the same conditions stated above,
and you may publicly display copies.</para>
</section>
<section id="gfdl-3"><title>COPYING IN QUANTITY</title>
<para>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.</para>
<para>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.</para>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-4"><title>MODIFICATIONS</title>
<para>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:</para>
<orderedlist id="gfdl-modif-cond" numeration="upperalpha">
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>State on the Title page the name of the publisher of
the Modified Version, as the publisher.</simpara></listitem>
<listitem><simpara>Preserve all the copyright notices of the Document.
</simpara></listitem>
<listitem><simpara>Add an appropriate copyright notice for your
modifications adjacent to the other copyright notices.
</simpara></listitem>
<listitem><simpara>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
<link linkend="gfdl-addendum">Addendum</link> below.
</simpara></listitem>
<listitem><simpara>Preserve in that license notice the full lists of
Invariant Sections and required Cover Texts given in the Document's
license notice.</simpara></listitem>
<listitem><simpara>Include an unaltered copy of this License.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>Delete any section Entitled "Endorsements".
Such a section may not be included in the Modified Version.
</simpara></listitem>
<listitem><simpara>Do not retitle any existing section to be Entitled
"Endorsements" or to conflict in title with any Invariant Section.
</simpara></listitem>
<listitem><simpara>Preserve any Warranty Disclaimers.
</simpara></listitem>
</orderedlist>
<para>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.</para>
<para>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.</para>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-5"><title>COMBINING DOCUMENTS</title>
<para>You may combine the Document with other documents released under
this License, under the terms defined in <link linkend="gfdl-4">section
4</link> 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.</para>
<para>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.</para>
<para>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".</para>
</section>
<section id="gfdl-6"><title>COLLECTIONS OF DOCUMENTS</title>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-7"><title>AGGREGATION WITH INDEPENDENT WORKS</title>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-8"><title>TRANSLATION</title>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-9"><title>TERMINATION</title>
<para>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt
to copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this License
will not have their licenses terminated so long as such parties remain
in full compliance.</para>
</section>
<section id="gfdl-10"><title>FUTURE REVISIONS OF THIS LICENSE</title>
<para>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
http://www.gnu.org/copyleft/.</para>
<para>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.</para>
</section>
<section id="gfdl-addendum"><title>ADDENDUM: How to use this License for
your documents</title>
<para>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:</para>
<blockquote id="copyright-sample"><para>
Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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".
</para></blockquote>
<para>If you have Invariant Sections, Front-Cover Texts and Back-Cover
Texts, replace the "with...Texts." line with this:</para>
<blockquote id="inv-cover-sample"><para>
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
</para></blockquote>
<para>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.</para>
<para>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.</para>
</section>
</appendix>
<appendix id="gfdl">
<title>GNU Free Documentation License</title>
<subtitle>Version 1.2, November 2002</subtitle>
<blockquote id="fsf-copyright">
<para>Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.</para>
</blockquote>
<section id="gfdl-0"><title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook, or
other functional and useful document "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.</para>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-1"><title>APPLICABILITY AND DEFINITIONS</title>
<para id="gfdl-doc">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.</para>
<para id="gfdl-mod-ver">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.</para>
<para id="gfdl-secnd-sect">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.</para>
<para id="gfdl-inv-sect">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.</para>
<para id="gfdl-cov-text">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.</para>
<para id="gfdl-transparent">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".</para>
<para>Examples of suitable formats for Transparent copies include plain
ASCII without markup, Texinfo input format, LaTeX 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.</para>
<para id="gfdl-title-page">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.</para>
<para id="gfdl-entitled">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.</para>
<para>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.</para>
</section>
<section id="gfdl-2"><title>VERBATIM COPYING</title>
<para>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.
</para>
<para>You may also lend copies, under the same conditions stated above,
and you may publicly display copies.</para>
</section>
<section id="gfdl-3"><title>COPYING IN QUANTITY</title>
<para>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.</para>
<para>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.</para>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-4"><title>MODIFICATIONS</title>
<para>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:</para>
<orderedlist id="gfdl-modif-cond" numeration="upperalpha">
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>State on the Title page the name of the publisher of
the Modified Version, as the publisher.</simpara></listitem>
<listitem><simpara>Preserve all the copyright notices of the Document.
</simpara></listitem>
<listitem><simpara>Add an appropriate copyright notice for your
modifications adjacent to the other copyright notices.
</simpara></listitem>
<listitem><simpara>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
<link linkend="gfdl-addendum">Addendum</link> below.
</simpara></listitem>
<listitem><simpara>Preserve in that license notice the full lists of
Invariant Sections and required Cover Texts given in the Document's
license notice.</simpara></listitem>
<listitem><simpara>Include an unaltered copy of this License.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>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.
</simpara></listitem>
<listitem><simpara>Delete any section Entitled "Endorsements".
Such a section may not be included in the Modified Version.
</simpara></listitem>
<listitem><simpara>Do not retitle any existing section to be Entitled
"Endorsements" or to conflict in title with any Invariant Section.
</simpara></listitem>
<listitem><simpara>Preserve any Warranty Disclaimers.
</simpara></listitem>
</orderedlist>
<para>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.</para>
<para>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.</para>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-5"><title>COMBINING DOCUMENTS</title>
<para>You may combine the Document with other documents released under
this License, under the terms defined in <link linkend="gfdl-4">section
4</link> 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.</para>
<para>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.</para>
<para>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".</para>
</section>
<section id="gfdl-6"><title>COLLECTIONS OF DOCUMENTS</title>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-7"><title>AGGREGATION WITH INDEPENDENT WORKS</title>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-8"><title>TRANSLATION</title>
<para>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.</para>
<para>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.</para>
</section>
<section id="gfdl-9"><title>TERMINATION</title>
<para>You may not copy, modify, sublicense, or distribute the Document
except as expressly provided for under this License. Any other attempt
to copy, modify, sublicense or distribute the Document is void, and will
automatically terminate your rights under this License. However,
parties who have received copies, or rights, from you under this License
will not have their licenses terminated so long as such parties remain
in full compliance.</para>
</section>
<section id="gfdl-10"><title>FUTURE REVISIONS OF THIS LICENSE</title>
<para>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
http://www.gnu.org/copyleft/.</para>
<para>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.</para>
</section>
<section id="gfdl-addendum"><title>ADDENDUM: How to use this License for
your documents</title>
<para>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:</para>
<blockquote id="copyright-sample"><para>
Copyright (c) YEAR YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
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".
</para></blockquote>
<para>If you have Invariant Sections, Front-Cover Texts and Back-Cover
Texts, replace the "with...Texts." line with this:</para>
<blockquote id="inv-cover-sample"><para>
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
</para></blockquote>
<para>If you have Invariant Sections without Cover Texts, or some other
combination of the three, merge those two alternatives to suit the
situation.</para>
<para>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.</para>
</section>
</appendix>