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

new...xml v sgml

This commit is contained in:
gferg 2001-12-04 21:26:54 +00:00
parent 631422a445
commit 170c5c6716
615 changed files with 14464 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

43
LDP/guide/docbook/LFS/HOWTO_EDIT Normal file
View File

@ -0,0 +1,43 @@
How to edit the LFS-BOOK
------------------------
This document explains the necessary steps to be taken in order to make
changes to the LFS-BOOK. Not every single aspect is detailed, just the
more tricky ones.
* No matter what, always make the following changes whenever you do
something:
Whenever you make a change, no matter how small, update the book's version
number:
1) Open the index.xml file.
2) Find <!ENTITY version "yyyymmdd"> and make sure it contains the date on
which you are making the change. If today is June 11th, 2001, change it
to <!ENTITY version "20010611".
3) Find <ENTITY releasedate "Month, day, year"> and make sure it contains
the same date as the 'version' entity. If today is June 11th, 2001, change
it to: <!ENTITY releasedate "June 11th, 2001">
* Adding a new package update to Bugzilla
1) Login to bugzilla
2) Open bug #30
3) Check if the package is listed from a previous update
4) If so, reopen it and change the version number to match the new one
5) If not, add a new bug and fill it out as usual
6) When added, go back to the new bug and under "Bug xx depends on"
enter "30" so that this new bug is added to the parent bug #30
7) Click on "Commit" to commit this change

110
LDP/guide/docbook/LFS/INSTALL Normal file
View File

