Merge branch 'master' of github.com:martin-a-brown/LDP

This commit is contained in:
Martin A. Brown 2016-01-20 09:19:46 -08:00
commit a9c9c5a2e9
56 changed files with 14373 additions and 5 deletions

1
.gitignore vendored Normal file
View File

@ -0,0 +1 @@
*~

View File

@ -66,9 +66,9 @@
<section id="intro_01">
<title>Why this guide?</title>
<para>The primary reason for writing this document is that a lot of readers feel the existing <ulink url="http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html">HOWTO</ulink> to be too short and incomplete, while the <ulink url="http://tldp.org/LDP/abs/html/">Bash Scripting</ulink> guide is too much of a reference work. There is nothing in between these two extremes. I also wrote this guide on the general principal that not enough free basic courses are available, though they should be.</para>
<para>The primary reason for writing this document is that a lot of readers feel the existing <ulink url="http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO.html">HOWTO</ulink> to be too short and incomplete, while the <ulink url="http://tldp.org/LDP/abs/html/">Bash Scripting</ulink> guide is too much of a reference work. There is nothing in between these two extremes. I also wrote this guide on the general principle that not enough free basic courses are available, though they should be.</para>
<para>This is a practical guide which, while not always being too serious, tries to give real-life instead of theoretical examples. I partly wrote it because I don't get excited with stripped down and over-simplified examples written by people who know what they are talking about, showing some really cool Bash feature so much out of its context that you cannot ever use it in practical circumstances. You can read that sort of stuff after finishing this book, which contains exercises and examples that will help you survive in the real world.</para>
<para>From my experience as UNIX/Linux user, system administrator and trainer, I know that people can have years of daily interaction with their systems, without having the slightest knowledge of task automation. Thus they often think that UNIX is not userfriendly, and even worse, they get the impression that it is slow and old-fashioned. This problem is another one that can be remedied by this guide.</para>
<para>From my experience as UNIX/Linux user, system administrator and trainer, I know that people can have years of daily interaction with their systems, without having the slightest knowledge of task automation. Thus they often think that UNIX is not user-friendly, and even worse, they get the impression that it is slow and old-fashioned. This problem is another one that can be remedied by this guide.</para>
</section>

View File

@ -55,7 +55,7 @@
<row><entry>[ <filename>FILE1</filename> <option>-ot</option> <filename>FILE2</filename> ]</entry><entry>True if <filename>FILE1</filename> is older than <filename>FILE2</filename>, or is <filename>FILE2</filename> exists and <filename>FILE1</filename> does not.</entry></row>
<row><entry>[ <filename>FILE1</filename> <option>-ef</option> <filename>FILE2</filename> ]</entry><entry>True if <filename>FILE1</filename> and <filename>FILE2</filename> refer to the same device and inode numbers.</entry></row>
<row><entry>[ <option>-o</option> OPTIONNAME ]</entry><entry>True if shell option <quote>OPTIONNAME</quote> is enabled.</entry></row>
<row><entry><option>[ -z</option> STRING ]</entry><entry>True of the length if <quote>STRING</quote> is zero.</entry></row>
<row><entry><option>[ -z</option> STRING ]</entry><entry>True if the length if <quote>STRING</quote> is zero.</entry></row>
<row><entry><option>[ -n</option> STRING ] or [ STRING ]</entry><entry>True if the length of <quote>STRING</quote> is non-zero.</entry></row>
<row><entry>[ STRING1 == STRING2 ] </entry><entry>True if the strings are equal. <quote>=</quote> may be used instead of <quote>==</quote> for strict POSIX compliance.</entry></row>
<row><entry>[ STRING1 != STRING2 ] </entry><entry>True if the strings are not equal.</entry></row>

View File

@ -0,0 +1,532 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!-- XML file was created by LyX 2.1.4
See http://www.lyx.org/ for more information -->
<article lang="en_US">
<articleinfo>
<title>Package Management Basics: apt, yum, dnf, pkg</title>
</articleinfo><sect1>
<title>Introduction</title>
<sect2>
<title>Why was this document written?</title>
<para>Most modern Unix-like operating systems offer a centralized mechanism for finding and installing software. Software is usually distributed in the form of;packages, kept in;repositories. Working with packages is known as;package management. Packages provide the basic components of an operating system, along with shared libraries, applications, services, and documentation.</para>
<para>A package management system does much more than one-time installation of software. It also provides tools for upgrading already-installed packages. Package repositories help to ensure that code has been vetted for use on your system, and that the installed versions of software have been approved by developers and package maintainers.</para>
<para>When configuring servers or development environments, it's often necessary look beyond official repositories. Packages in the stable release of a distribution may be out of date, especially where new or rapidly-changing software is concerned. Nevertheless, package management is a vital skill for system administrators and developers, and the wealth of packaged software for major distributions is a tremendous resource.</para>
<para>This guide is intended as a quick reference for the fundamentals of finding, installing, and upgrading packages on a variety of distributions, and should help you translate that knowledge between systems.</para></sect2><sect2>
<title>Audience</title>
<para>For those new to Linux who need a basic understanding of package management.</para></sect2><sect2>
<title>Original version of this doc</title>
<para>The original version of this guide can be found at <ulink url="https://www.digitalocean.com/community/tutorials/package-management-basics-apt-yum-dnf-pkg">Digital Ocean</ulink>.</para></sect2><sect2>
<title>Revision History</title>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="center"/>
<colspec colname="col2" align="center"/>
<tbody>
<row>
<entry align="center" valign="top">15.1.2016</entry>
<entry align="center" valign="top">v1.0 converted and edited for TLDP</entry>
<entry align="center" valign="top">Jason Evans</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Contributions</title>
<itemizedlist>
<listitem><para><ulink url="https://www.digitalocean.com/community/users/bpb">Brennen Bearnes</ulink> (original author).</para></listitem><listitem><para><ulink url="http://wiki.tldp.org/Jason%20Evans">Jason Evans</ulink> (editor and maintainer for TLDP)</para></listitem></itemizedlist></sect2><sect2>
<title>Feedback</title>
<para>Missing information, missing links, missing characters? Mail it to the maintainer of this document: <ulink url="mailto://jsevans at youvegotthe.info">jsevans at youvegotthe.info</ulink></para></sect2><sect2>
<title>Copyright information</title>
<para>This work is licensed under a <ulink url="https://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</ulink>.</para></sect2><sect2>
<title>What do you need?</title>
<para>This guide covers Debian, Ubuntu, CentOS, Fedora, and FreeBSD and will require one of those distributions to be installed</para></sect2></sect1><sect1>
<title>Package Management Systems: A Brief Overview</title>
<para>Most package systems are built around collections of package files. A package file is usually an archive which contains compiled binaries and other resources making up the software, along with installation scripts. Packages also contain valuable metadata, including their;dependencies, a list of other packages required to install and run them.</para>
<para>While their functionality and benefits are broadly similar, packaging formats and tools vary by platform:</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">Operating System </entry>
<entry align="left" valign="top">Format </entry>
<entry align="center" valign="top">Tool(s)</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian </entry>
<entry align="left" valign="top">.deb </entry>
<entry align="center" valign="top">apt, apt-cache, apt-get, dpkg</entry>
</row>
<row>
<entry align="center" valign="top">Ubuntu </entry>
<entry align="left" valign="top">.deb </entry>
<entry align="center" valign="top">apt, apt-cache, apt-get, dpkg</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">.rpm </entry>
<entry align="center" valign="top">yum</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">.rpm </entry>
<entry align="center" valign="top">dnf</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD </entry>
<entry align="left" valign="top">Ports,;.txz </entry>
<entry align="center" valign="top">make, pkg</entry>
</row>
</tbody>
</tgroup></informaltable>
<para>In Debian and systems based on it, like Ubuntu, Linux Mint, and Raspbian, the package format is the;.debfile. APT, the Advanced Packaging Tool, provides commands used for most common operations: Searching repositories, installing collections of packages and their dependencies, and managing upgrades. APT commands operate as a front-end to the lower-level;dpkg;utility, which handles the installation of individual;.deb;files on the local system, and is sometimes invoked directly.</para>
<para>CentOS, Fedora, and other members of the Red Hat family use RPM files. In CentOS,;yum;is used to interact with both individual package files and repositories.</para>
<para>In recent versions of Fedora,;yum;has been supplanted by;dnf, a modernized fork which retains most ofyum's interface.</para>
<para>FreeBSD's binary package system is administered with the;pkg;command. FreeBSD also offers the Ports Collection, a local directory structure and tools which allow the user to fetch, compile, and install packages directly from source using Makefiles. It's usually much more convenient to use;pkg, but occasionally a pre-compiled package is unavailable, or you may need to change compile-time options.</para><sect2>
<title>Update Package Lists</title>
<para>Most systems keep a local database of the packages available from remote repositories. It's best to update this database before installing or upgrading packages. As a partial exception to this pattern,;yumand;dnf;will check for updates before performing some operations, but you can ask them at any time whether updates are available.</para>
<informaltable><tgroup cols="2" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="center" valign="top">Command</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="center" valign="top">sudo apt-get update</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="center" valign="top">yum check-update</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="center" valign="top">dnf check-update</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="center" valign="top">sudo pkg update</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="center" valign="top">sudo portsnap fetch update</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Upgrade Installed Packages</title>
<para>Making sure that all of the installed software on a machine stays up to date would be an enormous undertaking without a package system. You would have to track upstream changes and security alerts for hundreds of different packages. While a package manager doesn't solve every problem you'll encounter when upgrading software, it does enable you to maintain most system components with a few commands.</para>
<para>On FreeBSD, upgrading installed ports can introduce breaking changes or require manual configuration steps. It's best to read;/usr/ports/UPDATING;before upgrading with;portmaster.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo apt-get upgrade </entry>
<entry align="center" valign="top">Only upgrades installed packages, where possible.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get dist-upgrade </entry>
<entry align="center" valign="top">May add or remove packages to satisfy new dependencies.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum update </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf upgrade </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg upgrade </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">less /usr/ports/UPDATING </entry>
<entry align="center" valign="top">Uses;less;to view update notes for ports (use arrow keys to scroll, pressq;to quit).</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">cd /usr/ports/ports-mgmt/portmaster &amp;&amp; sudo make install &amp;&amp; sudo portmaster -a </entry>
<entry align="center" valign="top">Installs;portmaster;and uses it to update installed ports.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Find a Package</title>
<para>Most distributions offer a graphical or menu-driven front end to package collections. These can be a good way to browse by category and discover new software. Often, however, the quickest and most effective way to locate a package is to search with command-line tools.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">apt-cache search;search_string </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">yum search;search_string </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">yum search all;search_string </entry>
<entry align="center" valign="top">Searches all fields, including description.</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">dnf search;search_string </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">dnf search all;search_string </entry>
<entry align="center" valign="top">Searches all fields, including description.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">pkg search;search_string </entry>
<entry align="center" valign="top">Searches by name.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">pkg search -f;search_string </entry>
<entry align="center" valign="top">Searches by name, returning full descriptions.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">pkg search -D;search_string </entry>
<entry align="center" valign="top">Searches description.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">cd /usr/ports &amp;&amp; make search name=package </entry>
<entry align="center" valign="top">Searches by name.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">cd /usr/ports &amp;&amp; make search key=search_string </entry>
<entry align="center" valign="top">Searches comments, descriptions, and dependencies.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>View Info About a Specific Package</title>
<para>When deciding what to install, it's often helpful to read detailed descriptions of packages. Along with human-readable text, these often include metadata like version numbers and a list of the package's dependencies.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">apt-cache show;package </entry>
<entry align="center" valign="top">Shows locally-cached info about a package.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">dpkg -s;package </entry>
<entry align="center" valign="top">Shows the current installed status of a package.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">yum info;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">yum deplist;package </entry>
<entry align="center" valign="top">Lists dependencies for a package.</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">dnf info;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">dnf repoquery -\/-requires;package </entry>
<entry align="center" valign="top">Lists dependencies for a package.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">pkg info;package </entry>
<entry align="center" valign="top">Shows info for an installed package.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">cd /usr/ports/category/port;&amp;&amp; cat pkg-descr </entry>
<entry align="center" valign="top"></entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Install a Package from Repositories</title>
<para>Once you know the name of a package, you can usually install it and its dependencies with a single command. In general, you can supply multiple packages to install simply by listing them all.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo apt-get install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get install -y;package </entry>
<entry align="center" valign="top">Assumes "yes" where;apt;would usually prompt to continue.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo yum install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo yum install -y;package </entry>
<entry align="center" valign="top">Assumes "yes" where;yum;would usually prompt to continue.</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo dnf install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo dnf install -y;package </entry>
<entry align="center" valign="top">Assumes "yes" where;dnf;would usually prompt to continue.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo pkg install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">cd /usr/ports/category/port;&amp;&amp; sudo make install </entry>
<entry align="center" valign="top">Builds and installs a port from source.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Install a Package from the Local Filesystem</title>
<para>Sometimes, even though software isn't officially packaged for a given operating system, a developer or vendor will offer package files for download. You can usually retrieve these with your web browser, or viacurl;on the command line. Once a package is on the target system, it can often be installed with a single command.</para>
<para>On Debian-derived systems,;dpkg;handles individual package files. If a package has unmet dependencies,;gdebi;can often be used to retrieve them from official repositories.</para>
<para>On CentOS and Fedora systems,;yum;and;dnf;are used to install individual files, and will also handle needed dependencies.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo dpkg -i;package.deb </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get install -ygdebi &amp;&amp; sudo gdebipackage.deb </entry>
<entry align="center" valign="top">Installs and uses gdebi to install package.deb and retrieve any missing dependencies.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum install;package.rpm </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf install;package.rpm </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg add;package.txz </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo pkg add -f;package.txz </entry>
<entry align="center" valign="top">Installs package even if already installed.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Remove One or More Installed Packages</title>
<para>Since a package manager knows what files are provided by a given package, it can usually remove them cleanly from a system if the software is no longer needed.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo apt-get remove;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get autoremove </entry>
<entry align="center" valign="top">Removes unneeded packages.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum remove;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf erase;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg delete;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo pkg autoremove </entry>
<entry align="center" valign="top">Removes unneeded packages.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">sudo pkg delete;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">cd /usr/ports/path_to_port;&amp;&amp; make deinstall </entry>
<entry align="center" valign="top">De-installs an installed port.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Get Help</title>
<para>In addition to web-based documentation, keep in mind that Unix manual pages (usually referred to as;man pages) are available for most commands from the shell. To read a page, use man:</para><screen>
<![CDATA[$ man page
]]></screen><para>In man, you can navigate with the arrow keys. Press / to search for text within the page, and q to quit.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">man apt-get </entry>
<entry align="center" valign="top">Updating the local package database and working with packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">man apt-cache </entry>
<entry align="center" valign="top">Querying the local package database.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">man dpkg </entry>
<entry align="center" valign="top">Working with individual package files and querying installed packages.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">man yum </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">man dnf </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">man pkg </entry>
<entry align="center" valign="top">Working with pre-compiled binary packages.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">man ports </entry>
<entry align="center" valign="top">Working with the Ports Collection.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2></sect1><sect1>
<title>Conclusion and Further Reading</title>
<para>This guide provides an overview of basic operations that can be cross-referenced between systems, but only scratches the surface of a complex topic. For greater detail on a given system, you can consult the following resources:</para><orderedlist>
<listitem><para><ulink url="https://www.digitalocean.com/community/tutorials/ubuntu-and-debian-package-management-essentials">This guide</ulink> covers Ubuntu and Debian package management in detail. </para></listitem><listitem><para>There's an <ulink url="https://www.centos.org/docs/5/html/yum/">official CentOS guide to managing software with~</ulink><ulink url="https://www.centos.org/docs/5/html/yum/">yum</ulink>. </para></listitem><listitem><para>There's a <ulink url="https://fedoraproject.org/wiki/Dnf">Fedora wiki page about~</ulink><ulink url="https://fedoraproject.org/wiki/Dnf">dnf</ulink>, and an <ulink url="https://dnf.readthedocs.org/en/latest/index.html">official manual for~</ulink><ulink url="https://dnf.readthedocs.org/en/latest/index.html">dnf</ulink><ulink url="https://dnf.readthedocs.org/en/latest/index.html">~itself</ulink>. </para></listitem><listitem><para><ulink url="https://www.digitalocean.com/community/tutorials/how-to-manage-packages-on-freebsd-10-1-with-pkg">This guide</ulink> covers FreeBSD package management using pkg. </para></listitem><listitem><para>The <ulink url="https://www.freebsd.org/doc/handbook/">FreeBSD Handbook</ulink>;contains a;<ulink url="https://www.freebsd.org/doc/handbook/ports-using.html">section on using the Ports Collection</ulink>. </para></listitem></orderedlist></sect1></article>