@ -0,0 +1,110 @@
Ok, so you have downloaded the XML source. Now what? You are probably
wanting to convert these XML files to easier to read HTML, PS, PDF, txt
or other formatted files. All that can be read below.
Let's start by downloading some software.
If all you want to do is being able to convert XML to HTML download the
following:
OpenJade - http://openjade.sourceforge.net/
DocBook-XML DTD - http://www.docbook.org/xml/4.1.2/
Modified DocBook Entities - http://www2.linuxfromscratch.org/
DSSSL DocBook Stylesheets - http://www.nwalsh.com/docbook/dsssl/
As the DocBook DTD and Stylesheets are made available as a zip achives you
may need to download the unzip package as well if your Linux system doesn't
have one:
Unzip - ftp://ftp.uu.net/pub/archiving/zip/src/
If you want to be able to convert the book into PS and PDF as well I
recommend using the Htmldoc program. This takes a html file (created
with openjade which you already downloaded) and converts it to PS or
PDF:
HTMLDOC - http://www.easysw.com/htmldoc/
FLTK (X front-end) - http://sourceforge.net/projects/fltk
If you want to be able to convert the book into TXT as well I recommend
using links to convert HTML to TXT using the -dump option to links.
Links - http://artax.karlin.mff.cuni.cz/~mikulas/links/
You have everything you need now. Let's install this stuff.
Create the /usr/share/docbook directory, cd into it and unpack the
docbook-xml dtd archive there.
Remove the ent directory and unpack the docbook-4.1.2-newent.tar.bz2 file.
This will create a new ent directory with entity files that work better
with XML.
Create the /usr/share/dsssl directory, cd into it and unpack the dsssl
stylesheet archive in there. Rename the directory that's created by tar
into 'docbook'. Now copy the lfs.dsl file you will find in
the LFS-BOOK XML archive into /usr/share/dsssl/docbook/html
The last step is installing OpenJade.
In order for openjade to be able to convert the DocBook based documents
into other formats, it needs to know where the DocBook DTD related
files are located. This is sort of the DocBook equivalent for the $PATH
variable. You have two ways of doing this:
1) You can set the $SGML_CATALOG_FILES variable and include the full
paths to the catalog files in it
or
2) You can hard-code the paths into the openjade binary.
If you choose option 1, add the following to your bash configuration
file, system wide profile or wherever you wish to include it:
export SGML_CATALOG_FILES=/usr/share/docbook/docbook.cat:/usr/share/dsssl/docbook/catalog:/usr/share/dsssl/openjade/catalog
Followed by installing openjade by running:
./configure --prefix=/usr
make
make install
cp -av dsssl /usr/share/dsssl/openjade
If you choose option 2, install OpenJade as follows:
./configure --prefix=/usr \
> --enable-default-catalog=/usr/share/docbook/docbook.cat:/usr/share/dsssl/docbook/catalog:/usr/share/dsssl/openjade/catalog
make
make install
cp -av dsssl /usr/share/dsssl/openjade
And you don't have to worry about the $SGML_CATALOG_FILES variable in
this case.
You're all set to convert XML to HTML (among a few other formats
supported by openjade) now. If you want to convert to PS and PDF as
well, install the following two packages.
FLTK (you can skip this one if you don't want the X front-end):
./configure --prefix=/usr
make
make install
HTMLDOC:
Install by running:
./configure --prefix=/usr
make
make install
The last package is Links which will be used for the HTML to TXT
conversion. Install it by running:
./configure --prefix=/usr
make
make install
There, all set now. Go back to the README file for some examples how to
convert this XML to the various other formats.

45
LDP/guide/docbook/LFS/README Normal file
View File

@ -0,0 +1,45 @@
How do I convert these XML files to other formats like HTML, PF, PS
and TXT? You need to have some software installed that deal with these
conversions. Please read the INSTALL file how to install that software.
Then come back to this file for examples how to convert these files
into various other formats.
XML to HTML:
------------
Create a directory in which you want to store the HTML files and cd into
that directory. Now run:
/usr/bin/openjade -t xml \
-d /usr/share/dsssl/docbook/html/lfs.dsl \
/usr/share/dsssl/docbook/dtds/decls/xml.dcl \
/path/to/index.xml
XML to NOCHUNKS-HTML:
--------------------
The NOCHUNKS HTML version is one big HTML file:
/usr/bin/openjade -t sgml \
-V nochunks \
-d /usr/share/dsssl/docbook/html/lfs.dsl \
/usr/share/dsssl/docbook/dtds/decls/xml.dcl \
/path/to/index.xml > nochunks.html
XML to TXT:
-----------
First create the NOCHUNKS HTML file, then convert by running:
/usr/bin/lynx -dump nochunks.html > output.txt
XML to PS and PDF:
------------------
First create the NOCHUNKS HTML file, then convert by starting
htmldoc. You can use the GUI and select the options. If you're
satisfied with the default options you can run this command:
/usr/bin/htmldoc --book --firstpage p1 -v -t <type> \
-f <output> nochunks.html
replace <type> by pdf13 to create a pdf file or replace <type> by ps3 to
create a ps file. There are other pdf and ps levels, see the man page for
possible other options. Replace <output> with the filename of the ps or
pdf file that is to be generated.

58
LDP/guide/docbook/LFS/appendixa/appendixa.xml Normal file
View File

@ -0,0 +1,58 @@
<appendix id="appendixa">
<title>Package descriptions</title>
<?dbhtml filename="appendixa.html" dir="appendixa"?>
&aa-introduction;
&aa-bash;
&aa-binutils;
&aa-bzip2;
&aa-diffutils;
&aa-fileutils;
&aa-gcc;
&aa-grep;
&aa-gzip;
&aa-kernel;
&aa-make;
&aa-mawk;
&aa-patch;
&aa-sed;
&aa-shellutils;
&aa-tar;
&aa-texinfo;
&aa-textutils;
&aa-glibc;
&aa-makedev;
&aa-manpages;
&aa-findutils;
&aa-ncurses;
&aa-vim;
&aa-bison;
&aa-less;
&aa-groff;
&aa-man;
&aa-perl;
&aa-m4;
&aa-autoconf;
&aa-automake;
&aa-flex;
&aa-file;
&aa-libtool;
&aa-bin86;
&aa-ed;
&aa-gettext;
&aa-kbd;
&aa-e2fsprogs;
&aa-lilo;
&aa-modutils;
&aa-procinfo;
&aa-procps;
&aa-psmisc;
&aa-reiserfs;
&aa-shadowpwd;
&aa-sysklogd;
&aa-sysvinit;
&aa-utillinux;
&aa-netkitbase;
&aa-nettools;
</appendix>

51
LDP/guide/docbook/LFS/appendixa/autoconf-desc.xml Normal file
View File

@ -0,0 +1,51 @@
<sect2>
<title>Contents</title>
<para>The Autoconf package contains the autoconf, autoheader, autoreconf,
autoscan, autoupdate and ifnames programs</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>autoconf</title>
<para>Autoconf is a tool for producing shell scripts that automatically
configure software source code packages to adapt to many kinds of
UNIX-like systems. The configuration scripts produced by Autoconf are
independent of Autoconf when they are run, so their users do not need to
have Autoconf.</para></sect3>
<sect3><title>autoheader</title>
<para>The autoheader program can create a template file of C #define
statements for configure to use</para></sect3>
<sect3><title>autoreconf</title>
<para>If there are a lot of Autoconf-generated configure scripts, the
autoreconf program can save some work. It runs autoconf (and
autoheader, where appropriate) repeatedly to remake the Autoconf
configure scripts and configuration header templates in the directory
tree rooted at the current directory.</para></sect3>
<sect3><title>autoscan</title>
<para>The autoscan program can help to create a configure.in file for
a software package. autoscan examines source files in the directory
tree rooted at a directory given as a command line argument, or the
current directory if none is given. It searches the source files for
common portability problems and creates a file configure.scan which
is a preliminary configure.in for that package.</para></sect3>
<sect3><title>autoupdate</title>
<para>The autoupdate program updates a configure.in file that calls
Autoconf macros by their old names to use the current
macro names.</para></sect3>
<sect3><title>ifnames</title>
<para>ifnames can help when writing a configure.in for a software
package. It prints the identifiers that the package already uses in C
preprocessor conditionals. If a package has already been set up to
have some portability, this program can help to figure out what its
configure needs to check for. It may help fill in some gaps in a
configure.in generated by autoscan.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/autoconf.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-autoconf">
<title>Autoconf</title>
<?dbhtml filename="autoconf.html" dir="appendixa"?>
&aa-autoconf-desc;
</sect1>

29
LDP/guide/docbook/LFS/appendixa/automake-desc.xml Normal file
View File

@ -0,0 +1,29 @@
<sect2>
<title>Contents</title>
<para>The Automake package contains the aclocal and automake programs</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>aclocal</title>
<para>Automake includes a number of Autoconf macros which can be used in
packages; some of them are actually required by Automake in certain
situations. These macros must be defined in the aclocal.m4-file;
otherwise they will not be seen by autoconf.</para>
<para>The aclocal program will automatically generate aclocal.m4 files
based on the contents of configure.in. This provides a convenient
way to get Automake-provided macros, without having to search around.
Also, the aclocal mechanism is extensible for use
by other packages.</para></sect3>
<sect3><title>automake</title>
<para>To create all the Makefile.in's for a package, run the automake
program in the top level directory, with no arguments. automake will
automatically find each appropriate Makefile.am (by scanning
configure.in) and generate the corresponding Makefile.in.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/automake.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-automake">
<title>Automake</title>
<?dbhtml filename="automake.html" dir="appendixa"?>
&aa-automake-desc;
</sect1>

16
LDP/guide/docbook/LFS/appendixa/bash-desc.xml Normal file
View File

@ -0,0 +1,16 @@
<sect2>
<title>Contents</title>
<para>The Bash package contains the bash program</para>
</sect2>
<sect2><title>Description</title>
<para>Bash is the Bourne-Again SHell, which is a widely used command
interpreter on Unix systems. Bash is a program that reads from standard
input, the keyboard. A user types something and the program will evaluate
what he has typed and do something with it, like running a program.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/bash.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-bash">
<title>Bash</title>
<?dbhtml filename="bash.html" dir="appendixa"?>
&aa-bash-desc;
</sect1>

34
LDP/guide/docbook/LFS/appendixa/bin86-desc.xml Normal file
View File

@ -0,0 +1,34 @@
<sect2>
<title>Contents</title>
<para>The Bin86 contains the as86, as86_encap, ld86, objdump86, nm86 and
size86 programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>as86</title>
<para>as86 is an assembler for the 8086...80386 processors.</para></sect3>
<sect3><title>as86_encap</title>
<para>as86_encap is a shell script to call as86 and convert the created binary
into a C file prog.v to be included in or linked with programs like boot
block installers.</para></sect3>
<sect3><title>ld86</title>
<para>ld86 understands only the object files produced by the as86 assembler, it
can link them into either an impure or a
separate I&amp;D executable.</para></sect3>
<sect3><title>objdump86</title>
<para>No description available.</para></sect3>
<sect3><title>nm86</title>
<para>No description available.</para></sect3>
<sect3><title>size86</title>
<para>No description available.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/bin86.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-bin86">
<title>Bin86</title>
<?dbhtml filename="bin86.html" dir="appendixa"?>
&aa-bin86-desc;
</sect1>

94
LDP/guide/docbook/LFS/appendixa/binutils-desc.xml Normal file
View File

@ -0,0 +1,94 @@
<sect2>
<title>Contents</title>
<para>The Binutils package contains the addr2line, as, ar, c++filt, gasp,
gprof, ld, nm, objcopy, objdump, ranlib, readelf, size, strings and strip
programs</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>addr2line</title>
<para>addr2line translates program addresses into file names and line numbers.
Given an address and an executable, it uses the debugging information in
the executable to figure out which file name and line number are associated
with a given address.</para></sect3>
<sect3><title>as</title>
<para>as is primarily intended to assemble the output of the GNU C compiler gcc
for use by the linker ld.</para></sect3>
<sect3><title>ar</title>
<para>The ar program creates, modifies, and extracts from archives. An archive
is a single file holding a collection of other files in a structure that makes
it possible to retrieve the original individual files (called members of
the archive).</para></sect3>
<sect3><title>c++filt</title>
<para>The C++ language provides function overloading, which means that it is
possible to
write many functions with the same name (providing each takes parameters
of different types). All C++ function names are encoded into a low-level
assembly label (this process is known as mangling). The c++filt program
does the inverse mapping: it decodes (demangles) low-level names into
user-level names so that the linker can keep these overloaded functions
from clashing.</para></sect3>
<sect3><title>gasp</title>
<para>Gasp is the Assembler Macro Preprocessor.</para></sect3>
<sect3><title>gprof</title>
<para>gprof displays call graph profile data.</para></sect3>
<sect3><title>ld</title>
<para>ld combines a number of object and archive files, relocates their data
and ties up symbol references. Often the last step in building a new compiled
program to run is a call to ld.</para></sect3>
<sect3><title>nm</title>
<para>nm lists the symbols from object files.</para></sect3>
<sect3><title>objcopy</title>
<para>objcopy utility copies the contents of an object file to another. objcopy
uses the GNU BFD Library to read and write the object files. It can write
the destination object file in a format different from that of the source
object file.</para></sect3>
<sect3><title>objdump</title>
<para>objdump displays information about one or more object files. The options
control what particular information to display. This information is mostly
useful to programmers who are working on the compilation tools, as opposed to
programmers who just want their program to compile and work.</para></sect3>
<sect3><title>ranlib</title>
<para>ranlib generates an index to the contents of an archive, and stores it in
the archive. The index lists each symbol defined by a member of an archive
that is a relocatable object file.</para></sect3>
<sect3><title>readelf</title>
<para>readelf displays information about elf type binaries.</para></sect3>
<sect3><title>size</title>
<para>size lists the section sizes --and the total size-- for each of the
object files objfile in its argument list. By default, one line of output is
generated for each object file or each module in an archive.</para></sect3>
<sect3><title>strings</title>
<para>For each file given, strings prints the printable character sequences
that are at least 4 characters long (or the number specified with an
option to the program) and are followed by an unprintable character. By
default, it only prints the strings from the initialized and loaded
sections of object files; for other types of files, it prints the strings
from the whole file.</para>
<para>strings is mainly useful for determining the contents of non-text files.</para></sect3>
<sect3><title>strip</title>
<para>strip discards all or specific symbols from object files. The list of
object files may include archives. At least one object file must be
given. strip modifies the files named in its argument, rather than writing
modified copies under different names.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/binutils.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-binutils">
<title>Binutils</title>
<?dbhtml filename="binutils.html" dir="appendixa"?>
&aa-binutils-desc;
</sect1>

49
LDP/guide/docbook/LFS/appendixa/bison-desc.xml Normal file
View File

@ -0,0 +1,49 @@
<sect2>
<title>Contents</title>
<para>The Bison package contains the bison program.</para>
</sect2>
<sect2><title>Description</title>
<para>Bison is a parser generator, a replacement for YACC. YACC stands for Yet
Another Compiler Compiler. What is Bison then? It is a program that
generates a program that analyzes the structure of a text file. Instead
of
writing the actual program a user specifies how things should be connected
and with
those rules a program is constructed that analyzes the text file.</para>
<para>There are a lot of examples where structure is needed and one of them is
the calculator.</para>
<para>Given the string :</para>
<blockquote><literallayout> 1 + 2 * 3</literallayout></blockquote>
<para>A human can easily come to the result 7. Why? Because of the structure.
Our brain knows
how to interpret the string. The computer doesn't know that and Bison
is a
tool to help it understand by presenting the string in the following way
to the compiler:</para>
<blockquote><literallayout> +
/ \
* 1
/ \
2 3</literallayout></blockquote>
<para>Starting at the bottom of a tree and coming across the numbers 2 and
3 which are joined by the multiplication symbol, the computer
multiplies 2 and 3. The result of that multiplication is remembered and
the next thing that the computer sees is the result of 2*3 and the
number 1 which are joined by the add symbol. Adding 1 to the previous
result makes 7. In calculating the most complex calculations can be
broken down in this tree format and the computer just starts at the
bottom and works its way up to the top and comes with the correct
answer. Of course, Bison isn't only used for calculators alone.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/bison.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-bison">
<title>Bison</title>
<?dbhtml filename="bison.html" dir="appendixa"?>
&aa-bison-desc;
</sect1>

29
LDP/guide/docbook/LFS/appendixa/bzip2-desc.xml Normal file
View File

@ -0,0 +1,29 @@
<sect2>
<title>Contents</title>
<para>The Bzip2 packages contains the bunzip2, bzcat, bzip2 and bzip2recover
programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>bunzip2</title>
<para>Bunzip2 decompresses files that are compressed with bzip2.</para></sect3>
<sect3><title>bzcat</title>
<para>bzcat (or bzip2 -dc) decompresses all specified files to the standard
output.</para></sect3>
<sect3><title>bzip2</title>
<para>bzip2 compresses files using the Burrows-Wheeler block sorting text
compression algorithm, and Huffman coding. Compression is generally
considerably better than that achieved by more conventional LZ77/LZ78-based
compressors, and approaches the performance of the PPM family of statistical
compressors.</para></sect3>
<sect3><title>bzip2recover</title>
<para>bzip2recover recovers data from damaged bzip2 files.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/bzip2.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-bzip2">
<title>Bzip2</title>
<?dbhtml filename="bzip2.html" dir="appendixa"?>
&aa-bzip2-desc;
</sect1>

24
LDP/guide/docbook/LFS/appendixa/diffutils-desc.xml Normal file
View File

@ -0,0 +1,24 @@
<sect2>
<title>Contents</title>
<para>The Diffutils package contains the cmp, diff, diff3 and sdiff programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>cmp and diff</title>
<para>cmp and diff both compare two files and report their differences. Both
programs have extra options which compare files in
different situations.</para></sect3>
<sect3><title>diff3</title>
<para>The difference between diff and diff3 is that diff compares 2 files,
diff3 compares 3 files.</para></sect3>
<sect3><title>sdiff</title>
<para>sdiff merges two files and interactively outputs
the results.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/diffutils.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-diffutils">
<title>Diffutils</title>
<?dbhtml filename="diffutils.html" dir="appendixa"?>
&aa-diffutils-desc;
</sect1>

65
LDP/guide/docbook/LFS/appendixa/e2fsprogs-desc.xml Normal file
View File

@ -0,0 +1,65 @@
<sect2>
<title>Contents</title>
<para>The e2fsprogs package contains the badblocks, chattr, debugfs,
dumpe2fs, e2fsck, e2label, fsck, fsck.ext2, lsattr, mke2fs,
mkfs.ext2, mklost+found, tune2fs and uuidgen programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>badblocks</title>
<para>badblocks is used to search for bad blocks on a device (usually a disk
partition).</para></sect3>
<sect3><title>chattr</title>
<para>chattr changes the file attributes on a Linux second extended file
system. </para></sect3>
<sect3><title>debugfs</title>
<para>The debugfs program is a file system debugger. It can be used to examine
and change the state of an ext2 file system.</para></sect3>
<sect3><title>dumpe2fs</title>
<para>dumpe2fs prints the super block and blocks group information for the
filesystem present on a specified device.</para></sect3>
<sect3><title>e2fsck and fsck.ext2</title>
<para>e2fsck is used to check a Linux second extended file system. fsck.ext2
does the same as e2fsck.</para></sect3>
<sect3><title>e2label</title>
<para>e2label will display or change the filesystem label on the ext2
filesystem located on the specified device.</para></sect3>
<sect3><title>fsck</title>
<para>fsck is used to check and optionally repair a Linux
file system.</para></sect3>
<sect3><title>lsattr</title>
<para>lsattr lists the file attributes on a second extended
file system.</para></sect3>
<sect3><title>mke2fs and mkfs.ext2</title>
<para>mke2fs is used to create a Linux second extended file system on a device
(usually a disk partition). mkfs.ext2 does the same as mke2fs.</para></sect3>
<sect3><title>mklost+found</title>
<para>mklost+found is used to create a lost+found directory in the current
working directory on a Linux second extended file system. mklost+found
pre-allocates disk blocks to the directory to make it
usable by e2fsck.</para></sect3>
<sect3><title>tune2fs</title>
<para>tune2fs adjusts tunable filesystem parameters on a Linux second extended
filesystem.</para></sect3>
<sect3><title>uuidgen</title>
<para>The uuidgen program creates a new universally unique identifier (UUID)
using the libuuid library. The new UUID can reasonably be considered unique
among all UUIDs created on the local system, and among UUIDs created on other
systems in the past and in the future.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/e2fsprogs.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-e2fsprogs">
<title>E2fsprogs</title>
<?dbhtml filename="e2fsprogs.html" dir="appendixa"?>
&aa-e2fsprogs-desc;
</sect1>

15
LDP/guide/docbook/LFS/appendixa/ed-desc.xml Normal file
View File

@ -0,0 +1,15 @@
<sect2>
<title>Contents</title>
<para>The Ed package contains the ed program.</para>
</sect2>
<sect2><title>Description</title>
<para>Ed is a line-oriented text editor. It is used to create, display,
modify and
otherwise manipulate text files.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/ed.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-ed">
<title>Ed</title>
<?dbhtml filename="ed.html" dir="appendixa"?>
&aa-ed-desc;
</sect1>

16
LDP/guide/docbook/LFS/appendixa/file-desc.xml Normal file
View File

@ -0,0 +1,16 @@
<sect2>
<title>Contents</title>
<para>The File package contains the file program.</para>
</sect2>
<sect2><title>Description</title>
<para>File tests each specified file in an attempt to classify it. There are
three sets of tests, performed in this order: filesystem tests,
magic number tests, and language tests. The first test that succeeds
causes the file type to be printed.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/file.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-file">
<title>File</title>
<?dbhtml filename="file.html" dir="appendixa"?>
&aa-file-desc;
</sect1>

96
LDP/guide/docbook/LFS/appendixa/fileutils-desc.xml Normal file
View File

@ -0,0 +1,96 @@
<sect2>
<title>Contents</title>
<para>The Fileutils package contains the chgrp, chmod, chown, cp, dd, df, dir,
dircolors, du, install, ln, ls, mkdir, mkfifo, mknod, mv, rm, rmdir,
shred, sync, touch and vdir programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>chgrp</title>
<para>chgrp changes the group ownership of each given file to the named group,
which can be either a group name or a numeric group ID.</para></sect3>
<sect3><title>chmod</title>
<para>chmod changes the permissions of each given file according to mode, which
can be either a symbolic representation of changes to make, or an octal
number representing the bit pattern for the new permissions.</para></sect3>
<sect3><title>chown</title>
<para>chown changes the user and/or group ownership of each
given file.</para></sect3>
<sect3><title>cp</title>
<para>cp copies files from one place to another.</para></sect3>
<sect3><title>dd</title>
<para>dd copies a file (from the standard input to the standard output, by
default) with a user-selectable blocksize, while optionally performing
conversions on it.</para></sect3>
<sect3><title>df</title>
<para>df displays the amount of disk space available on the filesystem
containing each file name argument. If no file name is given, the space
available on all currently mounted filesystems is shown.</para></sect3>
<sect3><title>dir, ls and vdir</title>
<para>dir and vdir are versions of ls with different default output formats.
These programs list each given file or directory name. Directory contents
are sorted alphabetically. For ls, files are by default listed in columns,
sorted vertically, if the standard output is a terminal; otherwise they
are listed one per line. For dir, files are by default listed in columns,
sorted vertically. For vdir, files are by default listed in
long format.</para></sect3>
<sect3><title>dircolors</title>
<para>dircolors outputs commands to set the LS_COLOR environment variable.
The LS_COLOR variable is use to change the default color scheme used by
ls and related utilities.</para></sect3>
<sect3><title>du</title>
<para>du displays the amount of disk space used by each argument and for each
subdirectory of directory arguments.</para></sect3>
<sect3><title>install</title>
<para>install copies files and sets their permission modes and, if possible,
their owner and group.</para></sect3>
<sect3><title>ln</title>
<para>ln makes hard or soft (symbolic) links between files.</para></sect3>
<sect3><title>mkdir</title>
<para>mkdir creates directories with a given name.</para></sect3>
<sect3><title>mkfifo</title>
<para>mkfifo creates a FIFO with each given name.</para></sect3>
<sect3><title>mknod</title>
<para>mknod creates a FIFO, character special file, or block special file
with the given file name.</para></sect3>
<sect3><title>mv</title>
<para>mv moves files from one directory to another or renames files, depending
on the arguments given to mv.</para></sect3>
<sect3><title>rm</title>
<para>rm removes files or directories.</para></sect3>
<sect3><title>rmdir</title>
<para>rmdir removes directories, if they are empty.</para></sect3>
<sect3><title>shred</title>
<para>shred deletes a file securely, overwriting it first so that its
contents can't be recovered.</para></sect3>
<sect3><title>sync</title>
<para>sync forces changed blocks to disk and updates the
super block.</para></sect3>
<sect3><title>touch</title>
<para>touch changes the access and modification times of each given file to the
current time. Files that do not exist are created empty.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/fileutils.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-fileutils">
<title>Fileutils</title>
<?dbhtml filename="fileutils.html" dir="appendixa"?>
&aa-fileutils-desc;
</sect1>

53
LDP/guide/docbook/LFS/appendixa/findutils-desc.xml Normal file
View File

@ -0,0 +1,53 @@
<sect2>
<title>Contents</title>
<para>The Findutils package contains the bigram, code, find, frcode, locate,
updatedb and xargs programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>bigram</title>
<para>bigram is used together with code to produce older-style locate
databases. To learn more about these last three programs, read the locatedb.5
manual page.</para></sect3>
<sect3><title>code</title>
<para>code is the ancestor of frcode. It was used in older-style locate
databases.</para></sect3>
<sect3><title>find</title>
<para>The find program searches for files in a directory hierarchy which match
a certain criteria. If no criteria is given, it lists all files in the
current directory and its subdirectories.</para></sect3>
<sect3><title>frcode</title>
<para>updatedb runs a program called frcode to compress the list of file names
using front-compression, which reduces the database size by a factor of
4 to 5.</para></sect3>
<sect3><title>locate</title>
<para>Locate scans a database which contain all files and directories on a
filesystem. This program lists the files and directories in this
database matching a certain criteria. If a user is looking for a file this
program will scan the database and tell him exactly where the files he
requested are located. This only makes sense if the locate database is
fairly up-to-date else it will provide out-of-date information.</para></sect3>
<sect3><title>updatedb</title>
<para>The updatedb program updates the locate database. It scans the entire
file system (including other file system that are currently mounted
unless it is told not to do so) and puts every directory and file it finds
into the database that's used by the locate program which retrieves this
information. It's good practice to update this database once a day to
have it up-to-date whenever it is needed.</para></sect3>
<sect3><title>xargs</title>
<para>The xargs command applies a command to a list of files. If there is
a need to perform the same command on multiple files, a file can be created
that contains all these files (one per line) and use xargs to perform that
command on the list.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/findutils.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-findutils">
<title>Findutils</title>
<?dbhtml filename="findutils.html" dir="appendixa"?>
&aa-findutils-desc;
</sect1>

18
LDP/guide/docbook/LFS/appendixa/flex-desc.xml Normal file
View File

@ -0,0 +1,18 @@
<sect2>
<title>Contents</title>
<para>The Flex package contains the flex program</para>
</sect2>
<sect2><title>Description</title>
<para>Flex is a tool for generating programs which recognize patterns in text.
Pattern recognition is very useful in many applications. A user sets up rules
what to look for and flex will make a program that looks for those
patterns. The reason people use flex is that it is much easier to sets up
rules for what to look for than to write the actual program that finds
the text.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/flex.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-flex">
<title>Flex</title>
<?dbhtml filename="flex.html" dir="appendixa"?>
&aa-flex-desc;
</sect1>

34
LDP/guide/docbook/LFS/appendixa/gcc-desc.xml Normal file
View File

@ -0,0 +1,34 @@
<sect2>
<title>Contents</title>
<para>The GCC package contains compilers, preprocessors and the GNU C++
Library.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>Compiler</title>
<para>A compiler translates source code in text format to a format
that a computer understands. After a source code file is compiled into
an object file, a linker will create an executable file from one or more
of these compiler generated object files.</para></sect3>
<sect3><title>Preprocessor</title>
<para>A preprocessor pre-processes a source file, such as including
the contents of header files into the source file. It's a good idea to
not
do this manually to save a lot of time. Someone just inserts a line
like #include &lt;filename&gt;. The preprocessor inserts the
contents of that file into the source file. That's one of the things a
preprocessor does.</para></sect3>
<sect3><title>C++ Library</title>
<para>The C++ library is used by C++ programs. The C++ library contains
functions that are frequently used in C++ programs. This way the
programmer doesn't have to write certain functions (such as writing a
string of text to the screen) from scratch every time he creates a
program.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/gcc.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-gcc">
<title>GCC</title>
<?dbhtml filename="gcc.html" dir="appendixa"?>
&aa-gcc-desc;
</sect1>