View File

@ -157,7 +157,7 @@ All about redirection
<sect1>
Sample: stdout 2 stderr
<p> This will cause the stdout ouput of a program to be written to the same filedescriptor
than stderr.
as stderr.
<tscreen><verb>
grep da * 1>&2
</verb></tscreen>
@ -167,7 +167,7 @@ All about redirection
<sect1>
Sample: stderr 2 stdout
<p> This will cause the stderr ouput of a program to be written to the same filedescriptor
than stdout.
as stdout.
<tscreen><verb>
grep * 2>&1
</verb></tscreen>

View File

@ -0,0 +1,309 @@
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass docbook
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
About this document
\end_layout
\begin_layout Subsection
Copyright and License
\end_layout
\begin_layout Standard
This work is licensed under the
\begin_inset CommandInset href
LatexCommand href
name "Creative Commons Attribution-ShareAlike 4.0 International License"
target "http://creativecommons.org/licenses/by-sa/4.0/"
\end_inset
\end_layout
\begin_layout Subsection
Revision History
\end_layout
\begin_layout Standard
\begin_inset Tabular
<lyxtabular version="3" rows="1" columns="3">
<features rotate="0" tabularvalignment="middle">
<column alignment="center" valignment="top">
<column alignment="center" valignment="top">
<column alignment="center" valignment="top">
<row>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
17.1.2016
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
v1.0 First draft written
\end_layout
\end_inset
</cell>
<cell alignment="center" valignment="top" topline="true" bottomline="true" leftline="true" rightline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
Jason Evans
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Subsection
Contributions
\end_layout
\begin_layout Itemize
\begin_inset CommandInset href
LatexCommand href
name "Jason Evans"
target "http://wiki.tldp.org/Jason%20Evans"
\end_inset
(Original author and maintainer for TLDP)
\end_layout
\begin_layout Subsection
Feedback
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "feedback"
\end_inset
\end_layout
\begin_layout Standard
Find something wrong with this document? (Or perhaps something right?) I
would love to hear from you.
Please email me at
\begin_inset CommandInset href
LatexCommand href
name "jsevans_at_youvegotthe.info"
target "jsevans_at_youvegotthe.info"
type "mailto:"
\end_inset
.
\end_layout
\begin_layout Section
About My Topic
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "about"
\end_inset
\end_layout
\begin_layout Standard
In the past, The Linux Documentation Project used CVS as a version control
system, however a few years ago it was moved to GitHub but there was no
accompanying documentation for adding new material to TLDP
\end_layout
\begin_layout Section
Basic Terminology and Commands
\end_layout
\begin_layout Standard
Push
\end_layout
\begin_layout Standard
Pull
\end_layout
\begin_layout Standard
Commit
\end_layout
\begin_layout Standard
Branch
\end_layout
\begin_layout Standard
Repository
\end_layout
\begin_layout Standard
Fork
\end_layout
\begin_layout Standard
Clone
\end_layout
\begin_layout Standard
Diff
\end_layout
\begin_layout Standard
Fetch
\end_layout
\begin_layout Section
What is Git and GutHub?
\end_layout
\begin_layout Subsection
What is Git?
\end_layout
\begin_layout Subsection
What does GitHub do?
\end_layout
\begin_layout Section
Installing Git
\end_layout
\begin_layout Subsection
From Ubuntu or Debian
\end_layout
\begin_layout Code
$ sudo apt-get install git
\end_layout
\begin_layout Subsection
From Fedora, CentOS, or RHEL
\end_layout
\begin_layout Code
$ sudo yum install git
\end_layout
\begin_layout Subsection
From Fedora 23 or later
\end_layout
\begin_layout Code
$ sudo dnf install git
\end_layout
\begin_layout Subsection
From OpenSuSE or SLES
\end_layout
\begin_layout Code
$ sudo zypper install git
\end_layout
\begin_layout Section
Finding TLDP on GitHub
\end_layout
\begin_layout Standard
TLDP's main GitHub url is
\begin_inset CommandInset href
LatexCommand href
target "https://github.com/tLDP/LDP"
\end_inset
.
Anyone can download the documents in TLDP anonymously, but an acount on
github.com is required to upload
\end_layout
\end_body
\end_document

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,532 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!-- XML file was created by LyX 2.1.4
See http://www.lyx.org/ for more information -->
<article lang="en_US">
<articleinfo>
<title>Package Management Basics: apt, yum, dnf, pkg</title>
</articleinfo><sect1>
<title>Introduction</title>
<sect2>
<title>Why was this document written?</title>
<para>Most modern Unix-like operating systems offer a centralized mechanism for finding and installing software. Software is usually distributed in the form of;packages, kept in;repositories. Working with packages is known as;package management. Packages provide the basic components of an operating system, along with shared libraries, applications, services, and documentation.</para>
<para>A package management system does much more than one-time installation of software. It also provides tools for upgrading already-installed packages. Package repositories help to ensure that code has been vetted for use on your system, and that the installed versions of software have been approved by developers and package maintainers.</para>
<para>When configuring servers or development environments, it's often necessary look beyond official repositories. Packages in the stable release of a distribution may be out of date, especially where new or rapidly-changing software is concerned. Nevertheless, package management is a vital skill for system administrators and developers, and the wealth of packaged software for major distributions is a tremendous resource.</para>
<para>This guide is intended as a quick reference for the fundamentals of finding, installing, and upgrading packages on a variety of distributions, and should help you translate that knowledge between systems.</para></sect2><sect2>
<title>Audience</title>
<para>For those new to Linux who need a basic understanding of package management.</para></sect2><sect2>
<title>Original version of this doc</title>
<para>The original version of this guide can be found at <ulink url="https://www.digitalocean.com/community/tutorials/package-management-basics-apt-yum-dnf-pkg">Digital Ocean</ulink>.</para></sect2><sect2>
<title>Revision History</title>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="center"/>
<colspec colname="col2" align="center"/>
<tbody>
<row>
<entry align="center" valign="top">15.1.2016</entry>
<entry align="center" valign="top">v1.0 converted and edited for TLDP</entry>
<entry align="center" valign="top">Jason Evans</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Contributions</title>
<itemizedlist>
<listitem><para><ulink url="https://www.digitalocean.com/community/users/bpb">Brennen Bearnes</ulink> (original author).</para></listitem><listitem><para><ulink url="http://wiki.tldp.org/Jason%20Evans">Jason Evans</ulink> (editor and maintainer for TLDP)</para></listitem></itemizedlist></sect2><sect2>
<title>Feedback</title>
<para>Missing information, missing links, missing characters? Mail it to the maintainer of this document: <ulink url="mailto://jsevans at youvegotthe.info">jsevans at youvegotthe.info</ulink></para></sect2><sect2>
<title>Copyright information</title>
<para>This work is licensed under a <ulink url="https://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</ulink>.</para></sect2><sect2>
<title>What do you need?</title>
<para>This guide covers Debian, Ubuntu, CentOS, Fedora, and FreeBSD and will require one of those distributions to be installed</para></sect2></sect1><sect1>
<title>Package Management Systems: A Brief Overview</title>
<para>Most package systems are built around collections of package files. A package file is usually an archive which contains compiled binaries and other resources making up the software, along with installation scripts. Packages also contain valuable metadata, including their;dependencies, a list of other packages required to install and run them.</para>
<para>While their functionality and benefits are broadly similar, packaging formats and tools vary by platform:</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">Operating System </entry>
<entry align="left" valign="top">Format </entry>
<entry align="center" valign="top">Tool(s)</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian </entry>
<entry align="left" valign="top">.deb </entry>
<entry align="center" valign="top">apt, apt-cache, apt-get, dpkg</entry>
</row>
<row>
<entry align="center" valign="top">Ubuntu </entry>
<entry align="left" valign="top">.deb </entry>
<entry align="center" valign="top">apt, apt-cache, apt-get, dpkg</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">.rpm </entry>
<entry align="center" valign="top">yum</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">.rpm </entry>
<entry align="center" valign="top">dnf</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD </entry>
<entry align="left" valign="top">Ports,;.txz </entry>
<entry align="center" valign="top">make, pkg</entry>
</row>
</tbody>
</tgroup></informaltable>
<para>In Debian and systems based on it, like Ubuntu, Linux Mint, and Raspbian, the package format is the;.debfile. APT, the Advanced Packaging Tool, provides commands used for most common operations: Searching repositories, installing collections of packages and their dependencies, and managing upgrades. APT commands operate as a front-end to the lower-level;dpkg;utility, which handles the installation of individual;.deb;files on the local system, and is sometimes invoked directly.</para>
<para>CentOS, Fedora, and other members of the Red Hat family use RPM files. In CentOS,;yum;is used to interact with both individual package files and repositories.</para>
<para>In recent versions of Fedora,;yum;has been supplanted by;dnf, a modernized fork which retains most ofyum's interface.</para>
<para>FreeBSD's binary package system is administered with the;pkg;command. FreeBSD also offers the Ports Collection, a local directory structure and tools which allow the user to fetch, compile, and install packages directly from source using Makefiles. It's usually much more convenient to use;pkg, but occasionally a pre-compiled package is unavailable, or you may need to change compile-time options.</para><sect2>
<title>Update Package Lists</title>
<para>Most systems keep a local database of the packages available from remote repositories. It's best to update this database before installing or upgrading packages. As a partial exception to this pattern,;yumand;dnf;will check for updates before performing some operations, but you can ask them at any time whether updates are available.</para>
<informaltable><tgroup cols="2" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="center" valign="top">Command</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="center" valign="top">sudo apt-get update</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="center" valign="top">yum check-update</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="center" valign="top">dnf check-update</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="center" valign="top">sudo pkg update</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="center" valign="top">sudo portsnap fetch update</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Upgrade Installed Packages</title>
<para>Making sure that all of the installed software on a machine stays up to date would be an enormous undertaking without a package system. You would have to track upstream changes and security alerts for hundreds of different packages. While a package manager doesn't solve every problem you'll encounter when upgrading software, it does enable you to maintain most system components with a few commands.</para>
<para>On FreeBSD, upgrading installed ports can introduce breaking changes or require manual configuration steps. It's best to read;/usr/ports/UPDATING;before upgrading with;portmaster.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo apt-get upgrade </entry>
<entry align="center" valign="top">Only upgrades installed packages, where possible.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get dist-upgrade </entry>
<entry align="center" valign="top">May add or remove packages to satisfy new dependencies.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum update </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf upgrade </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg upgrade </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">less /usr/ports/UPDATING </entry>
<entry align="center" valign="top">Uses;less;to view update notes for ports (use arrow keys to scroll, pressq;to quit).</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">cd /usr/ports/ports-mgmt/portmaster &amp;&amp; sudo make install &amp;&amp; sudo portmaster -a </entry>
<entry align="center" valign="top">Installs;portmaster;and uses it to update installed ports.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Find a Package</title>
<para>Most distributions offer a graphical or menu-driven front end to package collections. These can be a good way to browse by category and discover new software. Often, however, the quickest and most effective way to locate a package is to search with command-line tools.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">apt-cache search;search_string </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">yum search;search_string </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">yum search all;search_string </entry>
<entry align="center" valign="top">Searches all fields, including description.</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">dnf search;search_string </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">dnf search all;search_string </entry>
<entry align="center" valign="top">Searches all fields, including description.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">pkg search;search_string </entry>
<entry align="center" valign="top">Searches by name.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">pkg search -f;search_string </entry>
<entry align="center" valign="top">Searches by name, returning full descriptions.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">pkg search -D;search_string </entry>
<entry align="center" valign="top">Searches description.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">cd /usr/ports &amp;&amp; make search name=package </entry>
<entry align="center" valign="top">Searches by name.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">cd /usr/ports &amp;&amp; make search key=search_string </entry>
<entry align="center" valign="top">Searches comments, descriptions, and dependencies.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>View Info About a Specific Package</title>
<para>When deciding what to install, it's often helpful to read detailed descriptions of packages. Along with human-readable text, these often include metadata like version numbers and a list of the package's dependencies.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">apt-cache show;package </entry>
<entry align="center" valign="top">Shows locally-cached info about a package.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">dpkg -s;package </entry>
<entry align="center" valign="top">Shows the current installed status of a package.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">yum info;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">yum deplist;package </entry>
<entry align="center" valign="top">Lists dependencies for a package.</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">dnf info;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">dnf repoquery -\/-requires;package </entry>
<entry align="center" valign="top">Lists dependencies for a package.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">pkg info;package </entry>
<entry align="center" valign="top">Shows info for an installed package.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">cd /usr/ports/category/port;&amp;&amp; cat pkg-descr </entry>
<entry align="center" valign="top"></entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Install a Package from Repositories</title>
<para>Once you know the name of a package, you can usually install it and its dependencies with a single command. In general, you can supply multiple packages to install simply by listing them all.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo apt-get install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get install -y;package </entry>
<entry align="center" valign="top">Assumes "yes" where;apt;would usually prompt to continue.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo yum install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo yum install -y;package </entry>
<entry align="center" valign="top">Assumes "yes" where;yum;would usually prompt to continue.</entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo dnf install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo dnf install -y;package </entry>
<entry align="center" valign="top">Assumes "yes" where;dnf;would usually prompt to continue.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg install;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo pkg install;package1 package2 ... </entry>
<entry align="center" valign="top">Installs all listed packages.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">cd /usr/ports/category/port;&amp;&amp; sudo make install </entry>
<entry align="center" valign="top">Builds and installs a port from source.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Install a Package from the Local Filesystem</title>
<para>Sometimes, even though software isn't officially packaged for a given operating system, a developer or vendor will offer package files for download. You can usually retrieve these with your web browser, or viacurl;on the command line. Once a package is on the target system, it can often be installed with a single command.</para>
<para>On Debian-derived systems,;dpkg;handles individual package files. If a package has unmet dependencies,;gdebi;can often be used to retrieve them from official repositories.</para>
<para>On CentOS and Fedora systems,;yum;and;dnf;are used to install individual files, and will also handle needed dependencies.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo dpkg -i;package.deb </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get install -ygdebi &amp;&amp; sudo gdebipackage.deb </entry>
<entry align="center" valign="top">Installs and uses gdebi to install package.deb and retrieve any missing dependencies.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum install;package.rpm </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf install;package.rpm </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg add;package.txz </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo pkg add -f;package.txz </entry>
<entry align="center" valign="top">Installs package even if already installed.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Remove One or More Installed Packages</title>
<para>Since a package manager knows what files are provided by a given package, it can usually remove them cleanly from a system if the software is no longer needed.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">sudo apt-get remove;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo apt-get autoremove </entry>
<entry align="center" valign="top">Removes unneeded packages.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">sudo yum remove;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">sudo dnf erase;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">sudo pkg delete;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">sudo pkg autoremove </entry>
<entry align="center" valign="top">Removes unneeded packages.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">sudo pkg delete;package </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">cd /usr/ports/path_to_port;&amp;&amp; make deinstall </entry>
<entry align="center" valign="top">De-installs an installed port.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2><sect2>
<title>Get Help</title>
<para>In addition to web-based documentation, keep in mind that Unix manual pages (usually referred to as;man pages) are available for most commands from the shell. To read a page, use man:</para><screen>
<![CDATA[$ man page
]]></screen><para>In man, you can navigate with the arrow keys. Press / to search for text within the page, and q to quit.</para>
<informaltable><tgroup cols="3" colsep="1" rowsep="1">
<colspec colname="col0" align="center"/>
<colspec colname="col1" align="left"/>
<colspec colname="col2" align="center"/>
<thead>
<row>
<entry align="center" valign="top">System </entry>
<entry align="left" valign="top">Command </entry>
<entry align="center" valign="top">Notes</entry>
</row>
</thead>
<tbody>
<row>
<entry align="center" valign="top">Debian / Ubuntu </entry>
<entry align="left" valign="top">man apt-get </entry>
<entry align="center" valign="top">Updating the local package database and working with packages.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">man apt-cache </entry>
<entry align="center" valign="top">Querying the local package database.</entry>
</row>
<row>
<entry align="center" valign="top"></entry>
<entry align="left" valign="top">man dpkg </entry>
<entry align="center" valign="top">Working with individual package files and querying installed packages.</entry>
</row>
<row>
<entry align="center" valign="top">CentOS </entry>
<entry align="left" valign="top">man yum </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">Fedora </entry>
<entry align="left" valign="top">man dnf </entry>
<entry align="center" valign="top"></entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Packages </entry>
<entry align="left" valign="top">man pkg </entry>
<entry align="center" valign="top">Working with pre-compiled binary packages.</entry>
</row>
<row>
<entry align="center" valign="top">FreeBSD Ports </entry>
<entry align="left" valign="top">man ports </entry>
<entry align="center" valign="top">Working with the Ports Collection.</entry>
</row>
</tbody>
</tgroup></informaltable></sect2></sect1><sect1>
<title>Conclusion and Further Reading</title>
<para>This guide provides an overview of basic operations that can be cross-referenced between systems, but only scratches the surface of a complex topic. For greater detail on a given system, you can consult the following resources:</para><orderedlist>
<listitem><para><ulink url="https://www.digitalocean.com/community/tutorials/ubuntu-and-debian-package-management-essentials">This guide</ulink> covers Ubuntu and Debian package management in detail. </para></listitem><listitem><para>There's an <ulink url="https://www.centos.org/docs/5/html/yum/">official CentOS guide to managing software with~</ulink><ulink url="https://www.centos.org/docs/5/html/yum/">yum</ulink>. </para></listitem><listitem><para>There's a <ulink url="https://fedoraproject.org/wiki/Dnf">Fedora wiki page about~</ulink><ulink url="https://fedoraproject.org/wiki/Dnf">dnf</ulink>, and an <ulink url="https://dnf.readthedocs.org/en/latest/index.html">official manual for~</ulink><ulink url="https://dnf.readthedocs.org/en/latest/index.html">dnf</ulink><ulink url="https://dnf.readthedocs.org/en/latest/index.html">~itself</ulink>. </para></listitem><listitem><para><ulink url="https://www.digitalocean.com/community/tutorials/how-to-manage-packages-on-freebsd-10-1-with-pkg">This guide</ulink> covers FreeBSD package management using pkg. </para></listitem><listitem><para>The <ulink url="https://www.freebsd.org/doc/handbook/">FreeBSD Handbook</ulink>;contains a;<ulink url="https://www.freebsd.org/doc/handbook/ports-using.html">section on using the Ports Collection</ulink>. </para></listitem></orderedlist></sect1></article>