40
LDP/guide/docbook/LFS/appendixa/gettext-desc.xml Normal file
View File

@ -0,0 +1,40 @@
<sect2>
<title>Contents</title>
<para>The gettext package contains the gettext, gettextize, msgcmp, msgcomm,
msgfmt, msgmerge, msgunfmt and xgettext programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>gettext</title>
<para>The gettext package is used for internationalization (also known as
i18n) and for localization (also known as l10n). Programs can be
compiled with Native Language Support (NLS) which enable them to output
messages in the users native language rather than in the default English
language.</para></sect3>
<sect3><title>gettextize</title>
<para>No description is currently available for this program.</para></sect3>
<sect3><title>msgcmp</title>
<para>No description is currently available for this program.</para></sect3>
<sect3><title>msgcomm</title>
<para>No description is currently available for this program.</para></sect3>
<sect3><title>msgfmt</title>
<para>No description is currently available for this program.</para></sect3>
<sect3><title>msgmerge</title>
<para>No description is currently available for this program.</para></sect3>
<sect3><title>msgunfmt</title>
<para>No description is currently available for this program.</para></sect3>
<sect3><title>xgettext</title>
<para>No description is currently available for this program.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/gettext.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-gettext">
<title>Gettext</title>
<?dbhtml filename="gettext.html" dir="appendixa"?>
&aa-gettext-desc;
</sect1>

26
LDP/guide/docbook/LFS/appendixa/glibc-desc.xml Normal file
View File

@ -0,0 +1,26 @@
<sect2>
<title>Contents</title>
<para>The Glibc package contains the GNU C Library.</para>
</sect2>
<sect2><title>Description</title>
<para>The C Library is a collection of commonly used functions in programs.
This way a programmer doesn't need to create his own functions for every
single task. The most common things like writing a string to the screen
are already present and at the disposal of the programmer.</para>
<para>The C library (actually almost every library) come in two flavors:
dynamic ones and static ones. In short when a program uses a static C
library, the code from the C library will be copied into the executable
file. When a program uses a dynamic library, that executable will not
contain the code from the C library, but instead a routine that loads
the functions from the library at the time the program is run. This
means a significant decrease in the file size of a program. The
documentation that comes with the C Library describes this in more
detail, as it is too complicated to explain here in one or two lines.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/glibc.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-glibc">
<title>Glibc</title>
<?dbhtml filename="glibc.html" dir="appendixa"?>
&aa-glibc-desc;
</sect1>

23
LDP/guide/docbook/LFS/appendixa/grep-desc.xml Normal file
View File

@ -0,0 +1,23 @@
<sect2>
<title>Contents</title>
<para>The grep package contains the egrep, fgrep and grep programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>egrep</title>
<para>egrep prints lines from files matching an extended regular expression
pattern.</para></sect3>
<sect3><title>fgrep</title>
<para>fgrep prints lines from files matching a list of fixed strings,
separated by newlines, any of which is to be matched.</para></sect3>
<sect3><title>grep</title>
<para>grep prints lines from files matching a basic regular expression
pattern.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/grep.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-grep">
<title>Grep</title>
<?dbhtml filename="grep.html" dir="appendixa"?>
&aa-grep-desc;
</sect1>

116
LDP/guide/docbook/LFS/appendixa/groff-desc.xml Normal file
View File

@ -0,0 +1,116 @@
<sect2>
<title>Contents</title>
<para>The Groff packages contains the addftinfo, afmtodit, eqn, grodvi, groff,
grog, grohtml, grolj4, grops, grotty, hpftodit, indxbib, lkbib, lookbib,
neqn, nroff, pfbtops, pic, psbb, refer, soelim, tbl, tfmtodit and troff
programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>addftinfo</title>
<para>addftinfo reads a troff font file and adds some additional font-metric
information that is used by the groff system.</para></sect3>
<sect3><title>afmtodit</title>
<para>afmtodit creates a font file for use with groff and grops.</para></sect3>
<sect3><title>eqn</title>
<para>eqn compiles descriptions of equations embedded within troff input files
into commands that are understood by troff.</para></sect3>
<sect3><title>grodvi</title>
<para>grodvi is a driver for groff that produces TeX dvi format.</para></sect3>
<sect3><title>groff</title>
<para>groff is a front-end to the groff document formatting system. Normally it
runs the troff program and a post-processor appropriate for the selected
device.</para></sect3>
<sect3><title>grog</title>
<para>grog reads files and guesses which of the groff options -e, -man, -me,
-mm, -ms, -p, -s, and -t are required for printing files, and prints the groff
command including those options on the standard output.</para></sect3>
<sect3><title>grohtml</title>
<para>grohtml translates the output of GNU troff to html</para></sect3>
<sect3><title>grolj4</title>
<para>grolj4 is a driver for groff that produces output in PCL5 format suitable
for an HP Laserjet 4 printer.</para></sect3>
<sect3><title>grops</title>
<para>grops translates the output of GNU troff to Postscript.</para></sect3>
<sect3><title>grotty</title>
<para>grotty translates the output of GNU troff into a form suitable for
typewriter-like devices.</para></sect3>
<sect3><title>hpftodit</title>
<para>hpftodit creates a font file for use with groff -Tlj4 from an HP
tagged font metric file.</para></sect3>
<sect3><title>indxbib</title>
<para>indxbib makes an inverted index for the bibliographic databases a
specified file for use with refer, lookbib, and lkbib.</para></sect3>
<sect3><title>lkbib</title>
<para>lkbib searches bibliographic databases for references that contain
specified keys and prints any references found on the
standard output.</para></sect3>
<sect3><title>lookbib</title>
<para>lookbib prints a prompt on the standard error (unless the standard input
is not a terminal), reads from the standard input a line containing a set
of keywords, searches the bibliographic databases in a specified file for
references containing those keywords, prints any references found on the
standard output, and repeats this process until the end of input.</para></sect3>
<sect3><title>neqn</title>
<para>The neqn script formats equations for ascii output.</para></sect3>
<sect3><title>nroff</title>
<para>The nroff script emulates the nroff command using groff.</para></sect3>
<sect3><title>pfbtops</title>
<para>pfbtops translates a Postscript font in .pfb format
to ASCII.</para></sect3>
<sect3><title>pic</title>
<para>pic compiles descriptions of pictures embedded within troff or TeX input
files into commands that are understood by TeX or troff.</para></sect3>
<sect3><title>psbb</title>
<para>psbb reads a file which should be a Postscript document conforming to the
Document Structuring conventions and looks for a
%%BoundingBox comment.</para></sect3>
<sect3><title>refer</title>
<para>refer copies the contents of a file to the standard output, except that
lines between .[ and .] are interpreted as citations, and lines between .R1
and .R2 are interpreted as commands about how citations are to be
processed.</para></sect3>
<sect3><title>soelim</title>
<para>soelim reads files and replaces lines of the form
<emphasis>.so file</emphasis> by the contents of
<emphasis>file</emphasis>.</para></sect3>
<sect3><title>tbl</title>
<para>tbl compiles descriptions of tables embedded within troff input files
into commands that are understood by troff.</para></sect3>
<sect3><title>tfmtodit</title>
<para>tfmtodit creates a font file for use with <userinput>groff
-Tdvi</userinput></para></sect3>
<sect3><title>troff</title>
<para>troff is highly compatible with Unix troff. Usually it should be invoked
using the groff command, which will also run preprocessors and
post-processors in the appropriate order and with the appropriate
options.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/groff.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-groff">
<title>Groff</title>
<?dbhtml filename="groff.html" dir="appendixa"?>
&aa-groff-desc;
</sect1>

53
LDP/guide/docbook/LFS/appendixa/gzip-desc.xml Normal file
View File

@ -0,0 +1,53 @@
<sect2>
<title>Contents</title>
<para>The Gzip package contains the compress, gunzip, gzexe, gzip, uncompress,
zcat, zcmp, zdiff, zforce, zgrep, zmore and znew programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>gunzip, uncompress</title>
<para>gunzip and uncompress decompress files which are compressed with
gzip.</para></sect3>
<sect3><title>gzexe</title>
<para>gzexe allows you to compress executables in place and have them
automatically uncompress and execute when they are run (at a penalty in
performance).</para></sect3>
<sect3><title>gzip</title>
<para>gzip reduces the size of the named files using
Lempel-Ziv coding (LZ77).</para></sect3>
<sect3><title>zcat</title>
<para>zcat uncompresses either a list of files on the command line or its
standard input and writes the uncompressed data on
standard output</para></sect3>
<sect3><title>zcmp</title>
<para>zcmp invokes the cmp program on compressed files.</para></sect3>
<sect3><title>zdiff</title>
<para>zdiff invokes the diff program on compressed files.</para></sect3>
<sect3><title>zforce</title>
<para>zforce forces a .gz extension on all gzip files so that gzip will not
compress them twice. This can be useful for files with names truncated
after a file transfer.</para></sect3>
<sect3><title>zgrep</title>
<para>zgrep invokes the grep program on compressed files.</para></sect3>
<sect3><title>zmore</title>
<para>zmore is a filter which allows examination of compressed or plain text
files one screen at a time on a soft-copy terminal (similar to the
more program).</para></sect3>
<sect3><title>znew</title>
<para>znew re-compresses files from .Z (compress) format to
.gz (gzip) format.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/gzip.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-gzip">
<title>Gzip</title>
<?dbhtml filename="gzip.html" dir="appendixa"?>
&aa-gzip-desc;
</sect1>