View File

@ -0,0 +1,6 @@
The Linux Documentation Project :: FAQ DocBook Template
-------------------------------------------------------
The following document is provided as a template for your own FAQ.
We hope you found it useful.
Please send suggestions to: feedback@tldp.org.

View File

@ -0,0 +1,137 @@
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Standard
\series bold
Q:
\series default
question 1
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 1
\end_layout
\begin_layout Standard
\series bold
Q:
\series default
question 2
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 2
\end_layout
\begin_layout Standard
\series bold
Q:
\series default
question 3
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 3
\end_layout
\begin_layout Standard
\series bold
Q:
\series default
question 4
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 4
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,81 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<article class="faq">
<articleinfo>
<title>XXX FAQ</title>
<author>
<firstname>your first name</firstname>
<surname>your last name</surname>
<affiliation>
<address>
<email>you@your.domain</email>
</address>
</affiliation>
</author>
<pubdate>date of first publication</pubdate>
<revhistory>
<revision>
<revnumber>number</revnumber>
<date>date</date>
<authorinitials>initials</authorinitials>
<revremark>updates</revremark>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>release date</date>
<authorinitials>your initials</authorinitials>
<revremark>First release for TLDP</revremark>
</revision>
</revhistory>
<legalnotice id="legalnotice">
<blockquote>
<para>Copyright YYYY your full name. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <ulink url="http://www.opencontent.org/openpub/"></ulink>).</para>
</blockquote>
</legalnotice>
<abstract>
<para>scope of the faq</para>
</abstract>
</articleinfo>
<qandaset defaultlabel="qanda">
<qandaentry>
<question>
<para>question 1</para>
</question>
<answer>
<para>answer 1</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>question 2</para>
</question>
<answer>
<para>answer 2</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>question 3</para>
</question>
<answer>
<para>answer 3</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>question 4</para>
</question>
<answer>
<para>answer 4</para>
</answer>
</qandaentry>
</qandaset>
</article>

View File

@ -0,0 +1,137 @@
#LyX file created by tex2lyx 2.1
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Standard
\series bold
Q:
\series default
question 1
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 1
\end_layout
\begin_layout Standard
\series bold
Q:
\series default
question 2
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 2
\end_layout
\begin_layout Standard
\series bold
Q:
\series default
question 3
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 3
\end_layout
\begin_layout Standard
\series bold
Q:
\series default
question 4
\end_layout
\begin_layout Standard
\series bold
A:
\series default
answer 4
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,15 @@
\textbf{Q:} question 1
\textbf{A:} answer 1
\textbf{Q:} question 2
\textbf{A:} answer 2
\textbf{Q:} question 3
\textbf{A:} answer 3
\textbf{Q:} question 4
\textbf{A:} answer 4

View File

@ -0,0 +1,79 @@
XXX FAQ
\begin{verbatim}
<author>
<firstname>your first name</firstname>
<surname>your last name</surname>
<affiliation>
<address>
\end{verbatim}
you@your.domain
\begin{verbatim}
</affiliation>
</author>
<pubdate>date of first publication</pubdate>
<revhistory>
<revision>
<revnumber>number</revnumber>
<date>date</date>
<authorinitials>initials</authorinitials>
<revremark>updates</revremark>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>release date</date>
<authorinitials>your initials</authorinitials>
<revremark>First release for TLDP</revremark>
</revision>
</revhistory>
<legalnotice id="legalnotice">
<blockquote>
<para>Copyright YYYY your full name. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at <ulink url="http://www.opencontent.org/openpub/"></ulink>).</para>
</blockquote>
</legalnotice>
<abstract>
<para>scope of the faq</para>
</abstract>
\end{verbatim}
\begin{verbatim}
<qandaentry>
<question>
<para>question 1</para>
</question>
<answer>
<para>answer 1</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>question 2</para>
</question>
<answer>
<para>answer 2</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>question 3</para>
</question>
<answer>
<para>answer 3</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>question 4</para>
</question>
<answer>
<para>answer 4</para>
</answer>
</qandaentry>
\end{verbatim}

View File

@ -0,0 +1,39 @@
The Linux Documentation Project :: Guide Template
-------------------------------------------------
The following documents are provided as templates for your own Guide
(book-length document). You are not required to use all of the templates
provided in this package for your document. They are only a suggestion of
what you might need based on the many documents we have reviewed and
accepted in our collection over the years. We hope you find them useful.
These files are all in DocBook XML version 4.2. If you would prefer to use
LinuxDoc, please download the LinuxDoc templates. If you are writing your
document in a different format, please follow the instructions in the
Author Guide on how to transform your document into DocBook before
submitting it to the collection.
http://www.tldp.org/LDP/LDP-Author-Guide/html/x2docbook.html
Please send suggestions to: feedback@tldp.org.
ldp-appendix.xml
A sample appendix. Typically used for the full text of your document's
license and additional instructions that are not part of the "core" of
your document.
ldp-bibliography.xml
A sample bibliography with sections.
ldp-glossary.xml
A sample glossary.
ldp-guide-chap1.xml and ldp-guide-chap2.xml
Two sample chapters with common DocBook markup.
ldp-guide-main.xml
The main file that refers to each of the additional XML files. When the
file is transformed from XML to another format, this file is the master
outline that informs the processing tool where each of the components
are.
If you are writing a shorter HOWTO, please use the ldp-howto.zip package
instead.

View File

@ -0,0 +1,33 @@
<appendix id="app1">
<title>Appendix one title</title>
<abstract>
<para>Says what this appendix is about, for instance further info on the web.</para>
</abstract>
<sect1>
<title>further info</title>
<sect2><title>about this subject</title>
<itemizedlist>
<listitem><para><ulink url="http://useful.org" />: about this and that.</para></listitem>
<listitem><para><ulink url="http://related.org" />: about other related stuff.</para></listitem>
<listitem><para><ulink url="http://other.org" />: more stuff.</para></listitem>
</itemizedlist>
</sect2>
<sect2><title>about other subject</title>
<itemizedlist>
<listitem><para><ulink url="http://useful2.org" />: about this and that.</para></listitem>
<listitem><para><ulink url="http://related2.org" />: about other related stuff.</para></listitem>
<listitem><para><ulink url="http://other2.org" />: more stuff.</para></listitem> </itemizedlist>
</sect2>
</sect1>
</appendix>

View File