37
LDP/guide/docbook/LFS/appendixa/introduction.xml Normal file
View File

@ -0,0 +1,37 @@
<sect1 id="aa-intro">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="appendixa"?>
<para>This appendix describes the following aspects of every package
that is installed in this book:</para>
<itemizedlist>
<listitem><para>What the package contains.</para></listitem>
<listitem><para>What each program from a package does.</para></listitem>
</itemizedlist>
<para>The packages are listed in the same order as they are installed in
chapter 5 and chapter 6.</para>
<para>Most information about these packages (especially the descriptions of
them) come from the man pages from those packages. We are not going to print
the entire man page, just the core elements to make it possible to
understand what a program does. To get knowledge of all details on a program,
we suggest you start by reading the complete man page in addition to
this appendix.</para>
<para>Certain packages are documented in more depth
than others, because we just happen to know more about certain
packages than I know about others. If anything should be added to the
following descriptions, please don't hesitate to email the mailing
lists. We intend that the list should contain an in-depth description
of every package installed, but we can't do it without help.</para>
<para>Please note that currently only what a package does is described and not
why it needs to be installed. This may be added later.</para>
</sect1>

97
LDP/guide/docbook/LFS/appendixa/kbd-desc.xml Normal file
View File

@ -0,0 +1,97 @@
<sect2>
<title>Contents</title>
<para>The Kbd package contains the chvt, deallocvt, dumpkeys, fgconsole,
getkeycodes, kbd_mode, kbdrate, loadkeys, loadunimap, mapscrn,
psfxtable, resizecons, screendump, setfont,
setkeycodes, setleds, setmetamode, setvesablank, showfont,
showkey, unicode_start, and unicode_stop programs.
There are some other programs that
don't get installed by default, as they are very optional. Take a look at the
Kbd package contents if you have trouble with your console.</para>
</sect2>
<sect2>
<title>Description</title>
<sect3><title>chvt</title>
<para>chvt changes foreground virtual terminal.</para></sect3>
<sect3><title>deallocvt</title>
<para>deallocvt deallocates unused virtual terminals.</para></sect3>
<sect3><title>dumpkeys</title>
<para>dumpkeys dumps keyboard translation tables.</para></sect3>
<sect3><title>fgconsole</title>
<para>fgconsole prints the number of the active virtual terminal.</para></sect3>
<sect3><title>getkeycodes</title>
<para>getkeycodes prints the kernel scancode-to-keycode
mapping table.</para></sect3>
<sect3><title>kbd_mode</title>
<para>kbd_mode reports or sets the keyboard mode.</para></sect3>
<sect3><title>kbdrate</title>
<para>kbdrate sets the keyboard repeat and delay rates.</para></sect3>
<sect3><title>loadkeys</title>
<para>loadkeys loads keyboard translation tables.</para></sect3>
<sect3><title>loadunimap</title>
<para>loadunimap loads the kernel unicode-to-font mapping table.</para></sect3>
<sect3><title>mapscrn</title>
<para>mapscrn loads a user defined output character
mapping table into the console driver. Note that it is obsolete and that its
features are built into setfont.</para></sect3>
<sect3><title>psfxtable</title>
<para>psfxtable is a tool for handling Unicode character tables for
console fonts.</para></sect3>
<sect3><title>resizecons</title>
<para>resizecons changes the kernel idea of the console size.</para></sect3>
<sect3><title>screendump</title>
<para>A screen shot utility for the console.</para></sect3>
<sect3><title>setfont</title>
<para>This lets you change the EGA/VGA fonts in console.</para></sect3>
<sect3><title>setkeycodes</title>
<para>setkeycodes loads kernel scancode-to-keycode mapping
table entries.</para></sect3>
<sect3><title>setleds</title>
<para>setleds sets the keyboard LEDs. Many people find it useful to have numlock
enabled by default, and it is by using this program that you can
achieve this.</para></sect3>
<sect3><title>setmetamode</title>
<para>setmetamode defines the keyboard meta key handling.</para></sect3>
<sect3><title>setvesablank</title>
<para>This lets you fiddle with the built-in hardware screensaver
(not toasters, only a blank screen).</para></sect3>
<sect3><title>showfont</title>
<para>showfont displays data about a font. The information shown includes font
information, font properties, character metrics, and
character bitmaps.</para></sect3>
<sect3><title>showkey</title>
<para>showkey examines the scancodes and keycodes sent by
the keyboard.</para></sect3>
<sect3><title>unicode_start</title>
<para>unicode_start puts the console in Unicode mode.</para></sect3>
<sect3><title>unicode_stop</title>
<para>unicode_stop reverts keyboard and console from
unicode mode.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/kbd.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-kbd">
<title>Kbd</title>
<?dbhtml filename="kbd.html" dir="appendixa"?>
&aa-kbd-desc;
</sect1>

18
LDP/guide/docbook/LFS/appendixa/kernel-desc.xml Normal file
View File

@ -0,0 +1,18 @@
<sect2><title>Contents</title>
<para>The Linux kernel package contains the Linux kernel.</para>
</sect2>
<sect2><title>Description</title>
<para>The Linux kernel is at the core of every Linux system. It's what makes
Linux tick. When a computer is turned on and boots a Linux system, the
very first piece of Linux software that gets loaded is the kernel. The
kernel initializes the system's hardware components such as serial
ports, parallel ports, sound cards, network cards, IDE controllers, SCSI
controllers and a lot more. In a nutshell the kernel makes the hardware
available so that the software can run.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/kernel.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-kernel">
<title>Linux kernel</title>
<?dbhtml filename="kernel.html" dir="appendixa"?>
&aa-kernel-desc;
</sect1>

20
LDP/guide/docbook/LFS/appendixa/less-desc.xml Normal file
View File

@ -0,0 +1,20 @@
<sect2><title>Contents</title>
<para>The Less package contains the less program</para>
</sect2>
<sect2><title>Description</title>
<para>The less program is a file pager (or text viewer). It displays the
contents
of a file with the ability to scroll. Less is an improvement on the
common
pager called <quote>more</quote>. Less has the ability to scroll
backwards
through files as well and it doesn't need to read the entire file when
it
starts, which makes it faster when reading large files.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/less.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-less">
<title>Less</title>
<?dbhtml filename="less.html" dir="appendixa"?>
&aa-less-desc;
</sect1>

23
LDP/guide/docbook/LFS/appendixa/libtool-desc.xml Normal file
View File

@ -0,0 +1,23 @@
<sect2><title>Contents</title>
<para>The Libtool package contains the libtool and libtoolize programs. It
also contains the ltdl library.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>libtool</title>
<para>Libtool provides generalized library-building
support services.</para></sect3>
<sect3><title>libtoolize</title>
<para>libtoolize provides a standard way to add libtool support to a
package.</para></sect3>
<sect3><title>ltdl library</title>
<para>Libtool provides a small library, called `libltdl', that aims at hiding
the various difficulties of dlopening libraries from programmers.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/libtool.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-libtool">
<title>Libtool</title>
<?dbhtml filename="libtool.html" dir="appendixa"?>
&aa-libtool-desc;
</sect1>

14
LDP/guide/docbook/LFS/appendixa/lilo-desc.xml Normal file
View File

@ -0,0 +1,14 @@
<sect2>
<title>Contents</title>
<para>The Lilo package contains the lilo program.</para>
</sect2>
<sect2><title>Description</title>
<para>lilo installs the Linux boot loader which is used to start a Linux
system.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/lilo.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-lilo">
<title>Lilo</title>
<?dbhtml filename="lilo.html" dir="appendixa"?>
&aa-lilo-desc;
</sect1>

19
LDP/guide/docbook/LFS/appendixa/m4-desc.xml Normal file
View File

@ -0,0 +1,19 @@
<sect2>
<title>Contents</title>
<para>The M4 package contains the M4 processor</para>
</sect2>
<sect2>
<title>Description</title>
<para>M4 is a macro processor. It copies input to output expanding macros as it
goes. Macros are either built-in or user-defined and can take any number
of arguments. Besides just doing macro expansion m4 has built-in functions
for including named files, running UNIX commands, doing integer arithmetic,
manipulating text in various ways, recursion, etc. M4 can be used either
as a front-end to a compiler or as a macro processor in its own right.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/m4.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-m4">
<title>M4</title>
<?dbhtml filename="m4.html" dir="appendixa"?>
&aa-m4-desc;
</sect1>

13
LDP/guide/docbook/LFS/appendixa/make-desc.xml Normal file
View File

@ -0,0 +1,13 @@
<sect2><title>Contents</title>
<para>The Make package contains the make program.</para>
</sect2>
<sect2><title>Description</title>
<para>make determines automatically which pieces of a large program need to be
recompiled, and issues the commands to recompile them.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/make.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-make">
<title>Make</title>
<?dbhtml filename="make.html" dir="appendixa"?>
&aa-make-desc;
</sect1>

13
LDP/guide/docbook/LFS/appendixa/makedev-desc.xml Normal file
View File

@ -0,0 +1,13 @@
<sect2><title>Contents</title>
<para>The MAKEDEV package contains the MAKEDEV script.</para>
</sect2>
<sect2><title>Description</title>
<para>MAKEDEV is a script that can help in creating the necessary static
device files that usually reside in the /dev directory.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/makedev.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-makedev">
<title>MAKEDEV</title>
<?dbhtml filename="makedev.html" dir="appendixa"?>
&aa-makedev-desc;
</sect1>

32
LDP/guide/docbook/LFS/appendixa/man-desc.xml Normal file
View File

@ -0,0 +1,32 @@
<sect2><title>Contents</title>
<para>The Man package contains the apropos, makewhatis, man and whatis
programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>apropos</title>
<para>apropos searches a set of database files containing short descriptions
of system commands for keywords and displays the result on the standard
output.</para></sect3>
<sect3><title>makewhatis</title>
<para>makewhatis reads all the manual pages contained in given sections of
manpath or the pre-formatted pages contained in the given sections of
catpath. For each page, it writes a line in the whatis database; each
line consists of the name of the page and a short description,
separated by a dash. The description is extracted using the content of
the NAME section of the manual page.</para></sect3>
<sect3><title>man</title>
<para>man formats and displays the on-line manual pages.</para></sect3>
<sect3><title>whatis</title>
<para>whatis searches a set of database files containing short descriptions
of system commands for keywords and displays the result on the standard
output. Only complete word matches are displayed.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/man.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-man">
<title>Man</title>
<?dbhtml filename="man.html" dir="appendixa"?>
&aa-man-desc;
</sect1>

14
LDP/guide/docbook/LFS/appendixa/manpages-desc.xml Normal file
View File

@ -0,0 +1,14 @@
<sect2><title>Contents</title>
<para>The Man-pages package contains various manual pages that don't come with
the packages.</para>
</sect2>
<sect2><title>Description</title>
<para>Examples of provided manual pages are the manual pages describing all
the C and C++ functions, few important /dev/ files and more.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/manpages.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-man-pages">
<title>Man-pages</title>
<?dbhtml filename="man-pages.html" dir="appendixa"?>
&aa-manpages-desc;
</sect1>

16
LDP/guide/docbook/LFS/appendixa/mawk-desc.xml Normal file
View File

@ -0,0 +1,16 @@
<sect2><title>Contents</title>
<para>The Mawk package contains the mawk program.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>mawk</title>
<para>Mawk is an interpreter for the AWK Programming Language. The AWK
language is useful for manipulation of data files, text retrieval and
processing, and for prototyping and experimenting
with algorithms.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/mawk.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-mawk">
<title>Mawk</title>
<?dbhtml filename="mawk.html" dir="appendixa"?>
&aa-mawk-desc;
</sect1>

54
LDP/guide/docbook/LFS/appendixa/modutils-desc.xml Normal file
View File

@ -0,0 +1,54 @@
<sect2>
<title>Contents</title>
<para>The Modutils package contains the depmod, genksyms, insmod,
insmod_ksymoops_clean, kerneld, kernelversion, ksyms, lsmod, modinfo,
modprobe and rmmod programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>depmod</title>
<para>depmod handles dependency descriptions for loadable
kernel modules.</para></sect3>
<sect3><title>genksyms</title>
<para>genksyms reads (on standard input) the output from gcc -E source.c
and generates a file containing version information.</para></sect3>
<sect3><title>insmod</title>
<para>insmod installs a loadable module in the running kernel.</para></sect3>
<sect3><title>insmod_ksymoops_clean</title>
<para>insmod_ksymoops_clean deletes saved ksyms and modules not accessed in
2 days.</para></sect3>
<sect3><title>kerneld</title>
<para>kerneld performs kernel action in user space (such as on-demand loading
of modules)</para></sect3>
<sect3><title>kernelversion</title>
<para>kernelversion reports the major version of the
running kernel.</para></sect3>
<sect3><title>ksyms</title>
<para>ksyms displays exported kernel symbols.</para></sect3>
<sect3><title>lsmod</title>
<para>lsmod shows information about all loaded modules.</para></sect3>
<sect3><title>modinfo</title>
<para>modinfo examines an object file associated with a kernel module and
displays any information that it can glean.</para></sect3>
<sect3><title>modprobe</title>
<para>Modprobe uses a Makefile-like dependency file, created by depmod,
to automatically load the relevant module(s) from the set of modules
available in predefined directory trees.</para></sect3>
<sect3><title>rmmod</title>
<para>rmmod unloads loadable modules from the running kernel.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/modutils.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-modutils">
<title>Modutils</title>
<?dbhtml filename="modutils.html" dir="appendixa"?>
&aa-modutils-desc;
</sect1>

52
LDP/guide/docbook/LFS/appendixa/ncurses-desc.xml Normal file
View File

@ -0,0 +1,52 @@
<sect2>
<title>Contents</title>
<para>The Ncurses package contains the ncurses, panel, menu and form
libraries. It also contains the clear, infocmp, tic, toe, tput and tset
programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>The libraries</title>
<para>The libraries that make up the Ncurses library are used to display text
(often in a fancy way) on the screen. An example where ncurses is used
is in the kernel's <quote>make menuconfig</quote> process. The libraries
contain routines to create panels, menu's, form and general text display
routines.</para></sect3>
<sect3><title>clear</title>
<para>The clear program clears the screen if this is possible. It looks in
the environment for the terminal type and then in the terminfo database
to figure out how to clear the screen.</para></sect3>
<sect3><title>infocmp</title>
<para>The infocmp program can be used to compare a binary terminfo entry with
other terminfo entries, rewrite a terminfo description to
take advantage of the use= terminfo field, or print out a
terminfo description from the binary file (term) in a variety of
formats (the opposite of what tic does).</para></sect3>
<sect3><title>tic</title>
<para>Tic is the terminfo entry-description compiler. The program translates a
terminfo file from source format into the binary format for use with the
ncurses library routines. Terminfo files contain information about the
capabilities of a terminal.</para></sect3>
<sect3><title>toe</title>
<para>The toe program lists all available terminal types by primary name with
descriptions.</para></sect3>
<sect3><title>tput</title>
<para>The tput program uses the terminfo database to make the values of
terminal-dependent capabilities and information available to the shell,
to initialize or reset the terminal, or return the long name of the
requested terminal type.</para></sect3>
<sect3><title>tset</title>
<para>The Tset program initializes terminals so they can be used, but it's not
widely used anymore. It's provided for 4.4BSD compatibility.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/ncurses.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-ncurses">
<title>Ncurses</title>
<?dbhtml filename="ncurses.html" dir="appendixa"?>
&aa-ncurses-desc;
</sect1>

20
LDP/guide/docbook/LFS/appendixa/netkitbase-desc.xml Normal file
View File

@ -0,0 +1,20 @@
<sect2>
<title>Contents</title>
<para>The Netkit-base package contains the inetd and ping programs.</para>
</sect2>
<sect2>
<title>Description</title>
<sect3><title>inetd</title>
<para>inetd is the mother of all daemons. It listens for connections, and
transfers the call to the appropriate daemon.</para></sect3>
<sect3><title>ping</title>
<para>ping sends ICMP ECHO_REQUEST packets to a host and determines its
response time.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/netkitbase.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-ns-netkitbase">
<title>Netkit-base</title>
<?dbhtml filename="netkit-base.html" dir="appendixa"?>
&aa-netkitbase-desc;
</sect1>

47
LDP/guide/docbook/LFS/appendixa/nettools-desc.xml Normal file
View File

@ -0,0 +1,47 @@
<sect2>
<title>Contents</title>
<para>The Net-tools package contains the arp, hostname, ifconfig, netstat,
plipconfig, rarp, route, and slattach programs.</para>
</sect2>
<sect2>
<title>Description</title>
<sect3><title>arp</title>
<para>arp is used to manipulate the kernel's ARP cache, usually to add
or delete an entry, or to dump the ARP cache.</para></sect3>
<sect3><title>hostname</title>
<para>hostname, with its symlinks domainname, dnsdomainname, nisdomainname,
ypdomainname, and nodename, is used to set or show the system's hostname (or
other, depending on the symlink used).</para></sect3>
<sect3><title>ifconfig</title>
<para>The ifconfig command is the general command used to configure network
interfaces.</para></sect3>
<sect3><title>netstat</title>
<para>netstat is a multi-purpose tool used to print the network connections,
routing tables, interface statistics, masquerade connections, and multicast
memberships.</para></sect3>
<sect3><title>plipconfig</title>
<para>plipconfig is used to fine-tune the PLIP device parameters, hopefully
making it faster.</para></sect3>
<sect3><title>rarp</title>
<para>Akin to the arp program, the rarp program manipulates the system's
RARP table.</para></sect3>
<sect3><title>route</title>
<para>route is the general utility which is used to manipulate the IP
routing table.</para></sect3>
<sect3><title>slattach</title>
<para>slattach attaches a network interface to a serial line, i.e.. puts a
normal terminal line into one of several "network" modes.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/nettools.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-ns-nettools">
<title>Net-tools</title>
<?dbhtml filename="net-tools.html" dir="appendixa"?>
&aa-nettools-desc;
</sect1>

22
LDP/guide/docbook/LFS/appendixa/patch-desc.xml Normal file
View File

@ -0,0 +1,22 @@
<sect2>
<title>Contents</title>
<para>The Patch package contains the patch program.</para>
</sect2>
<sect2><title>Description</title>
<para>The patch program modifies a file according to a patch file. A patch
file usually is a list created by the diff program that contains
instructions on how an original file needs to be modified. Patch is used
a lot for source code patches since it saves time and space. Imagine
a package that is 1MB in size. The next version of that package
only has changes in two files of the first version. It can be shipped as an
entirely new package of 1MB or just as a patch file of 1KB which will
update the first version to make it identical to the second version. So
if the first version was downloaded already, a patch file avoids
a second large download.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/patch.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-patch">
<title>Patch</title>
<?dbhtml filename="patch.html" dir="appendixa"?>
&aa-patch-desc;
</sect1>

16
LDP/guide/docbook/LFS/appendixa/perl-desc.xml Normal file
View File

@ -0,0 +1,16 @@
<sect2>
<title>Contents</title>
<para>The Perl package contains Perl - Practical Extraction and Report
Language</para>
</sect2>
<sect2>
<title>Description</title>
<para>Perl combines the features and capabilities of C, awk, sed and sh into
one powerful programming language.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/perl.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-perl">
<title>Perl</title>
<?dbhtml filename="perl.html" dir="appendixa"?>
&aa-perl-desc;
</sect1>

14
LDP/guide/docbook/LFS/appendixa/procinfo-desc.xml Normal file
View File

@ -0,0 +1,14 @@
<sect2>
<title>Contents</title>
<para>The Procinfo package contains the procinfo program.</para>
</sect2>
<sect2><title>Description</title>
<para>procinfo gathers some system data from the /proc directory
and prints it nicely formatted on the standard output device.</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/procinfo.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-procinfo">
<title>Procinfo</title>
<?dbhtml filename="procinfo.html" dir="appendixa"?>
&aa-procinfo-desc;
</sect1>

60
LDP/guide/docbook/LFS/appendixa/procps-desc.xml Normal file
View File

@ -0,0 +1,60 @@
<sect2>
<title>Contents</title>
<para>The Procps package contains the free, kill, oldps, ps, skill, snice,
sysctl, tload, top, uptime, vmstat, w and watch programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>free</title>
<para>free displays the total amount of free and used physical and swap memory
in the system, as well as the shared memory and buffers used by the
kernel.</para></sect3>
<sect3><title>kill</title>
<para>kills sends signals to processes.</para></sect3>
<sect3><title>oldps and ps</title>
<para>ps gives a snapshot of the current processes.</para></sect3>
<sect3><title>skill</title>
<para>skill sends signals to process matching a criteria.</para></sect3>
<sect3><title>snice</title>
<para>snice changes the scheduling priority for process matching a
criteria.</para></sect3>
<sect3><title>sysctl</title>
<para>sysctl modifies kernel parameters at runtime.</para></sect3>
<sect3><title>tload</title>
<para>tload prints a graph of the current system load average to the
specified tty (or the tty of the tload process if
none is specified).</para></sect3>
<sect3><title>top</title>
<para>top provides an ongoing look at processor activity
in real time.</para></sect3>
<sect3><title>uptime</title>
<para>uptime gives a one line display of the following information: the current
time, how long the system has been running, how many users are currently
logged on, and the system load averages for the past 1, 5, and 15
minutes.</para></sect3>
<sect3><title>vmstat</title>
<para>vmstat reports information about processes, memory, paging, block IO,
traps, and cpu activity.</para></sect3>
<sect3><title>w</title>
<para>w displays information about the users currently on the machine, and
their processes.</para></sect3>
<sect3><title>watch</title>
<para>watch runs command repeatedly, displaying its output (the first
screen full).</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/procps.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-procps">
<title>Procps</title>
<?dbhtml filename="procps.html" dir="appendixa"?>
&aa-procps-desc;
</sect1>

27
LDP/guide/docbook/LFS/appendixa/psmisc-desc.xml Normal file
View File

@ -0,0 +1,27 @@
<sect2>
<title>Contents</title>
<para>The Psmisc package contains the fuser, killall, pidof and pstree
programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>fuser</title>
<para>fuser displays the PIDs of processes using the specified files or file
systems.</para></sect3>
<sect3><title>killall</title>
<para>killall sends a signal to all processes running any of the specified
commands.</para></sect3>
<sect3><title>pidof</title>
<para>Pidof finds the process id's (pids) of the named programs and
prints those id's on standard output.</para></sect3>
<sect3><title>pstree</title>
<para>pstree shows running processes as a tree.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/psmisc.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-psmisc">
<title>Psmisc</title>
<?dbhtml filename="psmisc.html" dir="appendixa"?>
&aa-psmisc-desc;
</sect1>

30
LDP/guide/docbook/LFS/appendixa/reiserfs-desc.xml Normal file
View File

@ -0,0 +1,30 @@
<sect2>
<title>Contents</title>
<para>The reiserfsprogs package contains the debugreiserfs, mkreiserfs,
reiserfsck, resize_reiserfs and unpack programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>debugreiserfs</title>
<para>debugreiserfs can sometimes help to solve problems with reiserfs
filesystems. If it is called without options it prints the super block
of any reiserfs filesystem found on the device.</para></sect3>
<sect3><title>mkreiserfs</title>
<para>mkreiserfs creates a reiserfs file system.</para></sect3>
<sect3><title>reiserfsck</title>
<para>reiserfsck checks a reiserfs file system.</para></sect3>
<sect3><title>resize_reiserfs</title>
<para>resize_reiserfs is used to resize an unmounted reiserfs file
system</para></sect3>
<sect3><title>unpack</title>
<para>No description is currently available for unpack.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/reiserfs.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-reiserfs">
<title>Reiserfsprogs</title>
<?dbhtml filename="reiserfs.html" dir="appendixa"?>
&aa-reiserfs-desc;
</sect1>

14
LDP/guide/docbook/LFS/appendixa/sed-desc.xml Normal file
View File

@ -0,0 +1,14 @@
<sect2>
<title>Contents</title>
<para>The Sed package contains the sed program.</para>
</sect2>
<sect2><title>Description</title>
<para>sed is a stream editor. A stream editor is used to perform basic text
transformations on an input stream (a file or input from a pipeline).</para>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/sed.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-sed">
<title>Sed</title>
<?dbhtml filename="sed.html" dir="appendixa"?>
&aa-sed-desc;
</sect1>

134
LDP/guide/docbook/LFS/appendixa/shadowpwd-desc.xml Normal file
View File

@ -0,0 +1,134 @@
<sect2>
<title>Contents</title>
<para>The Shadow Password Suite contains the chage, chfn, chpasswd, chsh,
dpasswd, expiry, faillog, gpasswd, groupadd, groupdel, groupmod, grpck,
grpconv, grpunconv, lastlog, login, newgrp, passwd, sg, su, logoutd,
mkpasswd, newusers, pwck, pwconv, pwunconv, useradd,
userdel, usermod, vigr and vipw programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>chage</title>
<para>chage changes the number of days between password changes and the date of
the last password change.</para></sect3>
<sect3><title>chfn</title>
<para>chfn changes user full name, office number, office extension, and home
phone number information for a user's account.</para></sect3>
<sect3><title>chpasswd</title>
<para>chpasswd reads a file of user name and password pairs from standard
input and uses this information to update a group of
existing users.</para></sect3>
<sect3><title>chsh</title>
<para>chsh changes the user login shell.</para></sect3>
<sect3><title>dpasswd</title>
<para>dpasswd adds, deletes, and updates dial-up passwords for
user login shells.</para></sect3>
<sect3><title>expiry</title>
<para>Checks and enforces password expiration policy.</para></sect3>
<sect3><title>faillog</title>
<para>faillog formats the contents of the failure log,/var/log/faillog, and
maintains failure counts and limits.</para></sect3>
<sect3><title>gpasswd</title>
<para>gpasswd is used to administer the /etc/group file</para></sect3>
<sect3><title>groupadd</title>
<para>The groupadd command creates a new group account using the values
specified on the command line and the default values from
the system.</para></sect3>
<sect3><title>groupdel</title>
<para>The groupdel command modifies the system account files, deleting all
entries that refer to group.</para></sect3>
<sect3><title>groupmod</title>
<para>The groupmod command modifies the system account files to reflect the
changes that are specified on the command line.</para></sect3>
<sect3><title>grpck</title>
<para>grpck verifies the integrity of the system authentication
information.</para></sect3>
<sect3><title>grpconv</title>
<para>grpunconv converts to shadow group files from normal
group files.</para></sect3>
<sect3><title>grpunconv</title>
<para>grpunconv converts from shadow group files to normal
group files.</para></sect3>
<sect3><title>lastlog</title>
<para>lastlog formats and prints the contents of the last login log,
/var/log/lastlog. The login-name, port, and last login time will be
printed.</para></sect3>
<sect3><title>login</title>
<para>login is used to establish a new session with the system.</para></sect3>
<sect3><title>newgrp</title>
<para>newgrp is used to change the current group ID during a
login session.</para></sect3>
<sect3><title>passwd</title>
<para>passwd changes passwords for user and group accounts.</para></sect3>
<sect3><title>sg</title>
<para>sg executes command as a different group ID.</para></sect3>
<sect3><title>su</title>
<para>Change the effective user id and group id to that of a user. This
replaces the su programs that's installed from the
Shellutils package.</para></sect3>
<sect3><title>logoutd</title>
<para>logoutd enforces the login time and port restrictions specified in
/etc/porttime.</para></sect3>
<sect3><title>mkpasswd</title>
<para>mkpasswd reads a file in the format given by the flags and converts it
to the corresponding database file format.</para></sect3>
<sect3><title>newusers</title>
<para>newusers reads a file of user name and clear text password pairs and uses
this information to update a group of existing users or to create new
users.</para></sect3>
<sect3><title>pwck</title>
<para>pwck verifies the integrity of the system authentication
information.</para></sect3>
<sect3><title>pwconv</title>
<para>pwconv converts to shadow passwd files from normal passwd
files.</para></sect3>
<sect3><title>pwunconv</title>
<para>pwunconv converts from shadow passwd files to normal files.</para></sect3>
<sect3><title>useradd</title>
<para>useradd creates a new user or update default new user
information.</para></sect3>
<sect3><title>userdel</title>
<para>userdel modifies the system account files, deleting all entries that
refer to a specified login name.</para></sect3>
<sect3><title>usermod</title>
<para>usermod modifies the system account files to reflect the changes that
are specified on the command line.</para></sect3>
<sect3><title>vipw and vigr</title>
<para>vipw and vigr will edit the files /etc/passwd and /etc/group,
respectively. With the -s flag, they will edit the shadow versions of
those files, /etc/shadow and /etc/gshadow, respectively.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/shadowpwd.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-shadow">
<title>Shadow Password Suite</title>
<?dbhtml filename="shadow.html" dir="appendixa"?>
&aa-shadowpwd-desc;
</sect1>

132
LDP/guide/docbook/LFS/appendixa/shellutils-desc.xml Normal file
View File

@ -0,0 +1,132 @@
<sect2>
<title>Contents</title>
<para>The Sh-utils package contains the basename, chroot, date, dirname,
echo, env, expr, factor, false, groups, hostid, hostname, id, logname,
nice, nohup, pathchk, pinky, printenv, printf, pwd, seq, sleep, stty,
su, tee, test, true, tty, uname, uptime, users, who, whoami and yes
programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>basename</title>
<para>basename strips directory and suffixes from filenames.</para></sect3>
<sect3><title>chroot</title>
<para>chroot runs a command or interactive shell with special
root directory.</para></sect3>
<sect3><title>date</title>
<para>date displays the current time in a specified format, or sets
the system date.</para></sect3>
<sect3><title>dirname</title>
<para>dirname strips non-directory suffixes from file name.</para></sect3>
<sect3><title>echo</title>
<para>echo displays a line of text.</para></sect3>
<sect3><title>env</title>
<para>env runs a program in a modified environment.</para></sect3>
<sect3><title>expr</title>
<para>expr evaluates expressions.</para></sect3>
<sect3><title>factor</title>
<para>factor prints the prime factors of all specified
integer numbers.</para></sect3>
<sect3><title>false</title>
<para>false always exits with a status code indicating failure.</para></sect3>
<sect3><title>groups</title>
<para>groups prints the groups a user is in.</para></sect3>
<sect3><title>hostid</title>
<para>hostid prints the numeric identifier (in hexadecimal) for the current
host.</para></sect3>
<sect3><title>hostname</title>
<para>hostname sets or prints the name of the current host system</para></sect3>
<sect3><title>id</title>
<para>id prints the real and effective UIDs and GIDs of a user or the current
user.</para></sect3>
<sect3><title>logname</title>
<para>logname prints the current user's login name.</para></sect3>
<sect3><title>nice</title>
<para>nice runs a program with modified scheduling priority.</para></sect3>
<sect3><title>nohup</title>
<para>nohup runs a command immune to hangups, with output to a
non-tty</para></sect3>
<sect3><title>pathchk</title>
<para>pathchk checks whether file names are valid or portable.</para></sect3>
<sect3><title>pinky</title>
<para>pinky is a lightweight finger utility which retrieves information about
a certain user</para></sect3>
<sect3><title>printenv</title>
<para>printenv prints all or part of the environment.</para></sect3>
<sect3><title>printf</title>
<para>printf formats and prints data (the same as the printf C
function).</para></sect3>
<sect3><title>pwd</title>
<para>pwd prints the name of the current/working directory</para></sect3>
<sect3><title>seq</title>
<para>seq prints numbers in a certain range with a certain
increment.</para></sect3>
<sect3><title>sleep</title>
<para>sleep delays for a specified amount of time.</para></sect3>
<sect3><title>stty</title>
<para>stty changes and prints terminal line settings.</para></sect3>
<sect3><title>su</title>
<para>su runs a shell with substitute user and group IDs</para></sect3>
<sect3><title>tee</title>
<para>tee reads from standard input and writes to standard output and
files.</para></sect3>
<sect3><title>test</title>
<para>test checks file types and compares values.</para></sect3>
<sect3><title>true</title>
<para>True always exits with a status code indicating success.</para></sect3>
<sect3><title>tty</title>
<para>tty prints the file name of the terminal connected to standard
input.</para></sect3>
<sect3><title>uname</title>
<para>uname prints system information.</para></sect3>
<sect3><title>uptime</title>
<para>uptime tells how long the system has been running.</para></sect3>
<sect3><title>users</title>
<para>users prints the user names of users currently logged in to the
current host.</para></sect3>
<sect3><title>who</title>
<para>who shows who is logged on.</para></sect3>
<sect3><title>whoami</title>
<para>whoami prints the user's effective userid.</para></sect3>
<sect3><title>yes</title>
<para>yes outputs a string repeatedly until killed.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/shellutils.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-shutils">
<title>Sh-utils</title>
<?dbhtml filename="sh-utils.html" dir="appendixa"?>
&aa-shellutils-desc;
</sect1>

21
LDP/guide/docbook/LFS/appendixa/sysklogd-desc.xml Normal file
View File

@ -0,0 +1,21 @@
<sect2>
<title>Contents</title>
<para>The Sysklogd package contains the klogd and syslogd programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>klogd</title>
<para>klogd is a system daemon which intercepts and logs Linux kernel
messages.</para></sect3>
<sect3><title>syslogd</title>
<para>Syslogd provides a kind of logging that many modern programs use. Every
logged message contains at least a time and a hostname field, normally a
program name field, too, but that depends on how trusty the logging
program is.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/sysklogd.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-sysklogd">
<title>Sysklogd</title>
<?dbhtml filename="sysklogd.html" dir="appendixa"?>
&aa-sysklogd-desc;
</sect1>

86
LDP/guide/docbook/LFS/appendixa/sysvinit-desc.xml Normal file
View File

@ -0,0 +1,86 @@
<sect2>
<title>Contents</title>
<para>The Sysvinit package contains the halt, init, killall5, last,
lastb, mesg, pidof, poweroff, reboot, runlevel, shutdown, sulogin,
telinit, utmpdump, wall,</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>halt</title>
<para>Halt notes that the system is being brought down in the file
/var/log/wtmp, and then either tells the kernel to halt, reboot or
poweroff the system. If halt or reboot is called when the system is not
in runlevel 0 or 6, shutdown will be invoked instead (with
the flag -h or -r).</para></sect3>
<sect3><title>init</title>
<para>Init is the parent of all processes. Its primary role is to create
processes from a script stored in the file /etc/inittab. This
file usually has entries which cause init to spawn gettys on each line that
users can log in. It also controls autonomous processes required by any
particular system.</para></sect3>
<sect3><title>killall5</title>
<para>killall5 is the SystemV killall command. It sends a signal to all
processes except the processes in its own session, so it won't kill the
shell that is running the script it was called from.</para></sect3>
<sect3><title>last</title>
<para>last searches back through the file /var/log/wtmp (or the file designated
by the -f flag) and displays a list of all users logged in (and out)
since that file was created.</para></sect3>
<sect3><title>lastb</title>
<para>lastb is the same as last, except that by default it shows a log of the
file /var/log/btmp, which contains all the bad login attempts.</para></sect3>
<sect3><title>mesg</title>
<para>Mesg controls the access to the users terminal by others. It's typically
used to allow or disallow other users to write to his terminal.</para></sect3>
<sect3><title>pidof</title>
<para>Pidof finds the process id's (pids) of the named programs and prints
those id's on standard output.</para></sect3>
<sect3><title>poweroff</title>
<para>poweroff is equivalent to shutdown -h -p now. It halts the computer and
switches off the computer (when using an APM compliant BIOS and APM is
enabled in the kernel).</para></sect3>
<sect3><title>reboot</title>
<para>reboot is equivalent to shutdown -r now. It reboots
the computer.</para></sect3>
<sect3><title>runlevel</title>
<para>Runlevel reads the system utmp file (typically /var/run/utmp) to locate
the runlevel record, and then prints the previous and current system
runlevel on its standard output, separated by a single space.</para></sect3>
<sect3><title>shutdown</title>
<para>shutdown brings the system down in a secure way. All logged-in users are
notified that the system is going down, and login is blocked.</para></sect3>
<sect3><title>sulogin</title>
<para>sulogin is invoked by init when the system goes into single user mode
(this is done through an entry in /etc/inittab). Init also tries to
execute sulogin when it is passed the -b flag from the boot loader
(eg, LILO).</para></sect3>
<sect3><title>telinit</title>
<para>telinit sends appropriate signals to init, telling it which runlevel to
change to.</para></sect3>
<sect3><title>utmpdump</title>
<para>utmpdumps prints the content of a file (usually /var/run/utmp) on
standard output in a user friendly format.</para></sect3>
<sect3><title>wall</title>
<para>Wall sends a message to everybody logged in with their mesg permission
set to yes.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/sysvinit.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-sysvinit">
<title>Sysvinit</title>
<?dbhtml filename="sysvinit.html" dir="appendixa"?>
&aa-sysvinit-desc;
</sect1>

20
LDP/guide/docbook/LFS/appendixa/tar-desc.xml Normal file
View File

@ -0,0 +1,20 @@
<sect2>
<title>Contents</title>
<para>The tar package contains the rmt and tar programs.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>rmt</title>
<para>rmt is a program used by the remote dump and restore programs in
manipulating a magnetic tape drive through an interprocess communication
connection.</para></sect3>
<sect3><title>tar</title>
<para>tar is an archiving program designed to store and extract files from
an archive file known as a tar file.</para></sect3>
</sect2>

8
LDP/guide/docbook/LFS/appendixa/tar.xml Normal file
View File

@ -0,0 +1,8 @@
<sect1 id="aa-tar">
<title>Tar</title>
<?dbhtml filename="tar.html" dir="appendixa"?>
&aa-tar-desc;
</sect1>

38
LDP/guide/docbook/LFS/appendixa/texinfo-desc.xml Normal file
View File

@ -0,0 +1,38 @@
<sect2>
<title>Contents</title>
<para>The Texinfo package contains the info, install-info, makeinfo, texi2dvi
and texindex programs</para>
</sect2>
<sect2>
<title>Description</title>
<sect3><title>info</title>
<para>The info program reads Info documents, usually contained in the
/usr/doc/info directory. Info documents are like man(ual) pages, but
they tend to be more in depth than just explaining the options to a
program.</para></sect3>
<sect3><title>install-info</title>
<para>The install-info program updates the info entries. When the info
program is run a list with available topics (ie: available info documents) will
be presented. The install-info program is used to maintain this list of
available topics. If info files are removed manually, it is also necessary
to delete the topic in the index file as well. This program is used for
that. It also works the other way around when info documents are
added.</para></sect3>
<sect3><title>makeinfo</title>
<para>The makeinfo program translates Texinfo source documents into various
formats. Available formats are: info files, plain text and HTML.</para></sect3>
<sect3><title>texi2dvi</title>
<para>The texi2dvi program prints Texinfo documents</para></sect3>
<sect3><title>texindex</title>
<para>The texindex program is used to sort Texinfo index files.</para></sect3>
</sect2>

Some files were not shown because too many files have changed in this diff Show More