@ -0,0 +1,176 @@
#LyX file created by tex2lyx 2.1
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Appendix one title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "app1"
\end_inset
\end_layout
\begin_layout Quote
Says what this appendix is about, for instance further info on the web.
\end_layout
\begin_layout Section
further info
\end_layout
\begin_layout Subsection
about this subject
\end_layout
\begin_layout Itemize
\begin_inset CommandInset href
LatexCommand href
name ""
target "http://useful.org"
\end_inset
: about this and that.
\end_layout
\begin_layout Itemize
\begin_inset CommandInset href
LatexCommand href
name ""
target "http://related.org"
\end_inset
: about other related stuff.
\end_layout
\begin_layout Itemize
\begin_inset CommandInset href
LatexCommand href
name ""
target "http://other.org"
\end_inset
: more stuff.
\end_layout
\begin_layout Subsection
about other subject
\end_layout
\begin_layout Itemize
\begin_inset CommandInset href
LatexCommand href
name ""
target "http://useful2.org"
\end_inset
: about this and that.
\end_layout
\begin_layout Itemize
\begin_inset CommandInset href
LatexCommand href
name ""
target "http://related2.org"
\end_inset
: about other related stuff.
\end_layout
\begin_layout Itemize
\begin_inset CommandInset href
LatexCommand href
name ""
target "http://other2.org"
\end_inset
: more stuff.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,29 @@
\section{Appendix one title}\label{app1}
\begin{quote}
Says what this appendix is about, for instance further info on the web.
\end{quote}
\section{further info}
\subsection{about this subject}
\begin{itemize}
\item
\href{http://useful.org}{}: about this and that.
\item
\href{http://related.org}{}: about other related stuff.
\item
\href{http://other.org}{}: more stuff.
\end{itemize}
\subsection{about other subject}
\begin{itemize}
\item
\href{http://useful2.org}{}: about this and that.
\item
\href{http://related2.org}{}: about other related stuff.
\item
\href{http://other2.org}{}: more stuff.
\end{itemize}

View File

@ -0,0 +1,21 @@
Appendix one title
Says what this appendix is about, for instance further info on the web.
further info
about this subject
: about this and that.
: about other related stuff.
: more stuff.
about other subject
: about this and that.
: about other related stuff.
: more stuff.

View File

@ -0,0 +1,216 @@
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
References and Resources
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "bibliography"
\end_inset
\end_layout
\begin_layout Section
HOWTOs
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "ref-howto"
\end_inset
\end_layout
\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
target "URL"
\end_inset
\end_layout
\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
target "URL 2"
\end_inset
\end_layout
\begin_layout Section
Hardware-specific Install Reports and Info
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "ref-installreports"
\end_inset
\end_layout
\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
target "URL 3"
\end_inset
\end_layout
\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
target "URL 4"
\end_inset
\end_layout
\begin_layout Section
Mailing List Threads
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "ref-mailinglist"
\end_inset
\end_layout
\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
target "URL 5"
\end_inset
\end_layout
\begin_layout Section
Packages and related software
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "ref-software"
\end_inset
\end_layout
\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
target "http://www.kernel.org"
\end_inset
\end_layout
\begin_layout Quote
Remember to choose
\begin_inset Quotes eld
\end_inset
F
\begin_inset Quotes erd
\end_inset
for full when you download your kernel source.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,68 @@
<bibliography id="bibliography">
<?dbhtml filename="bibliography.html"?>
<title>References and Resources</title>
<!-- these are just examples...you do not need to use these sections. -->
<!-- A full bibliography entry would use the following template. -->
<!--
<biblioentry>
<title>
</title>
<bibliosource><ulink url="" /></bibliosource>
<author><firstname></firstname><surname></surname></author>
<copyright><year></year>
<holder></holder></copyright>
<editor><firstname></firstname><surname></surname></editor>
<isbn></isbn>
<publisher>
<publishername></publishername>
</publisher>
</biblioentry>
-->
<bibliodiv id="ref-howto" xreflabel="HOWTOs">
<title>HOWTOs</title>
<biblioentry>
<title>Document Title</title>
<bibliosource><ulink url="URL" /></bibliosource>
</biblioentry>
<biblioentry>
<title>Document Title 2</title>
<bibliosource><ulink url="URL 2" /></bibliosource>
</biblioentry>
</bibliodiv>
<bibliodiv id="ref-installreports" xreflabel="Hardware-specific Install Reports and Info">
<title>Hardware-specific Install Reports and Info</title>
<biblioentry>
<title>Installation Reports</title>
<bibliosource><ulink url="URL 3"/></bibliosource>
</biblioentry>
<biblioentry>
<title>Blacklist</title>
<bibliosource><ulink url="URL 4"/></bibliosource>
</biblioentry>
</bibliodiv>
<bibliodiv id="ref-mailinglist" xreflabel="Mailing List Threads">
<title>Mailing List Threads</title>
<biblioentry>
<title>mailing_list_name thread: subject line</title>
<bibliosource><ulink url="URL 5" /></bibliosource>
</biblioentry>
<bibliodiv id="ref-software" xreflabel="Packages and related software">
<title>Packages and related software</title>
<biblioentry>
<title>The Kernel</title>
<bibliosource><ulink url="http://www.kernel.org" /></bibliosource>
<abstract><para>Remember to choose "F" for full when you download your
kernel source.</para></abstract>
</biblioentry>
</bibliodiv>
</bibliography>

View File

@ -0,0 +1,26 @@
\section{References and Resources}\label{bibliography}
\section{HOWTOs}\label{ref-howto}
\href{URL}{}
\href{URL 2}{}
\section{Hardware-specific Install Reports and
Info}\label{ref-installreports}
\href{URL 3}{}
\href{URL 4}{}
\section{Mailing List Threads}\label{ref-mailinglist}
\href{URL 5}{}
\section{Packages and related software}\label{ref-software}
\href{http://www.kernel.org}{}
\begin{quote}
Remember to choose "F" for full when you download your kernel source.
\end{quote}

View File

@ -0,0 +1,49 @@
References and Resources
HOWTOs
\begin{verbatim}
<biblioentry>
<title>Document Title</title>
<bibliosource><ulink url="URL" /></bibliosource>
</biblioentry>
<biblioentry>
<title>Document Title 2</title>
<bibliosource><ulink url="URL 2" /></bibliosource>
</biblioentry>
\end{verbatim}
Hardware-specific Install Reports and Info
\begin{verbatim}
<biblioentry>
<title>Installation Reports</title>
<bibliosource><ulink url="URL 3"/></bibliosource>
</biblioentry>
<biblioentry>
<title>Blacklist</title>
<bibliosource><ulink url="URL 4"/></bibliosource>
</biblioentry>
\end{verbatim}
Mailing List Threads
\begin{verbatim}
<biblioentry>
<title>mailing_list_name thread: subject line</title>
<bibliosource><ulink url="URL 5" /></bibliosource>
</biblioentry>
\end{verbatim}
Packages and related software
\begin{verbatim}
<biblioentry>
<title>The Kernel</title>
<bibliosource><ulink url="http://www.kernel.org" /></bibliosource>
<abstract><para>Remember to choose "F" for full when you download your
kernel source.</para></abstract>
</biblioentry>
\end{verbatim}

View File

@ -0,0 +1,86 @@
<glossary id="glossary"><?dbhtml filename="gloss.html"?>
<title>Glossary</title>
<abstract>
<para>This is a glossary.</para>
</abstract>
<glossdiv><title>A</title>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv><title>B</title>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv><title>C</title>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
</glossdiv>
And so on, for all the letters in the alphabet and all the items you want in the list.
</glossary>

View File

@ -0,0 +1,35 @@
\section{Glossary}\label{glossary}
\begin{quote}
This is a glossary.
\end{quote}
\begin{description}
\item[entryname]
definition
\item[entryname]
definition
\item[entryname]
definition
\end{description}
\begin{description}
\item[entryname]
definition
\item[entryname]
definition
\item[entryname]
definition
\end{description}
\begin{description}
\item[entryname]
definition
\item[entryname]
definition
\item[entryname]
definition
\end{description}
And so on, for all the letters in the alphabet and all the items you
want in the list.

View File

@ -0,0 +1,98 @@
Glossary
This is a glossary.
A
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
B
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
C
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
And so on, for all the letters in the alphabet and all the items you
want in the list.

View File

@ -0,0 +1,248 @@
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Title of first chapter
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "chapux5f01"
\end_inset
\end_layout
\begin_layout Quote
What we will do in this chapter:
\end_layout
\begin_deeper
\begin_layout Itemize
stuff
\end_layout
\begin_layout Itemize
more stuff
\end_layout
\begin_layout Itemize
talk about other stuff
\end_layout
\begin_layout Itemize
play with stuff
\end_layout
\end_deeper
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Standard
Usually some introduction
\end_layout
\begin_layout Standard
on all the aspects of stuff.
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01ux5f02"
\end_inset
\end_layout
\begin_layout Standard
In-depth discussion
\end_layout
\begin_layout Standard
Explain concepts.
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01ux5f03"
\end_inset
\end_layout
\begin_layout Standard
Maybe some examples
\end_layout
\begin_layout Standard
And a hint to the next section of the chapter.
\end_layout
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f02"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f02ux5f01"
\end_inset
\end_layout
\begin_layout Standard
More stuff
\end_layout
\begin_layout Standard
More stuff
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f02ux5f02"
\end_inset
\end_layout
\begin_layout Standard
This is the second subsection of the second section of the first chapter.
\end_layout
\begin_layout Standard
Add as many sections and subsections as you want.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,53 @@
<?xml version='1.0' encoding='ISO-8859-1'?>
<chapter id="chap_01"><title>Title of first chapter</title>
<abstract>
<para>What we will do in this chapter:</para>
<para>
<itemizedlist>
<listitem><para>stuff</para></listitem>
<listitem><para>more stuff</para></listitem>
<listitem><para>talk about other stuff</para></listitem>
<listitem><para>play with stuff</para></listitem>
</itemizedlist>
</para>
</abstract>
<sect1 id="sect_01_01">
<title>Section1 title</title>
<sect2 id="sect_01_01_01"><title>Section2 title</title>
<para>Usually some introduction</para>
<para>on all the aspects of stuff.</para>
</sect2>
<sect2 id="sect_01_01_02"><title>Section2 title</title>
<para>In-depth discussion</para>
<para>Explain concepts.</para>
</sect2>
<sect2 id="sect_01_01_03">
<title>Section2 title</title>
<para>Maybe some examples</para>
<para>And a hint to the next section of the chapter.</para>
</sect2>
</sect1>
<sect1 id="sect_01_02">
<title>Section1 title</title>
<sect2 id="sect_01_02_01">
<title>Section2 title</title>
<para>More stuff</para>
<para>More stuff</para>
</sect2>
<sect2 id="sect_01_02_02">
<title>Section2 title</title>
<para>This is the second subsection of the second section of the first chapter.</para>
<para>Add as many sections and subsections as you want.</para>
</sect2>
</sect1>
</chapter>

View File

@ -0,0 +1,255 @@
#LyX file created by tex2lyx 2.1
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Title of first chapter
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "chapux5f01"
\end_inset
\end_layout
\begin_layout Quote
What we will do in this chapter:
\end_layout
\begin_deeper
\begin_layout Itemize
stuff
\end_layout
\begin_layout Itemize
more stuff
\end_layout
\begin_layout Itemize
talk about other stuff
\end_layout
\begin_layout Itemize
play with stuff
\end_layout
\end_deeper
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Standard
Usually some introduction
\end_layout
\begin_layout Standard
on all the aspects of stuff.
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01ux5f02"
\end_inset
\end_layout
\begin_layout Standard
In-depth discussion
\end_layout
\begin_layout Standard
Explain concepts.
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f01ux5f03"
\end_inset
\end_layout
\begin_layout Standard
Maybe some examples
\end_layout
\begin_layout Standard
And a hint to the next section of the chapter.
\end_layout
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f02"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f02ux5f01"
\end_inset
\end_layout
\begin_layout Standard
More stuff
\end_layout
\begin_layout Standard
More stuff
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f01ux5f02ux5f02"
\end_inset
\end_layout
\begin_layout Standard
This is the second subsection of the second section of the first chapter.
\end_layout
\begin_layout Standard
Add as many sections and subsections as you want.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,51 @@
\section{Title of first chapter}\label{chapux5f01}
\begin{quote}
What we will do in this chapter:
\begin{itemize}
\item
stuff
\item
more stuff
\item
talk about other stuff
\item
play with stuff
\end{itemize}
\end{quote}
\section{Section1 title}\label{sectux5f01ux5f01}
\subsection{Section2 title}\label{sectux5f01ux5f01ux5f01}
Usually some introduction
on all the aspects of stuff.
\subsection{Section2 title}\label{sectux5f01ux5f01ux5f02}
In-depth discussion
Explain concepts.
\subsection{Section2 title}\label{sectux5f01ux5f01ux5f03}
Maybe some examples
And a hint to the next section of the chapter.
\section{Section1 title}\label{sectux5f01ux5f02}
\subsection{Section2 title}\label{sectux5f01ux5f02ux5f01}
More stuff
More stuff
\subsection{Section2 title}\label{sectux5f01ux5f02ux5f02}
This is the second subsection of the second section of the first
chapter.
Add as many sections and subsections as you want.

View File

@ -0,0 +1,48 @@
Title of first chapter
What we will do in this chapter:
stuff
more stuff
talk about other stuff
play with stuff
Section1 title
Section2 title
Usually some introduction
on all the aspects of stuff.
Section2 title
In-depth discussion
Explain concepts.
Section2 title
Maybe some examples
And a hint to the next section of the chapter.
Section1 title
Section2 title
More stuff
More stuff
Section2 title
This is the second subsection of the second section of the first
chapter.
Add as many sections and subsections as you want.

View File

@ -0,0 +1,459 @@
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Title of second chapter
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "chapux5f02"
\end_inset
\end_layout
\begin_layout Quote
What we will do in this chapter:
\end_layout
\begin_deeper
\begin_layout Itemize
stuff
\end_layout
\begin_layout Itemize
more stuff
\end_layout
\begin_layout Itemize
talk about other stuff
\end_layout
\begin_layout Itemize
play with stuff
\end_layout
\end_deeper
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Subsubsection
Section3 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Standard
Intro
\end_layout
\begin_layout Standard
\begin_inset FormulaMacro
\newcommand{\labelenumi}{\arabic{enumi}.}
\end_inset
\end_layout
\begin_layout Enumerate
Summing up a few things
\end_layout
\begin_layout Enumerate
in a list
\end_layout
\begin_layout Enumerate
where items are numbered
\end_layout
\begin_layout Standard
Explanations
\end_layout
\begin_layout Subsubsection
Section3 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Standard
Other explanation
\end_layout
\begin_layout Itemize
Summing up a few things
\end_layout
\begin_layout Itemize
in a list
\end_layout
\begin_layout Itemize
where items are not numbered
\end_layout
\begin_layout Standard
And discussion
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f02"
\end_inset
\end_layout
\begin_layout Standard
Showing a picture in text:
\end_layout
\begin_layout Standard
PNG is for on-line browsing, EPS for printing.
\family typewriter
gimp
\family default
and/or
\family typewriter
convert
\family default
will do the trick, starting from about any source format.
\end_layout
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f02"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f02ux5f01"
\end_inset
\end_layout
\begin_layout Standard
This is a table with two colums:
\end_layout
\begin_layout Standard
\begin_inset Tabular
<lyxtabular version="3" rows="6" columns="2">
<features rotate="0" booktabs="true" islongtable="true" longtabularalignment="center">
<column alignment="none" valignment="top" special="@{}l">
<column alignment="none" valignment="top" special="l@{}">
<row endfirsthead="true" caption="true">
<cell multicolumn="1" alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Table title
\end_layout
\end_inset
\end_layout
\end_inset
</cell>
<cell multicolumn="2" alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\end_layout
\end_inset
</cell>
</row>
<row endfirsthead="true">
<cell alignment="none" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
first colum header
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
second colum header
\end_layout
\end_inset
</cell>
</row>
<row endhead="true">
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
first colum header
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
second colum header
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
item
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
meaning
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
item
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
meaning
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
item
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
meaning
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f02ux5f02"
\end_inset
\end_layout
\begin_layout Standard
This is a link to the first section of the first chapter: ?.
\end_layout
\begin_layout Standard
This is an external link:
\begin_inset CommandInset href
LatexCommand href
target "http://www.somewhere.org"
\end_inset
.
\end_layout
\begin_layout Standard
This is also
\begin_inset CommandInset href
LatexCommand href
name "an external link"
target "http://www.somewhere.org"
\end_inset
, only here you don't see the URL.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,90 @@
<?xml version='1.0' encoding='ISO-8859-1'?>
<chapter id="chap_02"><title>Title of second chapter</title>
<abstract>
<para>What we will do in this chapter:</para>
<para>
<itemizedlist>
<listitem><para>stuff</para></listitem>
<listitem><para>more stuff</para></listitem>
<listitem><para>talk about other stuff</para></listitem>
<listitem><para>play with stuff</para></listitem>
</itemizedlist>
</para>
</abstract>
<sect1 id="sect_02_01">
<title>Section1 title</title>
<sect2 id="sect_02_01_01"><title>Section2 title</title>
<sect3 id="sect_02_01_01_01"><title>Section3 title</title>
<para>Intro</para>
<orderedlist>
<listitem><para>Summing up a few things</para></listitem>
<listitem><para>in a list</para></listitem>
<listitem><para>where items are numbered</para></listitem>
</orderedlist>
<para>Explanations</para>
</sect3>
<sect3 id="sect_02_01_01_01"><title>Section3 title</title>
<para>Other explanation</para>
<itemizedlist>
<listitem><para>Summing up a few things</para></listitem>
<listitem><para>in a list</para></listitem>
<listitem><para>where items are not numbered</para></listitem>
</itemizedlist>
<para>And discussion</para>
</sect3>
</sect2>
<sect2 id="sect_02_01_02"><title>Section2 title</title>
<para>Showing a picture in text:</para>
<figure><title></title>
<mediaobject>
<imageobject>
<imagedata fileref="your_images_dir/image.eps" format="EPS"></imagedata></imageobject>
<imageobject>
<imagedata fileref="your_images_dir/image.png" format="PNG"></imagedata></imageobject>
</mediaobject>
</figure>
<para>PNG is for on-line browsing, EPS for printing. <command>gimp</command> and/or <command>convert</command> will do the trick, starting from about any source format.</para>
</sect2>
</sect1>
<sect1 id="sect_02_02">
<title>Section1 title</title>
<sect2 id="sect_02_02_01">
<title>Section2 title</title>
<para>This is a table with two colums:</para>
<table id="tab_02_01" frame="all"><title>Table title</title>
<tgroup cols="2" align="left" colsep="1" rowsep="1">
<thead>
<row><entry>first colum header</entry><entry>second colum header</entry></row>
</thead>
<tbody>
<row><entry>item</entry><entry>meaning</entry></row>
<row><entry>item</entry><entry>meaning</entry></row>
<row><entry>item</entry><entry>meaning</entry></row>
</tbody>
</tgroup>
</table>
</sect2>
<sect2 id="sect_02_02_02">
<title>Section2 title</title>
<para>This is a link to the first section of the first chapter: <xref linkend="sect_01_01" />.</para>
<para>This is an external link: <ulink url="http://www.somewhere.org" />.</para>
<para>This is also <ulink url="http://www.somewhere.org">an external link</ulink>, only here you don't see the URL.</para>
</sect2>
</sect1>
</chapter>

View File

@ -0,0 +1,459 @@
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Title of second chapter
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "chapux5f02"
\end_inset
\end_layout
\begin_layout Quote
What we will do in this chapter:
\end_layout
\begin_deeper
\begin_layout Itemize
stuff
\end_layout
\begin_layout Itemize
more stuff
\end_layout
\begin_layout Itemize
talk about other stuff
\end_layout
\begin_layout Itemize
play with stuff
\end_layout
\end_deeper
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Subsubsection
Section3 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Standard
Intro
\end_layout
\begin_layout Standard
\begin_inset FormulaMacro
\newcommand{\labelenumi}{\arabic{enumi}.}
\end_inset
\end_layout
\begin_layout Enumerate
Summing up a few things
\end_layout
\begin_layout Enumerate
in a list
\end_layout
\begin_layout Enumerate
where items are numbered
\end_layout
\begin_layout Standard
Explanations
\end_layout
\begin_layout Subsubsection
Section3 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f01ux5f01"
\end_inset
\end_layout
\begin_layout Standard
Other explanation
\end_layout
\begin_layout Itemize
Summing up a few things
\end_layout
\begin_layout Itemize
in a list
\end_layout
\begin_layout Itemize
where items are not numbered
\end_layout
\begin_layout Standard
And discussion
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f01ux5f02"
\end_inset
\end_layout
\begin_layout Standard
Showing a picture in text:
\end_layout
\begin_layout Standard
PNG is for on-line browsing, EPS for printing.
\family typewriter
gimp
\family default
and/or
\family typewriter
convert
\family default
will do the trick, starting from about any source format.
\end_layout
\begin_layout Section
Section1 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f02"
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f02ux5f01"
\end_inset
\end_layout
\begin_layout Standard
This is a table with two colums:
\end_layout
\begin_layout Standard
\begin_inset Tabular
<lyxtabular version="3" rows="6" columns="2">
<features rotate="0" booktabs="true" islongtable="true" longtabularalignment="center">
<column alignment="none" valignment="top" special="@{}l">
<column alignment="none" valignment="top" special="l@{}">
<row endfirsthead="true" caption="true">
<cell multicolumn="1" alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\begin_inset Caption Standard
\begin_layout Plain Layout
Table title
\end_layout
\end_inset
\end_layout
\end_inset
</cell>
<cell multicolumn="2" alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
\end_layout
\end_inset
</cell>
</row>
<row endfirsthead="true">
<cell alignment="none" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
first colum header
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
second colum header
\end_layout
\end_inset
</cell>
</row>
<row endhead="true">
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
first colum header
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
second colum header
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
item
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
meaning
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
item
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
meaning
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
item
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Plain Layout
meaning
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Subsection
Section2 title
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "sectux5f02ux5f02ux5f02"
\end_inset
\end_layout
\begin_layout Standard
This is a link to the first section of the first chapter: ?.
\end_layout
\begin_layout Standard
This is an external link:
\begin_inset CommandInset href
LatexCommand href
target "http://www.somewhere.org"
\end_inset
.
\end_layout
\begin_layout Standard
This is also
\begin_inset CommandInset href
LatexCommand href
name "an external link"
target "http://www.somewhere.org"
\end_inset
, only here you don't see the URL.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,92 @@
\section{Title of second chapter}\label{chapux5f02}
\begin{quote}
What we will do in this chapter:
\begin{itemize}
\item
stuff
\item
more stuff
\item
talk about other stuff
\item
play with stuff
\end{itemize}
\end{quote}
\section{Section1 title}\label{sectux5f02ux5f01}
\subsection{Section2 title}\label{sectux5f02ux5f01ux5f01}
\subsubsection{Section3 title}\label{sectux5f02ux5f01ux5f01ux5f01}
Intro
\begin{enumerate}
\def\labelenumi{\arabic{enumi}.}
\item
Summing up a few things
\item
in a list
\item
where items are numbered
\end{enumerate}
Explanations
\subsubsection{Section3 title}\label{sectux5f02ux5f01ux5f01ux5f01}
Other explanation
\begin{itemize}
\item
Summing up a few things
\item
in a list
\item
where items are not numbered
\end{itemize}
And discussion
\subsection{Section2 title}\label{sectux5f02ux5f01ux5f02}
Showing a picture in text:
\includegraphics{your_images_dir/image.eps}
PNG is for on-line browsing, EPS for printing. \texttt{gimp} and/or
\texttt{convert} will do the trick, starting from about any source
format.
\section{Section1 title}\label{sectux5f02ux5f02}
\subsection{Section2 title}\label{sectux5f02ux5f02ux5f01}
This is a table with two colums:
\begin{longtable}[c]{@{}ll@{}}
\caption{Table title}\tabularnewline
\toprule
first colum header & second colum header\tabularnewline
\midrule
\endfirsthead
\toprule
first colum header & second colum header\tabularnewline
\midrule
\endhead
item & meaning\tabularnewline
item & meaning\tabularnewline
item & meaning\tabularnewline
\bottomrule
\end{longtable}
\subsection{Section2 title}\label{sectux5f02ux5f02ux5f02}
This is a link to the first section of the first chapter: ?.
This is an external link: \href{http://www.somewhere.org}{}.
This is also \href{http://www.somewhere.org}{an external link}, only
here you don't see the URL.

View File

@ -0,0 +1,68 @@
Title of second chapter
What we will do in this chapter:
stuff
more stuff
talk about other stuff
play with stuff
Section1 title
Section2 title
Section3 title
Intro
Summing up a few things
in a list
where items are numbered
Explanations
Section3 title
Other explanation
Summing up a few things
in a list
where items are not numbered
And discussion
Section2 title
Showing a picture in text:
PNG is for on-line browsing, EPS for printing. gimp and/or convert will
do the trick, starting from about any source format.
Section1 title
Section2 title
This is a table with two colums:
Table title
first colum headersecond colum header
itemmeaning itemmeaning itemmeaning
Section2 title
This is a link to the first section of the first chapter: .
This is an external link: .
This is also an external link, only here you don't see the URL.

View File

@ -0,0 +1,253 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY chap1 SYSTEM "ldp-guide-chap1.xml">
<!ENTITY chap2 SYSTEM "ldp-guide-chap2.xml">
<!-- and so on for each of your chapters -->
<!ENTITY app1 SYSTEM "ldp-appendix.xml">
<!ENTITY gloss SYSTEM "ldp-glossary.xml">
]>
<book>
<bookinfo>
<title>Your title</title>
<subtitle>An optional subtitle</subtitle>
<authorgroup>
<author>
<firstname>Your given name</firstname>
<surname>Your last name</surname>
<affiliation>
<orgname>Your organization</orgname>
<address>
<email>you@your.domain</email>
</address>
</affiliation>
</author>
</authorgroup>
<edition>Optional version information</edition>
<keywordset>
<keyword>Add</keyword>
<keyword>as</keyword>
<keyword>many</keyword>
<keyword>keywords</keyword>
<keyword>as</keyword>
<keyword>you</keyword>
<keyword>want</keyword>
<keyword>.</keyword>
</keywordset>
</bookinfo>
<preface>
<title>Introduction</title>
<section id="intro_01">
<title>Why was this document written?</title>
<para>Some explanations.</para>
</section>
<section id="intro_02">
<title>Audience</title>
<para>Explain for whom it has been written.</para>
</section>
<section id="intro_03">
<title>New versions of this doc</title>
<para>Point to <ulink url="http://somewhere.org">the latest version</ulink> of this document.</para>
</section>
<section id="intro_04">
<title>Revision History</title>
<para>
<revhistory>
<revision>
<revnumber>1.2</revnumber>
<date>2003-02-28</date>
<authorinitials>MG</authorinitials>
<revremark>More stuff you changed.</revremark>
</revision>
<revision>
<revnumber>1.1</revnumber>
<date>2003-01-22</date>
<authorinitials>MG</authorinitials>
<revremark>Stuff you changed.</revremark>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>2002-12-29</date>
<authorinitials>MG</authorinitials>
<revremark>Initial release for TLDP</revremark>
</revision>
</revhistory>
</para>
</section>
<section id="intro_05">
<title>Contributions</title>
<para>Thank people who helped realizing this doc.</para>
</section>
<section id="intro_06">
<title>Feedback</title>
<para>
Missing information, missing links, missing characters? Mail it to the
maintainer of this document: <address><email>you@your.domain</email></address>
</para>
</section>
<section id="intro_07">
<title>Copyright information</title>
<para>Copyright 2002 Your_first_name Your_last_name.
</para>
<para> Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or any later
version published by the Free Software Foundation; with no Invariant
Sections, with no Front-Cover Texts and no Back-Cover Texts. A copy of the
license is included in <xref linkend="app4" /> entitled <quote>GNU Free
Documentation License</quote>.
</para>
<para>Read <ulink url="http://www.fsf.org/gnu/manifesto.html">The GNU Manifesto
</ulink> if you want to know why this license was chosen for this book.
</para>
<para>The author and publisher have made every effort in the preparation of this
book to ensure the accuracy of the information. However, the information
contained in this book is offered without warranty, either express or implied.
Neither the author nor the publisher nor any dealer or distributor will be held
liable for any damages caused or alleged to be caused either directly or
indirectly by this book.
</para>
<para>The logos, trademarks and symbols used in this book are the properties of
their respective owners.
</para>
</section>
<section id="intro_08">
<title>What do you need?</title>
<para>List requirements: materials, knowledge.</para>
</section>
<section id="intro_09">
<title>Conventions used in this document</title>
<para>The following typographic and usage conventions occur in this text:
</para>
<table id="conventions" frame="all"><title>Typographic and usage conventions</title>
<tgroup cols="2" align="left" colsep="1" rowsep="1">
<thead>
<row><entry>Text type</entry><entry>Meaning</entry></row>
</thead>
<tbody>
<row>
<entry><quote>Quoted text</quote></entry>
<entry>Quotes from people, quoted computer output.</entry>
</row>
<row>
<entry><screen>terminal view</screen></entry>
<entry>Literal computer input and output captured from the terminal,
usually rendered with a light grey background.</entry>
</row>
<row>
<entry><command>command</command></entry>
<entry>Name of a command that can be entered on the command line.</entry>
</row>
<row>
<entry><varname>VARIABLE</varname></entry>
<entry>Name of a variable or pointer to content of a variable, as in
<varname>$VARNAME</varname>.</entry>
</row>
<row>
<entry><option>option</option></entry>
<entry>Option to a command, as in <quote>the <option>-a</option> option to the
<command>ls</command> command</quote>.</entry>
</row>
<row>
<entry><parameter>argument</parameter></entry>
<entry>Argument to a command, as in <quote>read
<command>man <parameter>ls</parameter></command></quote>.</entry>
</row>
<row>
<entry><cmdsynopsis><command>command <option>options</option>
<parameter>arguments</parameter></command></cmdsynopsis></entry>
<entry>Command synopsis or general usage, on a separated line.</entry>
</row>
<row>
<entry><filename>filename</filename></entry>
<entry>Name of a file or directory, for example <quote>Change to the
<filename>/usr/bin</filename> directory.</quote></entry>
</row>
<row>
<entry><keycap>Key</keycap></entry>
<entry>Keys to hit on the keyboard, such as <quote>type <keycap>Q</keycap>
to quit</quote>.</entry>
</row>
<row>
<entry><guibutton>Button</guibutton></entry>
<entry>Graphical button to click, like the <guibutton>OK</guibutton>
button.</entry>
</row>
<row>
<entry><menuchoice><guimenu>Menu</guimenu><guimenuitem>Choice</guimenuitem>
</menuchoice></entry>
<entry>Choice to select from a graphical menu, for instance: <quote>Select
<menuchoice><guimenu>Help</guimenu><guimenuitem>About Mozilla</guimenuitem>
</menuchoice> in your browser.</quote></entry>
</row>
<row>
<entry><emphasis>Terminology</emphasis></entry>
<entry>Important term or concept: <quote>The Linux <emphasis>kernel</emphasis>
is the heart of the system.</quote></entry>
</row>
<row>
<entry>See <xref linkend="chap_01" /></entry><entry>link to related subject
within this guide.</entry>
</row>
<row>
<entry><ulink url="http://tille.soti.org">The author</ulink></entry>
<entry>Clickable link to an external web resource.</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section id="intro_10">
<title>Organization of this document</title>
<para>List chapters (and optionally, appendices) with a short content for each (only for longer docs).</para>
<itemizedlist>
<listitem><para><xref linkend="chap_01" />: short description.</para></listitem>
<listitem><para><xref linkend="chap_02" />: short description.</para></listitem>
<listitem><para><xref linkend="chap_03" />: short description.</para></listitem>
<listitem><para><xref linkend="chap_04" />: short description.</para></listitem>
<listitem><para><xref linkend="chap_05" />: short description.</para></listitem>
</itemizedlist>
</section>
</preface>
<toc></toc>
&chap1;
&chap2;
&app1;
&gloss;
</book>

View File

@ -0,0 +1,914 @@
#LyX file created by tex2lyx 2.1
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Introduction
\end_layout
\begin_layout Subsection
Why was this document written?
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f01"
\end_inset
\end_layout
\begin_layout Standard
Some explanations.
\end_layout
\begin_layout Subsection
Audience
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f02"
\end_inset
\end_layout
\begin_layout Standard
Explain for whom it has been written.
\end_layout
\begin_layout Subsection
New versions of this doc
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f03"
\end_inset
\end_layout
\begin_layout Standard
Point to
\begin_inset CommandInset href
LatexCommand href
name "the latest version"
target "http://somewhere.org"
\end_inset
of this document.
\end_layout
\begin_layout Subsection
Revision History
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f04"
\end_inset
\end_layout
\begin_layout Standard
1.2 2003-02-28 MG More stuff you changed. 1.1 2003-01-22 MG Stuff you changed. 1.0 2002-12-29 MG Initial release for TLDP
\end_layout
\begin_layout Subsection
Contributions
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f05"
\end_inset
\end_layout
\begin_layout Standard
Thank people who helped realizing this doc.
\end_layout
\begin_layout Subsection
Feedback
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f06"
\end_inset
\end_layout
\begin_layout Standard
Missing information, missing links, missing characters? Mail it to the maintainer of this document:
\begin_inset CommandInset href
LatexCommand href
name "nolinkurl{you@your.domain}"
target "you@your.domain"
type "mailto:"
\end_inset
\end_layout
\begin_layout Subsection
Copyright information
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f07"
\end_inset
\end_layout
\begin_layout Standard
Copyright 2002 Your_first_name Your_last_name.
\end_layout
\begin_layout Standard
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts and no Back-Cover Texts. A copy of the license is included in ? entitled
\begin_inset Quotes eld
\end_inset
GNU Free Documentation License
\begin_inset Quotes erd
\end_inset
.
\end_layout
\begin_layout Standard
Read
\begin_inset CommandInset href
LatexCommand href
name "The GNU Manifesto"
target "http://www.fsf.org/gnu/manifesto.html"
\end_inset
if you want to know why this license was chosen for this book.
\end_layout
\begin_layout Standard
The author and publisher have made every effort in the preparation of this book to ensure the accuracy of the information. However, the information contained in this book is offered without warranty, either express or implied. Neither the author nor the publisher nor any dealer or distributor will be held liable for any damages caused or alleged to be caused either directly or indirectly by this book.
\end_layout
\begin_layout Standard
The logos, trademarks and symbols used in this book are the properties of their respective owners.
\end_layout
\begin_layout Subsection
What do you need?
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f08"
\end_inset
\end_layout
\begin_layout Standard
List requirements: materials, knowledge.
\end_layout
\begin_layout Subsection
Conventions used in this document
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f09"
\end_inset
\end_layout
\begin_layout Standard
The following typographic and usage conventions occur in this text:
\end_layout
\begin_layout Standard
\begin_inset Tabular
<lyxtabular version="3" rows="17" columns="2">
<features rotate="0" booktabs="true" islongtable="true">
<column alignment="none" valignment="top" special="@{}l">
<column alignment="none" valignment="top" special="l@{}">
<row endfirsthead="true" caption="true">
<cell multicolumn="1" alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\begin_inset Caption Standard
\begin_layout Plain Layout
Typographic and usage conventions
\end_layout
\end_inset
\end_layout
\end_inset
</cell>
<cell multicolumn="2" alignment="none" valignment="top" usebox="none">
\begin_inset Text
\end_inset
</cell>
</row>
<row endfirsthead="true">
<cell alignment="none" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
Text type
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
Meaning
\end_layout
\end_inset
</cell>
</row>
<row endhead="true">
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
Text type
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
Meaning
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
\begin_inset Quotes eld
\end_inset
Quoted text
\begin_inset Quotes erd
\end_inset
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" topline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
Quotes from people, quoted computer output.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Verbatim
terminal view
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Literal computer input and output captured from the terminal, usually rendered with a light grey background.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\family typewriter
command
\family default
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Name of a command that can be entered on the command line.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\family typewriter
VARIABLE
\family default
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Name of a variable or pointer to content of a variable, as in
\family typewriter
$VARNAME
\family default
.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\family typewriter
option
\family default
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Option to a command, as in
\begin_inset Quotes eld
\end_inset
the
\family typewriter
-a
\family default
option to the
\family typewriter
ls
\family default
command
\begin_inset Quotes erd
\end_inset
.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\family typewriter
argument
\family default
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Argument to a command, as in
\begin_inset Quotes eld
\end_inset
read
\family typewriter
man
\begin_inset space \space{}
\end_inset
ls
\family default
\begin_inset Quotes erd
\end_inset
.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\family typewriter
command
\begin_inset space \space{}
\end_inset
options
\begin_inset space \space{}
\end_inset
arguments
\family default
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Command synopsis or general usage, on a separated line.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\family typewriter
filename
\family default
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Name of a file or directory, for example
\begin_inset Quotes eld
\end_inset
Change to the
\family typewriter
/usr/bin
\family default
directory.
\begin_inset Quotes erd
\end_inset
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Key
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Keys to hit on the keyboard, such as
\begin_inset Quotes eld
\end_inset
type Q to quit
\begin_inset Quotes erd
\end_inset
.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Button
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Graphical button to click, like the OK button.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
{
\end_layout
\end_inset
Menu
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
\backslash
textgreater
\end_layout
\end_inset
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
{}
\end_layout
\end_inset
Choice
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
}
\end_layout
\end_inset
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Choice to select from a graphical menu, for instance:
\begin_inset Quotes eld
\end_inset
Select
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
{
\end_layout
\end_inset
Help
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
\backslash
textgreater
\end_layout
\end_inset
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
{}
\end_layout
\end_inset
About Mozilla
\begin_inset ERT
status collapsed
\begin_layout Plain Layout
}
\end_layout
\end_inset
in your browser.
\begin_inset Quotes erd
\end_inset
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
\emph on
Terminology
\emph default
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
Important term or concept:
\begin_inset Quotes eld
\end_inset
The Linux
\emph on
kernel
\emph default
is the heart of the system.
\begin_inset Quotes erd
\end_inset
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
See ?
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" usebox="none">
\begin_inset Text
\begin_layout Standard
link to related subject within this guide.
\end_layout
\end_inset
</cell>
</row>
<row>
<cell alignment="none" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
\begin_inset CommandInset href
LatexCommand href
name "The author"
target "http://tille.soti.org"
\end_inset
\end_layout
\end_inset
</cell>
<cell alignment="none" valignment="top" bottomline="true" usebox="none">
\begin_inset Text
\begin_layout Standard
Clickable link to an external web resource.
\end_layout
\end_inset
</cell>
</row>
</lyxtabular>
\end_inset
\end_layout
\begin_layout Subsection
Organization of this document
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "introux5f10"
\end_inset
\end_layout
\begin_layout Standard
List chapters (and optionally, appendices) with a short content for each (only for longer docs).
\end_layout
\begin_layout Itemize
?: short description.
\end_layout
\begin_layout Itemize
?: short description.
\end_layout
\begin_layout Itemize
?: short description.
\end_layout
\begin_layout Itemize
?: short description.
\end_layout
\begin_layout Itemize
?: short description.
\end_layout
\begin_layout Standard
CHAP1 CHAP2 APP1 GLOSS
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,125 @@
\section{Introduction}
\subsection{Why was this document written?}\label{introux5f01}
Some explanations.
\subsection{Audience}\label{introux5f02}
Explain for whom it has been written.
\subsection{New versions of this doc}\label{introux5f03}
Point to \href{http://somewhere.org}{the latest version} of this
document.
\subsection{Revision History}\label{introux5f04}
1.2 2003-02-28 MG More stuff you changed. 1.1 2003-01-22 MG Stuff you
changed. 1.0 2002-12-29 MG Initial release for TLDP
\subsection{Contributions}\label{introux5f05}
Thank people who helped realizing this doc.
\subsection{Feedback}\label{introux5f06}
Missing information, missing links, missing characters? Mail it to the
maintainer of this document:
\href{mailto:you@your.domain}{\nolinkurl{you@your.domain}}
\subsection{Copyright information}\label{introux5f07}
Copyright 2002 Your\_first\_name Your\_last\_name.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with no Front-Cover Texts and no Back-Cover Texts. A
copy of the license is included in ? entitled ``GNU Free Documentation
License''.
Read \href{http://www.fsf.org/gnu/manifesto.html}{The GNU Manifesto} if
you want to know why this license was chosen for this book.
The author and publisher have made every effort in the preparation of
this book to ensure the accuracy of the information. However, the
information contained in this book is offered without warranty, either
express or implied. Neither the author nor the publisher nor any dealer
or distributor will be held liable for any damages caused or alleged to
be caused either directly or indirectly by this book.
The logos, trademarks and symbols used in this book are the properties
of their respective owners.
\subsection{What do you need?}\label{introux5f08}
List requirements: materials, knowledge.
\subsection{Conventions used in this document}\label{introux5f09}
The following typographic and usage conventions occur in this text:
\begin{longtable}[c]{@{}ll@{}}
\caption{Typographic and usage conventions}\tabularnewline
\toprule
Text type & Meaning\tabularnewline
\midrule
\endfirsthead
\toprule
Text type & Meaning\tabularnewline
\midrule
\endhead
``Quoted text'' & Quotes from people, quoted computer
output.\tabularnewline
\begin{verbatim}
terminal view
\end{verbatim}
& Literal computer input and output captured from the terminal, usually
rendered with a light grey background.\tabularnewline
\texttt{command} & Name of a command that can be entered on the command
line.\tabularnewline
\texttt{VARIABLE} & Name of a variable or pointer to content of a
variable, as in \texttt{\$VARNAME}.\tabularnewline
\texttt{option} & Option to a command, as in ``the \texttt{-a} option to
the \texttt{ls} command''.\tabularnewline
\texttt{argument} & Argument to a command, as in ``read
\texttt{man\ ls}''.\tabularnewline
\texttt{command\ options\
arguments} & Command synopsis or general usage, on a separated
line.\tabularnewline
\texttt{filename} & Name of a file or directory, for example ``Change to
the \texttt{/usr/bin} directory.''\tabularnewline
Key & Keys to hit on the keyboard, such as ``type Q to
quit''.\tabularnewline
Button & Graphical button to click, like the OK button.\tabularnewline
{Menu \textgreater{} Choice} & Choice to select from a graphical menu,
for instance: ``Select {Help \textgreater{} About Mozilla} in your
browser.''\tabularnewline
\emph{Terminology} & Important term or concept: ``The Linux
\emph{kernel} is the heart of the system.''\tabularnewline
See ? & link to related subject within this guide.\tabularnewline
\href{http://tille.soti.org}{The author} & Clickable link to an external
web resource.\tabularnewline
\bottomrule
\end{longtable}
\subsection{Organization of this document}\label{introux5f10}
List chapters (and optionally, appendices) with a short content for each
(only for longer docs).
\begin{itemize}
\item
?: short description.
\item
?: short description.
\item
?: short description.
\item
?: short description.
\item
?: short description.
\end{itemize}
CHAP1 CHAP2 APP1 GLOSS

View File

@ -0,0 +1,124 @@
{]}\textgreater{}
Your title
\begin{verbatim}
<subtitle>An optional subtitle</subtitle>
\end{verbatim}
Your given name Your last name Your organization
\begin{verbatim}
<email>you@your.domain</email>
</address>
</affiliation>
\end{verbatim}
Optional version information
Add as many keywords as you want .
Introduction
Why was this document written?
Some explanations.
Audience
Explain for whom it has been written.
New versions of this doc
Point to the latest version of this document.
Revision History
1.2 2003-02-28 MG More stuff you changed. 1.1 2003-01-22 MG Stuff you
changed. 1.0 2002-12-29 MG Initial release for TLDP
Contributions
Thank people who helped realizing this doc.
Feedback
Missing information, missing links, missing characters? Mail it to the
maintainer of this document:
you@your.domain
Copyright information
Copyright 2002 Your\_first\_name Your\_last\_name.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; with no
Invariant Sections, with no Front-Cover Texts and no Back-Cover Texts. A
copy of the license is included in entitled GNU Free Documentation
License.
Read The GNU Manifesto if you want to know why this license was chosen
for this book.
The author and publisher have made every effort in the preparation of
this book to ensure the accuracy of the information. However, the
information contained in this book is offered without warranty, either
express or implied. Neither the author nor the publisher nor any dealer
or distributor will be held liable for any damages caused or alleged to
be caused either directly or indirectly by this book.
The logos, trademarks and symbols used in this book are the properties
of their respective owners.
What do you need?
List requirements: materials, knowledge.
Conventions used in this document
The following typographic and usage conventions occur in this text:
Typographic and usage conventions
Text typeMeaning
Quoted text Quotes from people, quoted computer output.
terminal view
Literal computer input and output captured from the terminal, usually
rendered with a light grey background. command Name of a command that
can be entered on the command line. VARIABLE Name of a variable or
pointer to content of a variable, as in \$VARNAME. option Option to a
command, as in the -a option to the ls command. argument Argument to a
command, as in read man ls.
command options arguments
Command synopsis or general usage, on a separated line. filename Name
of a file or directory, for example Change to the /usr/bin directory.
Key Keys to hit on the keyboard, such as type Q to quit. Button
Graphical button to click, like the OK button. MenuChoice Choice to
select from a graphical menu, for instance: Select HelpAbout Mozilla in
your browser. Terminology Important term or concept: The Linux kernel is
the heart of the system. See link to related subject within this guide.
The author Clickable link to an external web resource.
Organization of this document
List chapters (and optionally, appendices) with a short content for each
(only for longer docs).
: short description.
: short description.
: short description.
: short description.
: short description.
\&chap1; \&chap2; \&app1; \&gloss;

View File

@ -0,0 +1,33 @@
<appendix id="app1">
<title>Appendix one title</title>
<abstract>
<para>Says what this appendix is about, for instance further info on the web.</para>
</abstract>
<sect1>
<title>further info</title>
<sect2><title>about this subject</title>
<itemizedlist>
<listitem><para><ulink url="http://useful.org" />: about this and that.</para></listitem>
<listitem><para><ulink url="http://related.org" />: about other related stuff.</para></listitem>
<listitem><para><ulink url="http://other.org" />: more stuff.</para></listitem>
</itemizedlist>
</sect2>
<sect2><title>about other subject</title>
<itemizedlist>
<listitem><para><ulink url="http://useful2.org" />: about this and that.</para></listitem>
<listitem><para><ulink url="http://related2.org" />: about other related stuff.</para></listitem>
<listitem><para><ulink url="http://other2.org" />: more stuff.</para></listitem> </itemizedlist>
</sect2>
</sect1>
</appendix>

View File

@ -0,0 +1,29 @@
\section{Appendix one title}\label{app1}
\begin{quote}
Says what this appendix is about, for instance further info on the web.
\end{quote}
\section{further info}
\subsection{about this subject}
\begin{itemize}
\item
\href{http://useful.org}{}: about this and that.
\item
\href{http://related.org}{}: about other related stuff.
\item
\href{http://other.org}{}: more stuff.
\end{itemize}
\subsection{about other subject}
\begin{itemize}
\item
\href{http://useful2.org}{}: about this and that.
\item
\href{http://related2.org}{}: about other related stuff.
\item
\href{http://other2.org}{}: more stuff.
\end{itemize}

View File

@ -0,0 +1,21 @@
Appendix one title
Says what this appendix is about, for instance further info on the web.
further info
about this subject
: about this and that.
: about other related stuff.
: more stuff.
about other subject
: about this and that.
: about other related stuff.
: more stuff.

View File

@ -0,0 +1,68 @@
<bibliography id="bibliography">
<?dbhtml filename="bibliography.html"?>
<title>References and Resources</title>
<!-- these are just examples...you do not need to use these sections. -->
<!-- A full bibliography entry would use the following template. -->
<!--
<biblioentry>
<title>
</title>
<bibliosource><ulink url="" /></bibliosource>
<author><firstname></firstname><surname></surname></author>
<copyright><year></year>
<holder></holder></copyright>
<editor><firstname></firstname><surname></surname></editor>
<isbn></isbn>
<publisher>
<publishername></publishername>
</publisher>
</biblioentry>
-->
<bibliodiv id="ref-howto" xreflabel="HOWTOs">
<title>HOWTOs</title>
<biblioentry>
<title>Document Title</title>
<bibliosource><ulink url="URL" /></bibliosource>
</biblioentry>
<biblioentry>
<title>Document Title 2</title>
<bibliosource><ulink url="URL 2" /></bibliosource>
</biblioentry>
</bibliodiv>
<bibliodiv id="ref-installreports" xreflabel="Hardware-specific Install Reports and Info">
<title>Hardware-specific Install Reports and Info</title>
<biblioentry>
<title>Installation Reports</title>
<bibliosource><ulink url="URL 3"/></bibliosource>
</biblioentry>
<biblioentry>
<title>Blacklist</title>
<bibliosource><ulink url="URL 4"/></bibliosource>
</biblioentry>
</bibliodiv>
<bibliodiv id="ref-mailinglist" xreflabel="Mailing List Threads">
<title>Mailing List Threads</title>
<biblioentry>
<title>mailing_list_name thread: subject line</title>
<bibliosource><ulink url="URL 5" /></bibliosource>
</biblioentry>
<bibliodiv id="ref-software" xreflabel="Packages and related software">
<title>Packages and related software</title>
<biblioentry>
<title>The Kernel</title>
<bibliosource><ulink url="http://www.kernel.org" /></bibliosource>
<abstract><para>Remember to choose "F" for full when you download your
kernel source.</para></abstract>
</biblioentry>
</bibliodiv>
</bibliography>

View File

@ -0,0 +1,26 @@
\section{References and Resources}\label{bibliography}
\section{HOWTOs}\label{ref-howto}
\href{URL}{}
\href{URL 2}{}
\section{Hardware-specific Install Reports and
Info}\label{ref-installreports}
\href{URL 3}{}
\href{URL 4}{}
\section{Mailing List Threads}\label{ref-mailinglist}
\href{URL 5}{}
\section{Packages and related software}\label{ref-software}
\href{http://www.kernel.org}{}
\begin{quote}
Remember to choose "F" for full when you download your kernel source.
\end{quote}

View File

@ -0,0 +1,49 @@
References and Resources
HOWTOs
\begin{verbatim}
<biblioentry>
<title>Document Title</title>
<bibliosource><ulink url="URL" /></bibliosource>
</biblioentry>
<biblioentry>
<title>Document Title 2</title>
<bibliosource><ulink url="URL 2" /></bibliosource>
</biblioentry>
\end{verbatim}
Hardware-specific Install Reports and Info
\begin{verbatim}
<biblioentry>
<title>Installation Reports</title>
<bibliosource><ulink url="URL 3"/></bibliosource>
</biblioentry>
<biblioentry>
<title>Blacklist</title>
<bibliosource><ulink url="URL 4"/></bibliosource>
</biblioentry>
\end{verbatim}
Mailing List Threads
\begin{verbatim}
<biblioentry>
<title>mailing_list_name thread: subject line</title>
<bibliosource><ulink url="URL 5" /></bibliosource>
</biblioentry>
\end{verbatim}
Packages and related software
\begin{verbatim}
<biblioentry>
<title>The Kernel</title>
<bibliosource><ulink url="http://www.kernel.org" /></bibliosource>
<abstract><para>Remember to choose "F" for full when you download your
kernel source.</para></abstract>
</biblioentry>
\end{verbatim}

View File

@ -0,0 +1,142 @@
#LyX 2.1 created this file. For more info see http://www.lyx.org/
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Glossary
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "glossary"
\end_inset
\end_layout
\begin_layout Quote
This is a glossary.
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout --Separator--
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout --Separator--
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Standard
And so on, for all the letters in the alphabet and all the items you want
in the list.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,86 @@
<glossary id="glossary"><?dbhtml filename="gloss.html"?>
<title>Glossary</title>
<abstract>
<para>This is a glossary.</para>
</abstract>
<glossdiv><title>A</title>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv><title>B</title>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
</glossdiv>
<glossdiv><title>C</title>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
<glossentry id="entryname">
<glossterm>entryname</glossterm>
<glossdef>
<para>definition</para>
</glossdef>
</glossentry>
</glossdiv>
And so on, for all the letters in the alphabet and all the items you want in the list.
</glossary>

View File

@ -0,0 +1,140 @@
#LyX file created by tex2lyx 2.1
\lyxformat 474
\begin_document
\begin_header
\textclass article
\use_default_options false
\maintain_unincluded_children false
\language english
\language_package none
\inputencoding auto
\fontencoding default
\font_roman default
\font_sans default
\font_typewriter default
\font_math auto
\font_default_family default
\use_non_tex_fonts false
\font_sc false
\font_osf false
\font_sf_scale 100
\font_tt_scale 100
\graphics default
\default_output_format default
\output_sync 0
\bibtex_command default
\index_command default
\paperfontsize default
\spacing single
\use_hyperref false
\papersize default
\use_geometry false
\use_package amsmath 1
\use_package amssymb 0
\use_package cancel 0
\use_package esint 1
\use_package mathdots 0
\use_package mathtools 0
\use_package mhchem 0
\use_package stackrel 0
\use_package stmaryrd 0
\use_package undertilde 0
\cite_engine basic
\cite_engine_type default
\biblio_style plain
\use_bibtopic false
\use_indices false
\paperorientation portrait
\suppress_date false
\justification true
\use_refstyle 0
\index Index
\shortcut idx
\color #008000
\end_index
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\paragraph_indentation default
\quotes_language english
\papercolumns 1
\papersides 1
\paperpagestyle default
\tracking_changes false
\output_changes false
\html_math_output 0
\html_css_as_file 0
\html_be_strict false
\end_header
\begin_body
\begin_layout Section
Glossary
\end_layout
\begin_layout Standard
\begin_inset CommandInset label
LatexCommand label
name "glossary"
\end_inset
\end_layout
\begin_layout Quote
This is a glossary.
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout --Separator--
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout --Separator--
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Description
entryname definition
\end_layout
\begin_layout Standard
And so on, for all the letters in the alphabet and all the items you want in the list.
\end_layout
\end_body
\end_document

View File

@ -0,0 +1,35 @@
\section{Glossary}\label{glossary}
\begin{quote}
This is a glossary.
\end{quote}
\begin{description}
\item[entryname]
definition
\item[entryname]
definition
\item[entryname]
definition
\end{description}
\begin{description}
\item[entryname]
definition
\item[entryname]
definition
\item[entryname]
definition
\end{description}
\begin{description}
\item[entryname]
definition
\item[entryname]
definition
\item[entryname]
definition
\end{description}
And so on, for all the letters in the alphabet and all the items you
want in the list.

View File

@ -0,0 +1,98 @@
Glossary
This is a glossary.
A
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
B
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
C
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
entryname
definition
\begin{verbatim}
</glossdef>
</glossentry>
\end{verbatim}
And so on, for all the letters in the alphabet and all the items you
want in the list.

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,722 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
[
<!--
This is where we will call the external files that we would like to
include in our document. Uncomment each line if you wish to call the
corresponding external file. At the end of the document you will
also need to uncomment the corresponding entity.
-->
<!-- Appendix -->
<!-- <!ENTITY appendix SYSTEM "ldp-appendix.xml"> -->
<!-- Remember to uncomment &appendix; in the document body as well. -->
<!-- Glossary -->
<!-- <!ENTITY glossary SYSTEM "ldp-glossary.xml"> -->
<!-- Remember to uncomment &glossary; in the document body as well. -->
<!-- Bibliography -->
<!-- <!ENTITY bibliography SYSTEM "ldp-bibliography.xml"> -->
<!-- Remember to uncomment &bibliography; in the document body as well. -->
]>
<article id="index">
<articleinfo>
<title>Sample XML HOWTO</title>
<author>
<firstname>Your Given Name</firstname>
<surname>Your Family Name (Surname)</surname>
<authorblurb><para>A short sentence about who you are.</para></authorblurb>
<affiliation>
<!-- The name of your organization is optional. -->
<orgname>
<ulink url="http://www.URL.com">company name</ulink>
</orgname>
<!-- A valid email is required. You may add a spam blocker, or get a Yahoo/Gmail/etc account. -->
<address>
<email>youremail@domain.NOSPAM.org</email>
</address>
</affiliation>
</author>
<!-- The date of publication. -->
<pubdate>YYYY-MM-DD</pubdate>
<!-- A short description of what is contained in this document. -->
<abstract>
<para>This is a sample DocBook XML HOWTO which you may use as a document template.</para>
</abstract>
<!-- A summary of the revisions to date. The latest revision should be at the top. -->
<revhistory>
<revision>
<revnumber>1.1</revnumber>
<date>2005-03-04</date>
<authorinitials>ME</authorinitials>
<revremark>A short note about what you have changed.</revremark>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>YYYY-MM-DD</date>
<authorinitials>ME</authorinitials>
<revremark>First official release.</revremark>
</revision>
</revhistory>
</articleinfo>
<!--
A little about file names...
If you would like, you can add an "id" to each of your sections.
The id will be used as the file name when output to HTML. Make sure
it is:
1) all one word
2) contains no spaces
As of March 2005, the LDP is using DSSSL processing tools. The
<?dbhtml filename="file.html" ?>
should match the id so that the file names are the same regardless of
processing tools.
-->
<sect1 id="about">
<?dbhtml filename="about.html"?>
<title>About this document</title>
<sect2 id="copyright">
<?dbhtml filename="copyright.html"?>
<title>Copyright and License</title>
<para>
Copyright (c) YEAR by YOUR NAME.</para>
<para>Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version
1.1 or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and with no Back-Cover
Texts.
A copy of the license is included in <xref linkend="gfdl"/>.
<!-- The LDP requires you to include the full text of the license. -->
</para>
</sect2>
<sect2 id="translations">
<?dbhtml filename="translations.html"?>
<title>Translations</title>
<!--
Probably your document will not have a translation to start.
Uncomment the following section when there are translations ready.
-->
<!--
<para>This document is also available in the following languages:</para>
<itemizedlist>
<listitem>
<para><ulink url="URL">LANGUAGE</ulink>. Include a note of thanks to your translation team.</para>
</listitem>
</itemizedlist>
-->
<para>If you know of any translations for this document, or you are interested in translating it, please email me <email>YOUR EMAIL</email>.</para>
</sect2>
<sect2 id="preface">
<title>Preface</title>
<para>Tell us why you decided to write this document.</para>
</sect2>
<sect2 id="thanks">
<title>Acknowledgments</title>
<para>No one ever writes documentation by themselves. Please take the time to thank the people who have helped you.</para>
<!-- If it is a long list of people, you may want to use a bullet list: -->
<!--
<itemizedlist>
<listitem><para></para></listitem>
<listitem><para></para></listitem>
<listitem><para></para></listitem>
</itemizedlist>
-->
</sect2>
<sect2 id="feedback">
<title>Feedback</title>
<para>Find something wrong with this document? (Or perhaps something right?) I would love to hear from you. Please email me at <email>YOUR EMAIL</email>.</para>
</sect2>
<sect2 id="conventions">
<title>Conventions used in this document</title>
<!--
This section was provided by Machtelt Garrels.
You do not need to include it in your document, especially if your HOWTO is
very short.
-->
<para>The following typographic and usage conventions occur in this text:
</para>
<table id="table-conventions" frame="all">
<title>Typographic and usage conventions</title>
<tgroup cols="2" align="left" colsep="1" rowsep="1">
<thead>
<row><entry>Text type</entry><entry>Meaning</entry></row>
</thead>
<tbody>
<row>
<entry><quote>Quoted text</quote></entry>
<entry>Quotes from people, quoted computer output.</entry>
</row>
<row>
<entry><screen>terminal view</screen></entry>
<entry>Literal computer input and output captured from the terminal.</entry>
</row>
<row>
<entry><command>command</command></entry>
<entry>Name of a command that can be entered on the command line.</entry>
</row>
<row>
<entry><option>option</option></entry>
<entry>Option to a command, as in <quote>the <option>-a</option> option to the
<command>ls</command> command</quote>.</entry>
</row>
<row>
<entry><parameter>parameter</parameter></entry>
<entry>Parameter to a command, as in <quote>read
<command>man <parameter>ls</parameter></command></quote>.</entry>
</row>
<row>
<entry><cmdsynopsis><command>command <option>options</option>
<parameter>arguments</parameter></command></cmdsynopsis></entry>
<entry>Command synopsis or general usage, on a separated line.</entry>
</row>
<row>
<entry><filename>filename</filename></entry>
<entry>Name of a file or directory, for example <quote>Change to the
<filename class="directory">/usr/bin</filename> directory.</quote></entry>
</row>
<row>
<entry><menuchoice><guimenu>Menu</guimenu><guimenuitem>Choice</guimenuitem>
</menuchoice></entry>
<entry>Choice to select from a graphical menu, for instance: <quote>Select
<menuchoice><guimenu>Help</guimenu><guimenuitem>About Mozilla</guimenuitem>
</menuchoice> in your browser.</quote></entry>
</row>
<row>
<entry><ulink url="http://www.xtrinsic.com">The author</ulink></entry>
<entry>Click-able link to an external web resource.</entry>
</row>
</tbody>
</tgroup>
</table>
<para>Thanks to Machtelt <quote>Tille</quote> Garrels for this list of conventions.</para>
</sect2>
</sect1>
<sect1 id="about">
<?dbhtml filename="about.html"?>
<title>About My Topic</title>
<para>Start by explaining the basics of your topic. Is a brief history lesson in order?</para>
<sect2 id="distro-news">
<title>Distribution News</title>
<para>If there is any news specific to each of the distrobutions of Linux, you can include it here.</para>
</sect2>
</sect1>
<sect1 id="install">
<?dbhtml filename="install.html"?>
<title>Installing from scratch</title>
<para>Write down each of the steps on how to install any necessary packages/software/etc. Do you need to recompile the kernel to activate new options?</para>
<para>If there are any step-by-step instructions, you may want to include them in an example so that they can be easily referred to later.</para>
<example id="ex-install" xreflabel="Installation Instructions">
<title>Installation Instructions</title>
<orderedlist>
<listitem><para>Step One.</para></listitem>
<listitem><para>Step Two.</para></listitem>
<listitem><para>Step Three.</para></listitem>
</orderedlist>
</example>
</sect1>
<sect1 id="using-softwarepackage" xreflabel="Using SOFTWARE">
<?dbhtml filename="using-softwarepackage.html"?>
<title>Using SOFTWARE</title>
<para>Finally! Now you can describe how to use your system/software/package.</para>
</sect1>
<!-- If you had a second appendix in an external file, you would call it
here with the following: -->
&appendix;
<!-- This exactly matches the word you used at the very top of the
document. Use whatever word makes sense to you so long as it only uses
letters, underscores and hyphens. -->
<appendix id="gfdl">
<title>GNU Free Documentation License</title>
<!-- - GNU Project - Free Software Foundation (FSF) -->
<!-- LINK REV="made" HREF="mailto:webmasters@gnu.org" -->
<!-- http://www.gnu.org/copyleft/fdl.html -->
<sect1>
<title>GNU Free Documentation License</title>
<para>Version 1.1, March 2000</para>
<blockquote>
<para>Copyright (C) 2000 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>
</sect1>
<sect1 id="gfdl-0">
<title>PREAMBLE</title>
<para>The purpose of this License is to make a manual, textbook,
or other written 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>
</sect1>
<sect1 id="gfdl-1">
<title>APPLICABILITY AND DEFINITIONS</title>
<para>This License applies to any manual or other work that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. The "Document",
below, refers to any such manual or work. Any member of the
public is a licensee, and is addressed as "you".</para>
<para>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>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.
(For example, 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>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.</para>
<para>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.</para>
<para>A "Transparent" copy of the Document means a
machine-readable copy, represented in a format whose specification
is available to the general public, whose contents can be viewed
and edited directly and 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 has been designed to thwart or discourage subsequent
modification by readers is not Transparent. 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 designed for human modification.
Opaque formats include PostScript, PDF, 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 produced by some word
processors for output purposes only.</para>
<para>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>
</sect1>
<sect1 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>
</sect1>
<sect1 id="gfdl-3">
<title>COPYING IN QUANTITY</title>
<para>If you publish printed copies 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 publicly-accessible
computer-network location containing a complete Transparent copy
of the Document, free of added material, which the general
network-using public has access to download anonymously at no
charge using public-standard network protocols. 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>
</sect1>
<sect1 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 numeration="upperalpha">
<listitem><para>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.</para>
</listitem>
<listitem><para>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 less than
five).</para>
</listitem>
<listitem><para>State on the Title page
the name of the publisher of the Modified Version, as the
publisher.</para>
</listitem>
<listitem><para>Preserve all the
copyright notices of the Document.</para>
</listitem>
<listitem><para>Add an appropriate
copyright notice for your modifications adjacent to the other
copyright notices.</para>
</listitem>
<listitem><para>Include, immediately
after the copyright notices, a license notice giving the public
permission to use the Modified Version under the terms of this
License, in the form shown in the Addendum below.</para>
</listitem>
<listitem><para>Preserve in that license
notice the full lists of Invariant Sections and required Cover
Texts given in the Document's license notice.</para>
</listitem>
<listitem><para>Include an unaltered
copy of this License.</para>
</listitem>
<listitem><para>Preserve the section
entitled "History", and 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.</para>
</listitem>
<listitem><para>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.</para>
</listitem>
<listitem><para>In any section entitled
"Acknowledgements" or "Dedications", preserve the section's
title, and preserve in the section all the substance and tone of
each of the contributor acknowledgements and/or dedications
given therein.</para>
</listitem>
<listitem><para>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.</para>
</listitem>
<listitem><para>Delete any section
entitled "Endorsements". Such a section may not be included in
the Modified Version.</para>
</listitem>
<listitem><para>Do not retitle any
existing section as "Endorsements" or to conflict in title with
any Invariant Section.</para>
</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>
</sect1>
<sect1 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 section 4 above for
modified versions, provided that you include in the combination
all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice.</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>
</sect1>
<sect1 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>
</sect1>
<sect1 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, does not as a whole count as a
Modified Version of the Document, provided no compilation
copyright is claimed for the compilation. Such a compilation is
called an "aggregate", and this License does not apply to the
other self-contained works thus compiled with the Document, on
account of their being thus compiled, if they 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 quarter of the entire aggregate, the Document's Cover Texts
may be placed on covers that surround only the Document within the
aggregate. Otherwise they must appear on covers around the whole
aggregate.</para>
</sect1>
<sect1 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 provided that you also
include the original English version of this License. In case of
a disagreement between the translation and the original English
version of this License, the original English version will
prevail.</para>
</sect1>
<sect1 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>
</sect1>
<sect1 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 <ulink
url="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</ulink>.</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>
</sect1>
<sect1 id="gfdl-11">
<title>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><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.1
or any later version published by the Free Software Foundation;
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
A copy of the license is included in the section entitled "GNU
Free Documentation License".
</para></blockquote>
<para>If you have no Invariant Sections, write "with no Invariant
Sections" instead of saying which ones are invariant. If you have
no Front-Cover Texts, write "no Front-Cover Texts" instead of
"Front-Cover Texts being LIST"; likewise for Back-Cover
Texts.</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>
</sect1>
</appendix>
<!-- Uncomment the following line if you are using an external file for
your glossary. You may also paste the contents of that file into the
template at this point if you prefer having a single, longer file. -->
<!-- &glossary; -->
<!-- Uncomment the following line if you are using an external file for
your bibliography. You may also paste the contents of that file into the
template at this point if you prefer having a single, longer file. -->
<!-- &bibliography; -->
</article>

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,473 @@
\section{About this document}\label{about}
\subsection{Copyright and License}\label{copyright}
Copyright (c) YEAR by YOUR NAME.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.1 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and with no Back-Cover Texts.
A copy of the license is included in ?.
\subsection{Translations}\label{translations}
If you know of any translations for this document, or you are interested
in translating it, please email me \href{mailto:YOUR EMAIL}{YOUR EMAIL}.
\subsection{Preface}\label{preface}
Tell us why you decided to write this document.
\subsection{Acknowledgments}\label{thanks}
No one ever writes documentation by themselves. Please take the time to
thank the people who have helped you.
\subsection{Feedback}\label{feedback}
Find something wrong with this document? (Or perhaps something right?) I
would love to hear from you. Please email me at
\href{mailto:YOUR EMAIL}{YOUR EMAIL}.
\subsection{Conventions used in this document}\label{conventions}
The following typographic and usage conventions occur in this text:
\begin{longtable}[c]{@{}ll@{}}
\caption{Typographic and usage conventions}\tabularnewline
\toprule
Text type & Meaning\tabularnewline
\midrule
\endfirsthead
\toprule
Text type & Meaning\tabularnewline
\midrule
\endhead
``Quoted text'' & Quotes from people, quoted computer
output.\tabularnewline
\begin{verbatim}
terminal view
\end{verbatim}
& Literal computer input and output captured from the
terminal.\tabularnewline
\texttt{command} & Name of a command that can be entered on the command
line.\tabularnewline
\texttt{option} & Option to a command, as in ``the \texttt{-a} option to
the \texttt{ls} command''.\tabularnewline
\texttt{parameter} & Parameter to a command, as in ``read
\texttt{man\ ls}''.\tabularnewline
\texttt{command\ options\
arguments} & Command synopsis or general usage, on a separated
line.\tabularnewline
\texttt{filename} & Name of a file or directory, for example ``Change to
the \texttt{/usr/bin} directory.''\tabularnewline
{Menu \textgreater{} Choice} & Choice to select from a graphical menu,
for instance: ``Select {Help \textgreater{} About Mozilla} in your
browser.''\tabularnewline
\href{http://www.xtrinsic.com}{The author} & Click-able link to an
external web resource.\tabularnewline
\bottomrule
\end{longtable}
Thanks to Machtelt ``Tille'' Garrels for this list of conventions.
\section{About My Topic}\label{about}
Start by explaining the basics of your topic. Is a brief history lesson
in order?
\subsection{Distribution News}\label{distro-news}
If there is any news specific to each of the distrobutions of Linux, you
can include it here.
\section{Installing from scratch}\label{install}
Write down each of the steps on how to install any necessary
packages/software/etc. Do you need to recompile the kernel to activate
new options?
If there are any step-by-step instructions, you may want to include them
in an example so that they can be easily referred to later.
\begin{enumerate}
\def\labelenumi{\arabic{enumi}.}
\item
Step One.
\item
Step Two.
\item
Step Three.
\end{enumerate}
\section{Using SOFTWARE}\label{using-softwarepackage}
Finally! Now you can describe how to use your system/software/package.
APPENDIX
\section{GNU Free Documentation License}\label{gfdl}
\section{GNU Free Documentation License}
Version 1.1, March 2000
\begin{quote}
Copyright (C) 2000 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.
\end{quote}
\section{PREAMBLE}\label{gfdl-0}
The purpose of this License is to make a manual, textbook, or other
written 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.
This License is a kind of "copyleft", which means that derivative works
of the document must themselves be free in the same sense. It
complements the GNU General Public License, which is a copyleft license
designed for free software.
We have designed this License in order to use it for manuals for free
software, because free software needs free documentation: a free program
should come with manuals providing the same freedoms that the software
does. But this License is not limited to software manuals; it can be
used for any textual work, regardless of subject matter or whether it is
published as a printed book. We recommend this License principally for
works whose purpose is instruction or reference.
\section{APPLICABILITY AND DEFINITIONS}\label{gfdl-1}
This License applies to any manual or other work that contains a notice
placed by the copyright holder saying it can be distributed under the
terms of this License. The "Document", below, refers to any such manual
or work. Any member of the public is a licensee, and is addressed as
"you".
A "Modified Version" of the Document means any work containing the
Document or a portion of it, either copied verbatim, or with
modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of
the Document that deals exclusively with the relationship of the
publishers or authors of the Document to the Document's overall subject
(or to related matters) and contains nothing that could fall directly
within that overall subject. (For example, if the Document is in part a
textbook of mathematics, a Secondary Section may not explain any
mathematics.) The relationship could be a matter of historical
connection with the subject or with related matters, or of legal,
commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are
designated, as being those of Invariant Sections, in the notice that
says that the Document is released under this License.
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 "Transparent" copy of the Document means a machine-readable copy,
represented in a format whose specification is available to the general
public, whose contents can be viewed and edited directly and
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 has been designed to thwart or discourage subsequent modification
by readers is not Transparent. A copy that is not "Transparent" is
called "Opaque".
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
designed for human modification. Opaque formats include PostScript, PDF,
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 produced by some
word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus
such following pages as are needed to hold, legibly, the material this
License requires to appear in the title page. For works in formats which
do not have any title page as such, "Title Page" means the text near the
most prominent appearance of the work's title, preceding the beginning
of the body of the text.
\section{VERBATIM COPYING}\label{gfdl-2}
You may copy and distribute the Document in any medium, either
commercially or noncommercially, provided that this License, the
copyright notices, and the license notice saying this License applies to
the Document are reproduced in all copies, and that you add no other
conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further copying
of the copies you make or distribute. However, you may accept
compensation in exchange for copies. If you distribute a large enough
number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and
you may publicly display copies.
\section{COPYING IN QUANTITY}\label{gfdl-3}
If you publish printed copies of the Document numbering more than 100,
and the Document's license notice requires Cover Texts, you must enclose
the copies in covers that carry, clearly and legibly, all these Cover
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the
back cover. Both covers must also clearly and legibly identify you as
the publisher of these copies. The front cover must present the full
title with all words of the title equally prominent and visible. You may
add other material on the covers in addition. Copying with changes
limited to the covers, as long as they preserve the title of the
Document and satisfy these conditions, can be treated as verbatim
copying in other respects.
If the required texts for either cover are too voluminous to fit
legibly, you should put the first ones listed (as many as fit
reasonably) on the actual cover, and continue the rest onto adjacent
pages.
If you publish or distribute Opaque copies of the Document numbering
more than 100, you must either include a machine-readable Transparent
copy along with each Opaque copy, or state in or with each Opaque copy a
publicly-accessible computer-network location containing a complete
Transparent copy of the Document, free of added material, which the
general network-using public has access to download anonymously at no
charge using public-standard network protocols. If you use the latter
option, you must take reasonably prudent steps, when you begin
distribution of Opaque copies in quantity, to ensure that this
Transparent copy will remain thus accessible at the stated location
until at least one year after the last time you distribute an Opaque
copy (directly or through your agents or retailers) of that edition to
the public.
It is requested, but not required, that you contact the authors of the
Document well before redistributing any large number of copies, to give
them a chance to provide you with an updated version of the Document.
\section{MODIFICATIONS}\label{gfdl-4}
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:
\begin{enumerate}
\def\labelenumi{\Alph{enumi}.}
\item
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.
\item
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 less than five).
\item
State on the Title page the name of the publisher of the Modified
Version, as the publisher.
\item
Preserve all the copyright notices of the Document.
\item
Add an appropriate copyright notice for your modifications adjacent to
the other copyright notices.
\item
Include, immediately after the copyright notices, a license notice
giving the public permission to use the Modified Version under the
terms of this License, in the form shown in the Addendum below.
\item
Preserve in that license notice the full lists of Invariant Sections
and required Cover Texts given in the Document's license notice.
\item
Include an unaltered copy of this License.
\item
Preserve the section entitled "History", and 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.
\item
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.
\item
In any section entitled "Acknowledgements" or "Dedications", preserve
the section's title, and preserve in the section all the substance and
tone of each of the contributor acknowledgements and/or dedications
given therein.
\item
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.
\item
Delete any section entitled "Endorsements". Such a section may not be
included in the Modified Version.
\item
Do not retitle any existing section as "Endorsements" or to conflict
in title with any Invariant Section.
\end{enumerate}
If the Modified Version includes new front-matter sections or appendices
that qualify as Secondary Sections and contain no material copied from
the Document, you may at your option designate some or all of these
sections as invariant. To do this, add their titles to the list of
Invariant Sections in the Modified Version's license notice. These
titles must be distinct from any other section titles.
You may add a section entitled "Endorsements", provided it contains
nothing but endorsements of your Modified Version by various
parties-\/-for example, statements of peer review or that the text has
been approved by an organization as the authoritative definition of a
standard.
You may add a passage of up to five words as a Front-Cover Text, and a
passage of up to 25 words as a Back-Cover Text, to the end of the list
of Cover Texts in the Modified Version. Only one passage of Front-Cover
Text and one of Back-Cover Text may be added by (or through arrangements
made by) any one entity. If the Document already includes a cover text
for the same cover, previously added by you or by arrangement made by
the same entity you are acting on behalf of, you may not add another;
but you may replace the old one, on explicit permission from the
previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License
give permission to use their names for publicity for or to assert or
imply endorsement of any Modified Version.
\section{COMBINING DOCUMENTS}\label{gfdl-5}
You may combine the Document with other documents released under this
License, under the terms defined in section 4 above for modified
versions, provided that you include in the combination all of the
Invariant Sections of all of the original documents, unmodified, and
list them all as Invariant Sections of your combined work in its license
notice.
The combined work need only contain one copy of this License, and
multiple identical Invariant Sections may be replaced with a single
copy. If there are multiple Invariant Sections with the same name but
different contents, make the title of each such section unique by adding
at the end of it, in parentheses, the name of the original author or
publisher of that section if known, or else a unique number. Make the
same adjustment to the section titles in the list of Invariant Sections
in the license notice of the combined work.
In the combination, you must combine any sections entitled "History" in
the various original documents, forming one section entitled "History";
likewise combine any sections entitled "Acknowledgements", and any
sections entitled "Dedications". You must delete all sections entitled
"Endorsements."
\section{COLLECTIONS OF DOCUMENTS}\label{gfdl-6}
You may make a collection consisting of the Document and other documents
released under this License, and replace the individual copies of this
License in the various documents with a single copy that is included in
the collection, provided that you follow the rules of this License for
verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute
it individually under this License, provided you insert a copy of this
License into the extracted document, and follow this License in all
other respects regarding verbatim copying of that document.
\section{AGGREGATION WITH INDEPENDENT WORKS}\label{gfdl-7}
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, does not as a whole count as a Modified Version of
the Document, provided no compilation copyright is claimed for the
compilation. Such a compilation is called an "aggregate", and this
License does not apply to the other self-contained works thus compiled
with the Document, on account of their being thus compiled, if they are
not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies
of the Document, then if the Document is less than one quarter of the
entire aggregate, the Document's Cover Texts may be placed on covers
that surround only the Document within the aggregate. Otherwise they
must appear on covers around the whole aggregate.
\section{TRANSLATION}\label{gfdl-8}
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
provided that you also include the original English version of this
License. In case of a disagreement between the translation and the
original English version of this License, the original English version
will prevail.
\section{TERMINATION}\label{gfdl-9}
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.
\section{FUTURE REVISIONS OF THIS LICENSE}\label{gfdl-10}
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
\url{http://www.gnu.org/copyleft/}.
Each version of the License is given a distinguishing version number. If
the Document specifies that a particular numbered version of this
License "or any later version" applies to it, you have the option of
following the terms and conditions either of that specified version or
of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version
number of this License, you may choose any version ever published (not
as a draft) by the Free Software Foundation.
\section{How to use this License for your documents}\label{gfdl-11}
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:
\begin{quote}
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.1 or any later version published by the
Free Software Foundation; with the Invariant Sections being LIST THEIR
TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover
Texts being LIST. A copy of the license is included in the section
entitled "GNU Free Documentation License".
\end{quote}
If you have no Invariant Sections, write "with no Invariant Sections"
instead of saying which ones are invariant. If you have no Front-Cover
Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being
LIST"; likewise for Back-Cover Texts.
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.

View File

@ -0,0 +1,591 @@
\begin{verbatim}
<!-- Appendix -->
<!-- <!ENTITY appendix SYSTEM "ldp-appendix.xml"> -->
<!-- Remember to uncomment &appendix; in the document body as well. -->
<!-- Glossary -->
<!-- <!ENTITY glossary SYSTEM "ldp-glossary.xml"> -->
<!-- Remember to uncomment &glossary; in the document body as well. -->
<!-- Bibliography -->
<!-- <!ENTITY bibliography SYSTEM "ldp-bibliography.xml"> -->
<!-- Remember to uncomment &bibliography; in the document body as well. -->
\end{verbatim}
{]}\textgreater{}
Sample XML HOWTO
Your Given Name Your Family Name (Surname)
A short sentence about who you are.
company name
\begin{verbatim}
<!-- A valid email is required. You may add a spam blocker, or get a Yahoo/Gmail/etc account. -->
<address>
<email>youremail@domain.NOSPAM.org</email>
</address>
</affiliation>
\end{verbatim}
YYYY-MM-DD
This is a sample DocBook XML HOWTO which you may use as a document
template.
1.1 2005-03-04 ME A short note about what you have changed. 1.0
YYYY-MM-DD ME First official release.
About this document
Copyright and License
\begin{verbatim}
Copyright (c) YEAR by YOUR NAME.</para>
<para>Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version
1.1 or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and with no Back-Cover
Texts.
A copy of the license is included in <xref linkend="gfdl"/>.
<!-- The LDP requires you to include the full text of the license. -->
\end{verbatim}
Translations
If you know of any translations for this document, or you are interested
in translating it, please email me YOUR EMAIL.
Preface
\begin{verbatim}
<para>Tell us why you decided to write this document.</para>
\end{verbatim}
Acknowledgments
No one ever writes documentation by themselves. Please take the time to
thank the people who have helped you.
Feedback
\begin{verbatim}
<para>Find something wrong with this document? (Or perhaps something right?) I would love to hear from you. Please email me at <email>YOUR EMAIL</email>.</para>
\end{verbatim}
Conventions used in this document
The following typographic and usage conventions occur in this text:
Typographic and usage conventions
Text typeMeaning
Quoted text Quotes from people, quoted computer output.
terminal view
Literal computer input and output captured from the terminal. command
Name of a command that can be entered on the command line. option Option
to a command, as in the -a option to the ls command. parameter Parameter
to a command, as in read man ls.
command options arguments
Command synopsis or general usage, on a separated line. filename Name
of a file or directory, for example Change to the /usr/bin directory.
MenuChoice Choice to select from a graphical menu, for instance: Select
HelpAbout Mozilla in your browser. The author Click-able link to an
external web resource.
Thanks to Machtelt Tille Garrels for this list of conventions.
About My Topic
Start by explaining the basics of your topic. Is a brief history lesson
in order?
Distribution News
If there is any news specific to each of the distrobutions of Linux, you
can include it here.
Installing from scratch
Write down each of the steps on how to install any necessary
packages/software/etc. Do you need to recompile the kernel to activate
new options?
If there are any step-by-step instructions, you may want to include them
in an example so that they can be easily referred to later.
Installation Instructions
\begin{verbatim}
<listitem><para>Step One.</para></listitem>
<listitem><para>Step Two.</para></listitem>
<listitem><para>Step Three.</para></listitem>
\end{verbatim}
Using SOFTWARE
Finally! Now you can describe how to use your system/software/package.
\&appendix;
GNU Free Documentation License
GNU Free Documentation License
\begin{verbatim}
<para>Version 1.1, March 2000</para>
<blockquote>
<para>Copyright (C) 2000 Free Software Foundation, Inc.
\end{verbatim}
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.
\begin{verbatim}
</blockquote>
</sect1>
\end{verbatim}
PREAMBLE
\begin{verbatim}
<para>The purpose of this License is to make a manual, textbook,
or other written 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>
\end{verbatim}
APPLICABILITY AND DEFINITIONS
\begin{verbatim}
<para>This License applies to any manual or other work that
contains a notice placed by the copyright holder saying it can be
distributed under the terms of this License. The "Document",
below, refers to any such manual or work. Any member of the
public is a licensee, and is addressed as "you".</para>
<para>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>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.
(For example, 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>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.</para>
<para>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.</para>
<para>A "Transparent" copy of the Document means a
machine-readable copy, represented in a format whose specification
is available to the general public, whose contents can be viewed
and edited directly and 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 has been designed to thwart or discourage subsequent
modification by readers is not Transparent. 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 designed for human modification.
Opaque formats include PostScript, PDF, 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 produced by some word
processors for output purposes only.</para>
<para>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>
\end{verbatim}
VERBATIM COPYING
\begin{verbatim}
<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>
\end{verbatim}
COPYING IN QUANTITY
\begin{verbatim}
<para>If you publish printed copies 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 publicly-accessible
computer-network location containing a complete Transparent copy
of the Document, free of added material, which the general
network-using public has access to download anonymously at no
charge using public-standard network protocols. 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>
\end{verbatim}
MODIFICATIONS
\begin{verbatim}
<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 numeration="upperalpha">
<listitem><para>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.</para>
</listitem>
<listitem><para>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 less than
five).</para>
</listitem>
<listitem><para>State on the Title page
the name of the publisher of the Modified Version, as the
publisher.</para>
</listitem>
<listitem><para>Preserve all the
copyright notices of the Document.</para>
</listitem>
<listitem><para>Add an appropriate
copyright notice for your modifications adjacent to the other
copyright notices.</para>
</listitem>
<listitem><para>Include, immediately
after the copyright notices, a license notice giving the public
permission to use the Modified Version under the terms of this
License, in the form shown in the Addendum below.</para>
</listitem>
<listitem><para>Preserve in that license
notice the full lists of Invariant Sections and required Cover
Texts given in the Document's license notice.</para>
</listitem>
<listitem><para>Include an unaltered
copy of this License.</para>
</listitem>
<listitem><para>Preserve the section
entitled "History", and 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.</para>
</listitem>
<listitem><para>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.</para>
</listitem>
<listitem><para>In any section entitled
"Acknowledgements" or "Dedications", preserve the section's
title, and preserve in the section all the substance and tone of
each of the contributor acknowledgements and/or dedications
given therein.</para>
</listitem>
<listitem><para>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.</para>
</listitem>
<listitem><para>Delete any section
entitled "Endorsements". Such a section may not be included in
the Modified Version.</para>
</listitem>
<listitem><para>Do not retitle any
existing section as "Endorsements" or to conflict in title with
any Invariant Section.</para>
</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>
\end{verbatim}
COMBINING DOCUMENTS
\begin{verbatim}
<para>You may combine the Document with other documents released
under this License, under the terms defined in section 4 above for
modified versions, provided that you include in the combination
all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your
combined work in its license notice.</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>
\end{verbatim}
COLLECTIONS OF DOCUMENTS
\begin{verbatim}
<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>
\end{verbatim}
AGGREGATION WITH INDEPENDENT WORKS
\begin{verbatim}
<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, does not as a whole count as a
Modified Version of the Document, provided no compilation
copyright is claimed for the compilation. Such a compilation is
called an "aggregate", and this License does not apply to the
other self-contained works thus compiled with the Document, on
account of their being thus compiled, if they 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 quarter of the entire aggregate, the Document's Cover Texts
may be placed on covers that surround only the Document within the
aggregate. Otherwise they must appear on covers around the whole
aggregate.</para>
\end{verbatim}
TRANSLATION
\begin{verbatim}
<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 provided that you also
include the original English version of this License. In case of
a disagreement between the translation and the original English
version of this License, the original English version will
prevail.</para>
\end{verbatim}
TERMINATION
\begin{verbatim}
<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>
\end{verbatim}
FUTURE REVISIONS OF THIS LICENSE
\begin{verbatim}
<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 <ulink
url="http://www.gnu.org/copyleft/">http://www.gnu.org/copyleft/</ulink>.</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>
\end{verbatim}
How to use this License for your documents
\begin{verbatim}
<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>
\end{verbatim}
\begin{verbatim}
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.1
or any later version published by the Free Software Foundation;
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
A copy of the license is included in the section entitled "GNU
Free Documentation License".
\end{verbatim}
\begin{verbatim}
<para>If you have no Invariant Sections, write "with no Invariant
Sections" instead of saying which ones are invariant. If you have
no Front-Cover Texts, write "no Front-Cover Texts" instead of
"Front-Cover Texts being LIST"; likewise for Back-Cover
Texts.</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>
\end{verbatim}