LDP
/
old-www
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
old-www/LDP/lfs/LFS-BOOK-6.1.1-NOCHUNKS.html

32430 lines
1.3 MiB
Raw Permalink Blame History

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content=
"application/xhtml+xml; charset=iso-8859-1" />
<title>
Linux From Scratch
</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.69.1" />
<style type="text/css">
/*<![CDATA[*/
/* Global settings */
body {
font-family: sans-serif;
text-align: left;
background: #fff;
color: #333;
margin: 1em;
padding: 0;
font-size: 1em;
line-height: 1.2em
}
a:link { color: #22b; }
a:visited { color: #7e4988; }
a:hover, a:focus { color: #d30e08; }
a:active { color: #6b77b1;}
/* Headers */
h1, h2, b, strong {
color: #000;
font-weight: bold;
}
h3, h4, h5, h6 {
color: #222;
}
h1 { font-size: 173%; text-align: center; }
h2 { font-size: 144%; }
h2.subtitle { text-align: center; }
h3 { font-size: 120%; padding-top: 0.2em; margin-top: 0.3em; }
h4 { font-size: 110%;}
h5, h6 { font-size: 110%; font-style: italic; }
/* TOC and Index*/
div.toc ul, div.index ul, div.navheader ul, div.navfooter ul {
list-style: none;
}
div.toc, div.dedication {
padding-left: 1em;
}
li.preface {
margin-left: 1em;
}
div.toc ul li h3, div.toc ul li h4 {
margin: .4em;
}
.item {
width: 15em;
float: left;
}
.secitem {
font-weight: normal;
width: 14em;
float: left;
}
/* Admonitions */
div.note, div.tip {
background-color: #fffff6;
border: 2px solid #dbddec;
width: 90%;
margin: .5em auto;
}
div.important, div.warning, div.caution {
background-color: #fffff6;
border: medium solid #400;
width: 90%;
margin: 1.5em auto;
color: #600;
font-size: larger;
}
div.important h3, div.warning h3, div.caution h3 {
color: #900;
}
h3.admontitle {
padding-left: 2.5em;
padding-top: 1em;
}
div.admonbody {
margin: .5em;
}
div.important em, div.warning em, div.caution em {
color: #000;
font-weight: bold;
}
div.important tt, div.warning tt, div.caution tt {
font-weight: bold;
}
/* variablelist and segmentedlist */
dl {
margin: 0;
padding: 0;
}
dt {
display: list-item;
font-weight: bold;
margin: .33em 0 0 1em;
padding: 0;
}
div.content dt {
list-style: none;
}
dd {
margin: 0 0 1em 3em;
padding: 0;
}
div.variablelist dd {
margin-bottom: 1em;
}
div.variablelist dd p {
margin-top: 0px;
}
dl.materials dd {
margin-left: 0px;
}
div.segmentedlist {
margin-top: 1em;
}
div.segmentedlist p {
margin: 0px auto;
}
/* itemizedlist */
div.itemizedlist {
margin-left: 1em;
}
/* Indented blocks */
p, ul, dl, code, blockquote {
padding-left: 1em;
}
/* Monospaced elements */
tt, code, kbd, pre, .command {
font-family: monospace;
}
pre.userinput {
color: #101310;
background-color: #e5e5e5;
border: 1px solid #050505;
padding: .5em 1em;
margin: 0 2em;
font-weight: bold;
}
pre.screen {
background-color: #e9e9e9;
border: 1px solid #050505;
padding: .5em 1em;
margin: 0 2em;
}
/* Sections */
div.package {
background: #f5f6f7;
border-bottom: 0.2em solid #dbddec;
padding: 0.5em 0.5em 0.3em 0.5em;
margin: 0px auto;
}
div.installation {
padding: 0 0.5em 0.3em 0.5em;
margin: 0.5em 0 0.5em 0;
}
div.configuration {
background: #fefefe;
border-top: 0.2em solid #dbddec;
padding: 0.5em;
margin: 0.5em 0 .5em 0;
}
div.content {
background: #f5f6f7;
border-top: 0.2em solid #dbddec;
border-bottom: 0.2em solid #dbddec;
padding: 0.5em 0.5em 1em 0.5em;
margin: 0.5em 0 .5em 0;
}
div.installation h3.title, div.content h3.title {
padding-top: 0.3em;
margin: 0;
}
div.book, div.preface, div.part, div.chapter, div.sect1, div.index {
padding-bottom: 0.5em;
}
div.preface h2, div.part h1, div.chapter h2.title, div.sect1 h2.title, div.index h1 {
background: #f5f6f7;
border-bottom: .2em solid #dbddec;
border-top: .2em solid #dbddec;
margin-top 1em;
padding: .5em;
text-align: center;
}
div.book h1 {
background: #f5f6f7;
margin: 0px auto;
padding: 0.5em;
}
div.book h2.subtitle {
background: #dbddec;
margin: 0px auto;
padding: 0.2em;
}
div.authorgroup, div p.copyright, div.abstract {
background: #f5f6f7;
margin: 0px auto;
padding: 1em 0.5em;
}
hr {
background: #dbddec;
height: .3em;
border: 0px;
margin: 0px auto;
padding: 0;
}
/*]]>*/
</style>
</head>
<body id="lfs" class="6.1.1">
<div class="book" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title">
<a id="id3480819" name="id3480819"></a>Linux From Scratch
</h1>
</div>
<div>
<h2 class="subtitle">
Version 6.1.1
</h2>
</div>
<div>
<div class="authorgroup">
<div class="author">
<h3 class="author">
<span class="firstname">Gerard</span> <span class=
"surname">Beekmans</span>
</h3>
</div>
</div>
</div>
<div>
<p class="copyright">
Copyright <20> 1999&ndash;2005 Gerard Beekmans
</p>
</div>
<div>
<div class="legalnotice">
<a id="id3481735" name="id3481735"></a>
<p>
Copyright (c) 1999&ndash;2005, Gerard Beekmans
</p>
<p>
All rights reserved.
</p>
<p>
Redistribution and use in source and binary forms, with or
without modification, are permitted provided that the
following conditions are met:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
Redistributions in any form must retain the above
copyright notice, this list of conditions and the
following disclaimer
</p>
</li>
<li>
<p>
Neither the name of &ldquo;<span class="quote">Linux
From Scratch</span>&rdquo; nor the names of its
contributors may be used to endorse or promote products
derived from this material without specific prior
written permission
</p>
</li>
<li>
<p>
Any material derived from Linux From Scratch must
contain a reference to the &ldquo;<span class=
"quote">Linux From Scratch</span>&rdquo; project
</p>
</li>
</ul>
</div>
<p>
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS &ldquo;<span class="quote">AS IS</span>&rdquo;
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGE.
</p>
</div>
</div>
</div>
<hr />
</div>
<div class="toc">
<h3>
Table of Contents
</h3>
<ul>
<li class="preface">
<h4>
Preface
</h4>
<ul>
<li class="sect1">
<a href="#pre-foreword">Foreword</a>
</li>
<li class="sect1">
<a href="#pre-audience">Audience</a>
</li>
<li class="sect1">
<a href="#pre-prerequisites">Prerequisites</a>
</li>
<li class="sect1">
<a href="#pre-hostreqs">Host System Requirements</a>
</li>
<li class="sect1">
<a href="#pre-typography">Typography</a>
</li>
<li class="sect1">
<a href="#pre-organization">Structure</a>
</li>
<li class="sect1">
<a href="#pre-errata">Errata</a>
</li>
</ul>
</li>
<li class="part">
<h3>
I. Introduction
</h3>
<ul>
<li class="chapter">
<h4>
1. Introduction
</h4>
<ul>
<li class="sect1">
<a href="#ch-scatter-how">How to Build an LFS System</a>
</li>
<li class="sect1">
<a href="#ch-scatter-changelog">Changelog</a>
</li>
<li class="sect1">
<a href="#ch-scatter-administrativa">Resources</a>
</li>
<li class="sect1">
<a href="#prepare-askforhelp">Help</a>
</li>
</ul>
</li>
</ul>
</li>
<li class="part">
<h3>
II. Preparing for the Build
</h3>
<ul>
<li class="chapter">
<h4>
2. Preparing a New Partition
</h4>
<ul>
<li class="sect1">
<a href="#space-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#space-creatingpartition">Creating a New
Partition</a>
</li>
<li class="sect1">
<a href="#space-creatingfilesystem">Creating a File
System on the Partition</a>
</li>
<li class="sect1">
<a href="#space-mounting">Mounting the New Partition</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
3. Packages and Patches
</h4>
<ul>
<li class="sect1">
<a href="#materials-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#materials-packages">All Packages</a>
</li>
<li class="sect1">
<a href="#materials-patches">Needed Patches</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
4. Final Preparations
</h4>
<ul>
<li class="sect1">
<a href="#prepare-aboutlfs">About $LFS</a>
</li>
<li class="sect1">
<a href="#ch-tools-creatingtoolsdir">Creating the
$LFS/tools Directory</a>
</li>
<li class="sect1">
<a href="#ch-tools-addinguser">Adding the LFS User</a>
</li>
<li class="sect1">
<a href="#ch-tools-settingenviron">Setting Up the
Environment</a>
</li>
<li class="sect1">
<a href="#prepare-aboutsbus">About SBUs</a>
</li>
<li class="sect1">
<a href="#prepare-abouttestsuites">About the Test
Suites</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
5. Constructing a Temporary System
</h4>
<ul>
<li class="sect1">
<a href="#ch-tools-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#ch-tools-toolchaintechnotes">Toolchain
Technical Notes</a>
</li>
<li class="sect1">
<a href="#ch-tools-binutils-pass1">Binutils-2.15.94.0.2.2
- Pass 1</a>
</li>
<li class="sect1">
<a href="#ch-tools-gcc-pass1">GCC-3.4.3 - Pass 1</a>
</li>
<li class="sect1">
<a href=
"#ch-tools-linux-libc-headers">Linux-Libc-Headers-2.6.11.2</a>
</li>
<li class="sect1">
<a href="#ch-tools-glibc">Glibc-2.3.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-adjusting">Adjusting the Toolchain</a>
</li>
<li class="sect1">
<a href="#ch-tools-tcl">Tcl-8.4.9</a>
</li>
<li class="sect1">
<a href="#ch-tools-expect">Expect-5.43.0</a>
</li>
<li class="sect1">
<a href="#ch-tools-dejagnu">DejaGNU-1.4.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-gcc-pass2">GCC-3.4.3 - Pass 2</a>
</li>
<li class="sect1">
<a href="#ch-tools-binutils-pass2">Binutils-2.15.94.0.2.2
- Pass 2</a>
</li>
<li class="sect1">
<a href="#ch-tools-gawk">Gawk-3.1.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-coreutils">Coreutils-5.2.1</a>
</li>
<li class="sect1">
<a href="#ch-tools-bzip2">Bzip2-1.0.3</a>
</li>
<li class="sect1">
<a href="#ch-tools-gzip">Gzip-1.3.5</a>
</li>
<li class="sect1">
<a href="#ch-tools-diffutils">Diffutils-2.8.1</a>
</li>
<li class="sect1">
<a href="#ch-tools-findutils">Findutils-4.2.23</a>
</li>
<li class="sect1">
<a href="#ch-tools-make">Make-3.80</a>
</li>
<li class="sect1">
<a href="#ch-tools-grep">Grep-2.5.1a</a>
</li>
<li class="sect1">
<a href="#ch-tools-sed">Sed-4.1.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-gettext">Gettext-0.14.3</a>
</li>
<li class="sect1">
<a href="#ch-tools-ncurses">Ncurses-5.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-patch">Patch-2.5.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-tar">Tar-1.15.1</a>
</li>
<li class="sect1">
<a href="#ch-tools-texinfo">Texinfo-4.8</a>
</li>
<li class="sect1">
<a href="#ch-tools-bash">Bash-3.0</a>
</li>
<li class="sect1">
<a href="#ch-tools-m4">M4-1.4.3</a>
</li>
<li class="sect1">
<a href="#ch-tools-bison">Bison-2.0</a>
</li>
<li class="sect1">
<a href="#ch-tools-flex">Flex-2.5.31</a>
</li>
<li class="sect1">
<a href="#ch-tools-util-linux">Util-linux-2.12q</a>
</li>
<li class="sect1">
<a href="#ch-tools-perl">Perl-5.8.7</a>
</li>
<li class="sect1">
<a href="#ch-tools-stripping">Stripping</a>
</li>
</ul>
</li>
</ul>
</li>
<li class="part">
<h3>
III. Building the LFS System
</h3>
<ul>
<li class="chapter">
<h4>
6. Installing Basic System Software
</h4>
<ul>
<li class="sect1">
<a href="#ch-system-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#ch-system-kernfs">Mounting Virtual Kernel File
Systems</a>
</li>
<li class="sect1">
<a href="#ch-system-chroot">Entering the Chroot
Environment</a>
</li>
<li class="sect1">
<a href="#ch-system-changingowner">Changing Ownership</a>
</li>
<li class="sect1">
<a href="#ch-system-creatingdirs">Creating
Directories</a>
</li>
<li class="sect1">
<a href="#ch-system-createfiles">Creating Essential
Symlinks</a>
</li>
<li class="sect1">
<a href="#ch-system-pwdgroup">Creating the passwd, group,
and log Files</a>
</li>
<li class="sect1">
<a href="#ch-system-devices">Populating /dev</a>
</li>
<li class="sect1">
<a href=
"#ch-system-linux-libc-headers">Linux-Libc-Headers-2.6.11.2</a>
</li>
<li class="sect1">
<a href="#ch-system-man-pages">Man-pages-2.01</a>
</li>
<li class="sect1">
<a href="#ch-system-glibc">Glibc-2.3.4</a>
</li>
<li class="sect1">
<a href="#ch-system-readjusting">Re-adjusting the
Toolchain</a>
</li>
<li class="sect1">
<a href="#ch-system-binutils">Binutils-2.15.94.0.2.2</a>
</li>
<li class="sect1">
<a href="#ch-system-gcc">GCC-3.4.3</a>
</li>
<li class="sect1">
<a href="#ch-system-coreutils">Coreutils-5.2.1</a>
</li>
<li class="sect1">
<a href="#ch-system-zlib">Zlib-1.2.3</a>
</li>
<li class="sect1">
<a href="#ch-system-mktemp">Mktemp-1.5</a>
</li>
<li class="sect1">
<a href="#ch-system-iana-etc">Iana-Etc-1.04</a>
</li>
<li class="sect1">
<a href="#ch-system-findutils">Findutils-4.2.23</a>
</li>
<li class="sect1">
<a href="#ch-system-gawk">Gawk-3.1.4</a>
</li>
<li class="sect1">
<a href="#ch-system-ncurses">Ncurses-5.4</a>
</li>
<li class="sect1">
<a href="#ch-system-readline">Readline-5.0</a>
</li>
<li class="sect1">
<a href="#ch-system-vim">Vim-6.3</a>
</li>
<li class="sect1">
<a href="#ch-system-m4">M4-1.4.3</a>
</li>
<li class="sect1">
<a href="#ch-system-bison">Bison-2.0</a>
</li>
<li class="sect1">
<a href="#ch-system-less">Less-382</a>
</li>
<li class="sect1">
<a href="#ch-system-groff">Groff-1.19.1</a>
</li>
<li class="sect1">
<a href="#ch-system-sed">Sed-4.1.4</a>
</li>
<li class="sect1">
<a href="#ch-system-flex">Flex-2.5.31</a>
</li>
<li class="sect1">
<a href="#ch-system-gettext">Gettext-0.14.3</a>
</li>
<li class="sect1">
<a href="#ch-system-inetutils">Inetutils-1.4.2</a>
</li>
<li class="sect1">
<a href="#ch-system-iproute2">IPRoute2-2.6.11-050330</a>
</li>
<li class="sect1">
<a href="#ch-system-perl">Perl-5.8.7</a>
</li>
<li class="sect1">
<a href="#ch-system-texinfo">Texinfo-4.8</a>
</li>
<li class="sect1">
<a href="#ch-system-autoconf">Autoconf-2.59</a>
</li>
<li class="sect1">
<a href="#ch-system-automake">Automake-1.9.5</a>
</li>
<li class="sect1">
<a href="#ch-system-bash">Bash-3.0</a>
</li>
<li class="sect1">
<a href="#ch-system-file">File-4.13</a>
</li>
<li class="sect1">
<a href="#ch-system-libtool">Libtool-1.5.14</a>
</li>
<li class="sect1">
<a href="#ch-system-bzip2">Bzip2-1.0.3</a>
</li>
<li class="sect1">
<a href="#ch-system-diffutils">Diffutils-2.8.1</a>
</li>
<li class="sect1">
<a href="#ch-system-kbd">Kbd-1.12</a>
</li>
<li class="sect1">
<a href="#ch-system-e2fsprogs">E2fsprogs-1.37</a>
</li>
<li class="sect1">
<a href="#ch-system-grep">Grep-2.5.1a</a>
</li>
<li class="sect1">
<a href="#ch-system-grub">GRUB-0.96</a>
</li>
<li class="sect1">
<a href="#ch-system-gzip">Gzip-1.3.5</a>
</li>
<li class="sect1">
<a href="#ch-system-hotplug">Hotplug-2004_09_23</a>
</li>
<li class="sect1">
<a href="#ch-system-man">Man-1.5p</a>
</li>
<li class="sect1">
<a href="#ch-system-make">Make-3.80</a>
</li>
<li class="sect1">
<a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a>
</li>
<li class="sect1">
<a href="#ch-system-patch">Patch-2.5.4</a>
</li>
<li class="sect1">
<a href="#ch-system-procps">Procps-3.2.5</a>
</li>
<li class="sect1">
<a href="#ch-system-psmisc">Psmisc-21.6</a>
</li>
<li class="sect1">
<a href="#ch-system-shadow">Shadow-4.0.9</a>
</li>
<li class="sect1">
<a href="#ch-system-sysklogd">Sysklogd-1.4.1</a>
</li>
<li class="sect1">
<a href="#ch-system-sysvinit">Sysvinit-2.86</a>
</li>
<li class="sect1">
<a href="#ch-system-tar">Tar-1.15.1</a>
</li>
<li class="sect1">
<a href="#ch-system-udev">Udev-056</a>
</li>
<li class="sect1">
<a href="#ch-system-util-linux">Util-linux-2.12q</a>
</li>
<li class="sect1">
<a href="#ch-system-aboutdebug">About Debugging
Symbols</a>
</li>
<li class="sect1">
<a href="#ch-system-strippingagain">Stripping Again</a>
</li>
<li class="sect1">
<a href="#ch-system-revisedchroot">Cleaning Up</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
7. Setting Up System Bootscripts
</h4>
<ul>
<li class="sect1">
<a href="#ch-scripts-introduction">Introduction</a>
</li>
<li class="sect1">
<a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a>
</li>
<li class="sect1">
<a href="#ch-scripts-usage">How Do These Bootscripts
Work?</a>
</li>
<li class="sect1">
<a href="#ch-scripts-udev">Device and Module Handling on
an LFS System</a>
</li>
<li class="sect1">
<a href="#ch-scripts-setclock">Configuring the setclock
Script</a>
</li>
<li class="sect1">
<a href="#ch-scripts-console">Configuring the Linux
Console</a>
</li>
<li class="sect1">
<a href="#ch-scripts-sysklogd">Configuring the sysklogd
script</a>
</li>
<li class="sect1">
<a href="#ch-scripts-inputrc">Creating the /etc/inputrc
File</a>
</li>
<li class="sect1">
<a href="#ch-scripts-profile">The Bash Shell Startup
Files</a>
</li>
<li class="sect1">
<a href="#ch-scripts-hostname">Configuring the localnet
Script</a>
</li>
<li class="sect1">
<a href="#ch-scripts-hosts">Creating the /etc/hosts
File</a>
</li>
<li class="sect1">
<a href="#ch-scripts-network">Configuring the network
Script</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
8. Making the LFS System Bootable
</h4>
<ul>
<li class="sect1">
<a href="#ch-bootable-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#ch-bootable-fstab">Creating the /etc/fstab
File</a>
</li>
<li class="sect1">
<a href="#ch-bootable-kernel">Linux-2.6.11.12</a>
</li>
<li class="sect1">
<a href="#ch-bootable-grub">Making the LFS System
Bootable</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
9. The End
</h4>
<ul>
<li class="sect1">
<a href="#ch-finish-theend">The End</a>
</li>
<li class="sect1">
<a href="#ch-finish-getcounted">Get Counted</a>
</li>
<li class="sect1">
<a href="#ch-finish-reboot">Rebooting the System</a>
</li>
<li class="sect1">
<a href="#ch-finish-whatnow">What Now?</a>
</li>
</ul>
</li>
</ul>
</li>
<li class="part">
<h3>
IV. Appendices
</h3>
<ul>
<li class="appendix">
<a href="#appendixa">A. Acronyms and Terms</a>
</li>
<li class="appendix">
<a href="#appendixb">B. Acknowledgments</a>
</li>
</ul>
</li>
<li class="index">
<h3>
<a href="#id3521702">Index</a>
</h3>
</li>
</ul>
</div>
<div class="preface" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="preface" name="preface"></a>Preface
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="pre-foreword" name=
"pre-foreword"></a>1.&nbsp;Foreword
</h2>
</div>
</div>
</div>
<p>
My adventures in Linux began in 1998 when I downloaded and
installed my first distribution. After working with it for a
while, I discovered issues I definitely would have liked to see
improved upon. For example, I didn't like the arrangement of the
bootscripts or the way programs were configured by default. I
tried a number of alternative distributions to address these
issues, yet each had its pros and cons. Finally, I realized that
if I wanted full satisfaction from my Linux system, I would have
to build my own from scratch.
</p>
<p>
What does this mean? I resolved not to use pre-compiled packages
of any kind, nor CD-ROMs or boot disks that would install basic
utilities. I would use my current Linux system to develop my own
customized system. This &ldquo;<span class=
"quote">perfect</span>&rdquo; Linux system would then have the
strengths of various systems without their associated weaknesses.
In the beginning, the idea was rather daunting, but I remained
committed to the idea that a system could be built that would
conform to my needs and desires rather than to a standard that
just did not fit what I was looking for.
</p>
<p>
After sorting through issues such as circular dependencies and
compile-time errors, I created a custom-built Linux system that
was fully operational and suitable to individual needs. This
process also allowed me to create compact and streamlined Linux
systems which are faster and take up less space than traditional
operating systems. I called this system a Linux From Scratch
system, or an LFS system for short.
</p>
<p>
As I shared my goals and experiences with other members of the
Linux community, it became apparent that there was sustained
interest in the ideas set forth in my Linux adventures. Such
custom-built LFS systems serve not only to meet user
specifications and requirements, but also serve as an ideal
learning opportunity for programmers and system administrators to
enhance their Linux skills. Out of this broadened interest, the
Linux From Scratch Project was born.
</p>
<p>
This <span class="emphasis"><em>Linux From Scratch</em></span>
book provides readers with the background and instruction to
design and build custom Linux systems. This book highlights the
Linux from Scratch project and the benefits of using this system.
Users can dictate all aspects of their system, including
directory layout, script setup, and security. The resulting
system will be compiled completely from the source code, and the
user will be able to specify where, why, and how programs are
installed. This book allows readers to fully customize Linux
systems to their own needs and allows users more control over
their system.
</p>
<p>
I hope you will have a great time working on your own LFS system,
and enjoy the numerous benefits of having a system that is truly
<span class="emphasis"><em>your own</em></span>.
</p>
<div class="literallayout">
<p>
--<br />
Gerard&nbsp;Beekmans<br />
gerard AT linuxfromscratch D0T org
</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="pre-audience" name=
"pre-audience"></a>2.&nbsp;Audience
</h2>
</div>
</div>
</div>
<p>
There are many reasons why somebody would want to read this book.
The principal reason is to install a Linux system from the source
code. A question many people raise is, &ldquo;<span class=
"quote">why go through all the hassle of manually building a
Linux system from scratch when you can just download and install
an existing one?</span>&rdquo; That is a good question and is the
impetus for this section of the book.
</p>
<p>
One important reason for LFS's existence is to help people learn
how a Linux system works from the inside out. Building an LFS
system helps demonstrate what makes Linux tick, and how things
work together and depend on each other. One of the best things
that this learning experience provides is the ability to
customize Linux to your own tastes and needs.
</p>
<p>
A key benefit of LFS is that it allows users to have more control
over the system without relying on someone else's Linux
implementation. With LFS, <span class=
"emphasis"><em>you</em></span> are in the driver's seat and
dictate every aspect of the system, such as the directory layout
and bootscript setup. You also dictate where, why, and how
programs are installed.
</p>
<p>
Another benefit of LFS is the ability to create a very compact
Linux system. When installing a regular distribution, one is
often forced to include several programs which are probably never
used. These programs waste disk space, or worse, CPU cycles. It
is not difficult to build an LFS system of less than 100
megabytes (MB), which is substantially smaller than the majority
of existing installations. Does this still sound like a lot of
space? A few of us have been working on creating a very small
embedded LFS system. We successfully built a system that was
specialized to run the Apache web server with approximately 8MB
of disk space used. Further stripping could bring this down to 5
MB or less. Try that with a regular distribution! This is only
one of the many benefits of designing your own Linux
implementation.
</p>
<p>
We could compare Linux distributions to a hamburger purchased at
a fast-food restaurant&mdash;you have no idea what might be in
what you are eating. LFS, on the other hand, does not give you a
hamburger. Rather, LFS provides the recipe to make the exact
hamburger desired. This allows users to review the recipe, omit
unwanted ingredients, and add your own ingredients to enhance the
flavor of the burger. When you are satisfied with the recipe,
move on to preparing it. It can be made to exact
specifications&mdash;broil it, bake it, deep-fry it, or barbecue
it.
</p>
<p>
Another analogy that we can use is that of comparing LFS with a
finished house. LFS provides the skeletal plan of a house, but it
is up to you to build it. LFS maintains the freedom to adjust
plans throughout the process, customizing it to the user's needs
and preferences.
</p>
<p>
An additional advantage of a custom built Linux system is
security. By compiling the entire system from source code, you
are empowered to audit everything and apply all the security
patches desired. It is no longer necessary to wait for somebody
else to compile binary packages that fix a security hole. Unless
you examine the patch and implement it yourself, you have no
guarantee that the new binary package was built correctly and
adequately fixes the problem.
</p>
<p>
The goal of Linux From Scratch is to build a complete and usable
foundation-level system. Readers who do not wish to build their
own Linux system from scratch may not benefit from the
information in this book. If you only want to know what happens
while the computer boots, we recommend the &ldquo;<span class=
"quote">From Power Up To Bash Prompt</span>&rdquo; HOWTO located
at <a href=
"http://axiom.anu.edu.au/~okeefe/p2b/"><i>http://axiom.anu.edu.au/~okeefe/p2b/</i></a>
or on The Linux Documentation Project's (TLDP) website at
<a href="http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html">
<i>http://www.tldp.org/HOWTO/From-PowerUp-To-Bash-Prompt-HOWTO.html</i></a>.
The HOWTO builds a system which is similar to that of this book,
but it focuses strictly on creating a system capable of booting
to a BASH prompt. Consider your objective. If you wish to build a
Linux system while learning along the way, then this book is your
best choice.
</p>
<p>
There are too many good reasons to build your own LFS system to
list them all here. This section is only the tip of the iceberg.
As you continue in your LFS experience, you will find the power
that information and knowledge truly bring.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="pre-prerequisites" name=
"pre-prerequisites"></a>3.&nbsp;Prerequisites
</h2>
</div>
</div>
</div>
<p>
Building an LFS system is not a simple task. It requires a
certain level of existing knowledge of Unix system administration
in order to resolve problems, and correctly execute the commands
listed. In particular, as an absolute minimum, the reader should
already have the ability to use the command line (shell) to copy
or move files and directories, list directory and file contents,
and change the current directory. It is also expected that the
reader has a reasonable knowledge of using and installing Linux
software.
</p>
<p>
Because the LFS book assumes <span class="emphasis"><em>at
least</em></span> this basic level of skill, the various LFS
support forums are unlikely to be able to provide you with much
assistance; you will find that your questions regarding such
basic knowledge will likely go unanswered, or you will simply be
referred to the LFS essential pre-reading list.
</p>
<p>
Before building an LFS system, we recommend reading the following
HOWTOs:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
Software-Building-HOWTO <a href=
"http://www.tldp.org/HOWTO/Software-Building-HOWTO.html"><i>
http://www.tldp.org/HOWTO/Software-Building-HOWTO.html</i></a>
</p>
<p>
This is a comprehensive guide to building and installing
&ldquo;<span class="quote">generic</span>&rdquo; Unix
software distributions under Linux.
</p>
</li>
<li>
<p>
The Linux Users' Guide <a href=
"http://www.linuxhq.com/guides/LUG/guide.html"><i>http://www.linuxhq.com/guides/LUG/guide.html</i></a>
</p>
<p>
This guide covers the usage of assorted Linux software.
</p>
</li>
<li>
<p>
The Essential Pre-Reading Hint <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/essential_prereading.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/essential_prereading.txt</i></a>
</p>
<p>
This is an LFS Hint written specifically for users new to
Linux. It includes a list of links to excellent sources of
information on a wide range of topics. Anyone attempting to
install LFS should have an understanding of many of the
topics in this hint.
</p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="pre-hostreqs" name="pre-hostreqs"></a>4.&nbsp;Host
System Requirements
</h2>
</div>
</div>
</div>
<p>
The host must be running at least a 2.6.2 kernel compiled with
GCC-3.0 or higher. There are two main reasons for this
requirement. First, the Native POSIX Threading Library (NPTL)
test suite will segfault if the host's kernel has not been
compiled with GCC-3.0 or a later version. Second, the 2.6.2 or
later version of the kernel is required for the use of Udev. Udev
creates devices dynamically by reading from the <tt class=
"systemitem">sysfs</tt> file system. However, support for this
filesystem has only recently been implemented in most of the
kernel drivers. We must be sure that all critical system devices
get created properly.
</p>
<p>
In order to determine whether the host kernel meets the
requirements outlined above, run the following command:
</p>
<pre class="userinput"><kbd class=
"command">cat /proc/version</kbd></pre>
<p>
This will produce output similar to:
</p>
<pre class="screen"><tt class=
"computeroutput">Linux version 2.6.2 (user@host) (gcc version 3.4.0) #1
Tue Apr 20 21:22:18 GMT 2004</tt></pre>
<p>
If the results of the above command do not state that the host
kernel is either 2.6.2 (or later), or that it was not compiled
using a GCC-3.0 (or later) compiler, one will need to be
installed. There are two methods you can take to solve this.
First, see if your Linux vendor provides a 2.6.2 (or later)
kernel package. If so, you may wish to install it. If your vendor
doesn't offer a 2.6.2 (or later) kernel package, or you would
prefer not to install it, then you can compile a 2.6 kernel
yourself. Instructions for compiling the kernel and configuring
the boot loader (assuming the host uses GRUB) are located in
<a href="#chapter-bootable">Chapter 8</a>. This second option can
also be seen as a gauge of your current Linux skills. If this
second requirement is too steep, then the LFS book will not
likely be much use to you at this time.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="pre-typography" name=
"pre-typography"></a>5.&nbsp;Typography
</h2>
</div>
</div>
</div>
<p>
To make things easier to follow, there are a few typographical
conventions used throughout this book. This section contains some
examples of the typographical format found throughout Linux From
Scratch.
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
This form of text is designed to be typed exactly as seen unless
otherwise noted in the surrounding text. It is also used in the
explanation sections to identify which of the commands is being
referenced.
</p>
<pre class="screen"><tt class=
"computeroutput">install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'</tt></pre>
<p>
This form of text (fixed-width text) shows screen output,
probably as the result of commands issued. This format is also
used to show filenames, such as <tt class=
"filename">/etc/ld.so.conf</tt>.
</p>
<p>
<span class="emphasis"><em>Emphasis</em></span>
</p>
<p>
This form of text is used for several purposes in the book. Its
main purpose is to emphasize important points or items.
</p>
<p>
<a href=
"http://www.linuxfromscratch.org/"><i>http://www.linuxfromscratch.org/</i></a>
</p>
<p>
This format is used for hyperlinks both within the LFS community
and to external pages. It includes HOWTOs, download locations,
and websites.
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; $LFS/etc/group &lt;&lt; "EOF"
<tt class="literal">root:x:0:
bin:x:1:
......</tt>
EOF</kbd></pre>
<p>
This format is used when creating configuration files. The first
command tells the system to create the file <tt class=
"filename">$LFS/etc/group</tt> from whatever is typed on the
following lines until the sequence end of file (EOF) is
encountered. Therefore, this entire section is generally typed as
seen.
</p>
<p>
<em class="replaceable"><tt>[REPLACED TEXT]</tt></em>
</p>
<p>
This format is used to encapsulate text that is not to be typed
as seen or copied-and-pasted.
</p>
<p>
<tt class="filename">passwd(5)</tt>
</p>
<p>
This format is used to refer to a specific manual page
(hereinafter referred to simply as a &ldquo;<span class=
"quote">man</span>&rdquo; page). The number inside parentheses
indicates a specific section inside of <span><strong class=
"command">man</strong></span>. For example, <span><strong class=
"command">passwd</strong></span> has two man pages. Per LFS
installation instructions, those two man pages will be located at
<tt class="filename">/usr/share/man/man1/passwd.1</tt> and
<tt class="filename">/usr/share/man/man5/passwd.5</tt>. Both man
pages have different information in them. When the book uses
<tt class="filename">passwd(5)</tt> it is specifically referring
to <tt class="filename">/usr/share/man/man5/passwd.5</tt>.
<span><strong class="command">man passwd</strong></span> will
print the first man page it finds that matches
&ldquo;<span class="quote">passwd</span>&rdquo;, which will be
<tt class="filename">/usr/share/man/man1/passwd.1</tt>. For this
example, you will need to run <span><strong class="command">man 5
passwd</strong></span> in order to read the specific page being
referred to. It should be noted that most man pages do not have
duplicate page names in different sections. Therefore,
<span><strong class="command">man <em class=
"replaceable"><tt>[program name]</tt></em></strong></span> is
generally sufficient.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="pre-organization" name=
"pre-organization"></a>6.&nbsp;Structure
</h2>
</div>
</div>
</div>
<p>
This book is divided into the following parts.
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.1. Part I - Introduction
</h3>
</div>
<p>
Part I explains a few important notes on how to proceed with
the LFS installation. This section also provides
meta-information about the book.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.2. Part II - Preparing for the Build
</h3>
</div>
<p>
Part II describes how to prepare for the building
process&mdash;making a partition, downloading the packages, and
compiling temporary tools.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.3. Part III - Building the LFS System
</h3>
</div>
<p>
Part III guides the reader through the building of the LFS
system&mdash;compiling and installing all the packages one by
one, setting up the boot scripts, and installing the kernel.
The resulting Linux system is the foundation on which other
software can be built to expand the system as desired. At the
end of this book, there is an easy to use reference listing all
of the programs, libraries, and important files that have been
installed.
</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="pre-errata" name="pre-errata"></a>7.&nbsp;Errata
</h2>
</div>
</div>
</div>
<p>
The software used to create an LFS system is constantly being
updated and enhanced. Security warnings and bug fixes may become
available after the LFS book has been released. To check whether
the package versions or instructions in this release of LFS need
any modifications to accommodate security vulnerabilities or
other bug fixes, please visit <a href=
"http://www.linuxfromscratch.org/lfs/errata/6.1.1/"><i>http://www.linuxfromscratch.org/lfs/errata/6.1.1/</i></a>
before proceeding with your build. You should note any changes
shown and apply them to the relevant section of the book as you
progress with building the LFS system.
</p>
</div>
</div>
<div class="part" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title">
<a id="part1" name="part1"></a>Part&nbsp;I.&nbsp;Introduction
</h1>
</div>
</div>
</div>
<div class="toc">
<h3>
Table of Contents
</h3>
<ul>
<li class="chapter">
<h4>
1. Introduction
</h4>
<ul>
<li class="sect1">
<a href="#ch-scatter-how">How to Build an LFS System</a>
</li>
<li class="sect1">
<a href="#ch-scatter-changelog">Changelog</a>
</li>
<li class="sect1">
<a href="#ch-scatter-administrativa">Resources</a>
</li>
<li class="sect1">
<a href="#prepare-askforhelp">Help</a>
</li>
</ul>
</li>
</ul>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-intro" name=
"chapter-intro"></a>Chapter&nbsp;1.&nbsp;Introduction
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scatter-how" name=
"ch-scatter-how"></a>1.1.&nbsp;How to Build an LFS System
</h2>
</div>
</div>
</div>
<p>
The LFS system will be built by using a previously installed
Linux distribution (such as Debian, Mandrake, Red Hat, or
SuSE). This existing Linux system (the host) will be used as a
starting point to provide necessary programs, including a
compiler, linker, and shell, to build the new system. Select
the &ldquo;<span class="quote">development</span>&rdquo; option
during the distribution installation to be able to access these
tools.
</p>
<p>
As an alternative to installing an entire separate distribution
onto your machine, you may wish to use the Linux From Scratch
LiveCD. The CD works well as a host system, providing all the
tools you need to successfully follow the instructions in this
book. Additionally, it contains all the source packages,
patches and a copy of this book. So once you have the CD, no
network connection or additional downloads are necessary. For
more information about the LFS LiveCD or to download a copy,
visit <a href=
"http://www.linuxfromscratch.org/livecd/"><i>http://www.linuxfromscratch.org/livecd/</i></a>.
</p>
<p>
<a href="#chapter-partitioning">Chapter 2</a> of this book
describes how to create a new Linux native partition and file
system, the place where the new LFS system will be compiled and
installed. <a href="#chapter-getting-materials">Chapter 3</a>
explains which packages and patches need to be downloaded to
build an LFS system and how to store them on the new file
system. <a href="#chapter-final-preps">Chapter 4</a> discusses
the setup for an appropriate working environment. Please read
<a href="#chapter-final-preps">Chapter 4</a> carefully as it
explains several important issues the developer should be aware
of before beginning to work through <a href=
"#chapter-temporary-tools">Chapter 5</a> and beyond.
</p>
<p>
<a href="#chapter-temporary-tools">Chapter 5</a> explains the
installation of a number of packages that will form the basic
development suite (or toolchain) which is used to build the
actual system in <a href="#chapter-building-system">Chapter
6</a>. Some of these packages are needed to resolve circular
dependencies&mdash;for example, to compile a compiler, you need
a compiler.
</p>
<p>
<a href="#chapter-temporary-tools">Chapter 5</a> also shows the
user how to build a first pass of the toolchain, including
Binutils and GCC (first pass basically means these two core
packages will be re-installed a second time). The next step is
to build Glibc, the C library. Glibc will be compiled by the
toolchain programs built in the first pass. Then, a second pass
of the toolchain will be built. This time, the toolchain will
be dynamically linked against the newly built Glibc. The
remaining <a href="#chapter-temporary-tools">Chapter 5</a>
packages are built using this second pass toolchain. When this
is done, the LFS installation process will no longer depend on
the host distribution, with the exception of the running
kernel.
</p>
<p>
This effort to isolate the new system from the host
distribution may seem excessive, but a full technical
explanation is provided in <a href=
"#ch-tools-toolchaintechnotes" title=
"5.2.&nbsp;Toolchain Technical Notes">Section&nbsp;5.2,
&ldquo;Toolchain Technical Notes&rdquo;</a>.
</p>
<p>
In <a href="#chapter-building-system">Chapter 6</a>, the full
LFS system is built. The <span><strong class=
"command">chroot</strong></span> (change root) program is used
to enter a virtual environment and start a new shell whose root
directory will be set to the LFS partition. This is very
similar to rebooting and instructing the kernel to mount the
LFS partition as the root partition. The system does not
actually reboot, but instead <span><strong class=
"command">chroot</strong></span>'s because creating a bootable
system requires additional work which is not necessary just
yet. The major advantage is that &ldquo;<span class=
"quote">chrooting</span>&rdquo; allows the builder to continue
using the host while LFS is being built. While waiting for
package compilation to complete, a user can switch to a
different virtual console (VC) or X desktop and continue using
the computer as normal.
</p>
<p>
To finish the installation, the LFS-Bootscripts are set up in
<a href="#chapter-bootscripts">Chapter 7</a>, and the kernel
and boot loader are set up in <a href=
"#chapter-bootable">Chapter 8</a>. <a href=
"#chapter-finalizing">Chapter 9</a> contains information on
furthering the LFS experience beyond this book. After the steps
in this book have been implemented, the computer will be ready
to reboot into the new LFS system.
</p>
<p>
This is the process in a nutshell. Detailed information on each
step is discussed in the following chapters and package
descriptions. Items that may seem complicated will be
clarified, and everything will fall into place as the reader
embarks on the LFS adventure.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scatter-changelog" name=
"ch-scatter-changelog"></a>1.2.&nbsp;Changelog
</h2>
</div>
</div>
</div>
<p>
This is version 6.1.1 of the Linux From Scratch book, dated
November 30, 2005. If this book is more than six months old, a
newer and better version is probably already available. To find
out, please check one of the mirrors via <a href=
"http://www.linuxfromscratch.org/"><i>http://www.linuxfromscratch.org/</i></a>.
</p>
<p>
Below is a list of changes made since the previous release of
the book. First a summary, then a detailed log.
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
Upgraded to:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
Perl 5.8.7
</p>
</li>
<li>
<p>
Zlib 1.2.3
</p>
</li>
</ul>
</div>
</li>
<li>
<p>
Added:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
binutils-2.15.94.0.2.2-gcc4-1.patch
</p>
</li>
<li>
<p>
bzip2-1.0.3-install_docs-1.patch
</p>
</li>
<li>
<p>
bzip2-1.0.3-bzgrep_security-1.patch
</p>
</li>
<li>
<p>
glibc-2.3.4-rtld_search_dirs-1.patch
</p>
</li>
<li>
<p>
glibc-2.3.4-tls_assert-1.patch
</p>
</li>
<li>
<p>
texinfo-4.8-tempfile_fix-1.patch
</p>
</li>
<li>
<p>
util-linux-2.12q-umount_fix-1.patch
</p>
</li>
<li>
<p>
vim-6.3-security_fix-2.patch
</p>
</li>
</ul>
</div>
</li>
<li>
<p>
Removed:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
zlib-1.2.2-security_fix-1.patch;
</p>
</li>
</ul>
</div>
</li>
<li>
<p>
November 30, 2005 [matt]: LFS-6.1.1 release.
</p>
</li>
<li>
<p>
November 24, 2005 [matt]: LFS-6.1.1-pre2 release.
</p>
</li>
<li>
<p>
November 24, 2005 [matt]: Fix an issue with Glibc that
prevents some programs (including OpenOffice.org) from
running.
</p>
</li>
<li>
<p>
November 23, 2005 [gerard]: Corrected reference to 'man
page' to 'HTML documentation' in chapter 6/sec
</p>
</li>
<li>
<p>
November 18, 2005 [manuel]: Fixed the unpack of the
module-init-tools-testsuite package.
</p>
</li>
<li>
<p>
November 18, 2005 [manuel]: PDF fixes.
</p>
</li>
<li>
<p>
November 17, 2005 [matt]: LFS-6.1.1-pre1 release.
</p>
</li>
<li>
<p>
November 12, 2005 [matt]: Improve the heuristic for
determining a locale that is supported by both Glibc and
packages outside LFS (bug 1642). Many thanks to Alexander
Patrakov for highlighting the numerous issues and for
reviewing the various suggested fixes.
</p>
</li>
<li>
<p>
November 12, 2005 [matt]: Omit running Bzip2's testsuite
as a separate step, as <span><strong class=
"command">make</strong></span> runs it automatically (bug
1652).
</p>
</li>
<li>
<p>
November 7, 2005 [matt]: Stop Udev from killing udevd
processes on the host system (fixes bug 1651). Thanks to
Alexander Patrakov for the report and the fix.
</p>
</li>
<li>
<p>
November 5, 2005 [matt]: Add a note to the toolchain
sanity check in chapter 5 to explain that if TCL fails to
build, it's an indication of a broken toolchain (bug
1581).
</p>
</li>
<li>
<p>
November 4, 2005 [matt]: Correct the instructions for
running Module-Init-Tools' testsuite (fixes bug 1597).
Thanks to Greg Schafer, Tushar Teredesai and to Randy
McMurchy for providing the patch.
</p>
</li>
<li>
<p>
October 29, 2005 [manuel]: PDF fixes.
</p>
</li>
<li>
<p>
October 23, 2005 [manuel]: Added Bash documentation
installation. Added notes about libiconv and Cracklib.
Fixed the installation of Sed documentation. Replaced a
patch for IPRoute2 by a sed command.
</p>
</li>
<li>
<p>
October 19, 2005 [manuel]: Updated the acknowledgements
to current trunk version. Ported some redaction changes
in preface and chapter01 pages. Moved chapter02 to part
II. Added -v switches. Ported several typos and redaction
fixes from trunk.
</p>
</li>
<li>
<p>
October 19, 2005 [manuel]: Updated the stylesheets,
Makefile and related files to current trunk versions.
</p>
</li>
<li>
<p>
October 15, 2005 [matt]: Use an updated version of the
Udev rules file (fixes bug 1639).
</p>
</li>
<li>
<p>
October 15, 2005 [matt]: Add a cdrom group as required by
the Udev rules file
</p>
</li>
<li>
<p>
October 14th, 2005 [ken]: Added a patch to allow binutils
to be built from a host running gcc-4, updated glibc
instructions for the rtld patch, updated space/time for
perl and zlib.
</p>
</li>
<li>
<p>
October 14th, 2005 [matt]: Added a patch to fix a
security vulnerability in util-linux.
</p>
</li>
<li>
<p>
October 14th, 2005 [matt]: Added the updated vim security
patch.
</p>
</li>
<li>
<p>
October 14th, 2005 [jhuntwork]: Added the bzip2 security
and install docs patches.
</p>
</li>
<li>
<p>
October 14th, 2005 [jhuntwork]: Added the tempfile patch
for texinfo.
</p>
</li>
<li>
<p>
October 14th, 2005 [ken]: Update packages and patches in
the changelog to only reflect changes since 6.1. Update
zlib.
</p>
</li>
<li>
<p>
October 13th, 2005 [ken]: Fix known errors in lists of
installed files and bump the perl version.
</p>
</li>
</ul>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scatter-administrativa" name=
"ch-scatter-administrativa"></a>1.3.&nbsp;Resources
</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="ch-scatter-faq" name="ch-scatter-faq"></a>
<h3 class="sect2">
1.3.1. FAQ
</h3>
</div>
<p>
If during the building of the LFS system you encounter any
errors, have any questions, or think there is a typo in the
book, please start by consulting the Frequently Asked
Questions (FAQ) that is located at <a href=
"http://www.linuxfromscratch.org/faq/"><i>http://www.linuxfromscratch.org/faq/</i></a>.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="ch-scatter-maillists" name="ch-scatter-maillists"></a>
<h3 class="sect2">
1.3.2. Mailing Lists
</h3>
</div>
<p>
The <tt class="uri">linuxfromscratch.org</tt> server hosts a
number of mailing lists used for the development of the LFS
project. These lists include the main development and support
lists, among others. If the FAQ does not solve the problem
you are having, the next step would be to search the mailing
lists at <a href=
"http://www.linuxfromscratch.org/search.html"><i>http://www.linuxfromscratch.org/search.html</i></a>.
</p>
<p>
For information on the different lists, how to subscribe,
archive locations, and additional information, visit <a href=
"http://www.linuxfromscratch.org/mail.html"><i>http://www.linuxfromscratch.org/mail.html</i></a>.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="ch-scatter-newsserver" name=
"ch-scatter-newsserver"></a>
<h3 class="sect2">
1.3.3. News Server
</h3>
</div>
<p>
The mailing lists hosted at <tt class=
"uri">linuxfromscratch.org</tt> are also accessible via the
Network News Transfer Protocol (NNTP) server. All messages
posted to a mailing list are copied to the corresponding
newsgroup, and vice versa.
</p>
<p>
The news server is located at <tt class=
"uri">news.linuxfromscratch.org</tt>.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="ch-scatter-irc" name="ch-scatter-irc"></a>
<h3 class="sect2">
1.3.4. IRC
</h3>
</div>
<p>
Several members of the LFS community offer assistance on our
community Internet Relay Chat (IRC) network. Before using
this support, please make sure that your question is not
already answered in the LFS FAQ or the mailing list archives.
You can find the IRC network at <tt class=
"uri">irc.linuxfromscratch.org</tt>. The support channel is
named #LFS-support.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="ch-scatter-references" name=
"ch-scatter-references"></a>
<h3 class="sect2">
1.3.5. References
</h3>
</div>
<p>
For additional information on the packages, useful tips are
available in the LFS Package Reference page located at
<a href=
"http://www.linuxfromscratch.org/~matthew/LFS-references.html">
<i>http://www.linuxfromscratch.org/~matthew/LFS-references.html</i></a>.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="ch-scatter-mirrors" name="ch-scatter-mirrors"></a>
<h3 class="sect2">
1.3.6. Mirror Sites
</h3>
</div>
<p>
The LFS project has a number of world-wide mirrors to make
accessing the website and downloading the required packages
more convenient. Please visit the LFS website at <a href=
"http://www.linuxfromscratch.org/mirrors.html"><i>http://www.linuxfromscratch.org/mirrors.html</i></a>
for a list of current mirrors.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="ch-scatter-contactinfo" name=
"ch-scatter-contactinfo"></a>
<h3 class="sect2">
1.3.7. Contact Information
</h3>
</div>
<p>
Please direct all your questions and comments to one of the
LFS mailing lists (see above).
</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="prepare-askforhelp" name=
"prepare-askforhelp"></a>1.4.&nbsp;Help
</h2>
</div>
</div>
</div>
<p>
If an issue or a question is encountered while working through
this book, check the FAQ page at <a href=
"http://www.linuxfromscratch.org/faq/#generalfaq"><i>http://www.linuxfromscratch.org/faq/#generalfaq</i></a>.
Questions are often already answered there. If your question is
not answered on this page, try to find the source of the
problem. The following hint will give you some guidance for
troubleshooting: <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/errors.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/errors.txt</i></a>.
</p>
<p>
If you cannot find your problem listed in the FAQ, search the
mailing lists at <a href=
"http://www.linuxfromscratch.org/search.html"><i>http://www.linuxfromscratch.org/search.html</i></a>.
</p>
<p>
We also have a wonderful LFS community that is willing to offer
assistance through the mailing lists and IRC (see the <a href=
"#ch-scatter-administrativa" title=
"1.3.&nbsp;Resources">Section&nbsp;1.3,
&ldquo;Resources&rdquo;</a> section of this book). However, we
get several support questions everyday and many of them can be
easily answered by going to the FAQ and by searching the
mailing lists first. So for us to offer the best assistance
possible, you need to do some research on your own first. That
allows us to focus on the more unusual support needs. If your
searches do not produce a solution, please include all relevant
information (mentioned below) in your request for help.
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
1.4.1. Things to Mention
</h3>
</div>
<p>
Apart from a brief explanation of the problem being
experienced, the essential things to include in any request
for help are:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
The version of the book being used (in this case 6.1.1)
</p>
</li>
<li>
<p>
The host distribution and version being used to create
LFS
</p>
</li>
<li>
<p>
The package or section the problem was encountered in
</p>
</li>
<li>
<p>
The exact error message or symptom being received
</p>
</li>
<li>
<p>
Note whether you have deviated from the book at all
</p>
</li>
</ul>
</div>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
Deviating from this book does <span class=
"emphasis"><em>not</em></span> mean that we will not help
you. After all, LFS is about personal preference. Being
upfront about any changes to the established procedure
helps us evaluate and determine possible causes of your
problem.
</p>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
1.4.2. Configure Script Problems
</h3>
</div>
<p>
If something goes wrong while running the
<span><strong class="command">configure</strong></span>
script, review the <tt class="filename">config.log</tt> file.
This file may contain errors encountered during
<span><strong class="command">configure</strong></span> which
were not printed to the screen. Include the <span class=
"emphasis"><em>relevant</em></span> lines if you need to ask
for help.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
1.4.3. Compilation Problems
</h3>
</div>
<p>
Both the screen output and the contents of various files are
useful in determining the cause of compilation problems. The
screen output from the <span><strong class=
"command">configure</strong></span> script and the
<span><strong class="command">make</strong></span> run can be
helpful. It is not necessary to include the entire output,
but do include enough of the relevant information. Below is
an example of the type of information to include from the
screen output from <span><strong class=
"command">make</strong></span>:
</p>
<pre class="screen"><tt class=
"computeroutput">gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\"
-DLIBDIR=\"/mnt/lfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o
expand.o file.o function.o getopt.o implicit.o job.o main.o
misc.o read.o remake.o rule.o signame.o variable.o vpath.o
default.o remote-stub.o version.o opt1.o
-lutil job.o: In function `load_too_high':
/lfs/tmp/make-3.79.1/job.c:1565: undefined reference
to `getloadavg'
collect2: ld returned 1 exit status
make[2]: *** [make] Error 1
make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2</tt></pre>
<p>
In this case, many people would just include the bottom
section:
</p>
<pre class="screen"><tt class=
"computeroutput">make [2]: *** [make] Error 1</tt></pre>
<p>
This is not enough information to properly diagnose the
problem because it only notes that something went wrong, not
<span class="emphasis"><em>what</em></span> went wrong. The
entire section, as in the example above, is what should be
saved because it includes the command that was executed and
the associated error message(s).
</p>
<p>
An excellent article about asking for help on the Internet is
available online at <a href=
"http://catb.org/~esr/faqs/smart-questions.html"><i>http://catb.org/~esr/faqs/smart-questions.html</i></a>.
Read and follow the hints in this document to increase the
likelihood of getting the help you need.
</p>
</div>
</div>
</div>
</div>
<div class="part" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title">
<a id="part2" name="part2"></a>Part&nbsp;II.&nbsp;Preparing
for the Build
</h1>
</div>
</div>
</div>
<div class="toc">
<h3>
Table of Contents
</h3>
<ul>
<li class="chapter">
<h4>
2. Preparing a New Partition
</h4>
<ul>
<li class="sect1">
<a href="#space-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#space-creatingpartition">Creating a New
Partition</a>
</li>
<li class="sect1">
<a href="#space-creatingfilesystem">Creating a File System
on the Partition</a>
</li>
<li class="sect1">
<a href="#space-mounting">Mounting the New Partition</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
3. Packages and Patches
</h4>
<ul>
<li class="sect1">
<a href="#materials-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#materials-packages">All Packages</a>
</li>
<li class="sect1">
<a href="#materials-patches">Needed Patches</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
4. Final Preparations
</h4>
<ul>
<li class="sect1">
<a href="#prepare-aboutlfs">About $LFS</a>
</li>
<li class="sect1">
<a href="#ch-tools-creatingtoolsdir">Creating the
$LFS/tools Directory</a>
</li>
<li class="sect1">
<a href="#ch-tools-addinguser">Adding the LFS User</a>
</li>
<li class="sect1">
<a href="#ch-tools-settingenviron">Setting Up the
Environment</a>
</li>
<li class="sect1">
<a href="#prepare-aboutsbus">About SBUs</a>
</li>
<li class="sect1">
<a href="#prepare-abouttestsuites">About the Test
Suites</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
5. Constructing a Temporary System
</h4>
<ul>
<li class="sect1">
<a href="#ch-tools-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#ch-tools-toolchaintechnotes">Toolchain Technical
Notes</a>
</li>
<li class="sect1">
<a href="#ch-tools-binutils-pass1">Binutils-2.15.94.0.2.2 -
Pass 1</a>
</li>
<li class="sect1">
<a href="#ch-tools-gcc-pass1">GCC-3.4.3 - Pass 1</a>
</li>
<li class="sect1">
<a href=
"#ch-tools-linux-libc-headers">Linux-Libc-Headers-2.6.11.2</a>
</li>
<li class="sect1">
<a href="#ch-tools-glibc">Glibc-2.3.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-adjusting">Adjusting the Toolchain</a>
</li>
<li class="sect1">
<a href="#ch-tools-tcl">Tcl-8.4.9</a>
</li>
<li class="sect1">
<a href="#ch-tools-expect">Expect-5.43.0</a>
</li>
<li class="sect1">
<a href="#ch-tools-dejagnu">DejaGNU-1.4.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-gcc-pass2">GCC-3.4.3 - Pass 2</a>
</li>
<li class="sect1">
<a href="#ch-tools-binutils-pass2">Binutils-2.15.94.0.2.2 -
Pass 2</a>
</li>
<li class="sect1">
<a href="#ch-tools-gawk">Gawk-3.1.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-coreutils">Coreutils-5.2.1</a>
</li>
<li class="sect1">
<a href="#ch-tools-bzip2">Bzip2-1.0.3</a>
</li>
<li class="sect1">
<a href="#ch-tools-gzip">Gzip-1.3.5</a>
</li>
<li class="sect1">
<a href="#ch-tools-diffutils">Diffutils-2.8.1</a>
</li>
<li class="sect1">
<a href="#ch-tools-findutils">Findutils-4.2.23</a>
</li>
<li class="sect1">
<a href="#ch-tools-make">Make-3.80</a>
</li>
<li class="sect1">
<a href="#ch-tools-grep">Grep-2.5.1a</a>
</li>
<li class="sect1">
<a href="#ch-tools-sed">Sed-4.1.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-gettext">Gettext-0.14.3</a>
</li>
<li class="sect1">
<a href="#ch-tools-ncurses">Ncurses-5.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-patch">Patch-2.5.4</a>
</li>
<li class="sect1">
<a href="#ch-tools-tar">Tar-1.15.1</a>
</li>
<li class="sect1">
<a href="#ch-tools-texinfo">Texinfo-4.8</a>
</li>
<li class="sect1">
<a href="#ch-tools-bash">Bash-3.0</a>
</li>
<li class="sect1">
<a href="#ch-tools-m4">M4-1.4.3</a>
</li>
<li class="sect1">
<a href="#ch-tools-bison">Bison-2.0</a>
</li>
<li class="sect1">
<a href="#ch-tools-flex">Flex-2.5.31</a>
</li>
<li class="sect1">
<a href="#ch-tools-util-linux">Util-linux-2.12q</a>
</li>
<li class="sect1">
<a href="#ch-tools-perl">Perl-5.8.7</a>
</li>
<li class="sect1">
<a href="#ch-tools-stripping">Stripping</a>
</li>
</ul>
</li>
</ul>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-partitioning" name=
"chapter-partitioning"></a>Chapter&nbsp;2.&nbsp;Preparing a
New Partition
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="space-introduction" name=
"space-introduction"></a>2.1.&nbsp;Introduction
</h2>
</div>
</div>
</div>
<p>
In this chapter, the partition which will host the LFS system
is prepared. We will create the partition itself, create a file
system on it, and mount it.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="space-creatingpartition" name=
"space-creatingpartition"></a>2.2.&nbsp;Creating a New
Partition
</h2>
</div>
</div>
</div>
<p>
Like most other operating systems, LFS is usually installed on
a dedicated partition. The recommended approach to building an
LFS system is to use an available empty partition or, if you
have enough unpartitioned space, to create one. However, an LFS
system (in fact even multiple LFS systems) may also be
installed on a partition already occupied by another operating
system and the different systems will co-exist peacefully. The
document <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/lfs_next_to_existing_systems.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/lfs_next_to_existing_systems.txt</i></a>
explains how to implement this, whereas this book discusses the
method of using a fresh partition for the installation.
</p>
<p>
A minimal system requires a partition of around 1.3 gigabytes
(GB). This is enough to store all the source tarballs and
compile the packages. However, if the LFS system is intended to
be the primary Linux system, additional software will probably
be installed which will require additional space (2-3 GB). The
LFS system itself will not take up this much room. A large
portion of this requirement is to provide sufficient free
temporary storage. Compiling packages can require a lot of disk
space which will be reclaimed after the package is installed.
</p>
<p>
Because there is not always enough Random Access Memory (RAM)
available for compilation processes, it is a good idea to use a
small disk partition as swap space. This is used by the kernel
to store seldom-used data and leave more memory available for
active processes. The swap partition for an LFS system can be
the same as the one used by the host system, in which case it
is not necessary to create another one.
</p>
<p>
Start a disk partitioning program such as <span><strong class=
"command">cfdisk</strong></span> or <span><strong class=
"command">fdisk</strong></span> with a command line option
naming the hard disk on which the new partition will be
created&mdash;for example <tt class="filename">/dev/hda</tt>
for the primary Integrated Drive Electronics (IDE) disk. Create
a Linux native partition and a swap partition, if needed.
Please refer to <tt class="filename">cfdisk(8)</tt> or
<tt class="filename">fdisk(8)</tt> if you do not yet know how
to use the programs.
</p>
<p>
Remember the designation of the new partition (e.g., <tt class=
"filename">hda5</tt>). This book will refer to this as the LFS
partition. Also remember the designation of the swap partition.
These names will be needed later for the <tt class=
"filename">/etc/fstab</tt> file.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="space-creatingfilesystem" name=
"space-creatingfilesystem"></a>2.3.&nbsp;Creating a File
System on the Partition
</h2>
</div>
</div>
</div>
<p>
Now that a blank partition has been set up, the file system can
be created. The most widely-used system in the Linux world is
the second extended file system (ext2), but with newer
high-capacity hard disks, journaling file systems are becoming
increasingly popular. We will create an ext2 file system. Build
instructions for other file systems can be found at <a href=
"http://www.linuxfromscratch.org/blfs/view/svn/postlfs/filesystems.html">
<i>http://www.linuxfromscratch.org/blfs/view/svn/postlfs/filesystems.html</i></a>.
</p>
<p>
To create an ext2 file system on the LFS partition, run the
following:
</p>
<pre class="userinput"><kbd class=
"command">mke2fs -v /dev/<em class=
"replaceable"><tt>[xxx]</tt></em></kbd></pre>
<p>
Replace <em class="replaceable"><tt>[xxx]</tt></em> with the
name of the LFS partition (<tt class="filename">hda5</tt> in
our previous example).
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
Some host distributions use custom features in their
filesystem creation tools (e2fsprogs). This can cause
problems when booting into your new LFS in Chapter 9, as
those features will not be supported by the LFS-installed
e2fsprogs; you will get an error similar to
&ldquo;<span class="quote">unsupported filesystem features,
upgrade your e2fsprogs</span>&rdquo;. To check if your host
system uses custom enhancements, run the following command:
</p>
<pre class="userinput"><kbd class=
"command">debugfs -R feature /dev/<em class=
"replaceable"><tt>[xxx]</tt></em></kbd></pre>
<p>
If the output contains features other than: dir_index;
filetype; large_file; resize_inode or sparse_super then
your host system may have custom enhancements. In that
case, to avoid later problems, you should compile the stock
e2fsprogs package and use the resulting binaries to
re-create the filesystem on your LFS partition:
</p>
<pre class="userinput"><kbd class="command">cd /tmp
tar -xjvf /path/to/sources/e2fsprogs-1.37.tar.bz2
cd e2fsprogs-1.37
mkdir -v build
cd build
../configure
make #note that we intentionally don't 'make install' here!
./misc/mke2fs -v /dev/<em class="replaceable"><tt>[xxx]</tt></em>
cd /tmp
rm -rfv e2fsprogs-1.37</kbd></pre>
</div>
</div>
<p>
If a swap partition was created, it will need to be initialized
for use by issuing the command below. If you are using an
existing swap partition, there is no need to format it.
</p>
<pre class="userinput"><kbd class=
"command">mkswap -v /dev/<em class=
"replaceable"><tt>[yyy]</tt></em></kbd></pre>
<p>
Replace <em class="replaceable"><tt>[yyy]</tt></em> with the
name of the swap partition.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="space-mounting" name=
"space-mounting"></a>2.4.&nbsp;Mounting the New Partition
</h2>
</div>
</div>
</div>
<p>
Now that a file system has been created, the partition needs to
be made accessible. In order to do this, the partition needs to
be mounted at a chosen mount point. For the purposes of this
book, it is assumed that the file system is mounted under
<tt class="filename">/mnt/lfs</tt>, but the directory choice is
up to you.
</p>
<p>
Choose a mount point and assign it to the <tt class=
"envar">LFS</tt> environment variable by running:
</p>
<pre class="userinput"><kbd class=
"command">export LFS=/mnt/lfs</kbd></pre>
<p>
Next, create the mount point and mount the LFS file system by
running:
</p>
<pre class="userinput"><kbd class="command">mkdir -pv $LFS
mount -v /dev/<em class="replaceable"><tt>[xxx]</tt></em> $LFS</kbd></pre>
<p>
Replace <em class="replaceable"><tt>[xxx]</tt></em> with the
designation of the LFS partition.
</p>
<p>
If using multiple partitions for LFS (e.g., one for <tt class=
"filename">/</tt> and another for <tt class=
"filename">/usr</tt>), mount them using:
</p>
<pre class="userinput"><kbd class="command">mkdir -pv $LFS
mount -v /dev/<em class="replaceable"><tt>[xxx]</tt></em> $LFS
mkdir -v $LFS/usr
mount -v /dev/<em class=
"replaceable"><tt>[yyy]</tt></em> $LFS/usr</kbd></pre>
<p>
Replace <em class="replaceable"><tt>[xxx]</tt></em> and
<em class="replaceable"><tt>[yyy]</tt></em> with the
appropriate partition names.
</p>
<p>
Ensure that this new partition is not mounted with permissions
that are too restrictive (such as the nosuid, nodev, or noatime
options). Run the <span><strong class=
"command">mount</strong></span> command without any parameters
to see what options are set for the mounted LFS partition. If
<em class="parameter"><tt>nosuid</tt></em>, <em class=
"parameter"><tt>nodev</tt></em>, and/or <em class=
"parameter"><tt>noatime</tt></em> are set, the partition will
need to be remounted.
</p>
<p>
Now that there is an established place to work, it is time to
download the packages.
</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-getting-materials" name=
"chapter-getting-materials"></a>Chapter&nbsp;3.&nbsp;Packages
and Patches
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="materials-introduction" name=
"materials-introduction"></a>3.1.&nbsp;Introduction
</h2>
</div>
</div>
</div>
<p>
This chapter includes a list of packages that need to be
downloaded for building a basic Linux system. The listed
version numbers correspond to versions of the software that are
known to work, and this book is based on their use. We highly
recommend not using newer versions because the build commands
for one version may not work with a newer version. The newest
package versions may also have problems that require
work-arounds. These work-arounds will be developed and
stabilized in the development version of the book.
</p>
<p>
Download locations may not always be accessible. If a download
location has changed since this book was published, Google
(<a href=
"http://www.google.com/"><i>http://www.google.com/</i></a>)
provides a useful search engine for most packages. If this
search is unsuccessful, try one of the alternative means of
downloading discussed at <a href=
"http://www.linuxfromscratch.org/lfs/packages.html"><i>http://www.linuxfromscratch.org/lfs/packages.html</i></a>.
</p>
<p>
Downloaded packages and patches will need to be stored
somewhere that is conveniently available throughout the entire
build. A working directory is also required to unpack the
sources and build them. <tt class="filename">$LFS/sources</tt>
can be used both as the place to store the tarballs and patches
and as a working directory. By using this directory, the
required elements will be located on the LFS partition and will
be available during all stages of the building process.
</p>
<p>
To create this directory, execute, as user <span class=
"emphasis"><em>root</em></span>, the following command before
starting the download session:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v $LFS/sources</kbd></pre>
<p>
Make this directory writable and sticky. &ldquo;<span class=
"quote">Sticky</span>&rdquo; means that even if multiple users
have write permission on a directory, only the owner of a file
can delete the file within a sticky directory. The following
command will enable the write and sticky modes:
</p>
<pre class="userinput"><kbd class=
"command">chmod -v a+wt $LFS/sources</kbd></pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="materials-packages" name=
"materials-packages"></a>3.2.&nbsp;All Packages
</h2>
</div>
</div>
</div>
<p>
Download or otherwise obtain the following packages:
</p>
<div class="materials">
<div class="variablelist">
<dl>
<dt>
<span class="term">Autoconf (2.59) - 908 kilobytes
(KB):</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/autoconf/"><i>http://ftp.gnu.org/gnu/autoconf/</i></a>
</p>
</dd>
<dt>
<span class="term">Automake (1.9.5) - 748 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/automake/"><i>http://ftp.gnu.org/gnu/automake/</i></a>
</p>
</dd>
<dt>
<span class="term">Bash (3.0) - 1,824 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/bash/"><i>http://ftp.gnu.org/gnu/bash/</i></a>
</p>
</dd>
<dt>
<span class="term">Bash Documentation (3.0) - 1,994
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/bash/"><i>http://ftp.gnu.org/gnu/bash/</i></a>
</p>
</dd>
<dt>
<span class="term">Binutils (2.15.94.0.2.2) - 11,056
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/devel/binutils/"><i>http://www.kernel.org/pub/linux/devel/binutils/</i></a>
</p>
</dd>
<dt>
<span class="term">Bison (2.0) - 916 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/bison/"><i>http://ftp.gnu.org/gnu/bison/</i></a>
</p>
</dd>
<dt>
<span class="term">Bzip2 (1.0.3) - 596 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.bzip.org/"><i>http://www.bzip.org/</i></a>
</p>
</dd>
<dt>
<span class="term">Coreutils (5.2.1) - 4,184 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/coreutils/"><i>http://ftp.gnu.org/gnu/coreutils/</i></a>
</p>
</dd>
<dt>
<span class="term">DejaGNU (1.4.4) - 852 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/dejagnu/"><i>http://ftp.gnu.org/gnu/dejagnu/</i></a>
</p>
</dd>
<dt>
<span class="term">Diffutils (2.8.1) - 648 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/diffutils/"><i>http://ftp.gnu.org/gnu/diffutils/</i></a>
</p>
</dd>
<dt>
<span class="term">E2fsprogs (1.37) - 3,100 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://prdownloads.sourceforge.net/e2fsprogs/"><i>http://prdownloads.sourceforge.net/e2fsprogs/</i></a>
</p>
</dd>
<dt>
<span class="term">Expect (5.43.0) - 416 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://expect.nist.gov/src/"><i>http://expect.nist.gov/src/</i></a>
</p>
</dd>
<dt>
<span class="term">File (4.13) - 324 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://ftp.gw.com/mirrors/pub/unix/file/"><i>ftp://ftp.gw.com/mirrors/pub/unix/file/</i></a>
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
File (4.13) may no longer be available at the
listed location. The site administrators of the
master download location occasionally remove older
versions when new ones are released. An alternative
download location that may have the correct version
available can also be found at: <a href=
"http://www.linuxfromscratch.org/lfs/download.html#ftp">
<i>http://www.linuxfromscratch.org/lfs/download.html#ftp</i></a>.
</p>
</div>
</div>
</dd>
<dt>
<span class="term">Findutils (4.2.23) - 784 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/findutils/"><i>http://ftp.gnu.org/gnu/findutils/</i></a>
</p>
</dd>
<dt>
<span class="term">Flex (2.5.31) - 672 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://prdownloads.sourceforge.net/lex/"><i>http://prdownloads.sourceforge.net/lex/</i></a>
</p>
</dd>
<dt>
<span class="term">Gawk (3.1.4) - 1,696 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/gawk/"><i>http://ftp.gnu.org/gnu/gawk/</i></a>
</p>
</dd>
<dt>
<span class="term">GCC (3.4.3) - 26,816 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/gcc/"><i>http://ftp.gnu.org/gnu/gcc/</i></a>
</p>
</dd>
<dt>
<span class="term">Gettext (0.14.3) - 4,568 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/gettext/"><i>http://ftp.gnu.org/gnu/gettext/</i></a>
</p>
</dd>
<dt>
<span class="term">Glibc (2.3.4) - 12,924 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/glibc/"><i>http://ftp.gnu.org/gnu/glibc/</i></a>
</p>
</dd>
<dt>
<span class="term">Glibc-Linuxthreads (2.3.4) - 236
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/glibc/"><i>http://ftp.gnu.org/gnu/glibc/</i></a>
</p>
</dd>
<dt>
<span class="term">Grep (2.5.1a) - 520 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/grep/"><i>http://ftp.gnu.org/gnu/grep/</i></a>
</p>
</dd>
<dt>
<span class="term">Groff (1.19.1) - 2,096 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/groff/"><i>http://ftp.gnu.org/gnu/groff/</i></a>
</p>
</dd>
<dt>
<span class="term">GRUB (0.96) - 768 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://alpha.gnu.org/gnu/grub/"><i>ftp://alpha.gnu.org/gnu/grub/</i></a>
</p>
</dd>
<dt>
<span class="term">Gzip (1.3.5) - 284 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://alpha.gnu.org/gnu/gzip/"><i>ftp://alpha.gnu.org/gnu/gzip/</i></a>
</p>
</dd>
<dt>
<span class="term">Hotplug (2004_09_23) - 40 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/utils/kernel/hotplug/">
<i>http://www.kernel.org/pub/linux/utils/kernel/hotplug/</i></a>
</p>
</dd>
<dt>
<span class="term">Iana-Etc (1.04) - 176 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.sethwklein.net/projects/iana-etc/downloads/">
<i>http://www.sethwklein.net/projects/iana-etc/downloads/</i></a>
</p>
</dd>
<dt>
<span class="term">Inetutils (1.4.2) - 752 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/inetutils/"><i>http://ftp.gnu.org/gnu/inetutils/</i></a>
</p>
</dd>
<dt>
<span class="term">IPRoute2 (2.6.11-050330) - 276
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://developer.osdl.org/dev/iproute2/download/"><i>http://developer.osdl.org/dev/iproute2/download/</i></a>
</p>
</dd>
<dt>
<span class="term">Kbd (1.12) - 624 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/utils/kbd/"><i>http://www.kernel.org/pub/linux/utils/kbd/</i></a>
</p>
</dd>
<dt>
<span class="term">Less (382) - 216 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/less/"><i>http://ftp.gnu.org/gnu/less/</i></a>
</p>
</dd>
<dt>
<span class="term">LFS-Bootscripts (3.2.1) - 32
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://downloads.linuxfromscratch.org/"><i>http://downloads.linuxfromscratch.org/</i></a>
</p>
</dd>
<dt>
<span class="term">Libtool (1.5.14) - 1,604 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/libtool/"><i>http://ftp.gnu.org/gnu/libtool/</i></a>
</p>
</dd>
<dt>
<span class="term">Linux (2.6.11.12) - 35,792 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/kernel/v2.6/"><i>http://www.kernel.org/pub/linux/kernel/v2.6/</i></a>
</p>
</dd>
<dt>
<span class="term">Linux-Libc-Headers (2.6.11.2) - 2,476
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ep09.pld-linux.org/~mmazur/linux-libc-headers/">
<i>http://ep09.pld-linux.org/~mmazur/linux-libc-headers/</i></a>
</p>
</dd>
<dt>
<span class="term">M4 (1.4.3) - 304 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/m4/"><i>http://ftp.gnu.org/gnu/m4/</i></a>
</p>
</dd>
<dt>
<span class="term">Make (3.80) - 904 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/make/"><i>http://ftp.gnu.org/gnu/make/</i></a>
</p>
</dd>
<dt>
<span class="term">Man (1.5p) - 208 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/utils/man/"><i>http://www.kernel.org/pub/linux/utils/man/</i></a>
</p>
</dd>
<dt>
<span class="term">Man-pages (2.01) - 1,640 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/docs/manpages/"><i>http://www.kernel.org/pub/linux/docs/manpages/</i></a>
</p>
</dd>
<dt>
<span class="term">Mktemp (1.5) - 68 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://ftp.mktemp.org/pub/mktemp/"><i>ftp://ftp.mktemp.org/pub/mktemp/</i></a>
</p>
</dd>
<dt>
<span class="term">Module-Init-Tools (3.1) - 128
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/">
<i>http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/</i></a>
</p>
</dd>
<dt>
<span class="term">Module-Init-Tools-Testsuite (3.1) - 34
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/">
<i>http://www.kernel.org/pub/linux/utils/kernel/module-init-tools/</i></a>
</p>
</dd>
<dt>
<span class="term">Ncurses (5.4) - 1,556 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://invisible-island.net/ncurses/"><i>ftp://invisible-island.net/ncurses/</i></a>
</p>
</dd>
<dt>
<span class="term">Patch (2.5.4) - 156 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/patch/"><i>http://ftp.gnu.org/gnu/patch/</i></a>
</p>
</dd>
<dt>
<span class="term">Perl (5.8.7) - 9,628 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.funet.fi/pub/CPAN/src/"><i>http://ftp.funet.fi/pub/CPAN/src/</i></a>
</p>
</dd>
<dt>
<span class="term">Procps (3.2.5) - 224 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://procps.sourceforge.net/"><i>http://procps.sourceforge.net/</i></a>
</p>
</dd>
<dt>
<span class="term">Psmisc (21.6) - 188 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://prdownloads.sourceforge.net/psmisc/"><i>http://prdownloads.sourceforge.net/psmisc/</i></a>
</p>
</dd>
<dt>
<span class="term">Readline (5.0) - 1,456 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/readline/"><i>http://ftp.gnu.org/gnu/readline/</i></a>
</p>
</dd>
<dt>
<span class="term">Sed (4.1.4) - 632 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/sed/"><i>http://ftp.gnu.org/gnu/sed/</i></a>
</p>
</dd>
<dt>
<span class="term">Shadow (4.0.9) - 1,084 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://ftp.pld.org.pl/software/shadow/"><i>ftp://ftp.pld.org.pl/software/shadow/</i></a>
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
Shadow (4.0.9) may no longer be available at the
listed location. The site administrators of the
master download location occasionally remove older
versions when new ones are released. An alternative
download location that may have the correct version
available cat also be found at: <a href=
"http://www.linuxfromscratch.org/lfs/download.html#ftp">
<i>http://www.linuxfromscratch.org/lfs/download.html#ftp</i></a>.
</p>
</div>
</div>
</dd>
<dt>
<span class="term">Sysklogd (1.4.1) - 72 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.infodrom.org/projects/sysklogd/download/"><i>
http://www.infodrom.org/projects/sysklogd/download/</i></a>
</p>
</dd>
<dt>
<span class="term">Sysvinit (2.86) - 88 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://ftp.cistron.nl/pub/people/miquels/sysvinit/"><i>ftp://ftp.cistron.nl/pub/people/miquels/sysvinit/</i></a>
</p>
</dd>
<dt>
<span class="term">Tar (1.15.1) - 1,580 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/tar/"><i>http://ftp.gnu.org/gnu/tar/</i></a>
</p>
</dd>
<dt>
<span class="term">Tcl (8.4.9) - 2,748 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://prdownloads.sourceforge.net/tcl/"><i>http://prdownloads.sourceforge.net/tcl/</i></a>
</p>
</dd>
<dt>
<span class="term">Texinfo (4.8) - 1,492 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://ftp.gnu.org/gnu/texinfo/"><i>http://ftp.gnu.org/gnu/texinfo/</i></a>
</p>
</dd>
<dt>
<span class="term">Udev (056) - 476 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/utils/kernel/hotplug/">
<i>http://www.kernel.org/pub/linux/utils/kernel/hotplug/</i></a>
</p>
</dd>
<dt>
<span class="term">Udev Rules Configuration - 5
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://downloads.linuxfromscratch.org/udev-config-4.rules">
<i>http://downloads.linuxfromscratch.org/udev-config-4.rules</i></a>
</p>
</dd>
<dt>
<span class="term">Util-linux (2.12q) - 1,344 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.kernel.org/pub/linux/utils/util-linux/"><i>http://www.kernel.org/pub/linux/utils/util-linux/</i></a>
</p>
</dd>
<dt>
<span class="term">Vim (6.3) - 3,620 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://ftp.vim.org/pub/vim/unix/"><i>ftp://ftp.vim.org/pub/vim/unix/</i></a>
</p>
</dd>
<dt>
<span class="term">Vim (6.3) language files (optional) -
540 KB:</span>
</dt>
<dd>
<p>
<a href=
"ftp://ftp.vim.org/pub/vim/extra/"><i>ftp://ftp.vim.org/pub/vim/extra/</i></a>
</p>
</dd>
<dt>
<span class="term">Zlib (1.2.3) - 415 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.zlib.net/"><i>http://www.zlib.net/</i></a>
</p>
</dd>
</dl>
</div>
</div>
<p>
Total size of these packages: 146 MB
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="materials-patches" name=
"materials-patches"></a>3.3.&nbsp;Needed Patches
</h2>
</div>
</div>
</div>
<p>
In addition to the packages, several patches are also required.
These patches correct any mistakes in the packages that should
be fixed by the maintainer. The patches also make small
modifications to make the packages easier to work with. The
following patches will be needed to build an LFS system:
</p>
<div class="materials">
<div class="variablelist">
<dl>
<dt>
<span class="term">Bash Avoid Wcontinued Patch - 1
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/bash-3.0-avoid_WCONTINUED-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/bash-3.0-avoid_WCONTINUED-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Bash Various Fixes - 23 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/bash-3.0-fixes-3.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/bash-3.0-fixes-3.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Binutils Build From Host Running Gcc4
Patch - 2 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/binutils-2.15.94.0.2.2-gcc4-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/binutils-2.15.94.0.2.2-gcc4-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Bzip2 Documentation Patch - 1
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/bzip2-1.0.3-install_docs-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/bzip2-1.0.3-install_docs-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Bzip2 Bzgrep Security Fixes Patch - 1
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/bzip2-1.0.3-bzgrep_security-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/bzip2-1.0.3-bzgrep_security-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Coreutils Suppress Uptime, Kill, Su
Patch - 15 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/coreutils-5.2.1-suppress_uptime_kill_su-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/coreutils-5.2.1-suppress_uptime_kill_su-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Coreutils Uname Patch - 4 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/coreutils-5.2.1-uname-2.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/coreutils-5.2.1-uname-2.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Expect Spawn Patch - 7 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/expect-5.43.0-spawn-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/expect-5.43.0-spawn-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Flex Brokenness Patch - 156 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/flex-2.5.31-debian_fixes-3.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/flex-2.5.31-debian_fixes-3.patch</i></a>
</p>
</dd>
<dt>
<span class="term">GCC Linkonce Patch - 12 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/gcc-3.4.3-linkonce-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/gcc-3.4.3-linkonce-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">GCC No-Fixincludes Patch - 1
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/gcc-3.4.3-no_fixincludes-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/gcc-3.4.3-no_fixincludes-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">GCC Specs Patch - 14 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/gcc-3.4.3-specs-2.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/gcc-3.4.3-specs-2.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Glibc Rtld Search Dirs Patch - 1
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/glibc-2.3.4-rtld_search_dirs-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/glibc-2.3.4-rtld_search_dirs-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Glibc Fix Testsuite Patch - 1
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/glibc-2.3.4-fix_test-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/glibc-2.3.4-fix_test-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Glibc TLS Assertion Patch - 6
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/glibc-2.3.4-tls_assert-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/glibc-2.3.4-tls_assert-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Gzip Security Patch - 2 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/gzip-1.3.5-security_fixes-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/gzip-1.3.5-security_fixes-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Inetutils Kernel Headers Patch - 1
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/inetutils-1.4.2-kernel_headers-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/inetutils-1.4.2-kernel_headers-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Inetutils No-Server-Man-Pages Patch -
4 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/inetutils-1.4.2-no_server_man_pages-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/inetutils-1.4.2-no_server_man_pages-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Mktemp Tempfile Patch - 3 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/mktemp-1.5-add_tempfile-2.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/mktemp-1.5-add_tempfile-2.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Perl Libc Patch - 1 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/perl-5.8.7-libc-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/perl-5.8.7-libc-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Readline Fixes Patch - 7 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/readline-5.0-fixes-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/readline-5.0-fixes-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Sysklogd Fixes Patch - 27 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/sysklogd-1.4.1-fixes-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/sysklogd-1.4.1-fixes-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Tar Sparse Fix Patch - 1 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/tar-1.15.1-sparse_fix-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/tar-1.15.1-sparse_fix-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Texinfo Tempfile Fix Patch - 2
KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/texinfo-4.8-tempfile_fix-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/texinfo-4.8-tempfile_fix-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Util-linux Cramfs Patch - 3 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/util-linux-2.12q-cramfs-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/util-linux-2.12q-cramfs-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Util-linux Umount Patch - 1 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/util-linux-2.12q-umount_fix-1.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/util-linux-2.12q-umount_fix-1.patch</i></a>
</p>
</dd>
<dt>
<span class="term">Vim Security Patch - 8 KB:</span>
</dt>
<dd>
<p>
<a href=
"http://www.linuxfromscratch.org/patches/lfs/6.1.1/vim-6.3-security_fix-2.patch">
<i>http://www.linuxfromscratch.org/patches/lfs/6.1.1/vim-6.3-security_fix-2.patch</i></a>
</p>
</dd>
</dl>
</div>
</div>
<p>
In addition to the above required patches, there exist a number
of optional patches created by the LFS community. These
optional patches solve minor problems or enable functionality
that is not enabled by default. Feel free to peruse the patches
database located at <a href=
"http://www.linuxfromscratch.org/patches/"><i>http://www.linuxfromscratch.org/patches/</i></a>
and acquire any additional patches to suit the system needs.
</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-final-preps" name=
"chapter-final-preps"></a>Chapter&nbsp;4.&nbsp;Final
Preparations
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="prepare-aboutlfs" name=
"prepare-aboutlfs"></a>4.1.&nbsp;About $LFS
</h2>
</div>
</div>
</div>
<p>
Throughout this book, the environment variable <tt class=
"envar">LFS</tt> will be used several times. It is paramount
that this variable is always defined. It should be set to the
mount point chosen for the LFS partition. Check that the
<tt class="envar">LFS</tt> variable is set up properly with:
</p>
<pre class="userinput"><kbd class="command">echo $LFS</kbd></pre>
<p>
Make sure the output shows the path to the LFS partition's
mount point, which is <tt class="filename">/mnt/lfs</tt> if the
provided example was followed. If the output is incorrect, the
variable can be set with:
</p>
<pre class="userinput"><kbd class=
"command">export LFS=/mnt/lfs</kbd></pre>
<p>
Having this variable set is beneficial in that commands such as
<span><strong class="command">mkdir $LFS/tools</strong></span>
can be typed literally. The shell will automatically replace
&ldquo;<span class="quote">$LFS</span>&rdquo; with
&ldquo;<span class="quote">/mnt/lfs</span>&rdquo; (or whatever
the variable was set to) when it processes the command line.
</p>
<p>
Do not forget to check that <tt class="envar">$LFS</tt> is set
whenever you leave and reenter the current working environment
(as when doing a &ldquo;<span class="quote">su</span>&rdquo; to
<span class="emphasis"><em>root</em></span> or another user).
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-creatingtoolsdir" name=
"ch-tools-creatingtoolsdir"></a>4.2.&nbsp;Creating the
$LFS/tools Directory
</h2>
</div>
</div>
</div>
<p>
All programs compiled in <a href=
"#chapter-temporary-tools">Chapter 5</a> will be installed
under <tt class="filename">$LFS/tools</tt> to keep them
separate from the programs compiled in <a href=
"#chapter-building-system">Chapter 6</a>. The programs compiled
here are temporary tools and will not be a part of the final
LFS system. By keeping these programs in a separate directory,
they can easily be discarded later after their use. This also
prevents these programs from ending up in the host production
directories (easy to do by accident in <a href=
"#chapter-temporary-tools">Chapter 5</a>).
</p>
<p>
Create the required directory by running the following as
<span class="emphasis"><em>root</em></span>:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v $LFS/tools</kbd></pre>
<p>
The next step is to create a <tt class="filename">/tools</tt>
symlink on the host system. This will point to the
newly-created directory on the LFS partition. Run this command
as <span class="emphasis"><em>root</em></span> as well:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv $LFS/tools /</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
The above command is correct. The <span><strong class=
"command">ln</strong></span> command has a few syntactic
variations, so be sure to check <span><strong class=
"command">info coreutils ln</strong></span> and <tt class=
"filename">ln(1)</tt> before reporting what you may think
is an error.
</p>
</div>
</div>
<p>
The created symlink enables the toolchain to be compiled so
that it always refers to <tt class="filename">/tools</tt>,
meaning that the compiler, assembler, and linker will work both
in this chapter (when we are still using some tools from the
host) and in the next (when we are &ldquo;<span class=
"quote">chrooted</span>&rdquo; to the LFS partition).
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-addinguser" name=
"ch-tools-addinguser"></a>4.3.&nbsp;Adding the LFS User
</h2>
</div>
</div>
</div>
<p>
When logged in as user <span class=
"emphasis"><em>root</em></span>, making a single mistake can
damage or destroy a system. Therefore, we recommend building
the packages in this chapter as an unprivileged user. You could
use your own user name, but to make it easier to set up a clean
working environment, create a new user called <span class=
"emphasis"><em>lfs</em></span> as a member of a new group (also
named <span class="emphasis"><em>lfs</em></span>) and use this
user during the installation process. As <span class=
"emphasis"><em>root</em></span>, issue the following commands
to add the new user:
</p>
<pre class="userinput"><kbd class="command">groupadd lfs
useradd -s /bin/bash -g lfs -m -k /dev/null lfs</kbd></pre>
<p>
The meaning of the command line options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class="parameter"><tt>-s
/bin/bash</tt></em></span>
</dt>
<dd>
<p>
This makes <span><strong class=
"command">bash</strong></span> the default shell for user
<span class="emphasis"><em>lfs</em></span>.
</p>
</dd>
<dt>
<span class="term"><em class="parameter"><tt>-g
lfs</tt></em></span>
</dt>
<dd>
<p>
This option adds user <span class=
"emphasis"><em>lfs</em></span> to group <span class=
"emphasis"><em>lfs</em></span>.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>-m</tt></em></span>
</dt>
<dd>
<p>
This creates a home directory for <span class=
"emphasis"><em>lfs</em></span>.
</p>
</dd>
<dt>
<span class="term"><em class="parameter"><tt>-k
/dev/null</tt></em></span>
</dt>
<dd>
<p>
This parameter prevents possible copying of files from a
skeleton directory (default is <tt class=
"filename">/etc/skel</tt>) by changing the input location
to the special null device.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>lfs</tt></em></span>
</dt>
<dd>
<p>
This is the actual name for the created group and user.
</p>
</dd>
</dl>
</div>
<p>
To log in as <span class="emphasis"><em>lfs</em></span> (as
opposed to switching to user <span class=
"emphasis"><em>lfs</em></span> when logged in as <span class=
"emphasis"><em>root</em></span>, which does not require the
<span class="emphasis"><em>lfs</em></span> user to have a
password), give <span class="emphasis"><em>lfs</em></span> a
password:
</p>
<pre class="userinput"><kbd class=
"command">passwd lfs</kbd></pre>
<p>
Grant <span class="emphasis"><em>lfs</em></span> full access to
<tt class="filename">$LFS/tools</tt> by making <span class=
"emphasis"><em>lfs</em></span> the directory owner:
</p>
<pre class="userinput"><kbd class=
"command">chown -v lfs $LFS/tools</kbd></pre>
<p>
If a separate working directory was created as suggested, give
user <span class="emphasis"><em>lfs</em></span> ownership of
this directory:
</p>
<pre class="userinput"><kbd class=
"command">chown -v lfs $LFS/sources</kbd></pre>
<p>
Next, login as user <span class="emphasis"><em>lfs</em></span>.
This can be done via a virtual console, through a display
manager, or with the following substitute user command:
</p>
<pre class="userinput"><kbd class="command">su - lfs</kbd></pre>
<p>
The &ldquo;<span class="quote"><em class=
"parameter"><tt>-</tt></em></span>&rdquo; instructs
<span><strong class="command">su</strong></span> to start a
login shell as opposed to a non-login shell. The difference
between these two types of shells can be found in detail in
<tt class="filename">bash(1)</tt> and <span><strong class=
"command">info bash</strong></span>.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-settingenviron" name=
"ch-tools-settingenviron"></a>4.4.&nbsp;Setting Up the
Environment
</h2>
</div>
</div>
</div>
<p>
Set up a good working environment by creating two new startup
files for the <span><strong class=
"command">bash</strong></span> shell. While logged in as user
<span class="emphasis"><em>lfs</em></span>, issue the following
command to create a new <tt class=
"filename">.bash_profile</tt>:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; ~/.bash_profile &lt;&lt; "EOF"
<tt class=
"literal">exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</tt>
EOF</kbd></pre>
<p>
When logged on as user <span class=
"emphasis"><em>lfs</em></span>, the initial shell is usually a
<span class="emphasis"><em>login</em></span> shell which reads
the <tt class="filename">/etc/profile</tt> of the host
(probably containing some settings and environment variables)
and then <tt class="filename">.bash_profile</tt>. The
<span><strong class="command">exec env
-i.../bin/bash</strong></span> command in the <tt class=
"filename">.bash_profile</tt> file replaces the running shell
with a new one with a completely empty environment, except for
the <tt class="envar">HOME</tt>, <tt class="envar">TERM</tt>,
and <tt class="envar">PS1</tt> variables. This ensures that no
unwanted and potentially hazardous environment variables from
the host system leak into the build environment. The technique
used here achieves the goal of ensuring a clean environment.
</p>
<p>
The new instance of the shell is a <span class=
"emphasis"><em>non-login</em></span> shell, which does not read
the <tt class="filename">/etc/profile</tt> or <tt class=
"filename">.bash_profile</tt> files, but rather reads the
<tt class="filename">.bashrc</tt> file instead. Create the
<tt class="filename">.bashrc</tt> file now:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; ~/.bashrc &lt;&lt; "EOF"
<tt class="literal">set +h
umask 022
LFS=/mnt/lfs
LC_ALL=POSIX
PATH=/tools/bin:/bin:/usr/bin
export LFS LC_ALL PATH</tt>
EOF</kbd></pre>
<p>
The <span><strong class="command">set +h</strong></span>
command turns off <span><strong class=
"command">bash</strong></span>'s hash function. Hashing is
ordinarily a useful feature&mdash;<span><strong class=
"command">bash</strong></span> uses a hash table to remember
the full path of executable files to avoid searching the
<tt class="envar">PATH</tt> time and again to find the same
executable. However, the new tools should be used as soon as
they are installed. By switching off the hash function, the
shell will always search the <tt class="envar">PATH</tt> when a
program is to be run. As such, the shell will find the newly
compiled tools in <tt class="filename">$LFS/tools</tt> as soon
as they are available without remembering a previous version of
the same program in a different location.
</p>
<p>
Setting the user file-creation mask (umask) to 022 ensures that
newly created files and directories are only writable by their
owner, but are readable and executable by anyone (assuming
default modes are used by the open(2) system call, new files
will end up with permission mode 644 and directories with mode
755).
</p>
<p>
The <tt class="envar">LFS</tt> variable should be set to the
chosen mount point.
</p>
<p>
The <tt class="envar">LC_ALL</tt> variable controls the
localization of certain programs, making their messages follow
the conventions of a specified country. If the host system uses
a version of Glibc older than 2.2.4, having <tt class=
"envar">LC_ALL</tt> set to something other than
&ldquo;<span class="quote">POSIX</span>&rdquo; or
&ldquo;<span class="quote">C</span>&rdquo; (during this
chapter) may cause issues if you exit the chroot environment
and wish to return later. Setting <tt class="envar">LC_ALL</tt>
to &ldquo;<span class="quote">POSIX</span>&rdquo; or
&ldquo;<span class="quote">C</span>&rdquo; (the two are
equivalent) ensures that everything will work as expected in
the chroot environment.
</p>
<p>
By putting <tt class="filename">/tools/bin</tt> ahead of the
standard <tt class="envar">PATH</tt>, all the programs
installed in <a href="#chapter-temporary-tools">Chapter 5</a>
are picked up by the shell immediately after their
installation. This, combined with turning off hashing, limits
the risk that old programs are used from the host when the same
programs are available in the chapter 5 environment.
</p>
<p>
Finally, to have the environment fully prepared for building
the temporary tools, source the just-created user profile:
</p>
<pre class="userinput"><kbd class=
"command">source ~/.bash_profile</kbd></pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="prepare-aboutsbus" name=
"prepare-aboutsbus"></a>4.5.&nbsp;About SBUs
</h2>
</div>
</div>
</div>
<p>
Many people would like to know beforehand approximately how
long it takes to compile and install each package. Because
Linux From Scratch can be built on many different systems, it
is impossible to provide accurate time estimates. The biggest
package (Glibc) will take approximately 20 minutes on the
fastest systems, but could take up to three days on slower
systems! Instead of providing actual times, the Standard Build
Unit (SBU) measure will be used instead.
</p>
<p>
The SBU measure works as follows. The first package to be
compiled from this book is Binutils in <a href=
"#chapter-temporary-tools">Chapter 5</a>. The time it takes to
compile this package is what will be referred to as the
Standard Build Unit or SBU. All other compile times will be
expressed relative to this time.
</p>
<p>
For example, consider a package whose compilation time is 4.5
SBUs. This means that if a system took 10 minutes to compile
and install the first pass of Binutils, it will take
<span class="emphasis"><em>approximately</em></span> 45 minutes
to build this example package. Fortunately, most build times
are shorter than the one for Binutils.
</p>
<p>
In general, SBUs are not entirely accurate because they depend
on many factors, including the host system's version of GCC.
Note that on Symmetric Multi-Processor (SMP)-based machines,
SBUs are even less accurate. They are provided here to give an
estimate of how long it might take to install a package, but
the numbers can vary by as much as dozens of minutes in some
cases.
</p>
<p>
To view actual timings for a number of specific machines, we
recommend The LinuxFromScratch SBU Home Page at <a href=
"http://www.linuxfromscratch.org/~bdubbs/"><i>http://www.linuxfromscratch.org/~bdubbs/</i></a>.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="prepare-abouttestsuites" name=
"prepare-abouttestsuites"></a>4.6.&nbsp;About the Test
Suites
</h2>
</div>
</div>
</div>
<p>
Most packages provide a test suite. Running the test suite for
a newly built package is a good idea because it can provide a
&ldquo;<span class="quote">sanity check</span>&rdquo;
indicating that everything compiled correctly. A test suite
that passes its set of checks usually proves that the package
is functioning as the developer intended. It does not, however,
guarantee that the package is totally bug free.
</p>
<p>
Some test suites are more important than others. For example,
the test suites for the core toolchain packages&mdash;GCC,
Binutils, and Glibc&mdash;are of the utmost importance due to
their central role in a properly functioning system. The test
suites for GCC and Glibc can take a very long time to complete,
especially on slower hardware, but are strongly recommended.
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
Experience has shown that there is little to be gained from
running the test suites in <a href=
"#chapter-temporary-tools">Chapter 5</a>. There can be no
escaping the fact that the host system always exerts some
influence on the tests in that chapter, often causing
inexplicable failures. Because the tools built in <a href=
"#chapter-temporary-tools">Chapter 5</a> are temporary and
eventually discarded, we do not recommend running the test
suites in <a href="#chapter-temporary-tools">Chapter 5</a>
for the average reader. The instructions for running those
test suites are provided for the benefit of testers and
developers, but they are strictly optional.
</p>
</div>
</div>
<p>
A common issue with running the test suites for Binutils and
GCC is running out of pseudo terminals (PTYs). This can result
in a high number of failing tests. This may happen for several
reasons, but the most likely cause is that the host system does
not have the <tt class="systemitem">devpts</tt> file system set
up correctly. This issue is discussed in greater detail in
<a href="#chapter-temporary-tools">Chapter 5</a>.
</p>
<p>
Sometimes package test suites will fail, but for reasons which
the developers are aware of and have deemed non-critical.
Consult the logs located at <a href=
"http://www.linuxfromscratch.org/lfs/build-logs/6.1.1/"><i>http://www.linuxfromscratch.org/lfs/build-logs/6.1.1/</i></a>
to verify whether or not these failures are expected. This site
is valid for all tests throughout this book.
</p>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-temporary-tools" name=
"chapter-temporary-tools"></a>Chapter&nbsp;5.&nbsp;Constructing
a Temporary System
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-introduction" name=
"ch-tools-introduction"></a>5.1.&nbsp;Introduction
</h2>
</div>
</div>
</div>
<p>
This chapter shows how to compile and install a minimal Linux
system. This system will contain just enough tools to start
constructing the final LFS system in <a href=
"#chapter-building-system">Chapter 6</a> and allow a working
environment with more user convenience than a minimum
environment would.
</p>
<p>
There are two steps in building this minimal system. The first
step is to build a new and host-independent toolchain
(compiler, assembler, linker, libraries, and a few useful
utilities). The second step uses this toolchain to build the
other essential tools.
</p>
<p>
The files compiled in this chapter will be installed under the
<tt class="filename">$LFS/tools</tt> directory to keep them
separate from the files installed in the next chapter and the
host production directories. Since the packages compiled here
are temporary, we do not want them to pollute the soon-to-be
LFS system.
</p>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
Before issuing the build instructions for a package, the
package should be unpacked as user <span class=
"emphasis"><em>lfs</em></span>, and a <span><strong class=
"command">cd</strong></span> into the created directory
should be performed. The build instructions assume that the
<span><strong class="command">bash</strong></span> shell is
in use.
</p>
</div>
</div>
<p>
Several of the packages are patched before compilation, but
only when the patch is needed to circumvent a problem. A patch
is often needed in both this and the next chapter, but
sometimes in only one or the other. Therefore, do not be
concerned if instructions for a downloaded patch seem to be
missing. Warning messages about <span class=
"emphasis"><em>offset</em></span> or <span class=
"emphasis"><em>fuzz</em></span> may also be encountered when
applying a patch. Do not worry about these warnings, as the
patch was still successfully applied.
</p>
<p>
During the compilation of most packages, there will be several
warnings that scroll by on the screen. These are normal and can
safely be ignored. These warnings are as they
appear&mdash;warnings about deprecated, but not invalid, use of
the C or C++ syntax. C standards change fairly often, and some
packages still use the older standard. This is not a problem,
but does prompt the warning.
</p>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
After installing each package, delete its source and build
directories, unless specifically instructed otherwise.
Deleting the sources prevents mis-configuration when the
same package is reinstalled later. Only three of the
packages need to retain the source and build directories in
order for their contents to be used by later commands. Pay
special attention to these reminders.
</p>
</div>
</div>
<p>
Check one last time that the <tt class="envar">LFS</tt>
environment variable is set up properly:
</p>
<pre class="userinput"><kbd class="command">echo $LFS</kbd></pre>
<p>
Make sure the output shows the path to the LFS partition's
mount point, which is <tt class="filename">/mnt/lfs</tt>, using
our example.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-toolchaintechnotes" name=
"ch-tools-toolchaintechnotes"></a>5.2.&nbsp;Toolchain
Technical Notes
</h2>
</div>
</div>
</div>
<p>
This section explains some of the rationale and technical
details behind the overall build method. It is not essential to
immediately understand everything in this section. Most of this
information will be clearer after performing an actual build.
This section can be referred back to at any time during the
process.
</p>
<p>
The overall goal of <a href="#chapter-temporary-tools">Chapter
5</a> is to provide a temporary environment that can be
chrooted into and from which can be produced a clean,
trouble-free build of the target LFS system in <a href=
"#chapter-building-system">Chapter 6</a>. Along the way, we
separate the new system from the host system as much as
possible, and in doing so, build a self-contained and
self-hosted toolchain. It should be noted that the build
process has been designed to minimize the risks for new readers
and provide maximum educational value at the same time.
</p>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
Before continuing, be aware of the name of the working
platform, often referred to as the target triplet. Many
times, the target triplet will probably be <span class=
"emphasis"><em>i686-pc-linux-gnu</em></span>. A simple way
to determine the name of the target triplet is to run the
<span><strong class="command">config.guess</strong></span>
script that comes with the source for many packages. Unpack
the Binutils sources and run the script: <strong class=
"userinput"><tt>./config.guess</tt></strong> and note the
output.
</p>
<p>
Also be aware of the name of the platform's dynamic linker,
often referred to as the dynamic loader (not to be confused
with the standard linker <span><strong class=
"command">ld</strong></span> that is part of Binutils). The
dynamic linker provided by Glibc finds and loads the shared
libraries needed by a program, prepares the program to run,
and then runs it. The name of the dynamic linker will
usually be <tt class="filename">ld-linux.so.2</tt>. On
platforms that are less prevalent, the name might be
<tt class="filename">ld.so.1</tt>, and newer 64 bit
platforms might be named something else entirely. The name
of the platform's dynamic linker can be determined by
looking in the <tt class="filename">/lib</tt> directory on
the host system. A sure-fire way to determine the name is
to inspect a random binary from the host system by running:
<strong class="userinput"><tt>readelf -l &lt;name of
binary&gt; | grep interpreter</tt></strong> and noting the
output. The authoritative reference covering all platforms
is in the <tt class="filename">shlib-versions</tt> file in
the root of the Glibc source tree.
</p>
</div>
</div>
<p>
Some key technical points of how the <a href=
"#chapter-temporary-tools">Chapter 5</a> build method works:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
The process is similar in principle to cross-compiling,
whereby tools installed in the same prefix work in
cooperation, and thus utilize a little GNU
&ldquo;<span class="quote">magic</span>&rdquo;
</p>
</li>
<li>
<p>
Careful manipulation of the standard linker's library
search path ensures programs are linked only against
chosen libraries
</p>
</li>
<li>
<p>
Careful manipulation of <span><strong class=
"command">gcc</strong></span>'s <tt class=
"filename">specs</tt> file tells the compiler which
target dynamic linker will be used
</p>
</li>
</ul>
</div>
<p>
Binutils is installed first because the <span><strong class=
"command">configure</strong></span> runs of both GCC and Glibc
perform various feature tests on the assembler and linker to
determine which software features to enable or disable. This is
more important than one might first realize. An incorrectly
configured GCC or Glibc can result in a subtly broken
toolchain, where the impact of such breakage might not show up
until near the end of the build of an entire distribution. A
test suite failure will usually highlight this error before too
much additional work is performed.
</p>
<p>
Binutils installs its assembler and linker in two locations,
<tt class="filename">/tools/bin</tt> and <tt class=
"filename">/tools/$TARGET_TRIPLET/bin</tt>. The tools in one
location are hard linked to the other. An important facet of
the linker is its library search order. Detailed information
can be obtained from <span><strong class=
"command">ld</strong></span> by passing it the <em class=
"parameter"><tt>--verbose</tt></em> flag. For example, an
<strong class="userinput"><tt>ld --verbose | grep
SEARCH</tt></strong> will illustrate the current search paths
and their order. It shows which files are linked by
<span><strong class="command">ld</strong></span> by compiling a
dummy program and passing the <em class=
"parameter"><tt>--verbose</tt></em> switch to the linker. For
example, <strong class="userinput"><tt>gcc dummy.c
-Wl,--verbose 2&gt;&amp;1 | grep succeeded</tt></strong> will
show all the files successfully opened during the linking.
</p>
<p>
The next package installed is GCC. An example of what can be
seen during its run of <span><strong class=
"command">configure</strong></span> is:
</p>
<pre class="screen"><tt class=
"computeroutput">checking what assembler to use...
/tools/i686-pc-linux-gnu/bin/as
checking what linker to use... /tools/i686-pc-linux-gnu/bin/ld</tt></pre>
<p>
This is important for the reasons mentioned above. It also
demonstrates that GCC's configure script does not search the
PATH directories to find which tools to use. However, during
the actual operation of <span><strong class=
"command">gcc</strong></span> itself, the same search paths are
not necessarily used. To find out which standard linker
<span><strong class="command">gcc</strong></span> will use,
run: <strong class="userinput"><tt>gcc
-print-prog-name=ld</tt></strong>.
</p>
<p>
Detailed information can be obtained from <span><strong class=
"command">gcc</strong></span> by passing it the <em class=
"parameter"><tt>-v</tt></em> command line option while
compiling a dummy program. For example, <strong class=
"userinput"><tt>gcc -v dummy.c</tt></strong> will show detailed
information about the preprocessor, compilation, and assembly
stages, including <span><strong class=
"command">gcc</strong></span>'s included search paths and their
order.
</p>
<p>
The next package installed is Glibc. The most important
considerations for building Glibc are the compiler, binary
tools, and kernel headers. The compiler is generally not an
issue since Glibc will always use the <span><strong class=
"command">gcc</strong></span> found in a <tt class=
"envar">PATH</tt> directory. The binary tools and kernel
headers can be a bit more complicated. Therefore, take no risks
and use the available configure switches to enforce the correct
selections. After the run of <span><strong class=
"command">configure</strong></span>, check the contents of the
<tt class="filename">config.make</tt> file in the <tt class=
"filename">glibc-build</tt> directory for all important
details. Note the use of <em class="parameter"><tt>CC="gcc
-B/tools/bin/"</tt></em> to control which binary tools are used
and the use of the <em class=
"parameter"><tt>-nostdinc</tt></em> and <em class=
"parameter"><tt>-isystem</tt></em> flags to control the
compiler's include search path. These items highlight an
important aspect of the Glibc package&mdash;it is very
self-sufficient in terms of its build machinery and generally
does not rely on toolchain defaults.
</p>
<p>
After the Glibc installation, make some adjustments to ensure
that searching and linking take place only within the
<tt class="filename">/tools</tt> prefix. Install an adjusted
<span><strong class="command">ld</strong></span>, which has a
hard-wired search path limited to <tt class=
"filename">/tools/lib</tt>. Then amend <span><strong class=
"command">gcc</strong></span>'s specs file to point to the new
dynamic linker in <tt class="filename">/tools/lib</tt>. This
last step is vital to the whole process. As mentioned above, a
hard-wired path to a dynamic linker is embedded into every
Executable and Link Format (ELF)-shared executable. This can be
inspected by running: <strong class="userinput"><tt>readelf -l
&lt;name of binary&gt; | grep interpreter</tt></strong>.
Amending gcc's specs file ensures that every program compiled
from here through the end of this chapter will use the new
dynamic linker in <tt class="filename">/tools/lib</tt>.
</p>
<p>
The need to use the new dynamic linker is also the reason why
the Specs patch is applied for the second pass of GCC. Failure
to do so will result in the GCC programs themselves having the
name of the dynamic linker from the host system's <tt class=
"filename">/lib</tt> directory embedded into them, which would
defeat the goal of getting away from the host.
</p>
<p>
During the second pass of Binutils, we are able to utilize the
<em class="parameter"><tt>--with-lib-path</tt></em> configure
switch to control <span><strong class=
"command">ld</strong></span>'s library search path. From this
point onwards, the core toolchain is self-contained and
self-hosted. The remainder of the <a href=
"#chapter-temporary-tools">Chapter 5</a> packages all build
against the new Glibc in <tt class="filename">/tools</tt>.
</p>
<p>
Upon entering the chroot environment in <a href=
"#chapter-building-system">Chapter 6</a>, the first major
package to be installed is Glibc, due to its self-sufficient
nature mentioned above. Once this Glibc is installed into
<tt class="filename">/usr</tt>, perform a quick changeover of
the toolchain defaults, then proceed in building the rest of
the target LFS system.
</p>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-binutils-pass1" name=
"ch-tools-binutils-pass1"></a>5.3.&nbsp;Binutils-2.15.94.0.2.2
- Pass 1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Binutils package contains a linker, an assembler, and
other tools for handling object files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">1.0 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">179 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Bison,
Coreutils, Diffutils, Flex, GCC, Gettext, Glibc, Grep,
M4, Make, Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.3.1. Installation of Binutils
</h3>
</div>
<p>
It is important that Binutils be the first package compiled
because both Glibc and GCC perform various tests on the
available linker and assembler to determine which of their
own features to enable.
</p>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
Binutils.
</p>
<p>
If you are building from a host running Gcc-4 or later, it is
necessary to patch the first build of this version of
Binutils so that it can be compiled by the host system.
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../binutils-2.15.94.0.2.2-gcc4-1.patch</kbd></pre>
<p>
The Binutils documentation recommends building Binutils
outside of the source directory in a dedicated build
directory:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../binutils-build
cd ../binutils-build</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
In order for the SBU values listed in the rest of the
book to be of any use, measure the time it takes to build
this package from the configuration, up to and including
the first install. To achieve this easily, wrap the three
commands in a <span><strong class=
"command">time</strong></span> command like this:
<strong class="userinput"><tt>time { ./configure ...
&amp;&amp; make &amp;&amp; make install; }</tt></strong>.
</p>
</div>
</div>
<p>
Now prepare Binutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../binutils-2.15.94.0.2.2/configure --prefix=/tools --disable-nls</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--prefix=/tools</tt></em></span>
</dt>
<dd>
<p>
This tells the configure script to prepare to install
the Binutils programs in the <tt class=
"filename">/tools</tt> directory.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-nls</tt></em></span>
</dt>
<dd>
<p>
This disables internationalization as i18n is not
needed for the temporary tools.
</p>
</dd>
</dl>
</div>
<p>
Continue with compiling the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Compilation is now complete. Ordinarily we would now run the
test suite, but at this early stage the test suite framework
(Tcl, Expect, and DejaGNU) is not yet in place. The benefits
of running the tests at this point are minimal since the
programs from this first pass will soon be replaced by those
from the second.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Next, prepare the linker for the &ldquo;<span class=
"quote">Adjusting</span>&rdquo; phase later on:
</p>
<pre class="userinput"><kbd class="command">make -C ld clean
make -C ld LIB_PATH=/tools/lib</kbd></pre>
<p>
The meaning of the make parameters:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class="parameter"><tt>-C ld
clean</tt></em></span>
</dt>
<dd>
<p>
This tells the make program to remove all compiled
files in the <tt class="filename">ld</tt> subdirectory.
</p>
</dd>
<dt>
<span class="term"><em class="parameter"><tt>-C ld
LIB_PATH=/tools/lib</tt></em></span>
</dt>
<dd>
<p>
This option rebuilds everything in the <tt class=
"filename">ld</tt> subdirectory. Specifying the
<tt class="envar">LIB_PATH</tt> Makefile variable on
the command line allows us to override the default
value and point it to the temporary tools location. The
value of this variable specifies the linker's default
library search path. This preparation is used later in
the chapter.
</p>
</dd>
</dl>
</div>
<div class="warning">
<div class="admonhead">
<h3 class="admontitle">
Warning
</h3>
</div>
<div class="admonbody">
<p>
<span class="emphasis"><em>Do not</em></span> remove the
Binutils build and source directories yet. These will be
needed again in their current state later in this
chapter.
</p>
</div>
</div>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-binutils" title=
"6.13.2.&nbsp;Contents of Binutils">Section&nbsp;6.13.2,
&ldquo;Contents of Binutils.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-gcc-pass1" name=
"ch-tools-gcc-pass1"></a>5.4.&nbsp;GCC-3.4.3 - Pass 1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The GCC package contains the GNU compiler collection, which
includes the C and C++ compilers.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">4.4 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">219 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Findutils, Gawk, Gettext, Glibc,
Grep, Make, Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.4.1. Installation of GCC
</h3>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
GCC.
</p>
<p>
The GCC documentation recommends building GCC outside of the
source directory in a dedicated build directory:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../gcc-build
cd ../gcc-build</kbd></pre>
<p>
Prepare GCC for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../gcc-3.4.3/configure --prefix=/tools \
--libexecdir=/tools/lib --with-local-prefix=/tools \
--disable-nls --enable-shared --enable-languages=c</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-local-prefix=/tools</tt></em></span>
</dt>
<dd>
<p>
The purpose of this switch is to remove <tt class=
"filename">/usr/local/include</tt> from
<span><strong class="command">gcc</strong></span>'s
include search path. This is not absolutely essential,
however, it helps to minimize the influence of the host
system.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-shared</tt></em></span>
</dt>
<dd>
<p>
This switch allows the building of <tt class=
"filename">libgcc_s.so.1</tt> and <tt class=
"filename">libgcc_eh.a</tt>. Having <tt class=
"filename">libgcc_eh.a</tt> available ensures that the
configure script for Glibc (the next package we
compile) produces the proper results.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-languages=c</tt></em></span>
</dt>
<dd>
<p>
This option ensures that only the C compiler is built.
</p>
</dd>
</dl>
</div>
<p>
Continue with compiling the package:
</p>
<pre class="userinput"><kbd class=
"command">make bootstrap</kbd></pre>
<p>
The meaning of the make parameters:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>bootstrap</tt></em></span>
</dt>
<dd>
<p>
This target does not just compile GCC, but compiles it
several times. It uses the programs compiled in a first
round to compile itself a second time, and then again a
third time. It then compares these second and third
compiles to make sure it can reproduce itself
flawlessly. This also implies that it was compiled
correctly.
</p>
</dd>
</dl>
</div>
<p>
Compilation is now complete. At this point, the test suite
would normally be run, but, as mentioned before, the test
suite framework is not in place yet. The benefits of running
the tests at this point are minimal since the programs from
this first pass will soon be replaced.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
As a finishing touch, create a symlink. Many programs and
scripts run <span><strong class="command">cc</strong></span>
instead of <span><strong class="command">gcc</strong></span>,
which is used to keep programs generic and therefore usable
on all kinds of UNIX systems where the GNU C compiler is not
always installed. Running <span><strong class=
"command">cc</strong></span> leaves the system administrator
free to decide which C compiler to install.
</p>
<pre class="userinput"><kbd class=
"command">ln -vs gcc /tools/bin/cc</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-gcc" title=
"6.14.2.&nbsp;Contents of GCC">Section&nbsp;6.14.2,
&ldquo;Contents of GCC.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-linux-libc-headers" name=
"ch-tools-linux-libc-headers"></a>5.5.&nbsp;Linux-Libc-Headers-2.6.11.2
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Linux-Libc-Headers package contains the
&ldquo;<span class="quote">sanitized</span>&rdquo; kernel
headers.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">26.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Coreutils</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.5.1. Installation of Linux-Libc-Headers
</h3>
</div>
<p>
For years it has been common practice to use
&ldquo;<span class="quote">raw</span>&rdquo; kernel headers
(straight from a kernel tarball) in <tt class=
"filename">/usr/include</tt>, but over the last few years,
the kernel developers have taken a strong stance that this
should not be done. This gave birth to the Linux-Libc-Headers
Project, which was designed to maintain an Application
Programming Interface (API) stable version of the Linux
headers.
</p>
<p>
Install the header files:
</p>
<pre class="userinput"><kbd class=
"command">cp -Rv include/asm-i386 /tools/include/asm
cp -Rv include/linux /tools/include</kbd></pre>
<p>
If your architecture is not i386 (compatible), adjust the
first command accordingly.
</p>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-linux-libc-headers" title=
"6.9.2.&nbsp;Contents of Linux-Libc-Headers">Section&nbsp;6.9.2,
&ldquo;Contents of Linux-Libc-Headers.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-glibc" name=
"ch-tools-glibc"></a>5.6.&nbsp;Glibc-2.3.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Glibc package contains the main C library. This library
provides the basic routines for allocating memory, searching
directories, opening and closing files, reading and writing
files, string handling, pattern matching, arithmetic, and so
on.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">11.8 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">454 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Gettext, Grep, Make,
Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.6.1. Installation of Glibc
</h3>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
Glibc.
</p>
<p>
It should be noted that compiling Glibc in any way other than
the method suggested in this book puts the stability of the
system at risk.
</p>
<p>
Glibc has two tests which fail when the running kernel is
2.6.11 or later. The problem has been determined to be with
the tests themselves, not with the C library or the kernel.
If you plan to run the testsuite apply this patch:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../glibc-2.3.4-fix_test-1.patch</kbd></pre>
<p>
The Glibc documentation recommends building Glibc outside of
the source directory in a dedicated build directory:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../glibc-build
cd ../glibc-build</kbd></pre>
<p>
Next, prepare Glibc for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../glibc-2.3.4/configure --prefix=/tools \
--disable-profile --enable-add-ons \
--enable-kernel=2.6.0 --with-binutils=/tools/bin \
--without-gd --with-headers=/tools/include \
--without-selinux</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-profile</tt></em></span>
</dt>
<dd>
<p>
This builds the libraries without profiling
information. Omit this option if profiling on the
temporary tools is necessary.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-add-ons</tt></em></span>
</dt>
<dd>
<p>
This tells Glibc to use the NPTL add-on as its
threading library.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-kernel=2.6.0</tt></em></span>
</dt>
<dd>
<p>
This tells Glibc to compile the library with support
for 2.6.x Linux kernels.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-binutils=/tools/bin</tt></em></span>
</dt>
<dd>
<p>
While not required, this switch ensures that there are
no errors pertaining to which Binutils programs get
used during the Glibc build.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--without-gd</tt></em></span>
</dt>
<dd>
<p>
This prevents the build of the <span><strong class=
"command">memusagestat</strong></span> program, which
insists on linking against the host's libraries (libgd,
libpng, libz, etc.).
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-headers=/tools/include</tt></em></span>
</dt>
<dd>
<p>
This tells Glibc to compile itself against the headers
recently installed to the tools directory, so that it
knows exactly what features the kernel has and can
optimize itself accordingly.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--without-selinux</tt></em></span>
</dt>
<dd>
<p>
When building from hosts that include SELinux
functionality (e.g. Fedora Core 3), Glibc will build
with support for SELinux. As the LFS tools environment
does not contain support for SELinux, a Glibc compiled
with such support will fail to operate correctly.
</p>
</dd>
</dl>
</div>
<p>
During this stage the following warning might appear:
</p>
<div class="blockquote">
<blockquote class="blockquote">
<pre class="screen"><tt class=
"computeroutput">configure: WARNING:
*** These auxiliary programs are missing or
*** incompatible versions: msgfmt
*** some features will be disabled.
*** Check the INSTALL file for required versions.</tt></pre>
</blockquote>
</div>
<p>
The missing or incompatible <span><strong class=
"command">msgfmt</strong></span> program is generally
harmless, but it can sometimes cause issues when running the
test suite. This <span><strong class=
"command">msgfmt</strong></span> program is part of the
Gettext package which the host distribution should provide.
If <span><strong class="command">msgfmt</strong></span> is
present but deemed incompatible, upgrade the host system's
Gettext package or continue without it and see if the test
suite runs without problems regardless.
</p>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Compilation is now complete. As mentioned earlier, running
the test suites for the temporary tools installed in this
chapter is not mandatory. To run the Glibc test suite (if
desired), the following command will do so:
</p>
<pre class="userinput"><kbd class=
"command">make check</kbd></pre>
<p>
For a discussion of test failures that are of particular
importance, please see <a href="#ch-system-glibc" title=
"6.11.&nbsp;Glibc-2.3.4">Section 6.11,
&ldquo;Glibc-2.3.4.&rdquo;</a>
</p>
<p>
In this chapter, some tests can be adversely affected by
existing tools or environmental issues on the host system.
Glibc test suite failures in this chapter are typically not
worrisome. The Glibc installed in <a href=
"#chapter-building-system">Chapter 6</a> is the one that will
ultimately end up being used, so that is the one that needs
to pass most tests (even in <a href=
"#chapter-building-system">Chapter 6</a>, some failures could
still occur, for example, with the math tests).
</p>
<p>
When experiencing a failure, make a note of it, then continue
by reissuing the <span><strong class="command">make
check</strong></span> command. The test suite should pick up
where it left off and continue. This stop-start sequence can
be circumvented by issuing a <span><strong class=
"command">make -k check</strong></span> command. If using
this option, be sure to log the output so that the log file
can be examined for failures later.
</p>
<p>
The install stage of Glibc will issue a harmless warning at
the end about the absence of <tt class=
"filename">/tools/etc/ld.so.conf</tt>. Prevent this warning
with:
</p>
<pre class="userinput"><kbd class="command">mkdir -v /tools/etc
touch /tools/etc/ld.so.conf</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Different countries and cultures have varying conventions for
how to communicate. These conventions range from the format
for representing dates and times to more complex issues, such
as the language spoken. The &ldquo;<span class=
"quote">internationalization</span>&rdquo; of GNU programs
works by locale.
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
If the test suites are not being run in this chapter (as
per the recommendation), there is no need to install the
locales now. The appropriate locales will be installed in
the next chapter.
</p>
</div>
</div>
<p>
To install the Glibc locales anyway, use the following
command:
</p>
<pre class="userinput"><kbd class=
"command">make localedata/install-locales</kbd></pre>
<p>
To save time, an alternative to running the previous command
(which generates and installs every locale Glibc is aware of)
is to install only those locales that are wanted and needed.
This can be achieved by using the <span><strong class=
"command">localedef</strong></span> command. Information on
this command is located in the <tt class=
"filename">INSTALL</tt> file in the Glibc source. However,
there are a number of locales that are essential in order for
the tests of future packages to pass, in particular, the
<span class="emphasis"><em>libstdc++</em></span> tests from
GCC. The following instructions, instead of the <em class=
"parameter"><tt>install-locales</tt></em> target used above,
will install the minimum set of locales necessary for the
tests to run successfully:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -pv /tools/lib/locale
localedef -i de_DE -f ISO-8859-1 de_DE
localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
localedef -i en_HK -f ISO-8859-1 en_HK
localedef -i en_PH -f ISO-8859-1 en_PH
localedef -i en_US -f ISO-8859-1 en_US
localedef -i es_MX -f ISO-8859-1 es_MX
localedef -i fa_IR -f UTF-8 fa_IR
localedef -i fr_FR -f ISO-8859-1 fr_FR
localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro
localedef -i it_IT -f ISO-8859-1 it_IT
localedef -i ja_JP -f EUC-JP ja_JP</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-glibc" title=
"6.11.4.&nbsp;Contents of Glibc">Section&nbsp;6.11.4,
&ldquo;Contents of Glibc.&rdquo;</a>
</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-adjusting" name=
"ch-tools-adjusting"></a>5.7.&nbsp;Adjusting the
Toolchain
</h2>
</div>
</div>
</div>
<p>
Now that the temporary C libraries have been installed, all
tools compiled in the rest of this chapter should be linked
against these libraries. In order to accomplish this, the
linker and the compiler's specs file need to be adjusted.
</p>
<p>
The linker, adjusted at the end of the first pass of Binutils,
is installed by running the following command from within the
<tt class="filename">binutils-build</tt> directory:
</p>
<pre class="userinput"><kbd class=
"command">make -C ld install</kbd></pre>
<p>
From this point onwards, everything will link only against the
libraries in <tt class="filename">/tools/lib</tt>.
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
If the earlier warning to retain the Binutils source and
build directories from the first pass was missed, ignore
the above command. This results in a small chance that the
subsequent testing programs will link against libraries on
the host. This is not ideal, but it is not a major problem.
The situation is corrected when the second pass of Binutils
is installed later.
</p>
</div>
</div>
<p>
Now that the adjusted linker is installed, the Binutils build
and source directories should be removed.
</p>
<p>
The next task is to amend the GCC specs file so that it points
to the new dynamic linker. A simple sed script will accomplish
this:
</p>
<pre class="userinput"><kbd class=
"command">SPECFILE=`gcc --print-file specs` &amp;&amp;
sed 's@ /lib/ld-linux.so.2@ /tools/lib/ld-linux.so.2@g' \
$SPECFILE &gt; tempspecfile &amp;&amp;
mv -f tempspecfile $SPECFILE &amp;&amp;
unset SPECFILE</kbd></pre>
<p>
<span>It is recommended that the above command be
copy-and-pasted in order to ensure accuracy.</span>
Alternatively, the specs file can be edited by hand. This is
done by replacing every occurrence of &ldquo;<span class=
"quote">/lib/ld-linux.so.2</span>&rdquo; with
&ldquo;<span class=
"quote">/tools/lib/ld-linux.so.2</span>&rdquo;
</p>
<p>
Be sure to visually inspect the specs file in order to verify
the intended changes have been made.
</p>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
If working on a platform where the name of the dynamic
linker is something other than <tt class=
"filename">ld-linux.so.2</tt>, replace &ldquo;<span class=
"quote">ld-linux.so.2</span>&rdquo; with the name of the
platform's dynamic linker in the above commands. Refer back
to <a href="#ch-tools-toolchaintechnotes" title=
"5.2.&nbsp;Toolchain Technical Notes">Section 5.2,
&ldquo;Toolchain Technical Notes,&rdquo;</a> if necessary.
</p>
</div>
</div>
<p>
There is a possibility that some include files from the host
system have found their way into GCC's private include dir.
This can happen as a result of GCC's &ldquo;<span class=
"quote">fixincludes</span>&rdquo; process, which runs as part
of the GCC build. This is explained in more detail later in
this chapter. Run the following command to eliminate this
possibility:
</p>
<pre class="userinput"><kbd class=
"command">rm -vf /tools/lib/gcc/*/*/include/{pthread.h,bits/sigthread.h}</kbd></pre>
<div class="caution">
<div class="admonhead">
<h3 class="admontitle">
Caution
</h3>
</div>
<div class="admonbody">
<p>
At this point, it is imperative to stop and ensure that the
basic functions (compiling and linking) of the new
toolchain are working as expected. To perform a sanity
check, run the following commands:
</p>
<pre class="userinput"><kbd class=
"command">echo 'main(){}' &gt; dummy.c
cc dummy.c
readelf -l a.out | grep ': /tools'</kbd></pre>
<p>
If everything is working correctly, there should be no
errors, and the output of the last command will be of the
form:
</p>
<pre class="screen"><tt class=
"computeroutput">[Requesting program interpreter:
/tools/lib/ld-linux.so.2]</tt></pre>
<p>
Note that <tt class="filename">/tools/lib</tt> appears as
the prefix of the dynamic linker.
</p>
<p>
If the output is not shown as above or there was no output
at all, then something is wrong. Investigate and retrace
the steps to find out where the problem is and correct it.
This issue must be resolved before continuing on. First,
perform the sanity check again, using <span><strong class=
"command">gcc</strong></span> instead of
<span><strong class="command">cc</strong></span>. If this
works, then the <tt class="filename">/tools/bin/cc</tt>
symlink is missing. Revisit <a href="#ch-tools-gcc-pass1"
title="5.4.&nbsp;GCC-3.4.3 - Pass 1">Section 5.4,
&ldquo;GCC-3.4.3 - Pass 1,&rdquo;</a> and install the
symlink. Next, ensure that the <tt class="envar">PATH</tt>
is correct. This can be checked by running
<span><strong class="command">echo $PATH</strong></span>
and verifying that <tt class="filename">/tools/bin</tt> is
at the head of the list. If the <tt class="envar">PATH</tt>
is wrong it could mean that you are not logged in as user
<span class="emphasis"><em>lfs</em></span> or that
something went wrong back in <a href=
"#ch-tools-settingenviron" title=
"4.4.&nbsp;Setting Up the Environment">Section 4.4,
&ldquo;Setting Up the Environment.&rdquo;</a> Another
option is that something may have gone wrong with the specs
file amendment above. In this case, redo the specs file
amendment<span>, being careful to copy-and-paste the
commands</span>.
</p>
<p>
Once all is well, clean up the test files:
</p>
<pre class="userinput"><kbd class=
"command">rm -v dummy.c a.out</kbd></pre>
<p>
Building TCL in the next section will serve as an
additional check that the toolchain has been built
properly. If TCL fails to build, it is an indication that
something has gone wrong with the Binutils, GCC, or Glibc
installation, but not with TCL itself.
</p>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-tcl" name=
"ch-tools-tcl"></a>5.8.&nbsp;Tcl-8.4.9
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Tcl package contains the Tool Command Language.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.9 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">23.3 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.8.1. Installation of Tcl
</h3>
</div>
<p>
This package and the next two (Expect and DejaGNU) are
installed to support running the test suites for GCC and
Binutils. Installing three packages for testing purposes may
seem excessive, but it is very reassuring, if not essential,
to know that the most important tools are working properly.
Even if the test suites are not run in this chapter (they are
not mandatory), these packages are required to run the test
suites in <a href="#chapter-building-system">Chapter 6</a>.
</p>
<p>
Prepare Tcl for compilation:
</p>
<pre class="userinput"><kbd class="command">cd unix
./configure --prefix=/tools</kbd></pre>
<p>
Build the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>TZ=UTC make test</tt></strong>. The Tcl test
suite is known to experience failures under certain host
conditions that are not fully understood. Therefore, test
suite failures here are not surprising, and are not
considered critical. The <em class=
"parameter"><tt>TZ=UTC</tt></em> parameter sets the time zone
to Coordinated Universal Time (UTC), also known as Greenwich
Mean Time (GMT), but only for the duration of the test suite
run. This ensures that the clock tests are exercised
correctly. Details on the <tt class="envar">TZ</tt>
environment variable are provided in <a href=
"#chapter-bootscripts">Chapter 7</a>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<div class="warning">
<div class="admonhead">
<h3 class="admontitle">
Warning
</h3>
</div>
<div class="admonbody">
<p>
<span class="emphasis"><em>Do not</em></span> remove the
<tt class="filename">tcl8.4.9</tt> source directory yet,
as the next package will need its internal headers.
</p>
</div>
</div>
<p>
Set a variable containing the full path of the current
directory. The next package, Expect, will use this variable
to find Tcl's headers.
</p>
<pre class="userinput"><kbd class="command">cd ..
export TCLPATH=`pwd`</kbd></pre>
<p>
Now make a necessary symbolic link:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv tclsh8.4 /tools/bin/tclsh</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-tcl" name="contents-tcl"></a>
<h3 class="sect2">
5.8.2. Contents of Tcl
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">tclsh (link
to tclsh8.4) and tclsh8.4</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
library:</span></strong> <span class=
"seg">libtcl8.4.so</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3487710" name="id3487710"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="tclsh8.4" name="tclsh8.4"></a><span class=
"term"><span><strong class=
"command">tclsh8.4</strong></span></span>
</td>
<td>
<p>
The Tcl command shell
</p>
</td>
</tr>
<tr>
<td>
<a id="tclsh" name="tclsh"></a><span class=
"term"><span><strong class=
"command">tclsh</strong></span></span>
</td>
<td>
<p>
A link to tclsh8.4
</p>
</td>
</tr>
<tr>
<td>
<a id="libtcl8.4.so" name=
"libtcl8.4.so"></a><span class="term"><tt class=
"filename">libtcl8.4.so</tt></span>
</td>
<td>
<p>
The Tcl library
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-expect" name=
"ch-tools-expect"></a>5.9.&nbsp;Expect-5.43.0
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Expect package contains a program for carrying out
scripted dialogues with other interactive programs.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">4.0 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, Sed, and
Tcl</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.9.1. Installation of Expect
</h3>
</div>
<p>
First, fix a bug that can result in false failures during the
GCC test suite run:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../expect-5.43.0-spawn-1.patch</kbd></pre>
<p>
Now prepare Expect for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools --with-tcl=/tools/lib \
--with-tclinclude=$TCLPATH --with-x=no</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-tcl=/tools/lib</tt></em></span>
</dt>
<dd>
<p>
This ensures that the configure script finds the Tcl
installation in the temporary tools location instead of
possibly locating an existing one on the host system.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-tclinclude=$TCLPATH</tt></em></span>
</dt>
<dd>
<p>
This explicitly tells Expect where to find Tcl's source
directory and internal headers. Using this option
avoids conditions where <span><strong class=
"command">configure</strong></span> fails because it
cannot automatically discover the location of the Tcl
source directory.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-x=no</tt></em></span>
</dt>
<dd>
<p>
This tells the configure script not to search for Tk
(the Tcl GUI component) or the X Window System
libraries, both of which may reside on the host system
but will not exist in the temporary environment.
</p>
</dd>
</dl>
</div>
<p>
Build the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make test</tt></strong>. Note that the Expect
test suite is known to experience failures under certain host
conditions that are not within our control. Therefore, test
suite failures here are not surprising and are not considered
critical.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make SCRIPTS="" install</kbd></pre>
<p>
The meaning of the make parameter:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>SCRIPTS=""</tt></em></span>
</dt>
<dd>
<p>
This prevents installation of the supplementary expect
scripts, which are not needed.
</p>
</dd>
</dl>
</div>
<p>
Now remove the <tt class="envar">TCLPATH</tt> variable:
</p>
<pre class="userinput"><kbd class=
"command">unset TCLPATH</kbd></pre>
<p>
The source directories of both Tcl and Expect can now be
removed.
</p>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-expect" name="contents-expect"></a>
<h3 class="sect2">
5.9.2. Contents of Expect
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
program:</span></strong> <span class="seg">expect</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
library:</span></strong> <span class=
"seg">libexpect-5.43.a</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3488003" name="id3488003"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="expect" name="expect"></a><span class=
"term"><span><strong class=
"command">expect</strong></span></span>
</td>
<td>
<p>
Communicates with other interactive programs
according to a script
</p>
</td>
</tr>
<tr>
<td>
<a id="libexpect" name="libexpect"></a><span class=
"term"><tt class=
"filename">libexpect-5.43.a</tt></span>
</td>
<td>
<p>
Contains functions that allow Expect to be used as
a Tcl extension or to be used directly from C or
C++ (without Tcl)
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-dejagnu" name=
"ch-tools-dejagnu"></a>5.10.&nbsp;DejaGNU-1.4.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The DejaGNU package contains a framework for testing other
programs.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">6.1 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.10.1. Installation of DejaGNU
</h3>
</div>
<p>
Prepare DejaGNU for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Build and install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-dejagnu" name="contents-dejagnu"></a>
<h3 class="sect2">
5.10.2. Contents of DejaGNU
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
program:</span></strong> <span class="seg">runtest</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3487853" name="id3487853"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="runtest" name="runtest"></a><span class=
"term"><span><strong class=
"command">runtest</strong></span></span>
</td>
<td>
<p>
A wrapper script that locates the proper
<span><strong class=
"command">expect</strong></span> shell and then
runs DejaGNU
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-gcc-pass2" name=
"ch-tools-gcc-pass2"></a>5.11.&nbsp;GCC-3.4.3 - Pass 2
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">11.0 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">292 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Findutils, Gawk, Gettext, Glibc,
Grep, Make, Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.11.1. Re-installation of GCC
</h3>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
GCC.
</p>
<p>
The tools required to test GCC and Binutils&mdash;Tcl, Expect
and DejaGNU&mdash;are installed now. GCC and Binutils can now
be rebuilt, linking them against the new Glibc and testing
them properly (if running the test suites in this chapter).
Please note that these test suites are highly dependent on
properly functioning PTYs which are provided by the host.
PTYs are most commonly implemented via the <tt class=
"systemitem">devpts</tt> file system. Check to see if the
host system is set up correctly in this regard by performing
a quick test:
</p>
<pre class="userinput"><kbd class=
"command">expect -c "spawn ls"</kbd></pre>
<p>
The response might be:
</p>
<pre class="screen"><tt class=
"computeroutput">The system has no more ptys.
Ask your system administrator to create more.</tt></pre>
<p>
If the above message is received, the host does not have its
PTYs set up properly. In this case, there is no point in
running the test suites for GCC and Binutils until this issue
is resolved. Please consult the LFS FAQ at <a href=
"http://www.linuxfromscratch.org//lfs/faq.html#no-ptys"><i>http://www.linuxfromscratch.org//lfs/faq.html#no-ptys</i></a>
for more information on how to get PTYs working.
</p>
<p>
First correct a known problem and make an essential
adjustment:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../gcc-3.4.3-no_fixincludes-1.patch
patch -Np1 -i ../gcc-3.4.3-specs-2.patch</kbd></pre>
<p>
The first patch disables the GCC <span><strong class=
"command">fixincludes</strong></span> script. This was
briefly mentioned earlier, but a more in-depth explanation of
the fixincludes process is warranted here. Under normal
circumstances, the GCC <span><strong class=
"command">fixincludes</strong></span> script scans the system
for header files that need to be fixed. It might find that
some Glibc header files on the host system need to be fixed,
and will fix them and put them in the GCC private include
directory. In <a href="#chapter-building-system">Chapter
6</a>, after the newer Glibc has been installed, this private
include directory will be searched before the system include
directory. This may result in GCC finding the fixed headers
from the host system, which most likely will not match the
Glibc version used for the LFS system.
</p>
<p>
The second patch changes GCC's default location of the
dynamic linker (typically <tt class=
"filename">ld-linux.so.2</tt>). It also removes <tt class=
"filename">/usr/include</tt> from GCC's include search path.
Patching now rather than adjusting the specs file after
installation ensures that the new dynamic linker is used
during the actual build of GCC. That is, all of the final
(and temporary) binaries created during the build will link
against the new Glibc.
</p>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
The above patches are critical in ensuring a successful
overall build. Do not forget to apply them.
</p>
</div>
</div>
<p>
Create a separate build directory again:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../gcc-build
cd ../gcc-build</kbd></pre>
<p>
Before starting to build GCC, remember to unset any
environment variables that override the default optimization
flags.
</p>
<p>
Now prepare GCC for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../gcc-3.4.3/configure --prefix=/tools \
--libexecdir=/tools/lib --with-local-prefix=/tools \
--enable-clocale=gnu --enable-shared \
--enable-threads=posix --enable-__cxa_atexit \
--enable-languages=c,c++ --disable-libstdcxx-pch</kbd></pre>
<p>
The meaning of the new configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-clocale=gnu</tt></em></span>
</dt>
<dd>
<p>
This option ensures the correct locale model is
selected for the C++ libraries under all circumstances.
If the configure script finds the <span class=
"emphasis"><em>de_DE</em></span> locale installed, it
will select the correct gnu locale model. However, if
the <span class="emphasis"><em>de_DE</em></span> locale
is not installed, there is the risk of building
Application Binary Interface (ABI)-incompatible C++
libraries because the incorrect generic locale model
may be selected.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-threads=posix</tt></em></span>
</dt>
<dd>
<p>
This enables C++ exception handling for multi-threaded
code.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-__cxa_atexit</tt></em></span>
</dt>
<dd>
<p>
This option allows use of <span class=
"emphasis"><em>__cxa_atexit</em></span>, rather than
<span class="emphasis"><em>atexit</em></span>, to
register C++ destructors for local statics and global
objects. This option is essential for fully
standards-compliant handling of destructors. It also
affects the C++ ABI, and therefore results in C++
shared libraries and C++ programs that are
interoperable with other Linux distributions.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-languages=c,c++</tt></em></span>
</dt>
<dd>
<p>
This option ensures that both the C and C++ compilers
are built.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-libstdcxx-pch</tt></em></span>
</dt>
<dd>
<p>
Do not build the pre-compiled header (PCH) for
<tt class="filename">libstdc++</tt>. It takes up a lot
of space, and we have no use for it.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
There is no need to use the <em class=
"parameter"><tt>bootstrap</tt></em> target now because the
compiler being used to compile this GCC was built from the
exact same version of the GCC sources used earlier.
</p>
<p>
Compilation is now complete. As previously mentioned, running
the test suites for the temporary tools compiled in this
chapter is not mandatory. To run the GCC test suite anyway,
use the following command:
</p>
<pre class="userinput"><kbd class=
"command">make -k check</kbd></pre>
<p>
The <em class="parameter"><tt>-k</tt></em> flag is used to
make the test suite run through to completion and not stop at
the first failure. The GCC test suite is very comprehensive
and is almost guaranteed to generate a few failures. To
receive a summary of the test suite results, run:
</p>
<pre class="userinput"><kbd class=
"command">../gcc-3.4.3/contrib/test_summary</kbd></pre>
<p>
For only the summaries, pipe the output through
<strong class="userinput"><tt>grep -A7 Summ</tt></strong>.
</p>
<p>
Results can be compared with those located at <a href=
"http://www.linuxfromscratch.org/lfs/build-logs/6.1.1/"><i>http://www.linuxfromscratch.org/lfs/build-logs/6.1.1/</i></a>.
</p>
<p>
A few unexpected failures cannot always be avoided. The GCC
developers are usually aware of these issues, but have not
resolved them yet. Unless the test results are vastly
different from those at the above URL, it is safe to
continue.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
At this point it is strongly recommended to repeat the
sanity check we performed earlier in this chapter. Refer
back to <a href="#ch-tools-adjusting" title=
"5.7.&nbsp;Adjusting the Toolchain">Section 5.7,
&ldquo;Adjusting the Toolchain,&rdquo;</a> and repeat the
test compilation. If the result is wrong, the most likely
reason is that the GCC Specs patch was not properly
applied.
</p>
</div>
</div>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-gcc" title=
"6.14.2.&nbsp;Contents of GCC">Section&nbsp;6.14.2,
&ldquo;Contents of GCC.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-binutils-pass2" name=
"ch-tools-binutils-pass2"></a>5.12.&nbsp;Binutils-2.15.94.0.2.2
- Pass 2
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Binutils package contains a linker, an assembler, and
other tools for handling object files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">1.5 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">114 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Bison,
Coreutils, Diffutils, Flex, GCC, Gettext, Glibc, Grep,
M4, Make, Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.12.1. Re-installation of Binutils
</h3>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
Binutils.
</p>
<p>
Create a separate build directory again:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../binutils-build
cd ../binutils-build</kbd></pre>
<p>
Prepare Binutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../binutils-2.15.94.0.2.2/configure --prefix=/tools \
--disable-nls --enable-shared --with-lib-path=/tools/lib</kbd></pre>
<p>
The meaning of the new configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-lib-path=/tools/lib</tt></em></span>
</dt>
<dd>
<p>
This tells the configure script to specify the library
search path during the compilation of Binutils,
resulting in <tt class="filename">/tools/lib</tt> being
passed to the linker. This prevents the linker from
searching through library directories on the host.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Compilation is now complete. As discussed earlier, running
the test suite is not mandatory for the temporary tools here
in this chapter. To run the Binutils test suite anyway, issue
the following command:
</p>
<pre class="userinput"><kbd class=
"command">make check</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Now prepare the linker for the &ldquo;<span class=
"quote">Re-adjusting</span>&rdquo; phase in the next chapter:
</p>
<pre class="userinput"><kbd class="command">make -C ld clean
make -C ld LIB_PATH=/usr/lib:/lib</kbd></pre>
<div class="warning">
<div class="admonhead">
<h3 class="admontitle">
Warning
</h3>
</div>
<div class="admonbody">
<p>
<span class="emphasis"><em>Do not</em></span> remove the
Binutils source and build directories yet. These
directories will be needed again in the next chapter in
their current state.
</p>
</div>
</div>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-binutils" title=
"6.13.2.&nbsp;Contents of Binutils">Section&nbsp;6.13.2,
&ldquo;Contents of Binutils.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-gawk" name=
"ch-tools-gawk"></a>5.13.&nbsp;Gawk-3.1.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Gawk package contains programs for manipulating text
files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">16.4 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.13.1. Installation of Gawk
</h3>
</div>
<p>
Prepare Gawk for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-gawk" title=
"6.20.2.&nbsp;Contents of Gawk">Section&nbsp;6.20.2,
&ldquo;Contents of Gawk.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-coreutils" name=
"ch-tools-coreutils"></a>5.14.&nbsp;Coreutils-5.2.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Coreutils package contains utilities for showing and
setting the basic system characteristics.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.9 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">53.3 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Perl, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.14.1. Installation of Coreutils
</h3>
</div>
<p>
Prepare Coreutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">DEFAULT_POSIX2_VERSION=199209 ./configure --prefix=/tools</kbd></pre>
<p>
This package has an issue when compiled against versions of
Glibc later than 2.3.2. Some of the Coreutils utilities (such
as <span><strong class="command">head</strong></span>,
<span><strong class="command">tail</strong></span>, and
<span><strong class="command">sort</strong></span>) will
reject their traditional syntax, a syntax that has been in
use for approximately 30 years. This old syntax is so
pervasive that compatibility should be preserved until the
many places where it is used can be updated. Backwards
compatibility is achieved by setting the <tt class=
"envar">DEFAULT_POSIX2_VERSION</tt> environment variable to
&ldquo;<span class="quote">199209</span>&rdquo; in the above
command. If you do not want Coreutils to be backwards
compatible with the traditional syntax, then omit setting the
<tt class="envar">DEFAULT_POSIX2_VERSION</tt> environment
variable. It is important to remember that doing so will have
consequences, including the need to patch the many packages
that still use the old syntax. Therefore, it is recommended
that the instructions be followed exactly as given above.
</p>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make RUN_EXPENSIVE_TESTS=yes
check</tt></strong>. The <em class=
"parameter"><tt>RUN_EXPENSIVE_TESTS=yes</tt></em> parameter
tells the test suite to run several additional tests that are
considered relatively expensive (in terms of CPU power and
memory usage) on some platforms, but generally are not a
problem on Linux.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-coreutils" title=
"6.15.2.&nbsp;Contents of Coreutils">Section&nbsp;6.15.2,
&ldquo;Contents of Coreutils.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-bzip2" name=
"ch-tools-bzip2"></a>5.15.&nbsp;Bzip2-1.0.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Bzip2 package contains programs for compressing and
decompressing files. Compressing text files with
<span><strong class="command">bzip2</strong></span> yields a
much better compression percentage than with the traditional
<span><strong class="command">gzip</strong></span>.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">3.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, and Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.15.1. Installation of Bzip2
</h3>
</div>
<p>
The Bzip2 package does not contain a <span><strong class=
"command">configure</strong></span> script. Compile and test
it with:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make PREFIX=/tools install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-bzip2" title=
"6.40.2.&nbsp;Contents of Bzip2">Section&nbsp;6.40.2,
&ldquo;Contents of Bzip2.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-gzip" name=
"ch-tools-gzip"></a>5.16.&nbsp;Gzip-1.3.5
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Gzip package contains programs for compressing and
decompressing files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">2.2 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.16.1. Installation of Gzip
</h3>
</div>
<p>
Prepare Gzip for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-gzip" title=
"6.46.2.&nbsp;Contents of Gzip">Section&nbsp;6.46.2,
&ldquo;Contents of Gzip.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-diffutils" name=
"ch-tools-diffutils"></a>5.17.&nbsp;Diffutils-2.8.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Diffutils package contains programs that show the
differences between files or directories.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">5.6 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.17.1. Installation of Diffutils
</h3>
</div>
<p>
Prepare Diffutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-diffutils" title=
"6.41.2.&nbsp;Contents of Diffutils">Section&nbsp;6.41.2,
&ldquo;Contents of Diffutils.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-findutils" name=
"ch-tools-findutils"></a>5.18.&nbsp;Findutils-4.2.23
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Findutils package contains programs to find files. These
programs are provided to recursively search through a
directory tree and to create, maintain, and search a database
(often faster than the recursive find, but unreliable if the
database has not been recently updated).
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">8.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.18.1. Installation of Findutils
</h3>
</div>
<p>
Prepare Findutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-findutils" title=
"6.19.2.&nbsp;Contents of Findutils">Section&nbsp;6.19.2,
&ldquo;Contents of Findutils.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-make" name=
"ch-tools-make"></a>5.19.&nbsp;Make-3.80
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Make package contains a program for compiling packages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">7.1 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.19.1. Installation of Make
</h3>
</div>
<p>
Prepare Make for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-make" title=
"6.49.2.&nbsp;Contents of Make">Section&nbsp;6.49.2,
&ldquo;Contents of Make.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-grep" name=
"ch-tools-grep"></a>5.20.&nbsp;Grep-2.5.1a
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Grep package contains programs for searching through
files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">4.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Make, Sed, and
Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.20.1. Installation of Grep
</h3>
</div>
<p>
Prepare Grep for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools \
--disable-perl-regexp</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-perl-regexp</tt></em></span>
</dt>
<dd>
<p>
This ensures that the <span><strong class=
"command">grep</strong></span> program does not get
linked against a Perl Compatible Regular Expression
(PCRE) library that may be present on the host but will
not be available once we enter the <span><strong class=
"command">chroot</strong></span> environment.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-grep" title=
"6.44.2.&nbsp;Contents of Grep">Section&nbsp;6.44.2,
&ldquo;Contents of Grep.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-sed" name=
"ch-tools-sed"></a>5.21.&nbsp;Sed-4.1.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Sed package contains a stream editor.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">8.4 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.21.1. Installation of Sed
</h3>
</div>
<p>
Prepare Sed for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-sed" title=
"6.28.2.&nbsp;Contents of Sed">Section&nbsp;6.28.2,
&ldquo;Contents of Sed.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-gettext" name=
"ch-tools-gettext"></a>5.22.&nbsp;Gettext-0.14.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Gettext package contains utilities for
internationalization and localization. These allow programs
to be compiled with NLS (Native Language Support), enabling
them to output messages in the user's native language.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.5 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">63.0 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Bison, Coreutils, Diffutils, Gawk, GCC, Glibc, Grep,
Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.22.1. Installation of Gettext
</h3>
</div>
<p>
Prepare Gettext for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools --disable-libasprintf \
--without-csharp</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-libasprintf</tt></em></span>
</dt>
<dd>
<p>
This flag tells Gettext not to build the <tt class=
"filename">asprintf</tt> library. Because nothing in
this chapter or the next requires this library and
Gettext gets rebuilt later, exclude it to save time and
space.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--without-csharp</tt></em></span>
</dt>
<dd>
<p>
This ensures that Gettext does not build support for
the C# compiler which may be present on the host but
will not be available once we enter the
<span><strong class="command">chroot</strong></span>
environment.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>. This takes quite
some time, around 7 SBUs. The Gettext test suite is known to
experience failures under certain host conditions, for
example when it finds a Java compiler on the host. An
experimental patch to disable Java is available from the LFS
Patches project at <a href=
"http://www.linuxfromscratch.org/patches/"><i>http://www.linuxfromscratch.org/patches/</i></a>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-gettext" title=
"6.30.2.&nbsp;Contents of Gettext">Section&nbsp;6.30.2,
&ldquo;Contents of Gettext.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-ncurses" name=
"ch-tools-ncurses"></a>5.23.&nbsp;Ncurses-5.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Ncurses package contains libraries for
terminal-independent handling of character screens.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.7 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">27.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.23.1. Installation of Ncurses
</h3>
</div>
<p>
Prepare Ncurses for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools --with-shared \
--without-debug --without-ada --enable-overwrite</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--without-ada</tt></em></span>
</dt>
<dd>
<p>
This ensures that Ncurses does not build support for
the Ada compiler which may be present on the host but
will not be available once we enter the
<span><strong class="command">chroot</strong></span>
environment.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-overwrite</tt></em></span>
</dt>
<dd>
<p>
This tells Ncurses to install its header files into
<tt class="filename">/tools/include</tt>, instead of
<tt class="filename">/tools/include/ncurses</tt>, to
ensure that other packages can find the Ncurses headers
successfully.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-ncurses" title=
"6.21.2.&nbsp;Contents of Ncurses">Section&nbsp;6.21.2,
&ldquo;Contents of Ncurses.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-patch" name=
"ch-tools-patch"></a>5.24.&nbsp;Patch-2.5.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Patch package contains a program for modifying or
creating files by applying a &ldquo;<span class=
"quote">patch</span>&rdquo; file typically created by the
<span><strong class="command">diff</strong></span> program.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">1.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.24.1. Installation of Patch
</h3>
</div>
<p>
Prepare Patch for compilation:
</p>
<pre class="userinput"><kbd class=
"command">CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/tools</kbd></pre>
<p>
The preprocessor flag <em class=
"parameter"><tt>-D_GNU_SOURCE</tt></em> is only needed on the
PowerPC platform. It can be left out on other architectures.
</p>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-patch" title=
"6.51.2.&nbsp;Contents of Patch">Section&nbsp;6.51.2,
&ldquo;Contents of Patch.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-tar" name=
"ch-tools-tar"></a>5.25.&nbsp;Tar-1.15.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Tar package contains an archiving program.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">12.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.25.1. Installation of Tar
</h3>
</div>
<p>
Prepare Tar for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-tar" title=
"6.57.2.&nbsp;Contents of Tar">Section&nbsp;6.57.2,
&ldquo;Contents of Tar.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-texinfo" name=
"ch-tools-texinfo"></a>5.26.&nbsp;Texinfo-4.8
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Texinfo package contains programs for reading, writing,
and converting info pages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">14.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Ncurses, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.26.1. Installation of Texinfo
</h3>
</div>
<p>
Prepare Texinfo for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-texinfo" title=
"6.34.2.&nbsp;Contents of Texinfo">Section&nbsp;6.34.2,
&ldquo;Contents of Texinfo.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-bash" name=
"ch-tools-bash"></a>5.27.&nbsp;Bash-3.0
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Bash package contains the Bourne-Again SHell.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">1.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">20.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make,
Ncurses, and Sed.</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.27.1. Installation of Bash
</h3>
</div>
<p>
Bash has a problem when compiled against newer versions of
Glibc, causing it to hang inappropriately. This patch fixes
the problem:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../bash-3.0-avoid_WCONTINUED-1.patch</kbd></pre>
<p>
Prepare Bash for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools --without-bash-malloc</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--without-bash-malloc</tt></em></span>
</dt>
<dd>
<p>
This options turns off the use of Bash's memory
allocation (malloc) function which is known to cause
segmentation faults. By turning this option off, Bash
will use the malloc functions from Glibc which are more
stable.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make tests</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Make a link for the programs that use <span><strong class=
"command">sh</strong></span> for a shell:
</p>
<pre class="userinput"><kbd class=
"command">ln -vs bash /tools/bin/sh</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-bash" title=
"6.37.2.&nbsp;Contents of Bash">Section&nbsp;6.37.2,
&ldquo;Contents of Bash.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-m4" name=
"ch-tools-m4"></a>5.28.&nbsp;M4-1.4.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The M4 package contains a macro processor.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">2.8 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Perl, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.28.1. Installation of M4
</h3>
</div>
<p>
Prepare M4 for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href="#contents-m4"
title="6.24.2.&nbsp;Contents of M4">Section&nbsp;6.24.2,
&ldquo;Contents of M4.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-bison" name=
"ch-tools-bison"></a>5.29.&nbsp;Bison-2.0
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Bison package contains a parser generator.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.6 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">10.0 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, M4,
Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.29.1. Installation of Bison
</h3>
</div>
<p>
Prepare Bison for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-bison" title=
"6.25.2.&nbsp;Contents of Bison">Section&nbsp;6.25.2,
&ldquo;Contents of Bison.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-flex" name=
"ch-tools-flex"></a>5.30.&nbsp;Flex-2.5.31
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Flex package contains a utility for generating programs
that recognize patterns in text.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.6 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">22.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Bison, Coreutils, Diffutils, GCC, Gettext, Glibc, Grep,
M4, Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.30.1. Installation of Flex
</h3>
</div>
<p>
Flex contains several known bugs. These can be fixed with the
following patch:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../flex-2.5.31-debian_fixes-3.patch</kbd></pre>
<p>
The GNU autotools will detect that the Flex source code has
been modified by the previous patch and tries to update the
man page accordingly. This does not work on many systems, and
the default page is fine, so make sure it does not get
regenerated:
</p>
<pre class="userinput"><kbd class=
"command">touch doc/flex.1</kbd></pre>
<p>
Now prepare Flex for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/tools</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-flex" title=
"6.29.2.&nbsp;Contents of Flex">Section&nbsp;6.29.2,
&ldquo;Contents of Flex.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-util-linux" name=
"ch-tools-util-linux"></a>5.31.&nbsp;Util-linux-2.12q
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Util-linux package contains miscellaneous utility
programs. Among them are utilities for handling file systems,
consoles, partitions, and messages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">8.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Ncurses, Sed, and Zlib</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.31.1. Installation of Util-linux
</h3>
</div>
<p>
Util-linux does not use the freshly installed headers and
libraries from the <tt class="filename">/tools</tt> directory
by default. This is fixed by altering the configure script:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's@/usr/include@/tools/include@g' configure</kbd></pre>
<p>
Prepare Util-linux for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure</kbd></pre>
<p>
Compile some support routines:
</p>
<pre class="userinput"><kbd class=
"command">make -C lib</kbd></pre>
<p>
Only a few of the utilities contained in this package need to
be built:
</p>
<pre class="userinput"><kbd class=
"command">make -C mount mount umount
make -C text-utils more</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Copy these programs to the temporary tools directory:
</p>
<pre class="userinput"><kbd class=
"command">cp mount/{,u}mount text-utils/more /tools/bin</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-utillinux" title=
"6.59.3.&nbsp;Contents of Util-linux">Section&nbsp;6.59.3,
&ldquo;Contents of Util-linux.&rdquo;</a>
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-perl" name=
"ch-tools-perl"></a>5.32.&nbsp;Perl-5.8.7
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Perl package contains the Practical Extraction and Report
Language.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.8 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">81.6 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
5.32.1. Installation of Perl
</h3>
</div>
<p>
First adapt some hard-wired paths to the C library by
applying the following patch:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../perl-5.8.7-libc-1.patch</kbd></pre>
<p>
Prepare Perl for compilation (make sure to get the 'IO Fcntl
POSIX' part of the command correct&mdash;they are all
letters):
</p>
<pre class="userinput"><kbd class=
"command">./configure.gnu --prefix=/tools -Dstatic_ext='IO Fcntl POSIX'</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>-Dstatic_ext='IO Fcntl
POSIX'</tt></em></span>
</dt>
<dd>
<p>
This tells Perl to build the minimum set of static
extensions needed for installing and testing the
Coreutils package in the next chapter.
</p>
</dd>
</dl>
</div>
<p>
Only a few of the utilities contained in this package need to
be built:
</p>
<pre class="userinput"><kbd class=
"command">make perl utilities</kbd></pre>
<p>
Although Perl comes with a test suite, it is not recommended
to run it at this point. Only part of Perl was built and
running <strong class="userinput"><tt>make test</tt></strong>
now will cause the rest of Perl to be built as well, which is
unnecessary at this point. The test suite can be run in the
next chapter if desired.
</p>
<p>
Install these tools and their libraries:
</p>
<pre class="userinput"><kbd class=
"command">cp -v perl pod/pod2man /tools/bin
mkdir -pv /tools/lib/perl5/5.8.7
cp -Rv lib/* /tools/lib/perl5/5.8.7</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<p>
Details on this package are located in <a href=
"#contents-perl" title=
"6.33.2.&nbsp;Contents of Perl">Section&nbsp;6.33.2,
&ldquo;Contents of Perl.&rdquo;</a>
</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-tools-stripping" name=
"ch-tools-stripping"></a>5.33.&nbsp;Stripping
</h2>
</div>
</div>
</div>
<p>
The steps in this section are optional, but if the LFS
partition is rather small, it is beneficial to learn that
unnecessary items can be removed. The executables and libraries
built so far contain about 130 MB of unneeded debugging
symbols. Remove those symbols with:
</p>
<pre class="userinput"><kbd class=
"command">strip --strip-debug /tools/lib/*
strip --strip-unneeded /tools/{,s}bin/*</kbd></pre>
<p>
The last of the above commands will skip some twenty files,
reporting that it does not recognize their file format. Most of
these are scripts instead of binaries.
</p>
<p>
Take care <span class="emphasis"><em>not</em></span> to use
<em class="parameter"><tt>--strip-unneeded</tt></em> on the
libraries. The static ones would be destroyed and the toolchain
packages would need to be built all over again.
</p>
<p>
To save another 30 MB, remove the documentation:
</p>
<pre class="userinput"><kbd class=
"command">rm -rf /tools/{info,man}</kbd></pre>
<p>
There will now be at least 850 MB of free space on the LFS file
system that can be used to build and install Glibc in the next
phase. If you can build and install Glibc, you can build and
install the rest too.
</p>
</div>
</div>
</div>
<div class="part" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title">
<a id="part3" name="part3"></a>Part&nbsp;III.&nbsp;Building
the LFS System
</h1>
</div>
</div>
</div>
<div class="toc">
<h3>
Table of Contents
</h3>
<ul>
<li class="chapter">
<h4>
6. Installing Basic System Software
</h4>
<ul>
<li class="sect1">
<a href="#ch-system-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#ch-system-kernfs">Mounting Virtual Kernel File
Systems</a>
</li>
<li class="sect1">
<a href="#ch-system-chroot">Entering the Chroot
Environment</a>
</li>
<li class="sect1">
<a href="#ch-system-changingowner">Changing Ownership</a>
</li>
<li class="sect1">
<a href="#ch-system-creatingdirs">Creating Directories</a>
</li>
<li class="sect1">
<a href="#ch-system-createfiles">Creating Essential
Symlinks</a>
</li>
<li class="sect1">
<a href="#ch-system-pwdgroup">Creating the passwd, group,
and log Files</a>
</li>
<li class="sect1">
<a href="#ch-system-devices">Populating /dev</a>
</li>
<li class="sect1">
<a href=
"#ch-system-linux-libc-headers">Linux-Libc-Headers-2.6.11.2</a>
</li>
<li class="sect1">
<a href="#ch-system-man-pages">Man-pages-2.01</a>
</li>
<li class="sect1">
<a href="#ch-system-glibc">Glibc-2.3.4</a>
</li>
<li class="sect1">
<a href="#ch-system-readjusting">Re-adjusting the
Toolchain</a>
</li>
<li class="sect1">
<a href="#ch-system-binutils">Binutils-2.15.94.0.2.2</a>
</li>
<li class="sect1">
<a href="#ch-system-gcc">GCC-3.4.3</a>
</li>
<li class="sect1">
<a href="#ch-system-coreutils">Coreutils-5.2.1</a>
</li>
<li class="sect1">
<a href="#ch-system-zlib">Zlib-1.2.3</a>
</li>
<li class="sect1">
<a href="#ch-system-mktemp">Mktemp-1.5</a>
</li>
<li class="sect1">
<a href="#ch-system-iana-etc">Iana-Etc-1.04</a>
</li>
<li class="sect1">
<a href="#ch-system-findutils">Findutils-4.2.23</a>
</li>
<li class="sect1">
<a href="#ch-system-gawk">Gawk-3.1.4</a>
</li>
<li class="sect1">
<a href="#ch-system-ncurses">Ncurses-5.4</a>
</li>
<li class="sect1">
<a href="#ch-system-readline">Readline-5.0</a>
</li>
<li class="sect1">
<a href="#ch-system-vim">Vim-6.3</a>
</li>
<li class="sect1">
<a href="#ch-system-m4">M4-1.4.3</a>
</li>
<li class="sect1">
<a href="#ch-system-bison">Bison-2.0</a>
</li>
<li class="sect1">
<a href="#ch-system-less">Less-382</a>
</li>
<li class="sect1">
<a href="#ch-system-groff">Groff-1.19.1</a>
</li>
<li class="sect1">
<a href="#ch-system-sed">Sed-4.1.4</a>
</li>
<li class="sect1">
<a href="#ch-system-flex">Flex-2.5.31</a>
</li>
<li class="sect1">
<a href="#ch-system-gettext">Gettext-0.14.3</a>
</li>
<li class="sect1">
<a href="#ch-system-inetutils">Inetutils-1.4.2</a>
</li>
<li class="sect1">
<a href="#ch-system-iproute2">IPRoute2-2.6.11-050330</a>
</li>
<li class="sect1">
<a href="#ch-system-perl">Perl-5.8.7</a>
</li>
<li class="sect1">
<a href="#ch-system-texinfo">Texinfo-4.8</a>
</li>
<li class="sect1">
<a href="#ch-system-autoconf">Autoconf-2.59</a>
</li>
<li class="sect1">
<a href="#ch-system-automake">Automake-1.9.5</a>
</li>
<li class="sect1">
<a href="#ch-system-bash">Bash-3.0</a>
</li>
<li class="sect1">
<a href="#ch-system-file">File-4.13</a>
</li>
<li class="sect1">
<a href="#ch-system-libtool">Libtool-1.5.14</a>
</li>
<li class="sect1">
<a href="#ch-system-bzip2">Bzip2-1.0.3</a>
</li>
<li class="sect1">
<a href="#ch-system-diffutils">Diffutils-2.8.1</a>
</li>
<li class="sect1">
<a href="#ch-system-kbd">Kbd-1.12</a>
</li>
<li class="sect1">
<a href="#ch-system-e2fsprogs">E2fsprogs-1.37</a>
</li>
<li class="sect1">
<a href="#ch-system-grep">Grep-2.5.1a</a>
</li>
<li class="sect1">
<a href="#ch-system-grub">GRUB-0.96</a>
</li>
<li class="sect1">
<a href="#ch-system-gzip">Gzip-1.3.5</a>
</li>
<li class="sect1">
<a href="#ch-system-hotplug">Hotplug-2004_09_23</a>
</li>
<li class="sect1">
<a href="#ch-system-man">Man-1.5p</a>
</li>
<li class="sect1">
<a href="#ch-system-make">Make-3.80</a>
</li>
<li class="sect1">
<a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a>
</li>
<li class="sect1">
<a href="#ch-system-patch">Patch-2.5.4</a>
</li>
<li class="sect1">
<a href="#ch-system-procps">Procps-3.2.5</a>
</li>
<li class="sect1">
<a href="#ch-system-psmisc">Psmisc-21.6</a>
</li>
<li class="sect1">
<a href="#ch-system-shadow">Shadow-4.0.9</a>
</li>
<li class="sect1">
<a href="#ch-system-sysklogd">Sysklogd-1.4.1</a>
</li>
<li class="sect1">
<a href="#ch-system-sysvinit">Sysvinit-2.86</a>
</li>
<li class="sect1">
<a href="#ch-system-tar">Tar-1.15.1</a>
</li>
<li class="sect1">
<a href="#ch-system-udev">Udev-056</a>
</li>
<li class="sect1">
<a href="#ch-system-util-linux">Util-linux-2.12q</a>
</li>
<li class="sect1">
<a href="#ch-system-aboutdebug">About Debugging Symbols</a>
</li>
<li class="sect1">
<a href="#ch-system-strippingagain">Stripping Again</a>
</li>
<li class="sect1">
<a href="#ch-system-revisedchroot">Cleaning Up</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
7. Setting Up System Bootscripts
</h4>
<ul>
<li class="sect1">
<a href="#ch-scripts-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a>
</li>
<li class="sect1">
<a href="#ch-scripts-usage">How Do These Bootscripts
Work?</a>
</li>
<li class="sect1">
<a href="#ch-scripts-udev">Device and Module Handling on an
LFS System</a>
</li>
<li class="sect1">
<a href="#ch-scripts-setclock">Configuring the setclock
Script</a>
</li>
<li class="sect1">
<a href="#ch-scripts-console">Configuring the Linux
Console</a>
</li>
<li class="sect1">
<a href="#ch-scripts-sysklogd">Configuring the sysklogd
script</a>
</li>
<li class="sect1">
<a href="#ch-scripts-inputrc">Creating the /etc/inputrc
File</a>
</li>
<li class="sect1">
<a href="#ch-scripts-profile">The Bash Shell Startup
Files</a>
</li>
<li class="sect1">
<a href="#ch-scripts-hostname">Configuring the localnet
Script</a>
</li>
<li class="sect1">
<a href="#ch-scripts-hosts">Creating the /etc/hosts
File</a>
</li>
<li class="sect1">
<a href="#ch-scripts-network">Configuring the network
Script</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
8. Making the LFS System Bootable
</h4>
<ul>
<li class="sect1">
<a href="#ch-bootable-introduction">Introduction</a>
</li>
<li class="sect1">
<a href="#ch-bootable-fstab">Creating the /etc/fstab
File</a>
</li>
<li class="sect1">
<a href="#ch-bootable-kernel">Linux-2.6.11.12</a>
</li>
<li class="sect1">
<a href="#ch-bootable-grub">Making the LFS System
Bootable</a>
</li>
</ul>
</li>
<li class="chapter">
<h4>
9. The End
</h4>
<ul>
<li class="sect1">
<a href="#ch-finish-theend">The End</a>
</li>
<li class="sect1">
<a href="#ch-finish-getcounted">Get Counted</a>
</li>
<li class="sect1">
<a href="#ch-finish-reboot">Rebooting the System</a>
</li>
<li class="sect1">
<a href="#ch-finish-whatnow">What Now?</a>
</li>
</ul>
</li>
</ul>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-building-system" name=
"chapter-building-system"></a>Chapter&nbsp;6.&nbsp;Installing
Basic System Software
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-introduction" name=
"ch-system-introduction"></a>6.1.&nbsp;Introduction
</h2>
</div>
</div>
</div>
<p>
In this chapter, we enter the building site and start
constructing the LFS system in earnest. That is, we chroot into
the temporary mini Linux system, make a few final preparations,
and then begin installing the packages.
</p>
<p>
The installation of this software is straightforward. Although
in many cases the installation instructions could be made
shorter and more generic, we have opted to provide the full
instructions for every package to minimize the possibilities
for mistakes. The key to learning what makes a Linux system
work is to know what each package is used for and why the user
(or the system) needs it. For every installed package, a
summary of its contents is given, followed by concise
descriptions of each program and library the package installed.
</p>
<p>
If using the compiler optimizations provided in this chapter,
please review the optimization hint at <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/optimization.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/optimization.txt</i></a>.
Compiler optimizations can make a program run slightly faster,
but they may also cause compilation difficulties and problems
when running the program. If a package refuses to compile when
using optimization, try to compile it without optimization and
see if that fixes the problem. Even if the package does compile
when using optimization, there is the risk it may have been
compiled incorrectly because of the complex interactions
between the code and build tools. The small potential gains
achieved in using compiler optimizations are often outweighed
by the risks. First-time builders of LFS are encouraged to
build without custom optimizations. The subsequent system will
still run very fast and be stable at the same time.
</p>
<p>
The order that packages are installed in this chapter needs to
be strictly followed to ensure that no program accidentally
acquires a path referring to <tt class="filename">/tools</tt>
hard-wired into it. For the same reason, do not compile
packages in parallel. Compiling in parallel may save time
(especially on dual-CPU machines), but it could result in a
program containing a hard-wired path to <tt class=
"filename">/tools</tt>, which will cause the program to stop
working when that directory is removed.
</p>
<p>
Before the installation instructions, each installation page
provides information about the package, including a concise
description of what it contains, approximately how long it will
take to build, how much disk space is required during this
building process, and any other packages needed to successfully
build the package. Following the installation instructions,
there is a list of programs and libraries (along with brief
descriptions of these) that the package installs.
</p>
<p>
To keep track of which package installs particular files, a
package manager can be used. For a general overview of
different styles of package managers, please refer to <a href=
"http://www.linuxfromscratch.org/blfs/view/svn/introduction/important.html">
<i>http://www.linuxfromscratch.org/blfs/view/svn/introduction/important.html</i></a>.
For a package management method specifically geared towards
LFS, we recommend <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/more_control_and_pkg_man.txt</i></a>.
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
The remainder of this book is to be performed while logged
in as user <span class="emphasis"><em>root</em></span> and
no longer as user <span class=
"emphasis"><em>lfs</em></span>. Also, double check that
<tt class="envar">$LFS</tt> is set.
</p>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-kernfs" name=
"ch-system-kernfs"></a>6.2.&nbsp;Mounting Virtual Kernel
File Systems
</h2>
</div>
</div>
</div>
<p>
Various file systems exported by the kernel are used to
communicate to and from the kernel itself. These file systems
are virtual in that no disk space is used for them. The content
of the file systems resides in memory.
</p>
<p>
Begin by creating directories onto which the file systems will
be mounted:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -pv $LFS/{proc,sys}</kbd></pre>
<p>
Now mount the file systems:
</p>
<pre class="userinput"><kbd class=
"command">mount -vt proc proc $LFS/proc
mount -vt sysfs sysfs $LFS/sys</kbd></pre>
<p>
Remember that if for any reason you stop working on the LFS
system and start again later, it is important to check that
these file systems are mounted again before entering the chroot
environment.
</p>
<p>
Additional file systems will soon be mounted from within the
chroot environment. To keep the host up to date, perform a
&ldquo;<span class="quote">fake mount</span>&rdquo; for each of
these now:
</p>
<pre class="userinput"><kbd class=
"command">mount -vft tmpfs tmpfs $LFS/dev
mount -vft tmpfs tmpfs $LFS/dev/shm
mount -vft devpts -o gid=4,mode=620 devpts $LFS/dev/pts</kbd></pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-chroot" name=
"ch-system-chroot"></a>6.3.&nbsp;Entering the Chroot
Environment
</h2>
</div>
</div>
</div>
<p>
It is time to enter the chroot environment to begin building
and installing the final LFS system. As user <span class=
"emphasis"><em>root</em></span>, run the following command to
enter the realm that is, at the moment, populated with only the
temporary tools:
</p>
<pre class="userinput"><kbd class=
"command">chroot "$LFS" /tools/bin/env -i \
HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login +h</kbd></pre>
<p>
The <em class="parameter"><tt>-i</tt></em> option given to the
<span><strong class="command">env</strong></span> command will
clear all variables of the chroot environment. After that, only
the <tt class="envar">HOME</tt>, <tt class="envar">TERM</tt>,
<tt class="envar">PS1</tt>, and <tt class="envar">PATH</tt>
variables are set again. The <em class=
"parameter"><tt>TERM=$TERM</tt></em> construct will set the
<tt class="envar">TERM</tt> variable inside chroot to the same
value as outside chroot. This variable is needed for programs
like <span><strong class="command">vim</strong></span> and
<span><strong class="command">less</strong></span> to operate
properly. If other variables are needed, such as <tt class=
"envar">CFLAGS</tt> or <tt class="envar">CXXFLAGS</tt>, this is
a good place to set them again.
</p>
<p>
From this point on, there is no need to use the <tt class=
"envar">LFS</tt> variable anymore, because all work will be
restricted to the LFS file system. This is because the Bash
shell is told that <tt class="filename">$LFS</tt> is now the
root (<tt class="filename">/</tt>) directory.
</p>
<p>
Notice that <tt class="filename">/tools/bin</tt> comes last in
the <tt class="envar">PATH</tt>. This means that a temporary
tool will no longer be used once its final version is
installed. This occurs when the shell does not
&ldquo;<span class="quote">remember</span>&rdquo; the locations
of executed binaries&mdash;for this reason, hashing is switched
off by passing the <em class="parameter"><tt>+h</tt></em>
option to <span><strong class="command">bash</strong></span>.
</p>
<p>
It is important that all the commands throughout the remainder
of this chapter and the following chapters are run from within
the chroot environment. If you leave this environment for any
reason (rebooting for example), remember to first mount the
<tt class="systemitem">proc</tt> and <tt class=
"systemitem">devpts</tt> file systems (discussed in the
previous section) and enter chroot again before continuing with
the installations.
</p>
<p>
Note that the <span><strong class=
"command">bash</strong></span> prompt will say <tt class=
"computeroutput">I have no name!</tt> This is normal because
the <tt class="filename">/etc/passwd</tt> file has not been
created yet.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-changingowner" name=
"ch-system-changingowner"></a>6.4.&nbsp;Changing
Ownership
</h2>
</div>
</div>
</div>
<p>
Currently, the <tt class="filename">/tools</tt> directory is
owned by the user <span class="emphasis"><em>lfs</em></span>, a
user that exists only on the host system. Although the
<tt class="filename">/tools</tt> directory can be deleted once
the LFS system has been finished, it can be retained to build
additional LFS systems. If the <tt class="filename">/tools</tt>
directory is kept as is, the files are owned by a user ID
without a corresponding account. This is dangerous because a
user account created later could get this same user ID and
would own the <tt class="filename">/tools</tt> directory and
all the files therein, thus exposing these files to possible
malicious manipulation.
</p>
<p>
To avoid this issue, add the <span class=
"emphasis"><em>lfs</em></span> user to the new LFS system later
when creating the <tt class="filename">/etc/passwd</tt> file,
taking care to assign it the same user and group IDs as on the
host system. Alternatively, assign the contents of the
<tt class="filename">/tools</tt> directory to user <span class=
"emphasis"><em>root</em></span> by running the following
command:
</p>
<pre class="userinput"><kbd class=
"command">chown -R 0:0 /tools</kbd></pre>
<p>
The command uses <em class="parameter"><tt>0:0</tt></em>
instead of <em class="parameter"><tt>root:root</tt></em>,
because <span><strong class="command">chown</strong></span> is
unable to resolve the name &ldquo;<span class=
"quote">root</span>&rdquo; until the password file has been
created. This book assumes you ran this <span><strong class=
"command">chown</strong></span> command.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-creatingdirs" name=
"ch-system-creatingdirs"></a>6.5.&nbsp;Creating
Directories
</h2>
</div>
</div>
</div>
<p>
It is time to create some structure in the LFS file system.
Create a standard directory tree by issuing the following
commands:
</p>
<pre class="userinput"><kbd class=
"command">install -dv /{bin,boot,dev,etc/opt,home,lib,mnt}
install -dv /{sbin,srv,usr/local,var,opt}
install -dv /root -m 0750
install -dv /tmp /var/tmp -m 1777
install -dv /media/{floppy,cdrom}
install -dv /usr/{bin,include,lib,sbin,share,src}
ln -sv share/{man,doc,info} /usr
install -dv /usr/share/{doc,info,locale,man}
install -dv /usr/share/{misc,terminfo,zoneinfo}
install -dv /usr/share/man/man{1,2,3,4,5,6,7,8}
install -dv /usr/local/{bin,etc,include,lib,sbin,share,src}
ln -sv share/{man,doc,info} /usr/local
install -dv /usr/local/share/{doc,info,locale,man}
install -dv /usr/local/share/{misc,terminfo,zoneinfo}
install -dv /usr/local/share/man/man{1,2,3,4,5,6,7,8}
install -dv /var/{lock,log,mail,run,spool}
install -dv /var/{opt,cache,lib/{misc,locate},local}
install -dv /opt/{bin,doc,include,info}
install -dv /opt/{lib,man/man{1,2,3,4,5,6,7,8}}</kbd></pre>
<p>
Directories are, by default, created with permission mode 755,
but this is not desirable for all directories. In the commands
above, two changes are made&mdash;one to the home directory of
user <span class="emphasis"><em>root</em></span>, and another
to the directories for temporary files.
</p>
<p>
The first mode change ensures that not just anybody can enter
the <tt class="filename">/root</tt> directory&mdash;the same as
a normal user would do with his or her home directory. The
second mode change makes sure that any user can write to the
<tt class="filename">/tmp</tt> and <tt class=
"filename">/var/tmp</tt> directories, but cannot remove another
user's files from them. The latter is prohibited by the
so-called &ldquo;<span class="quote">sticky bit,</span>&rdquo;
the highest bit (1) in the 1777 bit mask.
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.5.1. FHS Compliance Note
</h3>
</div>
<p>
The directory tree is based on the Filesystem Hierarchy
Standard (FHS) (available at <a href=
"http://www.pathname.com/fhs/"><i>http://www.pathname.com/fhs/</i></a>).
In addition to the tree created above, this standard
stipulates the existence of <tt class=
"filename">/usr/local/games</tt> and <tt class=
"filename">/usr/share/games</tt>. The FHS is not precise as
to the structure of the <tt class=
"filename">/usr/local/share</tt> subdirectory, so we create
only the directories that are needed. However, feel free to
create these directories if you prefer to conform more
strictly to the FHS.
</p>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-createfiles" name=
"ch-system-createfiles"></a>6.6.&nbsp;Creating Essential
Symlinks
</h2>
</div>
</div>
</div>
<p>
Some programs use hard-wired paths to programs which do not
exist yet. In order to satisfy these programs, create a number
of symbolic links which will be replaced by real files
throughout the course of this chapter after the software has
been installed.
</p>
<pre class="userinput"><kbd class=
"command">ln -sv /tools/bin/{bash,cat,pwd,stty} /bin
ln -sv /tools/bin/perl /usr/bin
ln -sv /tools/lib/libgcc_s.so{,.1} /usr/lib
ln -sv bash /bin/sh</kbd></pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-pwdgroup" name=
"ch-system-pwdgroup"></a>6.7.&nbsp;Creating the passwd,
group, and log Files
</h2>
</div>
</div>
</div>
<p>
In order for user <span class="emphasis"><em>root</em></span>
to be able to login and for the name &ldquo;<span class=
"quote">root</span>&rdquo; to be recognized, there must be
relevant entries in the <tt class="filename">/etc/passwd</tt>
and <tt class="filename">/etc/group</tt> files.
</p>
<p>
Create the <tt class="filename">/etc/passwd</tt> file by
running the following command:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/passwd &lt;&lt; "EOF"
<tt class="literal">root:x:0:0:root:/root:/bin/bash</tt>
EOF</kbd></pre>
<p>
The actual password for <span class=
"emphasis"><em>root</em></span> (the &ldquo;<span class=
"quote">x</span>&rdquo; used here is just a placeholder) will
be set later.
</p>
<p>
Create the <tt class="filename">/etc/group</tt> file by running
the following command:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/group &lt;&lt; "EOF"
<tt class="literal">root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
video:x:12:
utmp:x:13:
usb:x:14:
cdrom:x:15:</tt>
EOF</kbd></pre>
<p>
The created groups are not part of any standard&mdash;they are
groups decided on in part by the requirements of the Udev
configuration in this chapter, and in part by common convention
employed by a number of existing Linux distributions. The Linux
Standard Base (LSB, available at <a href=
"http://www.linuxbase.org"><i>http://www.linuxbase.org</i></a>)
recommends only that, besides the group &ldquo;<span class=
"quote">root</span>&rdquo; with a Group ID (GID) of 0, a group
&ldquo;<span class="quote">bin</span>&rdquo; with a GID of 1 be
present. All other group names and GIDs can be chosen freely by
the system administrator since well-written programs do not
depend on GID numbers, but rather use the group's name.
</p>
<p>
To remove the &ldquo;<span class="quote">I have no
name!</span>&rdquo; prompt, start a new shell. Since a full
Glibc was installed in <a href=
"#chapter-temporary-tools">Chapter 5</a> and the <tt class=
"filename">/etc/passwd</tt> and <tt class=
"filename">/etc/group</tt> files have been created, user name
and group name resolution will now work.
</p>
<pre class="userinput"><kbd class=
"command">exec /tools/bin/bash --login +h</kbd></pre>
<p>
Note the use of the <em class="parameter"><tt>+h</tt></em>
directive. This tells <span><strong class=
"command">bash</strong></span> not to use its internal path
hashing. Without this directive, <span><strong class=
"command">bash</strong></span> would remember the paths to
binaries it has executed. To ensure the use of the newly
compiled binaries as soon as they are installed, the <em class=
"parameter"><tt>+h</tt></em> directive will be used for the
duration of this chapter.
</p>
<p>
The <span><strong class="command">login</strong></span>,
<span><strong class="command">agetty</strong></span>, and
<span><strong class="command">init</strong></span> programs
(and others) use a number of log files to record information
such as who was logged into the system and when. However, these
programs will not write to the log files if they do not already
exist. Initialize the log files and give them proper
permissions:
</p>
<pre class="userinput"><kbd class=
"command">touch /var/run/utmp /var/log/{btmp,lastlog,wtmp}
chgrp -v utmp /var/run/utmp /var/log/lastlog
chmod -v 664 /var/run/utmp /var/log/lastlog</kbd></pre>
<p>
The <tt class="filename">/var/run/utmp</tt> file records the
users that are currently logged in. The <tt class=
"filename">/var/log/wtmp</tt> file records all logins and
logouts. The <tt class="filename">/var/log/lastlog</tt> file
records when each user last logged in. The <tt class=
"filename">/var/log/btmp</tt> file records the bad login
attempts.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-devices" name=
"ch-system-devices"></a>6.8.&nbsp;Populating /dev
</h2>
</div>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.8.1. Creating Initial Device Nodes
</h3>
</div>
<p>
When the kernel boots the system, it requires the presence of
a few device nodes, in particular the <tt class=
"filename">console</tt> and <tt class="filename">null</tt>
devices. The device nodes will be created on the hard disk so
that they are available before <span><strong class=
"command">udev</strong></span> has been started, and
additionally when Linux is started in single user mode (hence
the restrictive permissions on <tt class=
"filename">console</tt>). Create the devices by running the
following commands:
</p>
<pre class="userinput"><kbd class=
"command">mknod -m 600 /dev/console c 5 1
mknod -m 666 /dev/null c 1 3</kbd></pre>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.8.2. Mounting tmpfs and Populating /dev
</h3>
</div>
<p>
The recommended method of populating the <tt class=
"filename">/dev</tt> directory with devices is to mount a
virtual filesystem (such as <tt class=
"systemitem">tmpfs</tt>) on the <tt class=
"filename">/dev</tt> directory, and allow the devices to be
created dynamically on that virtual filesystem as they are
detected or accessed. This is generally done during the boot
process. Since this new system has not been booted, it is
necessary to do what the LFS-Bootscripts package would
otherwise do by mounting <tt class="filename">/dev</tt>:
</p>
<pre class="userinput"><kbd class=
"command">mount -nvt tmpfs none /dev</kbd></pre>
<p>
The Udev package is what actually creates the devices in the
<tt class="filename">/dev</tt> directory. Since it will not
be installed until later on in the process, manually create
the minimal set of device nodes needed to complete the
building of this system:
</p>
<pre class="userinput"><kbd class=
"command">mknod -m 622 /dev/console c 5 1
mknod -m 666 /dev/null c 1 3
mknod -m 666 /dev/zero c 1 5
mknod -m 666 /dev/ptmx c 5 2
mknod -m 666 /dev/tty c 5 0
mknod -m 444 /dev/random c 1 8
mknod -m 444 /dev/urandom c 1 9
chown -v root:tty /dev/{console,ptmx,tty}</kbd></pre>
<p>
There are some symlinks and directories required by LFS that
are created during system startup by the LFS-Bootscripts
package. Since this is a chroot environment and not a booted
environment, those symlinks and directories need to be
created here:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv /proc/self/fd /dev/fd
ln -sv /proc/self/fd/0 /dev/stdin
ln -sv /proc/self/fd/1 /dev/stdout
ln -sv /proc/self/fd/2 /dev/stderr
ln -sv /proc/kcore /dev/core
mkdir -v /dev/pts
mkdir -v /dev/shm</kbd></pre>
<p>
Finally, mount the proper virtual (kernel) file systems on
the newly-created directories:
</p>
<pre class="userinput"><kbd class=
"command">mount -vt devpts -o gid=4,mode=620 none /dev/pts
mount -vt tmpfs none /dev/shm</kbd></pre>
<p>
The <span><strong class="command">mount</strong></span>
commands executed above may result in the following warning
message:
</p>
<pre class="screen"><tt class=
"computeroutput">can't open /etc/fstab: No such file or directory.</tt></pre>
<p>
This file&mdash;<tt class=
"filename">/etc/fstab</tt>&mdash;has not been created yet but
is also not required for the file systems to be properly
mounted. As such, the warning can be safely ignored.
</p>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-linux-libc-headers" name=
"ch-system-linux-libc-headers"></a>6.9.&nbsp;Linux-Libc-Headers-2.6.11.2
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Linux-Libc-Headers package contains the
&ldquo;<span class="quote">sanitized</span>&rdquo; kernel
headers.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">26.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Coreutils</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.9.1. Installation of Linux-Libc-Headers
</h3>
</div>
<p>
For years it has been common practice to use
&ldquo;<span class="quote">raw</span>&rdquo; kernel headers
(straight from a kernel tarball) in <tt class=
"filename">/usr/include</tt>, but over the last few years,
the kernel developers have taken a strong stance that this
should not be done. This gave birth to the Linux-Libc-Headers
Project, which was designed to maintain an API stable version
of the Linux headers.
</p>
<p>
Install the header files:
</p>
<pre class="userinput"><kbd class=
"command">cp -Rv include/asm-i386 /usr/include/asm
cp -Rv include/linux /usr/include</kbd></pre>
<p>
Ensure that all the headers are owned by root:
</p>
<pre class="userinput"><kbd class=
"command">chown -Rv root:root /usr/include/{asm,linux}</kbd></pre>
<p>
Make sure the users can read the headers:
</p>
<pre class="userinput"><kbd class=
"command">find /usr/include/{asm,linux} -type d -exec chmod -v 755 {} \;
find /usr/include/{asm,linux} -type f -exec chmod -v 644 {} \;</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-linux-libc-headers" name=
"contents-linux-libc-headers"></a>
<h3 class="sect2">
6.9.2. Contents of Linux-Libc-Headers
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
headers:</span></strong> <span class=
"seg">/usr/include/{asm,linux}/*.h</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3481744" name="id3481744"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="linux-libc-headers" name=
"linux-libc-headers"></a><span class=
"term"><tt class="filename">/usr/include/{asm,linux}/*.h</tt></span>
</td>
<td>
<p>
The Linux API headers
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-man-pages" name=
"ch-system-man-pages"></a>6.10.&nbsp;Man-pages-2.01
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Man-pages package contains over 1,200 man pages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">25.8 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Coreutils,
and Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.10.1. Installation of Man-pages
</h3>
</div>
<p>
Install Man-pages by running:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-manpages" name="contents-manpages"></a>
<h3 class="sect2">
6.10.2. Contents of Man-pages
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
files:</span></strong> <span class="seg">various man
pages</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3491567" name="id3491567"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="man-pages" name="man-pages"></a><span class=
"term"><tt class="filename">man pages</tt></span>
</td>
<td>
<p>
Describe the C and C++ functions, important device
files, and significant configuration files
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-glibc" name=
"ch-system-glibc"></a>6.11.&nbsp;Glibc-2.3.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Glibc package contains the main C library. This library
provides the basic routines for allocating memory, searching
directories, opening and closing files, reading and writing
files, string handling, pattern matching, arithmetic, and so
on.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">12.3 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">476 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Gettext, Grep, Make,
Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.11.1. Installation of Glibc
</h3>
</div>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
Some packages outside of LFS suggest installing GNU
libiconv in order to translate data from one encoding to
another. The project's home page (<a href=
"http://www.gnu.org/software/libiconv/"><i>http://www.gnu.org/software/libiconv/</i></a>)
says &ldquo;<span class="quote">This library provides an
<tt class="function">iconv()</tt> implementation, for use
on systems which don't have one, or whose implementation
cannot convert from/to Unicode.</span> &rdquo; Glibc
provides an <tt class="function">iconv()</tt>
implementation and can convert from/to Unicode, therefore
libiconv is not required on an LFS system.
</p>
</div>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
Glibc.
</p>
<p>
The Glibc build system is self-contained and will install
perfectly, even though the compiler specs file and linker are
still pointing at <tt class="filename">/tools</tt>. The specs
and linker cannot be adjusted before the Glibc install
because the Glibc autoconf tests would give false results and
defeat the goal of achieving a clean build.
</p>
<p>
The linuxthreads tarball contains the man pages for the
threading libraries installed by Glibc. Unpack the tarball
from within the Glibc source directory:
</p>
<pre class="userinput"><kbd class=
"command">tar -xjvf ../glibc-linuxthreads-2.3.4.tar.bz2</kbd></pre>
<p>
In certain rare circumstances, Glibc can segfault when no
standard search directories exist. The following patch
prevents this:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../glibc-2.3.4-rtld_search_dirs-1.patch</kbd></pre>
<p>
Glibc has two tests which fail when the running kernel is
2.6.11.x The problem has been determined to be with the tests
themselves, not with the libc nor the kernel. This patch
fixes the problem:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../glibc-2.3.4-fix_test-1.patch</kbd></pre>
<p>
Apply the following patch to fix a bug in Glibc that can
prevent some programs (including OpenOffice.org) from
running:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../glibc-2.3.4-tls_assert-1.patch</kbd></pre>
<p>
The Glibc documentation recommends building Glibc outside of
the source directory in a dedicated build directory:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../glibc-build
cd ../glibc-build</kbd></pre>
<p>
Prepare Glibc for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../glibc-2.3.4/configure --prefix=/usr \
--disable-profile --enable-add-ons \
--enable-kernel=2.6.0 --libexecdir=/usr/lib/glibc</kbd></pre>
<p>
The meaning of the new configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--libexecdir=/usr/lib/glibc</tt></em></span>
</dt>
<dd>
<p>
This changes the location of the <span><strong class=
"command">pt_chown</strong></span> program from its
default of <tt class="filename">/usr/libexec</tt> to
<tt class="filename">/usr/lib/glibc</tt>.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
In this section, the test suite for Glibc is considered
critical. Do not skip it under any circumstance.
</p>
</div>
</div>
<p>
Test the results:
</p>
<pre class="userinput"><kbd class=
"command">make -k check &gt;glibc-check-log 2&gt;&amp;1
grep Error glibc-check-log</kbd></pre>
<p>
The Glibc test suite is highly dependent on certain functions
of the host system, in particular the kernel. In general, the
Glibc test suite is always expected to pass. However, in
certain circumstances, some failures are unavoidable. This is
a list of the most common issues:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
The <span class="emphasis"><em>math</em></span> tests
sometimes fail when running on systems where the CPU is
not a relatively new genuine Intel or authentic AMD.
Certain optimization settings are also known to be a
factor here.
</p>
</li>
<li>
<p>
The <span class="emphasis"><em>gettext</em></span> test
sometimes fails due to host system issues. The exact
reasons are not yet clear.
</p>
</li>
<li>
<p>
If you have mounted the LFS partition with the
<em class="parameter"><tt>noatime</tt></em> option, the
<span class="emphasis"><em>atime</em></span> test will
fail. As mentioned in <a href="#space-mounting" title=
"2.4.&nbsp;Mounting the New Partition">Section 2.4,
&ldquo;Mounting the New Partition&rdquo;</a>, do not
use the <em class="parameter"><tt>noatime</tt></em>
option while building LFS.
</p>
</li>
<li>
<p>
When running on older and slower hardware, some tests
can fail because of test timeouts being exceeded.
</p>
</li>
</ul>
</div>
<p>
Though it is a harmless message, the install stage of Glibc
will complain about the absence of <tt class=
"filename">/etc/ld.so.conf</tt>. Prevent this warning with:
</p>
<pre class="userinput"><kbd class=
"command">touch /etc/ld.so.conf</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
The locales that can make the system respond in a different
language were not installed by the above command. Install
this with:
</p>
<pre class="userinput"><kbd class=
"command">make localedata/install-locales</kbd></pre>
<p>
To save time, an alternative to running the previous command
(which generates and installs every locale listed in the
glibc-2.3.4/localedata/SUPPORTED file) is to install only
those locales that are wanted and needed. This can be
achieved by using the <span><strong class=
"command">localedef</strong></span> command. Information on
this command is located in the <tt class=
"filename">INSTALL</tt> file in the Glibc source. However,
there are a number of locales that are essential in order for
the tests of future packages to pass, in particular, the
<span class="emphasis"><em>libstdc++</em></span> tests from
GCC. The following instructions, instead of the <em class=
"parameter"><tt>install-locales</tt></em> target used above,
will install the minimum set of locales necessary for the
tests to run successfully:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -pv /usr/lib/locale
localedef -i de_DE -f ISO-8859-1 de_DE
localedef -i de_DE@euro -f ISO-8859-15 de_DE@euro
localedef -i en_HK -f ISO-8859-1 en_HK
localedef -i en_PH -f ISO-8859-1 en_PH
localedef -i en_US -f ISO-8859-1 en_US
localedef -i es_MX -f ISO-8859-1 es_MX
localedef -i fa_IR -f UTF-8 fa_IR
localedef -i fr_FR -f ISO-8859-1 fr_FR
localedef -i fr_FR@euro -f ISO-8859-15 fr_FR@euro
localedef -i it_IT -f ISO-8859-1 it_IT
localedef -i ja_JP -f EUC-JP ja_JP</kbd></pre>
<p>
Some locales installed by the <span><strong class=
"command">make localedata/install-locales</strong></span>
command above are not properly supported by some applications
that are in the LFS and BLFS books. Because of the various
problems that arise due to application programmers making
assumptions that break in such locales, LFS should not be
used in locales that utilize multibyte character sets
(including UTF-8) or right-to-left writing order. Numerous
unofficial and unstable patches are required to fix these
problems, and it has been decided by the LFS developers not
to support such complex locales at this time. This applies to
the ja_JP and fa_IR locales as well&mdash;they have been
installed only for GCC and Gettext tests to pass, and the
<span><strong class="command">watch</strong></span> program
(part of the Procps package) does not work properly in them.
Various attempts to circumvent these restrictions are
documented in internationalization-related hints.
</p>
<p>
Build the linuxthreads man pages, which are a great reference
on the threading API (applicable to NPTL as well):
</p>
<pre class="userinput"><kbd class=
"command">make -C ../glibc-2.3.4/linuxthreads/man</kbd></pre>
<p>
Install these pages:
</p>
<pre class="userinput"><kbd class=
"command">make -C ../glibc-2.3.4/linuxthreads/man install</kbd></pre>
</div>
<div class="configuration" lang="en" xml:lang="en">
<div class="titlepage">
<a id="conf-glibc" name="conf-glibc"></a>
<h3 class="sect2">
6.11.2. Configuring Glibc
</h3>
</div>
<p>
The <tt class="filename">/etc/nsswitch.conf</tt> file needs
to be created because, although Glibc provides defaults when
this file is missing or corrupt, the Glibc defaults do not
work well in a networked environment. The time zone also
needs to be configured.
</p>
<p>
Create a new file <tt class=
"filename">/etc/nsswitch.conf</tt> by running the following:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/nsswitch.conf &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/nsswitch.conf
passwd: files
group: files
shadow: files
hosts: files dns
networks: files
protocols: files
services: files
ethers: files
rpc: files
# End /etc/nsswitch.conf</tt>
EOF</kbd></pre>
<p>
To determine the local time zone, run the following script:
</p>
<pre class="userinput"><kbd class=
"command">tzselect</kbd></pre>
<p>
After answering a few questions about the location, the
script will output the name of the time zone (e.g.,
<span class="emphasis"><em>EST5EDT</em></span> or
<span class="emphasis"><em>Canada/Eastern</em></span>). Then
create the <tt class="filename">/etc/localtime</tt> file by
running:
</p>
<pre class="userinput"><kbd class=
"command">cp -v --remove-destination /usr/share/zoneinfo/<em class=
"replaceable"><tt>[xxx]</tt></em> \
/etc/localtime</kbd></pre>
<p>
Replace <em class="replaceable"><tt>[xxx]</tt></em> with the
name of the time zone that <span><strong class=
"command">tzselect</strong></span> provided (e.g.,
Canada/Eastern).
</p>
<p>
The meaning of the cp option:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--remove-destination</tt></em></span>
</dt>
<dd>
<p>
This is needed to force removal of the already existing
symbolic link. The reason for copying the file instead
of using a symlink is to cover the situation where
<tt class="filename">/usr</tt> is on a separate
partition. This could be important when booted into
single user mode.
</p>
</dd>
</dl>
</div>
</div>
<div class="configuration" lang="en" xml:lang="en">
<div class="titlepage">
<a id="conf-ld" name="conf-ld"></a>
<h3 class="sect2">
6.11.3. Configuring Dynamic Loader
</h3>
</div>
<p>
By default, the dynamic loader (<tt class=
"filename">/lib/ld-linux.so.2</tt>) searches through
<tt class="filename">/lib</tt> and <tt class=
"filename">/usr/lib</tt> for dynamic libraries that are
needed by programs as they are run. However, if there are
libraries in directories other than <tt class=
"filename">/lib</tt> and <tt class="filename">/usr/lib</tt>,
these need to be added to the <tt class=
"filename">/etc/ld.so.conf</tt> file in order for the dynamic
loader to find them. Two directories that are commonly known
to contain additional libraries are <tt class=
"filename">/usr/local/lib</tt> and <tt class=
"filename">/opt/lib</tt>, so add those directories to the
dynamic loader's search path.
</p>
<p>
Create a new file <tt class="filename">/etc/ld.so.conf</tt>
by running the following:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/ld.so.conf &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/ld.so.conf
/usr/local/lib
/opt/lib
# End /etc/ld.so.conf</tt>
EOF</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-glibc" name="contents-glibc"></a>
<h3 class="sect2">
6.11.4. Contents of Glibc
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">catchsegv,
gencat, getconf, getent, iconv, iconvconfig, ldconfig,
ldd, lddlibc4, locale, localedef, mtrace, nscd,
nscd_nischeck, pcprofiledump, pt_chown, rpcgen, rpcinfo,
sln, sprof, tzselect, xtrace, zdump, and zic</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class="seg">ld.so,
libBrokenLocale.[a,so], libSegFault.so, libanl.[a,so],
libbsd-compat.a, libc.[a,so], libcrypt.[a,so],
libdl.[a,so], libg.a, libieee.a, libm.[a,so],
libmcheck.a, libmemusage.so, libnsl.a, libnss_compat.so,
libnss_dns.so, libnss_files.so, libnss_hesiod.so,
libnss_nis.so, libnss_nisplus.so, libpcprofile.so,
libpthread.[a,so], libresolv.[a,so], librpcsvc.a,
librt.[a,so], libthread_db.so, and libutil.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3492372" name="id3492372"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="catchsegv" name="catchsegv"></a><span class=
"term"><span><strong class=
"command">catchsegv</strong></span></span>
</td>
<td>
<p>
Can be used to create a stack trace when a program
terminates with a segmentation fault
</p>
</td>
</tr>
<tr>
<td>
<a id="gencat" name="gencat"></a><span class=
"term"><span><strong class=
"command">gencat</strong></span></span>
</td>
<td>
<p>
Generates message catalogues
</p>
</td>
</tr>
<tr>
<td>
<a id="getconf" name="getconf"></a><span class=
"term"><span><strong class=
"command">getconf</strong></span></span>
</td>
<td>
<p>
Displays the system configuration values for file
system specific variables
</p>
</td>
</tr>
<tr>
<td>
<a id="getent" name="getent"></a><span class=
"term"><span><strong class=
"command">getent</strong></span></span>
</td>
<td>
<p>
Gets entries from an administrative database
</p>
</td>
</tr>
<tr>
<td>
<a id="iconv" name="iconv"></a><span class=
"term"><span><strong class=
"command">iconv</strong></span></span>
</td>
<td>
<p>
Performs character set conversion
</p>
</td>
</tr>
<tr>
<td>
<a id="iconvconfig" name=
"iconvconfig"></a><span class=
"term"><span><strong class=
"command">iconvconfig</strong></span></span>
</td>
<td>
<p>
Creates fastloading <span><strong class=
"command">iconv</strong></span> module
configuration files
</p>
</td>
</tr>
<tr>
<td>
<a id="ldconfig" name="ldconfig"></a><span class=
"term"><span><strong class=
"command">ldconfig</strong></span></span>
</td>
<td>
<p>
Configures the dynamic linker runtime bindings
</p>
</td>
</tr>
<tr>
<td>
<a id="ldd" name="ldd"></a><span class=
"term"><span><strong class=
"command">ldd</strong></span></span>
</td>
<td>
<p>
Reports which shared libraries are required by each
given program or shared library
</p>
</td>
</tr>
<tr>
<td>
<a id="lddlibc4" name="lddlibc4"></a><span class=
"term"><span><strong class=
"command">lddlibc4</strong></span></span>
</td>
<td>
<p>
Assists <span><strong class=
"command">ldd</strong></span> with object files
</p>
</td>
</tr>
<tr>
<td>
<a id="locale" name="locale"></a><span class=
"term"><span><strong class=
"command">locale</strong></span></span>
</td>
<td>
<p>
Tells the compiler to enable or disable the use of
POSIX locales for built-in operations
</p>
</td>
</tr>
<tr>
<td>
<a id="localedef" name="localedef"></a><span class=
"term"><span><strong class=
"command">localedef</strong></span></span>
</td>
<td>
<p>
Compiles locale specifications
</p>
</td>
</tr>
<tr>
<td>
<a id="mtrace" name="mtrace"></a><span class=
"term"><span><strong class=
"command">mtrace</strong></span></span>
</td>
<td>
<p>
Reads and interprets a memory trace file and
displays a summary in human-readable format
</p>
</td>
</tr>
<tr>
<td>
<a id="nscd" name="nscd"></a><span class=
"term"><span><strong class=
"command">nscd</strong></span></span>
</td>
<td>
<p>
A daemon that provides a cache for the most common
name service requests
</p>
</td>
</tr>
<tr>
<td>
<a id="nscd_nischeck" name=
"nscd_nischeck"></a><span class=
"term"><span><strong class=
"command">nscd_nischeck</strong></span></span>
</td>
<td>
<p>
Checks whether or not secure mode is necessary for
NIS+ lookup
</p>
</td>
</tr>
<tr>
<td>
<a id="pcprofiledump" name=
"pcprofiledump"></a><span class=
"term"><span><strong class=
"command">pcprofiledump</strong></span></span>
</td>
<td>
<p>
Dumps information generated by PC profiling
</p>
</td>
</tr>
<tr>
<td>
<a id="pt_chown" name="pt_chown"></a><span class=
"term"><span><strong class=
"command">pt_chown</strong></span></span>
</td>
<td>
<p>
A helper program for <span><strong class=
"command">grantpt</strong></span> to set the owner,
group and access permissions of a slave pseudo
terminal
</p>
</td>
</tr>
<tr>
<td>
<a id="rpcgen" name="rpcgen"></a><span class=
"term"><span><strong class=
"command">rpcgen</strong></span></span>
</td>
<td>
<p>
Generates C code to implement the Remote Procecure
Call (RPC) protocol
</p>
</td>
</tr>
<tr>
<td>
<a id="rpcinfo" name="rpcinfo"></a><span class=
"term"><span><strong class=
"command">rpcinfo</strong></span></span>
</td>
<td>
<p>
Makes an RPC call to an RPC server
</p>
</td>
</tr>
<tr>
<td>
<a id="sln" name="sln"></a><span class=
"term"><span><strong class=
"command">sln</strong></span></span>
</td>
<td>
<p>
A statically linked <span><strong class=
"command">ln</strong></span> program
</p>
</td>
</tr>
<tr>
<td>
<a id="sprof" name="sprof"></a><span class=
"term"><span><strong class=
"command">sprof</strong></span></span>
</td>
<td>
<p>
Reads and displays shared object profiling data
</p>
</td>
</tr>
<tr>
<td>
<a id="tzselect" name="tzselect"></a><span class=
"term"><span><strong class=
"command">tzselect</strong></span></span>
</td>
<td>
<p>
Asks the user about the location of the system and
reports the corresponding time zone description
</p>
</td>
</tr>
<tr>
<td>
<a id="xtrace" name="xtrace"></a><span class=
"term"><span><strong class=
"command">xtrace</strong></span></span>
</td>
<td>
<p>
Traces the execution of a program by printing the
currently executed function
</p>
</td>
</tr>
<tr>
<td>
<a id="zdump" name="zdump"></a><span class=
"term"><span><strong class=
"command">zdump</strong></span></span>
</td>
<td>
<p>
The time zone dumper
</p>
</td>
</tr>
<tr>
<td>
<a id="zic" name="zic"></a><span class=
"term"><span><strong class=
"command">zic</strong></span></span>
</td>
<td>
<p>
The time zone compiler
</p>
</td>
</tr>
<tr>
<td>
<a id="ld.so" name="ld.so"></a><span class=
"term"><tt class="filename">ld.so</tt></span>
</td>
<td>
<p>
The helper program for shared library executables
</p>
</td>
</tr>
<tr>
<td>
<a id="libBrokenLocale" name=
"libBrokenLocale"></a><span class="term"><tt class=
"filename">libBrokenLocale</tt></span>
</td>
<td>
<p>
Used by programs, such as Mozilla, to solve broken
locales
</p>
</td>
</tr>
<tr>
<td>
<a id="libSegFault" name=
"libSegFault"></a><span class="term"><tt class=
"filename">libSegFault</tt></span>
</td>
<td>
<p>
The segmentation fault signal handler
</p>
</td>
</tr>
<tr>
<td>
<a id="libanl" name="libanl"></a><span class=
"term"><tt class="filename">libanl</tt></span>
</td>
<td>
<p>
An asynchronous name lookup library
</p>
</td>
</tr>
<tr>
<td>
<a id="libbsd-compat" name=
"libbsd-compat"></a><span class="term"><tt class=
"filename">libbsd-compat</tt></span>
</td>
<td>
<p>
Provides the portability needed in order to run
certain Berkey Software Distribution (BSD) programs
under Linux
</p>
</td>
</tr>
<tr>
<td>
<a id="libc" name="libc"></a><span class=
"term"><tt class="filename">libc</tt></span>
</td>
<td>
<p>
The main C library
</p>
</td>
</tr>
<tr>
<td>
<a id="libcrypt" name="libcrypt"></a><span class=
"term"><tt class="filename">libcrypt</tt></span>
</td>
<td>
<p>
The cryptography library
</p>
</td>
</tr>
<tr>
<td>
<a id="libdl" name="libdl"></a><span class=
"term"><tt class="filename">libdl</tt></span>
</td>
<td>
<p>
The dynamic linking interface library
</p>
</td>
</tr>
<tr>
<td>
<a id="libg" name="libg"></a><span class=
"term"><tt class="filename">libg</tt></span>
</td>
<td>
<p>
A runtime library for <span><strong class=
"command">g++</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="libieee" name="libieee"></a><span class=
"term"><tt class="filename">libieee</tt></span>
</td>
<td>
<p>
The Institute of Electrical and Electronic
Engineers (IEEE) floating point library
</p>
</td>
</tr>
<tr>
<td>
<a id="libm" name="libm"></a><span class=
"term"><tt class="filename">libm</tt></span>
</td>
<td>
<p>
The mathematical library
</p>
</td>
</tr>
<tr>
<td>
<a id="libmcheck" name="libmcheck"></a><span class=
"term"><tt class="filename">libmcheck</tt></span>
</td>
<td>
<p>
Contains code run at boot
</p>
</td>
</tr>
<tr>
<td>
<a id="libmemusage" name=
"libmemusage"></a><span class="term"><tt class=
"filename">libmemusage</tt></span>
</td>
<td>
<p>
Used by <span><strong class=
"command">memusage</strong></span> to help collect
information about the memory usage of a program
</p>
</td>
</tr>
<tr>
<td>
<a id="libnsl" name="libnsl"></a><span class=
"term"><tt class="filename">libnsl</tt></span>
</td>
<td>
<p>
The network services library
</p>
</td>
</tr>
<tr>
<td>
<a id="libnss" name="libnss"></a><span class=
"term"><tt class="filename">libnss</tt></span>
</td>
<td>
<p>
The Name Service Switch libraries, containing
functions for resolving host names, user names,
group names, aliases, services, protocols, etc.
</p>
</td>
</tr>
<tr>
<td>
<a id="libpcprofile" name=
"libpcprofile"></a><span class="term"><tt class=
"filename">libpcprofile</tt></span>
</td>
<td>
<p>
Contains profiling functions used to track the
amount of CPU time spent in specific source code
lines
</p>
</td>
</tr>
<tr>
<td>
<a id="libpthread" name="libpthread"></a><span class=
"term"><tt class="filename">libpthread</tt></span>
</td>
<td>
<p>
The POSIX threads library
</p>
</td>
</tr>
<tr>
<td>
<a id="libresolv" name="libresolv"></a><span class=
"term"><tt class="filename">libresolv</tt></span>
</td>
<td>
<p>
Contains functions for creating, sending, and
interpreting packets to the Internet domain name
servers
</p>
</td>
</tr>
<tr>
<td>
<a id="librpcsvc" name="librpcsvc"></a><span class=
"term"><tt class="filename">librpcsvc</tt></span>
</td>
<td>
<p>
Contains functions providing miscellaneous RPC
services
</p>
</td>
</tr>
<tr>
<td>
<a id="librt" name="librt"></a><span class=
"term"><tt class="filename">librt</tt></span>
</td>
<td>
<p>
Contains functions providing most of the interfaces
specified by the POSIX.1b Realtime Extension
</p>
</td>
</tr>
<tr>
<td>
<a id="libthread_db" name=
"libthread_db"></a><span class="term"><tt class=
"filename">libthread_db</tt></span>
</td>
<td>
<p>
Contains functions useful for building debuggers
for multi-threaded programs
</p>
</td>
</tr>
<tr>
<td>
<a id="libutil" name="libutil"></a><span class=
"term"><tt class="filename">libutil</tt></span>
</td>
<td>
<p>
Contains code for &ldquo;<span class=
"quote">standard</span>&rdquo; functions used in
many different Unix utilities
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-readjusting" name=
"ch-system-readjusting"></a>6.12.&nbsp;Re-adjusting the
Toolchain
</h2>
</div>
</div>
</div>
<p>
Now that the final C libraries have been installed, it is time
to adjust the toolchain again. The toolchain will be adjusted
so that it will link any newly compiled program against these
new libraries. This is the same process used in the
&ldquo;<span class="quote">Adjusting</span>&rdquo; phase in the
beginning of <a href="#chapter-temporary-tools">Chapter 5</a>,
but with the adjustments reversed. In <a href=
"#chapter-temporary-tools">Chapter 5</a>, the chain was guided
from the host's <tt class="filename">/{,usr/}lib</tt>
directories to the new <tt class="filename">/tools/lib</tt>
directory. Now, the chain will be guided from that same
<tt class="filename">/tools/lib</tt> directory to the LFS
<tt class="filename">/{,usr/}lib</tt> directories.
</p>
<p>
Start by adjusting the linker. The source and build directories
from the second pass of Binutils were retained for this
purpose. Install the adjusted linker by running the following
command from within the <tt class=
"filename">binutils-build</tt> directory:
</p>
<pre class="userinput"><kbd class=
"command">make -C ld INSTALL=/tools/bin/install install</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
If the earlier warning to retain the Binutils source and
build directories from the second pass in <a href=
"#chapter-temporary-tools">Chapter 5</a> was missed, or if
they were accidentally deleted or are inaccessible, ignore
the above command. The result will be that the next
package, Binutils, will link against the C libraries in
<tt class="filename">/tools</tt> rather than in <tt class=
"filename">/{,usr/}lib</tt>. This is not ideal, however,
testing has shown that the resulting Binutils program
binaries should be identical.
</p>
</div>
</div>
<p>
From now on, every compiled program will link only against the
libraries in <tt class="filename">/usr/lib</tt> and <tt class=
"filename">/lib</tt>. The extra <em class=
"parameter"><tt>INSTALL=/tools/bin/install</tt></em> option is
needed because the <tt class="filename">Makefile</tt> file
created during the second pass still contains the reference to
<span><strong class="command">/usr/bin/install</strong></span>,
which has not been installed yet. Some host distributions
contain a <tt class="filename">ginstall</tt> symbolic link
which takes precedence in the <tt class=
"filename">Makefile</tt> file and can cause a problem. The
above command takes care of this issue.
</p>
<p>
Remove the Binutils source and build directories now.
</p>
<p>
Next, amend the GCC specs file so that it points to the new
dynamic linker. A <span><strong class=
"command">perl</strong></span> command accomplishes this:
</p>
<pre class="userinput"><kbd class=
"command">perl -pi -e 's@ /tools/lib/ld-linux.so.2@ /lib/ld-linux.so.2@g;' \
-e 's@\*startfile_prefix_spec:\n@$_/usr/lib/ @g;' \
`gcc --print-file specs`</kbd></pre>
<p>
It is a good idea to visually inspect the specs file to verify
the intended change was actually made.
</p>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
If working on a platform where the name of the dynamic
linker is something other than <tt class=
"filename">ld-linux.so.2</tt>, substitute
&ldquo;<span class="quote">ld-linux.so.2</span>&rdquo; with
the name of the platform's dynamic linker in the above
commands. Refer back to <a href=
"#ch-tools-toolchaintechnotes" title=
"5.2.&nbsp;Toolchain Technical Notes">Section 5.2,
&ldquo;Toolchain Technical Notes,&rdquo;</a> if necessary.
</p>
</div>
</div>
<div class="caution">
<div class="admonhead">
<h3 class="admontitle">
Caution
</h3>
</div>
<div class="admonbody">
<p>
It is imperative at this point to stop and ensure that the
basic functions (compiling and linking) of the adjusted
toolchain are working as expected. To do this, perform a
sanity check:
</p>
<pre class="userinput"><kbd class=
"command">echo 'main(){}' &gt; dummy.c
cc dummy.c
readelf -l a.out | grep ': /lib'</kbd></pre>
<p>
If everything is working correctly, there should be no
errors, and the output of the last command will be
(allowing for platform-specific differences in dynamic
linker name):
</p>
<pre class="screen"><tt class=
"computeroutput">[Requesting program interpreter: /lib/ld-linux.so.2]</tt></pre>
<p>
Note that <tt class="filename">/lib</tt> is now the prefix
of our dynamic linker.
</p>
<p>
If the output does not appear as shown above or is not
received at all, then something is seriously wrong.
Investigate and retrace the steps to find out where the
problem is and correct it. The most likely reason is that
something went wrong with the specs file amendment above.
Any issues will need to be resolved before continuing on
with the process.
</p>
<p>
Once everything is working correctly, clean up the test
files:
</p>
<pre class="userinput"><kbd class=
"command">rm -v dummy.c a.out</kbd></pre>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-binutils" name=
"ch-system-binutils"></a>6.13.&nbsp;Binutils-2.15.94.0.2.2
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Binutils package contains a linker, an assembler, and
other tools for handling object files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">1.3 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">158 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Bison,
Coreutils, Diffutils, Flex, GCC, Gettext, Glibc, Grep,
M4, Make, Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.13.1. Installation of Binutils
</h3>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
Binutils.
</p>
<p>
Verify that the PTYs are working properly inside the chroot
environment. Check that everything is set up correctly by
performing a simple test:
</p>
<pre class="userinput"><kbd class=
"command">expect -c "spawn ls"</kbd></pre>
<p>
If the following message shows up, the chroot environment is
not set up for proper PTY operation:
</p>
<pre class="screen"><tt class=
"computeroutput">The system has no more ptys.
Ask your system administrator to create more.</tt></pre>
<p>
This issue needs to be resolved before running the test
suites for Binutils and GCC.
</p>
<p>
The Binutils documentation recommends building Binutils
outside of the source directory in a dedicated build
directory:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../binutils-build
cd ../binutils-build</kbd></pre>
<p>
Prepare Binutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../binutils-2.15.94.0.2.2/configure --prefix=/usr \
--enable-shared</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class=
"command">make tooldir=/usr</kbd></pre>
<p>
Normally, the tooldir (the directory where the executables
will ultimately be located) is set to <tt class=
"filename">$(exec_prefix)/$(target_alias)</tt>. For example,
i686 machines would expand that to <tt class=
"filename">/usr/i686-pc-linux-gnu</tt>. Because this is a
custom system, this target-specific directory in <tt class=
"filename">/usr</tt> is not required. <tt class=
"filename">$(exec_prefix)/$(target_alias)</tt> would be used
if the system was used to cross-compile (for example,
compiling a package on an Intel machine that generates code
that can be executed on PowerPC machines).
</p>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
The test suite for Binutils in this section is considered
critical. Do not skip it under any circumstances.
</p>
</div>
</div>
<p>
Test the results:
</p>
<pre class="userinput"><kbd class=
"command">make check</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make tooldir=/usr install</kbd></pre>
<p>
Install the <tt class="filename">libiberty</tt> header file
that is needed by some packages:
</p>
<pre class="userinput"><kbd class=
"command">cp -v ../binutils-2.15.94.0.2.2/include/libiberty.h /usr/include</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-binutils" name="contents-binutils"></a>
<h3 class="sect2">
6.13.2. Contents of Binutils
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">addr2line,
ar, as, c++filt, gprof, ld, nm, objcopy, objdump, ranlib,
readelf, size, strings, and strip</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class="seg">libiberty.a,
libbfd.[a,so], and libopcodes.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3494467" name="id3494467"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="addr2line" name="addr2line"></a><span class=
"term"><span><strong class=
"command">addr2line</strong></span></span>
</td>
<td>
<p>
Translates program addresses to file names and line
numbers; given an address and the name of an
executable, it uses the debugging information in
the executable to determine which source file and
line number are associated with the address
</p>
</td>
</tr>
<tr>
<td>
<a id="ar" name="ar"></a><span class=
"term"><span><strong class=
"command">ar</strong></span></span>
</td>
<td>
<p>
Creates, modifies, and extracts from archives
</p>
</td>
</tr>
<tr>
<td>
<a id="as" name="as"></a><span class=
"term"><span><strong class=
"command">as</strong></span></span>
</td>
<td>
<p>
An assembler that assembles the output of
<span><strong class="command">gcc</strong></span>
into object files
</p>
</td>
</tr>
<tr>
<td>
<a id="c-filt" name="c-filt"></a><span class=
"term"><span><strong class=
"command">c++filt</strong></span></span>
</td>
<td>
<p>
Used by the linker to de-mangle C++ and Java
symbols and to keep overloaded functions from
clashing
</p>
</td>
</tr>
<tr>
<td>
<a id="gprof" name="gprof"></a><span class=
"term"><span><strong class=
"command">gprof</strong></span></span>
</td>
<td>
<p>
Displays call graph profile data
</p>
</td>
</tr>
<tr>
<td>
<a id="ld" name="ld"></a><span class=
"term"><span><strong class=
"command">ld</strong></span></span>
</td>
<td>
<p>
A linker that combines a number of object and
archive files into a single file, relocating their
data and tying up symbol references
</p>
</td>
</tr>
<tr>
<td>
<a id="nm" name="nm"></a><span class=
"term"><span><strong class=
"command">nm</strong></span></span>
</td>
<td>
<p>
Lists the symbols occurring in a given object file
</p>
</td>
</tr>
<tr>
<td>
<a id="objcopy" name="objcopy"></a><span class=
"term"><span><strong class=
"command">objcopy</strong></span></span>
</td>
<td>
<p>
Translates one type of object file into another
</p>
</td>
</tr>
<tr>
<td>
<a id="objdump" name="objdump"></a><span class=
"term"><span><strong class=
"command">objdump</strong></span></span>
</td>
<td>
<p>
Displays information about the given object file,
with options controlling the particular information
to display; the information shown is useful to
programmers who are working on the compilation
tools
</p>
</td>
</tr>
<tr>
<td>
<a id="ranlib" name="ranlib"></a><span class=
"term"><span><strong class=
"command">ranlib</strong></span></span>
</td>
<td>
<p>
Generates an index of the contents of an archive
and stores it in the archive; the index lists all
of the symbols defined by archive members that are
relocatable object files
</p>
</td>
</tr>
<tr>
<td>
<a id="readelf" name="readelf"></a><span class=
"term"><span><strong class=
"command">readelf</strong></span></span>
</td>
<td>
<p>
Displays information about ELF type binaries
</p>
</td>
</tr>
<tr>
<td>
<a id="size" name="size"></a><span class=
"term"><span><strong class=
"command">size</strong></span></span>
</td>
<td>
<p>
Lists the section sizes and the total size for the
given object files
</p>
</td>
</tr>
<tr>
<td>
<a id="strings" name="strings"></a><span class=
"term"><span><strong class=
"command">strings</strong></span></span>
</td>
<td>
<p>
Outputs, for each given file, the sequences of
printable characters that are of at least the
specified length (defaulting to four); for object
files, it prints, by default, only the strings from
the initializing and loading sections while for
other types of files, it scans the entire file
</p>
</td>
</tr>
<tr>
<td>
<a id="strip" name="strip"></a><span class=
"term"><span><strong class=
"command">strip</strong></span></span>
</td>
<td>
<p>
Discards symbols from object files
</p>
</td>
</tr>
<tr>
<td>
<a id="libiberty" name="libiberty"></a><span class=
"term"><tt class="filename">libiberty</tt></span>
</td>
<td>
<p>
Contains routines used by various GNU programs,
including <span><strong class=
"command">getopt</strong></span>,
<span><strong class=
"command">obstack</strong></span>,
<span><strong class=
"command">strerror</strong></span>,
<span><strong class=
"command">strtol</strong></span>, and
<span><strong class=
"command">strtoul</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="libbfd" name="libbfd"></a><span class=
"term"><tt class="filename">libbfd</tt></span>
</td>
<td>
<p>
The Binary File Descriptor library
</p>
</td>
</tr>
<tr>
<td>
<a id="libopcodes" name="libopcodes"></a><span class=
"term"><tt class="filename">libopcodes</tt></span>
</td>
<td>
<p>
A library for dealing with opcodes&mdash;the
&ldquo;<span class="quote">readable
text</span>&rdquo; versions of instructions for the
processor; it is used for building utilities like
<span><strong class=
"command">objdump</strong></span>.
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-gcc" name=
"ch-system-gcc"></a>6.14.&nbsp;GCC-3.4.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The GCC package contains the GNU compiler collection, which
includes the C and C++ compilers.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">11.7 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">451 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Findutils, Gawk, Gettext, Glibc,
Grep, Make, Perl, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.14.1. Installation of GCC
</h3>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
GCC.
</p>
<p>
Apply only the No-Fixincludes patch (not the Specs patch)
also used in the previous chapter:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../gcc-3.4.3-no_fixincludes-1.patch</kbd></pre>
<p>
GCC fails to compile some packages outside of a base Linux
From Scratch install (e.g., Mozilla and kdegraphics) when
used in conjunction with newer versions of Binutils. Apply
the following patch to fix this issue:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../gcc-3.4.3-linkonce-1.patch</kbd></pre>
<p>
Apply a <span><strong class="command">sed</strong></span>
substitution that will suppress the installation of
<tt class="filename">libiberty.a</tt>. The version of
<tt class="filename">libiberty.a</tt> provided by Binutils
will be used instead:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's/install_to_$(INSTALL_DEST) //' libiberty/Makefile.in</kbd></pre>
<p>
The GCC documentation recommends building GCC outside of the
source directory in a dedicated build directory:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v ../gcc-build
cd ../gcc-build</kbd></pre>
<p>
Prepare GCC for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../gcc-3.4.3/configure --prefix=/usr \
--libexecdir=/usr/lib --enable-shared \
--enable-threads=posix --enable-__cxa_atexit \
--enable-clocale=gnu --enable-languages=c,c++</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<div class="important">
<div class="admonhead">
<h3 class="admontitle">
Important
</h3>
</div>
<div class="admonbody">
<p>
In this section, the test suite for GCC is considered
critical. Do not skip it under any circumstance.
</p>
</div>
</div>
<p>
Test the results, but do not stop at errors:
</p>
<pre class="userinput"><kbd class=
"command">make -k check</kbd></pre>
<p>
Some of the errors are known issues and were noted in the
previous chapter. The test suite notes from <a href=
"#ch-tools-gcc-pass2" title=
"5.11.&nbsp;GCC-3.4.3 - Pass 2">Section 5.11,
&ldquo;GCC-3.4.3 - Pass 2,&rdquo;</a> are still relevant
here. Be sure to refer back to them as necessary.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Some packages expect the C preprocessor to be installed in
the <tt class="filename">/lib</tt> directory. To support
those packages, create this symlink:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv ../usr/bin/cpp /lib</kbd></pre>
<p>
Many packages use the name <span><strong class=
"command">cc</strong></span> to call the C compiler. To
satisfy those packages, create a symlink:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv gcc /usr/bin/cc</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
At this point, it is strongly recommended to repeat the
sanity check performed earlier in this chapter. Refer
back to <a href="#ch-system-readjusting" title=
"6.12.&nbsp;Re-adjusting the Toolchain">Section 6.12,
&ldquo;Re-adjusting the Toolchain,&rdquo;</a> and repeat
the check. If the results are in error, then the most
likely reason is that the GCC Specs patch from <a href=
"#chapter-temporary-tools">Chapter 5</a> was erroneously
applied here.
</p>
</div>
</div>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-gcc" name="contents-gcc"></a>
<h3 class="sect2">
6.14.2. Contents of GCC
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">c++, cc (link
to gcc), cpp, g++, gcc, gccbug, and gcov</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class="seg">libgcc.a,
libgcc_eh.a, libgcc_s.so, libstdc++.[a,so], and
libsupc++.a</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3495163" name="id3495163"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="cc" name="cc"></a><span class=
"term"><span><strong class=
"command">cc</strong></span></span>
</td>
<td>
<p>
The C compiler
</p>
</td>
</tr>
<tr>
<td>
<a id="cpp" name="cpp"></a><span class=
"term"><span><strong class=
"command">cpp</strong></span></span>
</td>
<td>
<p>
The C preprocessor; it is used by the compiler to
expand the #include, #define, and similar
statements in the source files
</p>
</td>
</tr>
<tr>
<td>
<a id="c" name="c"></a><span class=
"term"><span><strong class=
"command">c++</strong></span></span>
</td>
<td>
<p>
The C++ compiler
</p>
</td>
</tr>
<tr>
<td>
<a id="g" name="g"></a><span class=
"term"><span><strong class=
"command">g++</strong></span></span>
</td>
<td>
<p>
The C++ compiler
</p>
</td>
</tr>
<tr>
<td>
<a id="gcc" name="gcc"></a><span class=
"term"><span><strong class=
"command">gcc</strong></span></span>
</td>
<td>
<p>
The C compiler
</p>
</td>
</tr>
<tr>
<td>
<a id="gccbug" name="gccbug"></a><span class=
"term"><span><strong class=
"command">gccbug</strong></span></span>
</td>
<td>
<p>
A shell script used to help create useful bug
reports
</p>
</td>
</tr>
<tr>
<td>
<a id="gcov" name="gcov"></a><span class=
"term"><span><strong class=
"command">gcov</strong></span></span>
</td>
<td>
<p>
A coverage testing tool; it is used to analyze
programs to determine where optimizations will have
the most effect
</p>
</td>
</tr>
<tr>
<td>
<a id="libgcc" name="libgcc"></a><span class=
"term"><tt class="filename">libgcc</tt></span>
</td>
<td>
<p>
Contains run-time support for <span><strong class=
"command">gcc</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="libstdc" name="libstdc"></a><span class=
"term"><tt class="filename">libstdc++</tt></span>
</td>
<td>
<p>
The standard C++ library
</p>
</td>
</tr>
<tr>
<td>
<a id="libsupc" name="libsupc"></a><span class=
"term"><tt class="filename">libsupc++</tt></span>
</td>
<td>
<p>
Provides supporting routines for the C++
programming language
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-coreutils" name=
"ch-system-coreutils"></a>6.15.&nbsp;Coreutils-5.2.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Coreutils package contains utilities for showing and
setting the basic system characteristics.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.9 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">52.8 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Perl, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.15.1. Installation of Coreutils
</h3>
</div>
<p>
A known issue with the <span><strong class=
"command">uname</strong></span> program from this package is
that the <em class="parameter"><tt>-p</tt></em> switch always
returns <tt class="computeroutput">unknown</tt>. The
following patch fixes this behavior for Intel architectures:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../coreutils-5.2.1-uname-2.patch</kbd></pre>
<p>
Prevent Coreutils from installing binaries that will be
installed by other packages later:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../coreutils-5.2.1-suppress_uptime_kill_su-1.patch</kbd></pre>
<p>
Now prepare Coreutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">DEFAULT_POSIX2_VERSION=199209 ./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
The test suite of Coreutils makes several assumptions about
the presence of system users and groups that are not valid
within the minimal environment that exists at the moment.
Therefore, additional items need to be set up before running
the tests. Skip down to &ldquo;<span class="quote">Install
the package</span>&rdquo; if not running the test suite.
</p>
<p>
Create two dummy groups and a dummy user:
</p>
<pre class="userinput"><kbd class=
"command">echo "dummy1:x:1000:" &gt;&gt; /etc/group
echo "dummy2:x:1001:dummy" &gt;&gt; /etc/group
echo "dummy:x:1000:1000:::/bin/bash" &gt;&gt; /etc/passwd</kbd></pre>
<p>
Now the test suite is ready to be run. First, run the tests
that are meant to be run as user <span class=
"emphasis"><em>root</em></span>:
</p>
<pre class="userinput"><kbd class=
"command">make NON_ROOT_USERNAME=dummy check-root</kbd></pre>
<p>
Then run the remainder of the tests as the <span class=
"emphasis"><em>dummy</em></span> user:
</p>
<pre class="userinput"><kbd class=
"command">src/su dummy -c "make RUN_EXPENSIVE_TESTS=yes check"</kbd></pre>
<p>
When testing is complete, remove the dummy user and groups:
</p>
<pre class="userinput"><kbd class=
"command">sed -i '/dummy/d' /etc/passwd /etc/group</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Move programs to the locations specified by the FHS:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /usr/bin/{cat,chgrp,chmod,chown,cp,date,dd,df,echo} /bin
mv -v /usr/bin/{false,hostname,ln,ls,mkdir,mknod,mv,pwd,rm} /bin
mv -v /usr/bin/{rmdir,stty,sync,true,uname} /bin
mv -v /usr/bin/chroot /usr/sbin</kbd></pre>
<p>
Some of the scripts in the LFS-Bootscripts package depend on
<span><strong class="command">head</strong></span> and
<span><strong class="command">sleep</strong></span>. As
<tt class="filename">/usr</tt> may not be available during
the early stages of booting, those binaries need to be on the
root partition:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /usr/bin/{head,sleep} /bin</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-coreutils" name="contents-coreutils"></a>
<h3 class="sect2">
6.15.2. Contents of Coreutils
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">basename,
cat, chgrp, chmod, chown, chroot, cksum, comm, cp,
csplit, cut, date, dd, df, dir, dircolors, dirname, du,
echo, env, expand, expr, factor, false, fmt, fold,
groups, head, hostid, hostname, id, install, join, link,
ln, logname, ls, md5sum, mkdir, mkfifo, mknod, mv, nice,
nl, nohup, od, paste, pathchk, pinky, pr, printenv,
printf, ptx, pwd, readlink, rm, rmdir, seq, sha1sum,
shred, sleep, sort, split, stat, stty, sum, sync, tac,
tail, tee, test, touch, tr, true, tsort, tty, uname,
unexpand, uniq, unlink, users, vdir, wc, who, whoami, and
yes</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3495671" name="id3495671"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="basename" name="basename"></a><span class=
"term"><span><strong class=
"command">basename</strong></span></span>
</td>
<td>
<p>
Strips any path and a given suffix from a file name
</p>
</td>
</tr>
<tr>
<td>
<a id="cat" name="cat"></a><span class=
"term"><span><strong class=
"command">cat</strong></span></span>
</td>
<td>
<p>
Concatenates files to standard output
</p>
</td>
</tr>
<tr>
<td>
<a id="chgrp" name="chgrp"></a><span class=
"term"><span><strong class=
"command">chgrp</strong></span></span>
</td>
<td>
<p>
Changes the group ownership of files and
directories
</p>
</td>
</tr>
<tr>
<td>
<a id="chmod" name="chmod"></a><span class=
"term"><span><strong class=
"command">chmod</strong></span></span>
</td>
<td>
<p>
Changes the permissions of each file to the given
mode; the mode can be either a symbolic
representation of the changes to make or an octal
number representing the new permissions
</p>
</td>
</tr>
<tr>
<td>
<a id="chown" name="chown"></a><span class=
"term"><span><strong class=
"command">chown</strong></span></span>
</td>
<td>
<p>
Changes the user and/or group ownership of files
and directories
</p>
</td>
</tr>
<tr>
<td>
<a id="chroot" name="chroot"></a><span class=
"term"><span><strong class=
"command">chroot</strong></span></span>
</td>
<td>
<p>
Runs a command with the specified directory as the
<tt class="filename">/</tt> directory
</p>
</td>
</tr>
<tr>
<td>
<a id="cksum" name="cksum"></a><span class=
"term"><span><strong class=
"command">cksum</strong></span></span>
</td>
<td>
<p>
Prints the Cyclic Redundancy Check (CRC) checksum
and the byte counts of each specified file
</p>
</td>
</tr>
<tr>
<td>
<a id="comm" name="comm"></a><span class=
"term"><span><strong class=
"command">comm</strong></span></span>
</td>
<td>
<p>
Compares two sorted files, outputting in three
columns the lines that are unique and the lines
that are common
</p>
</td>
</tr>
<tr>
<td>
<a id="cp" name="cp"></a><span class=
"term"><span><strong class=
"command">cp</strong></span></span>
</td>
<td>
<p>
Copies files
</p>
</td>
</tr>
<tr>
<td>
<a id="csplit" name="csplit"></a><span class=
"term"><span><strong class=
"command">csplit</strong></span></span>
</td>
<td>
<p>
Splits a given file into several new files,
separating them according to given patterns or line
numbers and outputting the byte count of each new
file
</p>
</td>
</tr>
<tr>
<td>
<a id="cut" name="cut"></a><span class=
"term"><span><strong class=
"command">cut</strong></span></span>
</td>
<td>
<p>
Prints sections of lines, selecting the parts
according to given fields or positions
</p>
</td>
</tr>
<tr>
<td>
<a id="date" name="date"></a><span class=
"term"><span><strong class=
"command">date</strong></span></span>
</td>
<td>
<p>
Displays the current time in the given format, or
sets the system date
</p>
</td>
</tr>
<tr>
<td>
<a id="dd" name="dd"></a><span class=
"term"><span><strong class=
"command">dd</strong></span></span>
</td>
<td>
<p>
Copies a file using the given block size and count,
while optionally performing conversions on it
</p>
</td>
</tr>
<tr>
<td>
<a id="df" name="df"></a><span class=
"term"><span><strong class=
"command">df</strong></span></span>
</td>
<td>
<p>
Reports the amount of disk space available (and
used) on all mounted file systems, or only on the
file systems holding the selected files
</p>
</td>
</tr>
<tr>
<td>
<a id="dir" name="dir"></a><span class=
"term"><span><strong class=
"command">dir</strong></span></span>
</td>
<td>
<p>
Lists the contents of each given directory (the
same as the <span><strong class=
"command">ls</strong></span> command)
</p>
</td>
</tr>
<tr>
<td>
<a id="dircolors" name="dircolors"></a><span class=
"term"><span><strong class=
"command">dircolors</strong></span></span>
</td>
<td>
<p>
Outputs commands to set the <tt class=
"envar">LS_COLOR</tt> environment variable to
change the color scheme used by
<span><strong class="command">ls</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="dirname" name="dirname"></a><span class=
"term"><span><strong class=
"command">dirname</strong></span></span>
</td>
<td>
<p>
Strips the non-directory suffix from a file name
</p>
</td>
</tr>
<tr>
<td>
<a id="du" name="du"></a><span class=
"term"><span><strong class=
"command">du</strong></span></span>
</td>
<td>
<p>
Reports the amount of disk space used by the
current directory, by each of the given directories
(including all subdirectories) or by each of the
given files
</p>
</td>
</tr>
<tr>
<td>
<a id="echo" name="echo"></a><span class=
"term"><span><strong class=
"command">echo</strong></span></span>
</td>
<td>
<p>
Displays the given strings
</p>
</td>
</tr>
<tr>
<td>
<a id="env" name="env"></a><span class=
"term"><span><strong class=
"command">env</strong></span></span>
</td>
<td>
<p>
Runs a command in a modified environment
</p>
</td>
</tr>
<tr>
<td>
<a id="expand" name="expand"></a><span class=
"term"><span><strong class=
"command">expand</strong></span></span>
</td>
<td>
<p>
Converts tabs to spaces
</p>
</td>
</tr>
<tr>
<td>
<a id="expr" name="expr"></a><span class=
"term"><span><strong class=
"command">expr</strong></span></span>
</td>
<td>
<p>
Evaluates expressions
</p>
</td>
</tr>
<tr>
<td>
<a id="factor" name="factor"></a><span class=
"term"><span><strong class=
"command">factor</strong></span></span>
</td>
<td>
<p>
Prints the prime factors of all specified integer
numbers
</p>
</td>
</tr>
<tr>
<td>
<a id="false" name="false"></a><span class=
"term"><span><strong class=
"command">false</strong></span></span>
</td>
<td>
<p>
Does nothing, unsuccessfully; it always exits with
a status code indicating failure
</p>
</td>
</tr>
<tr>
<td>
<a id="fmt" name="fmt"></a><span class=
"term"><span><strong class=
"command">fmt</strong></span></span>
</td>
<td>
<p>
Reformats the paragraphs in the given files
</p>
</td>
</tr>
<tr>
<td>
<a id="fold" name="fold"></a><span class=
"term"><span><strong class=
"command">fold</strong></span></span>
</td>
<td>
<p>
Wraps the lines in the given files
</p>
</td>
</tr>
<tr>
<td>
<a id="groups" name="groups"></a><span class=
"term"><span><strong class=
"command">groups</strong></span></span>
</td>
<td>
<p>
Reports a user's group memberships
</p>
</td>
</tr>
<tr>
<td>
<a id="head" name="head"></a><span class=
"term"><span><strong class=
"command">head</strong></span></span>
</td>
<td>
<p>
Prints the first ten lines (or the given number of
lines) of each given file
</p>
</td>
</tr>
<tr>
<td>
<a id="hostid" name="hostid"></a><span class=
"term"><span><strong class=
"command">hostid</strong></span></span>
</td>
<td>
<p>
Reports the numeric identifier (in hexadecimal) of
the host
</p>
</td>
</tr>
<tr>
<td>
<a id="hostname" name="hostname"></a><span class=
"term"><span><strong class=
"command">hostname</strong></span></span>
</td>
<td>
<p>
Reports or sets the name of the host
</p>
</td>
</tr>
<tr>
<td>
<a id="id" name="id"></a><span class=
"term"><span><strong class=
"command">id</strong></span></span>
</td>
<td>
<p>
Reports the effective user ID, group ID, and group
memberships of the current user or specified user
</p>
</td>
</tr>
<tr>
<td>
<a id="install" name="install"></a><span class=
"term"><span><strong class=
"command">install</strong></span></span>
</td>
<td>
<p>
Copies files while setting their permission modes
and, if possible, their owner and group
</p>
</td>
</tr>
<tr>
<td>
<a id="join" name="join"></a><span class=
"term"><span><strong class=
"command">join</strong></span></span>
</td>
<td>
<p>
Joins the lines that have identical join fields
from two separate files
</p>
</td>
</tr>
<tr>
<td>
<a id="link" name="link"></a><span class=
"term"><span><strong class=
"command">link</strong></span></span>
</td>
<td>
<p>
Creates a hard link with the given name to a file
</p>
</td>
</tr>
<tr>
<td>
<a id="ln" name="ln"></a><span class=
"term"><span><strong class=
"command">ln</strong></span></span>
</td>
<td>
<p>
Makes hard links or soft (symbolic) links between
files
</p>
</td>
</tr>
<tr>
<td>
<a id="logname" name="logname"></a><span class=
"term"><span><strong class=
"command">logname</strong></span></span>
</td>
<td>
<p>
Reports the current user's login name
</p>
</td>
</tr>
<tr>
<td>
<a id="ls" name="ls"></a><span class=
"term"><span><strong class=
"command">ls</strong></span></span>
</td>
<td>
<p>
Lists the contents of each given directory
</p>
</td>
</tr>
<tr>
<td>
<a id="md5sum" name="md5sum"></a><span class=
"term"><span><strong class=
"command">md5sum</strong></span></span>
</td>
<td>
<p>
Reports or checks Message Digest 5 (MD5) checksums
</p>
</td>
</tr>
<tr>
<td>
<a id="mkdir" name="mkdir"></a><span class=
"term"><span><strong class=
"command">mkdir</strong></span></span>
</td>
<td>
<p>
Creates directories with the given names
</p>
</td>
</tr>
<tr>
<td>
<a id="mkfifo" name="mkfifo"></a><span class=
"term"><span><strong class=
"command">mkfifo</strong></span></span>
</td>
<td>
<p>
Creates First-In, First-Outs (FIFOs), a
&ldquo;<span class="quote">named pipe</span>&rdquo;
in UNIX parlance, with the given names
</p>
</td>
</tr>
<tr>
<td>
<a id="mknod" name="mknod"></a><span class=
"term"><span><strong class=
"command">mknod</strong></span></span>
</td>
<td>
<p>
Creates device nodes with the given names; a device
node is a character special file, a block special
file, or a FIFO
</p>
</td>
</tr>
<tr>
<td>
<a id="mv" name="mv"></a><span class=
"term"><span><strong class=
"command">mv</strong></span></span>
</td>
<td>
<p>
Moves or renames files or directories
</p>
</td>
</tr>
<tr>
<td>
<a id="nice" name="nice"></a><span class=
"term"><span><strong class=
"command">nice</strong></span></span>
</td>
<td>
<p>
Runs a program with modified scheduling priority
</p>
</td>
</tr>
<tr>
<td>
<a id="nl" name="nl"></a><span class=
"term"><span><strong class=
"command">nl</strong></span></span>
</td>
<td>
<p>
Numbers the lines from the given files
</p>
</td>
</tr>
<tr>
<td>
<a id="nohup" name="nohup"></a><span class=
"term"><span><strong class=
"command">nohup</strong></span></span>
</td>
<td>
<p>
Runs a command immune to hangups, with its output
redirected to a log file
</p>
</td>
</tr>
<tr>
<td>
<a id="od" name="od"></a><span class=
"term"><span><strong class=
"command">od</strong></span></span>
</td>
<td>
<p>
Dumps files in octal and other formats
</p>
</td>
</tr>
<tr>
<td>
<a id="paste" name="paste"></a><span class=
"term"><span><strong class=
"command">paste</strong></span></span>
</td>
<td>
<p>
Merges the given files, joining sequentially
corresponding lines side by side, separated by tab
characters
</p>
</td>
</tr>
<tr>
<td>
<a id="pathchk" name="pathchk"></a><span class=
"term"><span><strong class=
"command">pathchk</strong></span></span>
</td>
<td>
<p>
Checks if file names are valid or portable
</p>
</td>
</tr>
<tr>
<td>
<a id="pinky" name="pinky"></a><span class=
"term"><span><strong class=
"command">pinky</strong></span></span>
</td>
<td>
<p>
Is a lightweight finger client; it reports some
information about the given users
</p>
</td>
</tr>
<tr>
<td>
<a id="pr" name="pr"></a><span class=
"term"><span><strong class=
"command">pr</strong></span></span>
</td>
<td>
<p>
Paginates and columnates files for printing
</p>
</td>
</tr>
<tr>
<td>
<a id="printenv" name="printenv"></a><span class=
"term"><span><strong class=
"command">printenv</strong></span></span>
</td>
<td>
<p>
Prints the environment
</p>
</td>
</tr>
<tr>
<td>
<a id="printf" name="printf"></a><span class=
"term"><span><strong class=
"command">printf</strong></span></span>
</td>
<td>
<p>
Prints the given arguments according to the given
format, much like the C printf function
</p>
</td>
</tr>
<tr>
<td>
<a id="ptx" name="ptx"></a><span class=
"term"><span><strong class=
"command">ptx</strong></span></span>
</td>
<td>
<p>
Produces a permuted index from the contents of the
given files, with each keyword in its context
</p>
</td>
</tr>
<tr>
<td>
<a id="pwd" name="pwd"></a><span class=
"term"><span><strong class=
"command">pwd</strong></span></span>
</td>
<td>
<p>
Reports the name of the current working directory
</p>
</td>
</tr>
<tr>
<td>
<a id="readlink" name="readlink"></a><span class=
"term"><span><strong class=
"command">readlink</strong></span></span>
</td>
<td>
<p>
Reports the value of the given symbolic link
</p>
</td>
</tr>
<tr>
<td>
<a id="rm" name="rm"></a><span class=
"term"><span><strong class=
"command">rm</strong></span></span>
</td>
<td>
<p>
Removes files or directories
</p>
</td>
</tr>
<tr>
<td>
<a id="rmdir" name="rmdir"></a><span class=
"term"><span><strong class=
"command">rmdir</strong></span></span>
</td>
<td>
<p>
Removes directories if they are empty
</p>
</td>
</tr>
<tr>
<td>
<a id="seq" name="seq"></a><span class=
"term"><span><strong class=
"command">seq</strong></span></span>
</td>
<td>
<p>
Prints a sequence of numbers within a given range
and with a given increment
</p>
</td>
</tr>
<tr>
<td>
<a id="sha1sum" name="sha1sum"></a><span class=
"term"><span><strong class=
"command">sha1sum</strong></span></span>
</td>
<td>
<p>
Prints or checks 160-bit Secure Hash Algorithm 1
(SHA1) checksums
</p>
</td>
</tr>
<tr>
<td>
<a id="shred" name="shred"></a><span class=
"term"><span><strong class=
"command">shred</strong></span></span>
</td>
<td>
<p>
Overwrites the given files repeatedly with complex
patterns, making it difficult to recover the data
</p>
</td>
</tr>
<tr>
<td>
<a id="sleep" name="sleep"></a><span class=
"term"><span><strong class=
"command">sleep</strong></span></span>
</td>
<td>
<p>
Pauses for the given amount of time
</p>
</td>
</tr>
<tr>
<td>
<a id="sort" name="sort"></a><span class=
"term"><span><strong class=
"command">sort</strong></span></span>
</td>
<td>
<p>
Sorts the lines from the given files
</p>
</td>
</tr>
<tr>
<td>
<a id="split" name="split"></a><span class=
"term"><span><strong class=
"command">split</strong></span></span>
</td>
<td>
<p>
Splits the given file into pieces, by size or by
number of lines
</p>
</td>
</tr>
<tr>
<td>
<a id="stat" name="stat"></a><span class=
"term"><span><strong class=
"command">stat</strong></span></span>
</td>
<td>
<p>
Displays file or filesystem status
</p>
</td>
</tr>
<tr>
<td>
<a id="stty" name="stty"></a><span class=
"term"><span><strong class=
"command">stty</strong></span></span>
</td>
<td>
<p>
Sets or reports terminal line settings
</p>
</td>
</tr>
<tr>
<td>
<a id="sum" name="sum"></a><span class=
"term"><span><strong class=
"command">sum</strong></span></span>
</td>
<td>
<p>
Prints checksum and block counts for each given
file
</p>
</td>
</tr>
<tr>
<td>
<a id="sync" name="sync"></a><span class=
"term"><span><strong class=
"command">sync</strong></span></span>
</td>
<td>
<p>
Flushes file system buffers; it forces changed
blocks to disk and updates the super block
</p>
</td>
</tr>
<tr>
<td>
<a id="tac" name="tac"></a><span class=
"term"><span><strong class=
"command">tac</strong></span></span>
</td>
<td>
<p>
Concatenates the given files in reverse
</p>
</td>
</tr>
<tr>
<td>
<a id="tail" name="tail"></a><span class=
"term"><span><strong class=
"command">tail</strong></span></span>
</td>
<td>
<p>
Prints the last ten lines (or the given number of
lines) of each given file
</p>
</td>
</tr>
<tr>
<td>
<a id="tee" name="tee"></a><span class=
"term"><span><strong class=
"command">tee</strong></span></span>
</td>
<td>
<p>
Reads from standard input while writing both to
standard output and to the given files
</p>
</td>
</tr>
<tr>
<td>
<a id="test" name="test"></a><span class=
"term"><span><strong class=
"command">test</strong></span></span>
</td>
<td>
<p>
Compares values and checks file types
</p>
</td>
</tr>
<tr>
<td>
<a id="touch" name="touch"></a><span class=
"term"><span><strong class=
"command">touch</strong></span></span>
</td>
<td>
<p>
Changes file timestamps, setting the access and
modification times of the given files to the
current time; files that do not exist are created
with zero length
</p>
</td>
</tr>
<tr>
<td>
<a id="tr" name="tr"></a><span class=
"term"><span><strong class=
"command">tr</strong></span></span>
</td>
<td>
<p>
Translates, squeezes, and deletes the given
characters from standard input
</p>
</td>
</tr>
<tr>
<td>
<a id="true" name="true"></a><span class=
"term"><span><strong class=
"command">true</strong></span></span>
</td>
<td>
<p>
Does nothing, successfully; it always exits with a
status code indicating success
</p>
</td>
</tr>
<tr>
<td>
<a id="tsort" name="tsort"></a><span class=
"term"><span><strong class=
"command">tsort</strong></span></span>
</td>
<td>
<p>
Performs a topological sort; it writes a completely
ordered list according to the partial ordering in a
given file
</p>
</td>
</tr>
<tr>
<td>
<a id="tty" name="tty"></a><span class=
"term"><span><strong class=
"command">tty</strong></span></span>
</td>
<td>
<p>
Reports the file name of the terminal connected to
standard input
</p>
</td>
</tr>
<tr>
<td>
<a id="uname" name="uname"></a><span class=
"term"><span><strong class=
"command">uname</strong></span></span>
</td>
<td>
<p>
Reports system information
</p>
</td>
</tr>
<tr>
<td>
<a id="unexpand" name="unexpand"></a><span class=
"term"><span><strong class=
"command">unexpand</strong></span></span>
</td>
<td>
<p>
Converts spaces to tabs
</p>
</td>
</tr>
<tr>
<td>
<a id="uniq" name="uniq"></a><span class=
"term"><span><strong class=
"command">uniq</strong></span></span>
</td>
<td>
<p>
Discards all but one of successive identical lines
</p>
</td>
</tr>
<tr>
<td>
<a id="unlink" name="unlink"></a><span class=
"term"><span><strong class=
"command">unlink</strong></span></span>
</td>
<td>
<p>
Removes the given file
</p>
</td>
</tr>
<tr>
<td>
<a id="users" name="users"></a><span class=
"term"><span><strong class=
"command">users</strong></span></span>
</td>
<td>
<p>
Reports the names of the users currently logged on
</p>
</td>
</tr>
<tr>
<td>
<a id="vdir" name="vdir"></a><span class=
"term"><span><strong class=
"command">vdir</strong></span></span>
</td>
<td>
<p>
Is the same as <span><strong class="command">ls
-l</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="wc" name="wc"></a><span class=
"term"><span><strong class=
"command">wc</strong></span></span>
</td>
<td>
<p>
Reports the number of lines, words, and bytes for
each given file, as well as a total line when more
than one file is given
</p>
</td>
</tr>
<tr>
<td>
<a id="who" name="who"></a><span class=
"term"><span><strong class=
"command">who</strong></span></span>
</td>
<td>
<p>
Reports who is logged on
</p>
</td>
</tr>
<tr>
<td>
<a id="whoami" name="whoami"></a><span class=
"term"><span><strong class=
"command">whoami</strong></span></span>
</td>
<td>
<p>
Reports the user name associated with the current
effective user ID
</p>
</td>
</tr>
<tr>
<td>
<a id="yes" name="yes"></a><span class=
"term"><span><strong class=
"command">yes</strong></span></span>
</td>
<td>
<p>
Repeatedly outputs &ldquo;<span class=
"quote">y</span>&rdquo; or a given string until
killed
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-zlib" name=
"ch-system-zlib"></a>6.16.&nbsp;Zlib-1.2.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Zlib package contains compression and decompression
routines used by some programs.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">3.1 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Binutils,
Coreutils, GCC, Glibc, Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.16.1. Installation of Zlib
</h3>
</div>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
Zlib is known to build its shared library incorrectly if
<tt class="envar">CFLAGS</tt> is specified in the
environment. If using a specified <tt class=
"envar">CFLAGS</tt> variable, be sure to add the
<em class="parameter"><tt>-fPIC</tt></em> directive to
the <tt class="envar">CFLAGS</tt> variable for the
duration of the configure command below, then remove it
afterwards.
</p>
</div>
</div>
<p>
Prepare Zlib for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --shared --libdir=/lib</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the shared library:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
The previous command installed a <tt class=
"filename">.so</tt> file in <tt class="filename">/lib</tt>.
We will remove it and relink it into <tt class=
"filename">/usr/lib</tt>:
</p>
<pre class="userinput"><kbd class="command">rm -v /lib/libz.so
ln -sfv ../../lib/libz.so.1.2.3 /usr/lib/libz.so</kbd></pre>
<p>
Build the static library:
</p>
<pre class="userinput"><kbd class="command">make clean
./configure --prefix=/usr
make</kbd></pre>
<p>
To test the results again, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the static library:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Fix the permissions on the static library:
</p>
<pre class="userinput"><kbd class=
"command">chmod -v 644 /usr/lib/libz.a</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-zlib" name="contents-zlib"></a>
<h3 class="sect2">
6.16.2. Contents of Zlib
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libz.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3497754" name="id3497754"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="libz" name="libz"></a><span class=
"term"><tt class="filename">libz</tt></span>
</td>
<td>
<p>
Contains compression and decompression functions
used by some programs
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-mktemp" name=
"ch-system-mktemp"></a>6.17.&nbsp;Mktemp-1.5
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Mktemp package contains programs used to create secure
temporary files in shell scripts.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">436 KB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Coreutils, Make,
and Patch</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.17.1. Installation of Mktemp
</h3>
</div>
<p>
Many scripts still use the deprecated <span><strong class=
"command">tempfile</strong></span> program, which has
functionality similar to <span><strong class=
"command">mktemp</strong></span>. Patch Mktemp to include a
<span><strong class="command">tempfile</strong></span>
wrapper:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../mktemp-1.5-add_tempfile-2.patch</kbd></pre>
<p>
Prepare Mktemp for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --with-libc</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-libc</tt></em></span>
</dt>
<dd>
<p>
This causes the <span><strong class=
"command">mktemp</strong></span> program to use the
<span class="emphasis"><em>mkstemp</em></span> and
<span class="emphasis"><em>mkdtemp</em></span>
functions from the system C library.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class="command">make install
make install-tempfile</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-mktemp" name="contents-mktemp"></a>
<h3 class="sect2">
6.17.2. Contents of Mktemp
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">mktemp and
tempfile</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3497943" name="id3497943"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="mktemp" name="mktemp"></a><span class=
"term"><span><strong class=
"command">mktemp</strong></span></span>
</td>
<td>
<p>
Creates temporary files in a secure manner; it is
used in scripts
</p>
</td>
</tr>
<tr>
<td>
<a id="tempfile" name="tempfile"></a><span class=
"term"><span><strong class=
"command">tempfile</strong></span></span>
</td>
<td>
<p>
Creates temporary files in a less secure manner
than <span><strong class=
"command">mktemp</strong></span>; it is installed
for backwards-compatibility
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-iana-etc" name=
"ch-system-iana-etc"></a>6.18.&nbsp;Iana-Etc-1.04
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Iana-Etc package provides data for network services and
protocols.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">1.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.18.1. Installation of Iana-Etc
</h3>
</div>
<p>
The following command converts the raw data provided by IANA
into the correct formats for the <tt class=
"filename">/etc/protocols</tt> and <tt class=
"filename">/etc/services</tt> data files:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-iana-etc" name="contents-iana-etc"></a>
<h3 class="sect2">
6.18.2. Contents of Iana-Etc
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
files:</span></strong> <span class="seg">/etc/protocols
and /etc/services</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3498026" name="id3498026"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="protocols" name="protocols"></a><span class=
"term"><tt class=
"filename">/etc/protocols</tt></span>
</td>
<td>
<p>
Describes the various DARPA Internet protocols that
are available from the TCP/IP subsystem
</p>
</td>
</tr>
<tr>
<td>
<a id="services" name="services"></a><span class=
"term"><tt class="filename">/etc/services</tt></span>
</td>
<td>
<p>
Provides a mapping between friendly textual names
for internet services, and their underlying
assigned port numbers and protocol types
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-findutils" name=
"ch-system-findutils"></a>6.19.&nbsp;Findutils-4.2.23
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Findutils package contains programs to find files. These
programs are provided to recursively search through a
directory tree and to create, maintain, and search a database
(often faster than the recursive find, but unreliable if the
database has not been recently updated).
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">9.4 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.19.1. Installation of Findutils
</h3>
</div>
<p>
Prepare Findutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --libexecdir=/usr/lib/locate \
--localstatedir=/var/lib/locate</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--localstatedir</tt></em></span>
</dt>
<dd>
<p>
This option changes the location of the
<span><strong class="command">locate</strong></span>
database to be in <tt class=
"filename">/var/lib/locate</tt>, which is
FHS-compliant.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-findutils" name="contents-findutils"></a>
<h3 class="sect2">
6.19.2. Contents of Findutils
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">bigram, code,
find, frcode, locate, updatedb, and xargs</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3498090" name="id3498090"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="bigram" name="bigram"></a><span class=
"term"><span><strong class=
"command">bigram</strong></span></span>
</td>
<td>
<p>
Was formerly used to produce <span><strong class=
"command">locate</strong></span> databases
</p>
</td>
</tr>
<tr>
<td>
<a id="code" name="code"></a><span class=
"term"><span><strong class=
"command">code</strong></span></span>
</td>
<td>
<p>
Was formerly used to produce <span><strong class=
"command">locate</strong></span> databases; it is
the ancestor of <span><strong class=
"command">frcode</strong></span>.
</p>
</td>
</tr>
<tr>
<td>
<a id="find" name="find"></a><span class=
"term"><span><strong class=
"command">find</strong></span></span>
</td>
<td>
<p>
Searches given directory trees for files matching
the specified criteria
</p>
</td>
</tr>
<tr>
<td>
<a id="frcode" name="frcode"></a><span class=
"term"><span><strong class=
"command">frcode</strong></span></span>
</td>
<td>
<p>
Is called by <span><strong class=
"command">updatedb</strong></span> to compress the
list of file names; it uses front-compression,
reducing the database size by a factor of four to
five.
</p>
</td>
</tr>
<tr>
<td>
<a id="locate" name="locate"></a><span class=
"term"><span><strong class=
"command">locate</strong></span></span>
</td>
<td>
<p>
Searches through a database of file names and
reports the names that contain a given string or
match a given pattern
</p>
</td>
</tr>
<tr>
<td>
<a id="updatedb" name="updatedb"></a><span class=
"term"><span><strong class=
"command">updatedb</strong></span></span>
</td>
<td>
<p>
Updates the <span><strong class=
"command">locate</strong></span> database; it scans
the entire file system (including other file
systems that are currently mounted, unless told not
to) and puts every file name it finds into the
database
</p>
</td>
</tr>
<tr>
<td>
<a id="xargs" name="xargs"></a><span class=
"term"><span><strong class=
"command">xargs</strong></span></span>
</td>
<td>
<p>
Can be used to apply a given command to a list of
files
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-gawk" name=
"ch-system-gawk"></a>6.20.&nbsp;Gawk-3.1.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Gawk package contains programs for manipulating text
files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">16.4 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.20.1. Installation of Gawk
</h3>
</div>
<p>
Prepare Gawk for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --libexecdir=/usr/lib</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-gawk" name="contents-gawk"></a>
<h3 class="sect2">
6.20.2. Contents of Gawk
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">awk (link to
gawk), gawk, gawk-3.1.4, grcat, igawk, pgawk,
pgawk-3.1.4, and pwcat</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3498500" name="id3498500"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="awk" name="awk"></a><span class=
"term"><span><strong class=
"command">awk</strong></span></span>
</td>
<td>
<p>
A link to <span><strong class=
"command">gawk</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="gawk" name="gawk"></a><span class=
"term"><span><strong class=
"command">gawk</strong></span></span>
</td>
<td>
<p>
A program for manipulating text files; it is the
GNU implementation of <span><strong class=
"command">awk</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="gawk-version" name=
"gawk-version"></a><span class=
"term"><span><strong class=
"command">gawk-3.1.4</strong></span></span>
</td>
<td>
<p>
A hard link to <span><strong class=
"command">gawk</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="grcat" name="grcat"></a><span class=
"term"><span><strong class=
"command">grcat</strong></span></span>
</td>
<td>
<p>
Dumps the group database <tt class=
"filename">/etc/group</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="igawk" name="igawk"></a><span class=
"term"><span><strong class=
"command">igawk</strong></span></span>
</td>
<td>
<p>
Gives <span><strong class=
"command">gawk</strong></span> the ability to
include files
</p>
</td>
</tr>
<tr>
<td>
<a id="pgawk" name="pgawk"></a><span class=
"term"><span><strong class=
"command">pgawk</strong></span></span>
</td>
<td>
<p>
The profiling version of <span><strong class=
"command">gawk</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="pgawk-version" name=
"pgawk-version"></a><span class=
"term"><span><strong class=
"command">pgawk-3.1.4</strong></span></span>
</td>
<td>
<p>
Hard link to <span><strong class=
"command">pgawk</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="pwcat" name="pwcat"></a><span class=
"term"><span><strong class=
"command">pwcat</strong></span></span>
</td>
<td>
<p>
Dumps the password database <tt class=
"filename">/etc/passwd</tt>
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-ncurses" name=
"ch-system-ncurses"></a>6.21.&nbsp;Ncurses-5.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Ncurses package contains libraries for
terminal-independent handling of character screens.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.6 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">18.6 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.21.1. Installation of Ncurses
</h3>
</div>
<p>
Prepare Ncurses for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --with-shared --without-debug</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Give the Ncurses libraries execute permissions:
</p>
<pre class="userinput"><kbd class=
"command">chmod -v 755 /usr/lib/*.5.4</kbd></pre>
<p>
Fix a library that should not be executable:
</p>
<pre class="userinput"><kbd class=
"command">chmod -v 644 /usr/lib/libncurses++.a</kbd></pre>
<p>
Move the libraries to the <tt class="filename">/lib</tt>
directory, where they are expected to reside:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /usr/lib/libncurses.so.5* /lib</kbd></pre>
<p>
Because the libraries have been moved, a few symlinks point
to non-existent files. Recreate those symlinks:
</p>
<pre class="userinput"><kbd class=
"command">ln -sfv ../../lib/libncurses.so.5 /usr/lib/libncurses.so
ln -sfv libncurses.so /usr/lib/libcurses.so</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-ncurses" name="contents-ncurses"></a>
<h3 class="sect2">
6.21.2. Contents of Ncurses
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">captoinfo
(link to tic), clear, infocmp, infotocap (link to tic),
reset (link to tset), tack, tic, toe, tput, and
tset</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libcurses.[a,so] (link to libncurses.[a,so]),
libform.[a,so], libmenu.[a,so], libncurses++.a,
libncurses.[a,so], and libpanel.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3498827" name="id3498827"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="captoinfo" name="captoinfo"></a><span class=
"term"><span><strong class=
"command">captoinfo</strong></span></span>
</td>
<td>
<p>
Converts a termcap description into a terminfo
description
</p>
</td>
</tr>
<tr>
<td>
<a id="clear" name="clear"></a><span class=
"term"><span><strong class=
"command">clear</strong></span></span>
</td>
<td>
<p>
Clears the screen, if possible
</p>
</td>
</tr>
<tr>
<td>
<a id="infocmp" name="infocmp"></a><span class=
"term"><span><strong class=
"command">infocmp</strong></span></span>
</td>
<td>
<p>
Compares or prints out terminfo descriptions
</p>
</td>
</tr>
<tr>
<td>
<a id="infotocap" name="infotocap"></a><span class=
"term"><span><strong class=
"command">infotocap</strong></span></span>
</td>
<td>
<p>
Converts a terminfo description into a termcap
description
</p>
</td>
</tr>
<tr>
<td>
<a id="reset" name="reset"></a><span class=
"term"><span><strong class=
"command">reset</strong></span></span>
</td>
<td>
<p>
Reinitializes a terminal to its default values
</p>
</td>
</tr>
<tr>
<td>
<a id="tack" name="tack"></a><span class=
"term"><span><strong class=
"command">tack</strong></span></span>
</td>
<td>
<p>
The terminfo action checker; it is mainly used to
test the accuracy of an entry in the terminfo
database
</p>
</td>
</tr>
<tr>
<td>
<a id="tic" name="tic"></a><span class=
"term"><span><strong class=
"command">tic</strong></span></span>
</td>
<td>
<p>
The terminfo entry-description compiler that
translates a terminfo file from source format into
the binary format needed for the ncurses library
routines. A terminfo file contains information on
the capabilities of a certain terminal
</p>
</td>
</tr>
<tr>
<td>
<a id="toe" name="toe"></a><span class=
"term"><span><strong class=
"command">toe</strong></span></span>
</td>
<td>
<p>
Lists all available terminal types, giving the
primary name and description for each
</p>
</td>
</tr>
<tr>
<td>
<a id="tput" name="tput"></a><span class=
"term"><span><strong class=
"command">tput</strong></span></span>
</td>
<td>
<p>
Makes the values of terminal-dependent capabilities
available to the shell; it can also be used to
reset or initialize a terminal or report its long
name
</p>
</td>
</tr>
<tr>
<td>
<a id="tset" name="tset"></a><span class=
"term"><span><strong class=
"command">tset</strong></span></span>
</td>
<td>
<p>
Can be used to initialize terminals
</p>
</td>
</tr>
<tr>
<td>
<a id="libcurses" name="libcurses"></a><span class=
"term"><tt class="filename">libcurses</tt></span>
</td>
<td>
<p>
A link to <tt class="filename">libncurses</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="libncurses" name="libncurses"></a><span class=
"term"><tt class="filename">libncurses</tt></span>
</td>
<td>
<p>
Contains functions to display text in many complex
ways on a terminal screen; a good example of the
use of these functions is the menu displayed during
the kernel's <span><strong class="command">make
menuconfig</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="libform" name="libform"></a><span class=
"term"><tt class="filename">libform</tt></span>
</td>
<td>
<p>
Contains functions to implement forms
</p>
</td>
</tr>
<tr>
<td>
<a id="libmenu" name="libmenu"></a><span class=
"term"><tt class="filename">libmenu</tt></span>
</td>
<td>
<p>
Contains functions to implement menus
</p>
</td>
</tr>
<tr>
<td>
<a id="libpanel" name="libpanel"></a><span class=
"term"><tt class="filename">libpanel</tt></span>
</td>
<td>
<p>
Contains functions to implement panels
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-readline" name=
"ch-system-readline"></a>6.22.&nbsp;Readline-5.0
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Readline package is a set of libraries that offers
command-line editing and history capabilities.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.11 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">9.1 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make,
Ncurses, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.22.1. Installation of Readline
</h3>
</div>
<p>
The following patch includes a fix for a problem where
Readline sometimes only shows 33 characters on a line and
then wraps to the next line. It also includes other fixes
recommended by the Readline author.
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../readline-5.0-fixes-1.patch</kbd></pre>
<p>
Prepare Readline for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --libdir=/lib</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class=
"command">make SHLIB_XLDFLAGS=-lncurses</kbd></pre>
<p>
The meaning of the make option:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>SHLIB_XLDFLAGS=-lncurses</tt></em></span>
</dt>
<dd>
<p>
This option forces Readline to link against the
<tt class="filename">libncurses</tt> library.
</p>
</dd>
</dl>
</div>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Give Readline's dynamic libraries more appropriate
permissions:
</p>
<pre class="userinput"><kbd class=
"command">chmod -v 755 /lib/lib{readline,history}.so*</kbd></pre>
<p>
Now move the static libraries to a more appropriate location:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /lib/lib{readline,history}.a /usr/lib</kbd></pre>
<p>
Next, remove the <tt class="filename">.so</tt> files in
<tt class="filename">/lib</tt> and relink them into
<tt class="filename">/usr/lib</tt>.
</p>
<pre class="userinput"><kbd class=
"command">rm -v /lib/lib{readline,history}.so
ln -sfv ../../lib/libreadline.so.5 /usr/lib/libreadline.so
ln -sfv ../../lib/libhistory.so.5 /usr/lib/libhistory.so</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-readline" name="contents-readline"></a>
<h3 class="sect2">
6.22.2. Contents of Readline
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libhistory.[a,so], and libreadline.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3499373" name="id3499373"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="libhistory" name="libhistory"></a><span class=
"term"><tt class="filename">libhistory</tt></span>
</td>
<td>
<p>
Provides a consistent user interface for recalling
lines of history
</p>
</td>
</tr>
<tr>
<td>
<a id="libreadline" name=
"libreadline"></a><span class="term"><tt class=
"filename">libreadline</tt></span>
</td>
<td>
<p>
Aids in the consistency of user interface across
discrete programs that need to provide a command
line interface
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-vim" name=
"ch-system-vim"></a>6.23.&nbsp;Vim-6.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Vim package contains a powerful text editor.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.4 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">38.0 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, Ncurses,
and Sed</span>
</div>
</div>
</div>
<div class="tip">
<div class="admonhead">
<h3 class="admontitle">
Alternatives to Vim
</h3>
</div>
<div class="admonbody">
<p>
If you prefer another editor&mdash;such as Emacs, Joe, or
Nano&mdash;please refer to <a href=
"http://www.linuxfromscratch.org/blfs/view/svn/postlfs/editors.html">
<i>http://www.linuxfromscratch.org/blfs/view/svn/postlfs/editors.html</i></a>
for suggested installation instructions.
</p>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.23.1. Installation of Vim
</h3>
</div>
<p>
First, unpack both <tt class="filename">vim-6.3.tar.bz2</tt>
and (optionally) <tt class=
"filename">vim-6.3-lang.tar.gz</tt> archives into the same
directory. Then, change the default location of the
<tt class="filename">vimrc</tt> configuration file to
<tt class="filename">/etc</tt>:
</p>
<pre class="userinput"><kbd class=
"command">echo '#define SYS_VIMRC_FILE "/etc/vimrc"' &gt;&gt; src/feature.h</kbd></pre>
<p>
Vim has two known security vulnerabilities that have already
been addressed upstream. The following patch fixes the
problems:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../vim-6.3-security_fix-2.patch</kbd></pre>
<p>
Now prepare Vim for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --enable-multibyte</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-multibyte</tt></em></span>
</dt>
<dd>
<p>
This optional but highly recommended switch enables
support for editing files in multibyte character
encodings. This is needed if using a locale with a
multibyte character set. This switch is also helpful to
be able to edit text files initially created in Linux
distributions like Fedora Core that use UTF-8 as a
default character set.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make test</tt></strong>. However, this test
suite outputs a lot of binary data to the screen, which can
cause issues with the settings of the current terminal. This
can be resolved by redirecting the output to a log file.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Many users are used to using <span><strong class=
"command">vi</strong></span> instead of <span><strong class=
"command">vim</strong></span>. To allow execution of
<span><strong class="command">vim</strong></span> when users
habitually enter <span><strong class=
"command">vi</strong></span>, create a symlink:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv vim /usr/bin/vi</kbd></pre>
<p>
If an X Window System is going to be installed on the LFS
system, it may be necessary to recompile Vim after installing
X. Vim comes with a GUI version of the editor that requires X
and some additional libraries to be installed. For more
information on this process, refer to the Vim documentation
and the Vim installation page in the BLFS book at <a href=
"http://www.linuxfromscratch.org/blfs/view/svn/postlfs/editors.html#postlfs-editors-vim">
<i>http://www.linuxfromscratch.org/blfs/view/svn/postlfs/editors.html#postlfs-editors-vim</i></a>.
</p>
</div>
<div class="configuration" lang="en" xml:lang="en">
<div class="titlepage">
<a id="conf-vim" name="conf-vim"></a>
<h3 class="sect2">
6.23.2. Configuring Vim
</h3>
</div>
<p>
By default, <span><strong class="command">vim</strong></span>
runs in vi-incompatible mode. This may be new to users who
have used other editors in the past. The &ldquo;<span class=
"quote">nocompatible</span>&rdquo; setting is included below
to highlight the fact that a new behavior is being used. It
also reminds those who would change to &ldquo;<span class=
"quote">compatible</span>&rdquo; mode that it should be the
first setting in the configuration file. This is necessary
because it changes other settings, and overrides must come
after this setting. Create a default <span><strong class=
"command">vim</strong></span> configuration file by running
the following:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/vimrc &lt;&lt; "EOF"
<tt class="literal">" Begin /etc/vimrc
set nocompatible
set backspace=2
syntax on
if (&amp;term == "iterm") || (&amp;term == "putty")
set background=dark
endif
" End /etc/vimrc</tt>
EOF</kbd></pre>
<p>
The <em class="parameter"><tt>set nocompatible</tt></em>
makes <span><strong class="command">vim</strong></span>
behave in a more useful way (the default) than the
vi-compatible manner. Remove the &ldquo;<span class=
"quote">no</span>&rdquo; to keep the old <span><strong class=
"command">vi</strong></span> behavior. The <em class=
"parameter"><tt>set backspace=2</tt></em> allows backspacing
over line breaks, autoindents, and the start of insert. The
<em class="parameter"><tt>syntax on</tt></em> enables vim's
syntax highlighting. Finally, the <span class=
"emphasis"><em>if</em></span> statement with the <em class=
"parameter"><tt>set background=dark</tt></em> corrects
<span><strong class="command">vim</strong></span>'s guess
about the background color of some terminal emulators. This
gives the highlighting a better color scheme for use on the
black background of these programs.
</p>
<p>
Documentation for other available options can be obtained by
running the following command:
</p>
<pre class="userinput"><kbd class=
"command">vim -c ':options'</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-vim" name="contents-vim"></a>
<h3 class="sect2">
6.23.3. Contents of Vim
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class=
"seg">efm_filter.pl, efm_perl.pl, ex (link to vim),
less.sh, mve.awk, pltags.pl, ref, rview (link to vim),
rvim (link to vim), shtags.pl, tcltags, vi (link to vim),
view (link to vim), vim, vim132, vim2html.pl, vimdiff
(link to vim), vimm, vimspell.sh, vimtutor, and
xxd</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3499721" name="id3499721"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="efm_filter.pl" name=
"efm_filter.pl"></a><span class=
"term"><span><strong class=
"command">efm_filter.pl</strong></span></span>
</td>
<td>
<p>
A filter for creating an error file that can be
read by <span><strong class=
"command">vim</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="efm_perl.pl" name=
"efm_perl.pl"></a><span class=
"term"><span><strong class=
"command">efm_perl.pl</strong></span></span>
</td>
<td>
<p>
Reformats the error messages of the Perl
interpreter for use with the &ldquo;<span class=
"quote">quickfix</span>&rdquo; mode of
<span><strong class="command">vim</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="ex" name="ex"></a><span class=
"term"><span><strong class=
"command">ex</strong></span></span>
</td>
<td>
<p>
Starts <span><strong class=
"command">vim</strong></span> in ex mode
</p>
</td>
</tr>
<tr>
<td>
<a id="less.sh" name="less.sh"></a><span class=
"term"><span><strong class=
"command">less.sh</strong></span></span>
</td>
<td>
<p>
A script that starts <span><strong class=
"command">vim</strong></span> with less.vim
</p>
</td>
</tr>
<tr>
<td>
<a id="mve.awk" name="mve.awk"></a><span class=
"term"><span><strong class=
"command">mve.awk</strong></span></span>
</td>
<td>
<p>
Processes <span><strong class=
"command">vim</strong></span> errors
</p>
</td>
</tr>
<tr>
<td>
<a id="pltags.pl" name="pltags.pl"></a><span class=
"term"><span><strong class=
"command">pltags.pl</strong></span></span>
</td>
<td>
<p>
Creates a tags file for Perl code for use by
<span><strong class="command">vim</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="ref" name="ref"></a><span class=
"term"><span><strong class=
"command">ref</strong></span></span>
</td>
<td>
<p>
Checks the spelling of arguments
</p>
</td>
</tr>
<tr>
<td>
<a id="rview" name="rview"></a><span class=
"term"><span><strong class=
"command">rview</strong></span></span>
</td>
<td>
<p>
Is a restricted version of <span><strong class=
"command">view</strong></span>; no shell commands
can be started and <span><strong class=
"command">view</strong></span> cannot be suspended
</p>
</td>
</tr>
<tr>
<td>
<a id="rvim" name="rvim"></a><span class=
"term"><span><strong class=
"command">rvim</strong></span></span>
</td>
<td>
<p>
Is a restricted version of <span><strong class=
"command">vim</strong></span>; no shell commands
can be started and <span><strong class=
"command">vim</strong></span> cannot be suspended
</p>
</td>
</tr>
<tr>
<td>
<a id="shtags.pl" name="shtags.pl"></a><span class=
"term"><span><strong class=
"command">shtags.pl</strong></span></span>
</td>
<td>
<p>
Generates a tags file for Perl scripts
</p>
</td>
</tr>
<tr>
<td>
<a id="tcltags" name="tcltags"></a><span class=
"term"><span><strong class=
"command">tcltags</strong></span></span>
</td>
<td>
<p>
Generates a tags file for TCL code
</p>
</td>
</tr>
<tr>
<td>
<a id="view" name="view"></a><span class=
"term"><span><strong class=
"command">view</strong></span></span>
</td>
<td>
<p>
Starts <span><strong class=
"command">vim</strong></span> in read-only mode
</p>
</td>
</tr>
<tr>
<td>
<a id="vi" name="vi"></a><span class=
"term"><span><strong class=
"command">vi</strong></span></span>
</td>
<td>
<p>
Is the editor
</p>
</td>
</tr>
<tr>
<td>
<a id="vim" name="vim"></a><span class=
"term"><span><strong class=
"command">vim</strong></span></span>
</td>
<td>
<p>
Is the editor
</p>
</td>
</tr>
<tr>
<td>
<a id="vim132" name="vim132"></a><span class=
"term"><span><strong class=
"command">vim132</strong></span></span>
</td>
<td>
<p>
Starts <span><strong class=
"command">vim</strong></span> with the terminal in
132-column mode
</p>
</td>
</tr>
<tr>
<td>
<a id="vim2html.pl" name=
"vim2html.pl"></a><span class=
"term"><span><strong class=
"command">vim2html.pl</strong></span></span>
</td>
<td>
<p>
Converts Vim documentation to HypterText Markup
Language (HTML)
</p>
</td>
</tr>
<tr>
<td>
<a id="vimdiff" name="vimdiff"></a><span class=
"term"><span><strong class=
"command">vimdiff</strong></span></span>
</td>
<td>
<p>
Edits two or three versions of a file with
<span><strong class="command">vim</strong></span>
and show differences
</p>
</td>
</tr>
<tr>
<td>
<a id="vimm" name="vimm"></a><span class=
"term"><span><strong class=
"command">vimm</strong></span></span>
</td>
<td>
<p>
Enables the DEC locator input model on a remote
terminal
</p>
</td>
</tr>
<tr>
<td>
<a id="vimspell.sh" name=
"vimspell.sh"></a><span class=
"term"><span><strong class=
"command">vimspell.sh</strong></span></span>
</td>
<td>
<p>
Spell checks a file and generates the syntax
statements necessary to highlight in
<span><strong class="command">vim</strong></span>.
This script requires the old Unix
<span><strong class="command">spell</strong></span>
command, which is provided neither in LFS nor in
BLFS
</p>
</td>
</tr>
<tr>
<td>
<a id="vimtutor" name="vimtutor"></a><span class=
"term"><span><strong class=
"command">vimtutor</strong></span></span>
</td>
<td>
<p>
Teaches the basic keys and commands of
<span><strong class="command">vim</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="xxd" name="xxd"></a><span class=
"term"><span><strong class=
"command">xxd</strong></span></span>
</td>
<td>
<p>
Creates a hex dump of the given file; it can also
do the reverse, so it can be used for binary
patching
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-m4" name=
"ch-system-m4"></a>6.24.&nbsp;M4-1.4.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The M4 package contains a macro processor.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">2.8 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Perl, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.24.1. Installation of M4
</h3>
</div>
<p>
Prepare M4 for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-m4" name="contents-m4"></a>
<h3 class="sect2">
6.24.2. Contents of M4
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
program:</span></strong> <span class="seg">m4</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3500322" name="id3500322"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="m4" name="m4"></a><span class=
"term"><span><strong class=
"command">m4</strong></span></span>
</td>
<td>
<p>
copies the given files while expanding the macros
that they contain. These macros are either built-in
or user-defined and can take any number of
arguments. Besides performing macro expansion,
<span><strong class="command">m4</strong></span>
has built-in functions for including named files,
running Unix commands, performing integer
arithmetic, manipulating text, recursion, etc. The
<span><strong class="command">m4</strong></span>
program can be used either as a front-end to a
compiler or as a macro processor in its own right.
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-bison" name=
"ch-system-bison"></a>6.25.&nbsp;Bison-2.0
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Bison package contains a parser generator.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.6 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">9.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, M4,
Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.25.1. Installation of Bison
</h3>
</div>
<p>
Prepare Bison for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-bison" name="contents-bison"></a>
<h3 class="sect2">
6.25.2. Contents of Bison
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">bison and
yacc</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
library:</span></strong> <span class="seg">liby.a</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3500362" name="id3500362"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="bison" name="bison"></a><span class=
"term"><span><strong class=
"command">bison</strong></span></span>
</td>
<td>
<p>
Generates, from a series of rules, a program for
analyzing the structure of text files; Bison is a
replacement for Yacc (Yet Another Compiler
Compiler)
</p>
</td>
</tr>
<tr>
<td>
<a id="yacc" name="yacc"></a><span class=
"term"><span><strong class=
"command">yacc</strong></span></span>
</td>
<td>
<p>
A wrapper for <span><strong class=
"command">bison</strong></span>, meant for programs
that still call <span><strong class=
"command">yacc</strong></span> instead of
<span><strong class=
"command">bison</strong></span>; it calls
<span><strong class="command">bison</strong></span>
with the <em class="parameter"><tt>-y</tt></em>
option
</p>
</td>
</tr>
<tr>
<td>
<a id="liby.a" name="liby.a"></a><span class=
"term"><tt class="filename">liby.a</tt></span>
</td>
<td>
<p>
The Yacc library containing implementations of
Yacc-compatible <span class=
"emphasis"><em>yyerror</em></span> and <span class=
"emphasis"><em>main</em></span> functions; this
library is normally not very useful, but POSIX
requires it
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-less" name=
"ch-system-less"></a>6.26.&nbsp;Less-382
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Less package contains a text file viewer.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">2.3 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, Ncurses,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.26.1. Installation of Less
</h3>
</div>
<p>
Prepare Less for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --bindir=/bin --sysconfdir=/etc</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--sysconfdir=/etc</tt></em></span>
</dt>
<dd>
<p>
This option tells the programs created by the package
to look in <tt class="filename">/etc</tt> for the
configuration files.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-less" name="contents-less"></a>
<h3 class="sect2">
6.26.2. Contents of Less
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">less,
lessecho, and lesskey</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3500494" name="id3500494"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="less" name="less"></a><span class=
"term"><span><strong class=
"command">less</strong></span></span>
</td>
<td>
<p>
A file viewer or pager; it displays the contents of
the given file, letting the user scroll, find
strings, and jump to marks
</p>
</td>
</tr>
<tr>
<td>
<a id="lessecho" name="lessecho"></a><span class=
"term"><span><strong class=
"command">lessecho</strong></span></span>
</td>
<td>
<p>
Needed to expand meta-characters, such as
<span class="emphasis"><em>*</em></span> and
<span class="emphasis"><em>?</em></span>, in
filenames on Unix systems
</p>
</td>
</tr>
<tr>
<td>
<a id="lesskey" name="lesskey"></a><span class=
"term"><span><strong class=
"command">lesskey</strong></span></span>
</td>
<td>
<p>
Used to specify the key bindings for
<span><strong class="command">less</strong></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-groff" name=
"ch-system-groff"></a>6.27.&nbsp;Groff-1.19.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Groff package contains programs for processing and
formatting text.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.5 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">38.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.27.1. Installation of Groff
</h3>
</div>
<p>
Groff expects the environment variable <tt class=
"envar">PAGE</tt> to contain the default paper size. For
users in the United States, <em class=
"parameter"><tt>PAGE=letter</tt></em> is appropriate.
Elsewhere, <em class="parameter"><tt>PAGE=A4</tt></em> may be
more suitable.
</p>
<p>
Prepare Groff for compilation:
</p>
<pre class="userinput"><kbd class="command">PAGE=<em class=
"replaceable"><tt>[paper_size]</tt></em> ./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Some documentation programs, such as <span><strong class=
"command">xman</strong></span>, will not work properly
without the following symlinks:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv soelim /usr/bin/zsoelim
ln -sv eqn /usr/bin/geqn
ln -sv tbl /usr/bin/gtbl</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-groff" name="contents-groff"></a>
<h3 class="sect2">
6.27.2. Contents of Groff
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">addftinfo,
afmtodit, eqn, eqn2graph, geqn (link to eqn), grn,
grodvi, groff, groffer, grog, grolbp, grolj4, grops,
grotty, gtbl (link to tbl), hpftodit, indxbib, lkbib,
lookbib, mmroff, neqn, nroff, pfbtops, pic, pic2graph,
post-grohtml, pre-grohtml, refer, soelim, tbl, tfmtodit,
troff, and zsoelim (link to soelim)</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3500884" name="id3500884"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="addftinfo" name="addftinfo"></a><span class=
"term"><span><strong class=
"command">addftinfo</strong></span></span>
</td>
<td>
<p>
Reads a troff font file and adds some additional
font-metric information that is used by the
<span><strong class="command">groff</strong></span>
system
</p>
</td>
</tr>
<tr>
<td>
<a id="afmtodit" name="afmtodit"></a><span class=
"term"><span><strong class=
"command">afmtodit</strong></span></span>
</td>
<td>
<p>
Creates a font file for use with
<span><strong class="command">groff</strong></span>
and <span><strong class=
"command">grops</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="eqn" name="eqn"></a><span class=
"term"><span><strong class=
"command">eqn</strong></span></span>
</td>
<td>
<p>
Compiles descriptions of equations embedded within
troff input files into commands that are understood
by <span><strong class=
"command">troff</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="eqn2graph" name="eqn2graph"></a><span class=
"term"><span><strong class=
"command">eqn2graph</strong></span></span>
</td>
<td>
<p>
Converts a troff EQN (equation) into a cropped
image
</p>
</td>
</tr>
<tr>
<td>
<a id="geqn" name="geqn"></a><span class=
"term"><span><strong class=
"command">geqn</strong></span></span>
</td>
<td>
<p>
A link to <span><strong class=
"command">eqn</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="grn" name="grn"></a><span class=
"term"><span><strong class=
"command">grn</strong></span></span>
</td>
<td>
<p>
A <span><strong class=
"command">groff</strong></span> preprocessor for
gremlin files
</p>
</td>
</tr>
<tr>
<td>
<a id="grodvi" name="grodvi"></a><span class=
"term"><span><strong class=
"command">grodvi</strong></span></span>
</td>
<td>
<p>
A driver for <span><strong class=
"command">groff</strong></span> that produces TeX
dvi format
</p>
</td>
</tr>
<tr>
<td>
<a id="groff" name="groff"></a><span class=
"term"><span><strong class=
"command">groff</strong></span></span>
</td>
<td>
<p>
A front-end to the groff document formatting
system; normally, it runs the <span><strong class=
"command">troff</strong></span> program and a
post-processor appropriate for the selected device
</p>
</td>
</tr>
<tr>
<td>
<a id="groffer" name="groffer"></a><span class=
"term"><span><strong class=
"command">groffer</strong></span></span>
</td>
<td>
<p>
Displays groff files and man pages on X and tty
terminals
</p>
</td>
</tr>
<tr>
<td>
<a id="grog" name="grog"></a><span class=
"term"><span><strong class=
"command">grog</strong></span></span>
</td>
<td>
<p>
Reads files and guesses which of the
<span><strong class="command">groff</strong></span>
options <em class="parameter"><tt>-e</tt></em>,
<em class="parameter"><tt>-man</tt></em>,
<em class="parameter"><tt>-me</tt></em>, <em class=
"parameter"><tt>-mm</tt></em>, <em class=
"parameter"><tt>-ms</tt></em>, <em class=
"parameter"><tt>-p</tt></em>, <em class=
"parameter"><tt>-s</tt></em>, and <em class=
"parameter"><tt>-t</tt></em> are required for
printing files, and reports the
<span><strong class="command">groff</strong></span>
command including those options
</p>
</td>
</tr>
<tr>
<td>
<a id="grolbp" name="grolbp"></a><span class=
"term"><span><strong class=
"command">grolbp</strong></span></span>
</td>
<td>
<p>
Is a <span><strong class=
"command">groff</strong></span> driver for Canon
CAPSL printers (LBP-4 and LBP-8 series laser
printers)
</p>
</td>
</tr>
<tr>
<td>
<a id="grolj4" name="grolj4"></a><span class=
"term"><span><strong class=
"command">grolj4</strong></span></span>
</td>
<td>
<p>
Is a driver for <span><strong class=
"command">groff</strong></span> that produces
output in PCL5 format suitable for an HP LaserJet 4
printer
</p>
</td>
</tr>
<tr>
<td>
<a id="grops" name="grops"></a><span class=
"term"><span><strong class=
"command">grops</strong></span></span>
</td>
<td>
<p>
Translates the output of GNU <span><strong class=
"command">troff</strong></span> to PostScript
</p>
</td>
</tr>
<tr>
<td>
<a id="grotty" name="grotty"></a><span class=
"term"><span><strong class=
"command">grotty</strong></span></span>
</td>
<td>
<p>
Translates the output of GNU <span><strong class=
"command">troff</strong></span> into a form
suitable for typewriter-like devices
</p>
</td>
</tr>
<tr>
<td>
<a id="gtbl" name="gtbl"></a><span class=
"term"><span><strong class=
"command">gtbl</strong></span></span>
</td>
<td>
<p>
A link to <span><strong class=
"command">tbl</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="hpftodit" name="hpftodit"></a><span class=
"term"><span><strong class=
"command">hpftodit</strong></span></span>
</td>
<td>
<p>
Creates a font file for use with
<span><strong class="command">groff
-Tlj4</strong></span> from an HP-tagged font metric
file
</p>
</td>
</tr>
<tr>
<td>
<a id="indxbib" name="indxbib"></a><span class=
"term"><span><strong class=
"command">indxbib</strong></span></span>
</td>
<td>
<p>
Creates an inverted index for the bibliographic
databases with a specified file for use with
<span><strong class=
"command">refer</strong></span>,
<span><strong class=
"command">lookbib</strong></span>, and
<span><strong class="command">lkbib</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="lkbib" name="lkbib"></a><span class=
"term"><span><strong class=
"command">lkbib</strong></span></span>
</td>
<td>
<p>
Searches bibliographic databases for references
that contain specified keys and reports any
references found
</p>
</td>
</tr>
<tr>
<td>
<a id="lookbib" name="lookbib"></a><span class=
"term"><span><strong class=
"command">lookbib</strong></span></span>
</td>
<td>
<p>
Prints a prompt on the standard error (unless the
standard input is not a terminal), reads a line
containing a set of keywords from the standard
input, 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
</p>
</td>
</tr>
<tr>
<td>
<a id="mmroff" name="mmroff"></a><span class=
"term"><span><strong class=
"command">mmroff</strong></span></span>
</td>
<td>
<p>
A simple preprocessor for <span><strong class=
"command">groff</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="neqn" name="neqn"></a><span class=
"term"><span><strong class=
"command">neqn</strong></span></span>
</td>
<td>
<p>
Formats equations for American Standard Code for
Information Interchange (ASCII) output
</p>
</td>
</tr>
<tr>
<td>
<a id="nroff" name="nroff"></a><span class=
"term"><span><strong class=
"command">nroff</strong></span></span>
</td>
<td>
<p>
A script that emulates the <span><strong class=
"command">nroff</strong></span> command using
<span><strong class="command">groff</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="pfbtops" name="pfbtops"></a><span class=
"term"><span><strong class=
"command">pfbtops</strong></span></span>
</td>
<td>
<p>
Translates a PostScript font in <tt class=
"filename">.pfb</tt> format to ASCII
</p>
</td>
</tr>
<tr>
<td>
<a id="pic" name="pic"></a><span class=
"term"><span><strong class=
"command">pic</strong></span></span>
</td>
<td>
<p>
Compiles descriptions of pictures embedded within
troff or TeX input files into commands understood
by TeX or <span><strong class=
"command">troff</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="pic2graph" name="pic2graph"></a><span class=
"term"><span><strong class=
"command">pic2graph</strong></span></span>
</td>
<td>
<p>
Converts a PIC diagram into a cropped image
</p>
</td>
</tr>
<tr>
<td>
<a id="post-grohtml" name=
"post-grohtml"></a><span class=
"term"><span><strong class=
"command">post-grohtml</strong></span></span>
</td>
<td>
<p>
Translates the output of GNU <span><strong class=
"command">troff</strong></span> to HTML
</p>
</td>
</tr>
<tr>
<td>
<a id="pre-grohtml" name=
"pre-grohtml"></a><span class=
"term"><span><strong class=
"command">pre-grohtml</strong></span></span>
</td>
<td>
<p>
Translates the output of GNU <span><strong class=
"command">troff</strong></span> to HTML
</p>
</td>
</tr>
<tr>
<td>
<a id="refer" name="refer"></a><span class=
"term"><span><strong class=
"command">refer</strong></span></span>
</td>
<td>
<p>
Copies the contents of a file to the standard
output, except that lines between <span class=
"emphasis"><em>.[</em></span> and <span class=
"emphasis"><em>.]</em></span> are interpreted as
citations, and lines between <span class=
"emphasis"><em>.R1</em></span> and <span class=
"emphasis"><em>.R2</em></span> are interpreted as
commands for how citations are to be processed
</p>
</td>
</tr>
<tr>
<td>
<a id="soelim" name="soelim"></a><span class=
"term"><span><strong class=
"command">soelim</strong></span></span>
</td>
<td>
<p>
Reads files and replaces lines of the form
<span class="emphasis"><em>.so file</em></span> by
the contents of the mentioned <span class=
"emphasis"><em>file</em></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="tbl" name="tbl"></a><span class=
"term"><span><strong class=
"command">tbl</strong></span></span>
</td>
<td>
<p>
Compiles descriptions of tables embedded within
troff input files into commands that are understood
by <span><strong class=
"command">troff</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="tfmtodit" name="tfmtodit"></a><span class=
"term"><span><strong class=
"command">tfmtodit</strong></span></span>
</td>
<td>
<p>
Creates a font file for use with
<span><strong class="command">groff
-Tdvi</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="troff" name="troff"></a><span class=
"term"><span><strong class=
"command">troff</strong></span></span>
</td>
<td>
<p>
Is highly compatible with Unix <span><strong class=
"command">troff</strong></span>; it should usually
be invoked using the <span><strong class=
"command">groff</strong></span> command, which will
also run preprocessors and post-processors in the
appropriate order and with the appropriate options
</p>
</td>
</tr>
<tr>
<td>
<a id="zsoelim" name="zsoelim"></a><span class=
"term"><span><strong class=
"command">zsoelim</strong></span></span>
</td>
<td>
<p>
A link to <span><strong class=
"command">soelim</strong></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-sed" name=
"ch-system-sed"></a>6.28.&nbsp;Sed-4.1.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Sed package contains a stream editor.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">8.4 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.28.1. Installation of Sed
</h3>
</div>
<p>
By default, Sed installs its HTML documentation in <tt class=
"filename">/usr/share/doc</tt>. Alter this to <tt class=
"filename">/usr/share/doc/sed-4.1.4</tt> by applying the
following <span><strong class="command">sed</strong></span>:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's@/doc@&amp;/sed-4.1.4@' doc/Makefile.in</kbd></pre>
<p>
Prepare Sed for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --bindir=/bin</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-sed" name="contents-sed"></a>
<h3 class="sect2">
6.28.2. Contents of Sed
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
program:</span></strong> <span class="seg">sed</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3501884" name="id3501884"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="sed" name="sed"></a><span class=
"term"><span><strong class=
"command">sed</strong></span></span>
</td>
<td>
<p>
Filters and transforms text files in a single pass
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-flex" name=
"ch-system-flex"></a>6.29.&nbsp;Flex-2.5.31
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Flex package contains a utility for generating programs
that recognize patterns in text.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">22.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Bison, Coreutils, Diffutils, GCC, Gettext, Glibc, Grep,
M4, Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.29.1. Installation of Flex
</h3>
</div>
<p>
Flex contains several known bugs. Fix these with the
following patch:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../flex-2.5.31-debian_fixes-3.patch</kbd></pre>
<p>
The GNU autotools detects that the Flex source code has been
modified by the previous patch and tries to update the man
page accordingly. This does not work correctly on many
systems, and the default page is fine, so make sure it does
not get regenerated:
</p>
<pre class="userinput"><kbd class=
"command">touch doc/flex.1</kbd></pre>
<p>
Prepare Flex for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
There are some packages that expect to find the <tt class=
"filename">lex</tt> library in <tt class=
"filename">/usr/lib</tt>. Create a symlink to account for
this:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv libfl.a /usr/lib/libl.a</kbd></pre>
<p>
A few programs do not know about <span><strong class=
"command">flex</strong></span> yet and try to run its
predecessor, <span><strong class=
"command">lex</strong></span>. To support those programs,
create a wrapper script named <tt class="filename">lex</tt>
that calls <tt class="filename">flex</tt> in
<span><strong class="command">lex</strong></span> emulation
mode:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /usr/bin/lex &lt;&lt; "EOF"
<tt class="literal">#!/bin/sh
# Begin /usr/bin/lex
exec /usr/bin/flex -l "$@"
# End /usr/bin/lex</tt>
EOF
chmod -v 755 /usr/bin/lex</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-flex" name="contents-flex"></a>
<h3 class="sect2">
6.29.2. Contents of Flex
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">flex and
lex</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
library:</span></strong> <span class="seg">libfl.a</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3502071" name="id3502071"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="flex" name="flex"></a><span class=
"term"><span><strong class=
"command">flex</strong></span></span>
</td>
<td>
<p>
A tool for generating programs that recognize
patterns in text; it allows for the versatility to
specify the rules for pattern-finding, eradicating
the need to develop a specialized program
</p>
</td>
</tr>
<tr>
<td>
<a id="lex" name="lex"></a><span class=
"term"><span><strong class=
"command">lex</strong></span></span>
</td>
<td>
<p>
A script that runs <span><strong class=
"command">flex</strong></span> in
<span><strong class="command">lex</strong></span>
emulation mode
</p>
</td>
</tr>
<tr>
<td>
<a id="libfl.a" name="libfl.a"></a><span class=
"term"><tt class="filename">libfl.a</tt></span>
</td>
<td>
<p>
The <tt class="filename">flex</tt> library
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-gettext" name=
"ch-system-gettext"></a>6.30.&nbsp;Gettext-0.14.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Gettext package contains utilities for
internationalization and localization. These allow programs
to be compiled with NLS (Native Language Support), enabling
them to output messages in the user's native language.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">1.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">65.1 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Bison, Coreutils, Diffutils, Gawk, GCC, Glibc, Grep,
Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.30.1. Installation of Gettext
</h3>
</div>
<p>
Prepare Gettext for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>. This takes a very
long time, around 7 SBUs.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-gettext" name="contents-gettext"></a>
<h3 class="sect2">
6.30.2. Contents of Gettext
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">autopoint,
config.charset, config.rpath, envsubst, gettext,
gettextize, hostname, msgattrib, msgcat, msgcmp, msgcomm,
msgconv, msgen, msgexec, msgfilter, msgfmt, msggrep,
msginit, msgmerge, msgunfmt, msguniq, ngettext, and
xgettext</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libasprintf.[a,so], libgettextlib.so,
libgettextpo.[a,so], and libgettextsrc.so</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3502122" name="id3502122"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="autopoint" name="autopoint"></a><span class=
"term"><span><strong class=
"command">autopoint</strong></span></span>
</td>
<td>
<p>
Copies standard Gettext infrastructure files into a
source package
</p>
</td>
</tr>
<tr>
<td>
<a id="config.charset" name=
"config.charset"></a><span class=
"term"><span><strong class=
"command">config.charset</strong></span></span>
</td>
<td>
<p>
Outputs a system-dependent table of character
encoding aliases
</p>
</td>
</tr>
<tr>
<td>
<a id="config.rpath" name=
"config.rpath"></a><span class=
"term"><span><strong class=
"command">config.rpath</strong></span></span>
</td>
<td>
<p>
Outputs a system-dependent set of variables,
describing how to set the runtime search path of
shared libraries in an executable
</p>
</td>
</tr>
<tr>
<td>
<a id="envsubst" name="envsubst"></a><span class=
"term"><span><strong class=
"command">envsubst</strong></span></span>
</td>
<td>
<p>
Substitutes environment variables in shell format
strings
</p>
</td>
</tr>
<tr>
<td>
<a id="gettext" name="gettext"></a><span class=
"term"><span><strong class=
"command">gettext</strong></span></span>
</td>
<td>
<p>
Translates a natural language message into the
user's language by looking up the translation in a
message catalog
</p>
</td>
</tr>
<tr>
<td>
<a id="gettextize" name="gettextize"></a><span class=
"term"><span><strong class=
"command">gettextize</strong></span></span>
</td>
<td>
<p>
Copies all standard Gettext files into the given
top-level directory of a package to begin
internationalizing it
</p>
</td>
</tr>
<tr>
<td>
<a id="hostname-gettext" name=
"hostname-gettext"></a><span class=
"term"><span><strong class=
"command">hostname</strong></span></span>
</td>
<td>
<p>
Displays a network hostname in various forms
</p>
</td>
</tr>
<tr>
<td>
<a id="msgattrib" name="msgattrib"></a><span class=
"term"><span><strong class=
"command">msgattrib</strong></span></span>
</td>
<td>
<p>
Filters the messages of a translation catalog
according to their attributes and manipulates the
attributes
</p>
</td>
</tr>
<tr>
<td>
<a id="msgcat" name="msgcat"></a><span class=
"term"><span><strong class=
"command">msgcat</strong></span></span>
</td>
<td>
<p>
Concatenates and merges the given <tt class=
"filename">.po</tt> files
</p>
</td>
</tr>
<tr>
<td>
<a id="msgcmp" name="msgcmp"></a><span class=
"term"><span><strong class=
"command">msgcmp</strong></span></span>
</td>
<td>
<p>
Compares two <tt class="filename">.po</tt> files to
check that both contain the same set of msgid
strings
</p>
</td>
</tr>
<tr>
<td>
<a id="msgcomm" name="msgcomm"></a><span class=
"term"><span><strong class=
"command">msgcomm</strong></span></span>
</td>
<td>
<p>
Finds the messages that are common to to the given
<tt class="filename">.po</tt> files
</p>
</td>
</tr>
<tr>
<td>
<a id="msgconv" name="msgconv"></a><span class=
"term"><span><strong class=
"command">msgconv</strong></span></span>
</td>
<td>
<p>
Converts a translation catalog to a different
character encoding
</p>
</td>
</tr>
<tr>
<td>
<a id="msgen" name="msgen"></a><span class=
"term"><span><strong class=
"command">msgen</strong></span></span>
</td>
<td>
<p>
Creates an English translation catalog
</p>
</td>
</tr>
<tr>
<td>
<a id="msgexec" name="msgexec"></a><span class=
"term"><span><strong class=
"command">msgexec</strong></span></span>
</td>
<td>
<p>
Applies a command to all translations of a
translation catalog
</p>
</td>
</tr>
<tr>
<td>
<a id="msgfilter" name="msgfilter"></a><span class=
"term"><span><strong class=
"command">msgfilter</strong></span></span>
</td>
<td>
<p>
Applies a filter to all translations of a
translation catalog
</p>
</td>
</tr>
<tr>
<td>
<a id="msgfmt" name="msgfmt"></a><span class=
"term"><span><strong class=
"command">msgfmt</strong></span></span>
</td>
<td>
<p>
Generates a binary message catalog from a
translation catalog
</p>
</td>
</tr>
<tr>
<td>
<a id="msggrep" name="msggrep"></a><span class=
"term"><span><strong class=
"command">msggrep</strong></span></span>
</td>
<td>
<p>
Extracts all messages of a translation catalog that
match a given pattern or belong to some given
source files
</p>
</td>
</tr>
<tr>
<td>
<a id="msginit" name="msginit"></a><span class=
"term"><span><strong class=
"command">msginit</strong></span></span>
</td>
<td>
<p>
Creates a new <tt class="filename">.po</tt> file,
initializing the meta information with values from
the user's environment
</p>
</td>
</tr>
<tr>
<td>
<a id="msgmerge" name="msgmerge"></a><span class=
"term"><span><strong class=
"command">msgmerge</strong></span></span>
</td>
<td>
<p>
Combines two raw translations into a single file
</p>
</td>
</tr>
<tr>
<td>
<a id="msgunfmt" name="msgunfmt"></a><span class=
"term"><span><strong class=
"command">msgunfmt</strong></span></span>
</td>
<td>
<p>
Decompiles a binary message catalog into raw
translation text
</p>
</td>
</tr>
<tr>
<td>
<a id="msguniq" name="msguniq"></a><span class=
"term"><span><strong class=
"command">msguniq</strong></span></span>
</td>
<td>
<p>
Unifies duplicate translations in a translation
catalog
</p>
</td>
</tr>
<tr>
<td>
<a id="ngettext" name="ngettext"></a><span class=
"term"><span><strong class=
"command">ngettext</strong></span></span>
</td>
<td>
<p>
Displays native language translations of a textual
message whose grammatical form depends on a number
</p>
</td>
</tr>
<tr>
<td>
<a id="xgettext" name="xgettext"></a><span class=
"term"><span><strong class=
"command">xgettext</strong></span></span>
</td>
<td>
<p>
Extracts the translatable message lines from the
given source files to make the first translation
template
</p>
</td>
</tr>
<tr>
<td>
<a id="libasprintf" name=
"libasprintf"></a><span class="term"><tt class=
"filename">libasprintf</tt></span>
</td>
<td>
<p>
defines the <span class=
"emphasis"><em>autosprintf</em></span> class, which
makes C formatted output routines usable in C++
programs, for use with the <span class=
"emphasis"><em>&lt;string&gt;</em></span> strings
and the <span class=
"emphasis"><em>&lt;iostream&gt;</em></span> streams
</p>
</td>
</tr>
<tr>
<td>
<a id="libgettextlib" name=
"libgettextlib"></a><span class="term"><tt class=
"filename">libgettextlib</tt></span>
</td>
<td>
<p>
a private library containing common routines used
by the various Gettext programs; these are not
intended for general use
</p>
</td>
</tr>
<tr>
<td>
<a id="libgettextpo" name=
"libgettextpo"></a><span class="term"><tt class=
"filename">libgettextpo</tt></span>
</td>
<td>
<p>
Used to write specialized programs that process
<tt class="filename">.po</tt> files; this library
is used when the standard applications shipped with
Gettext (such as <span><strong class=
"command">msgcomm</strong></span>,
<span><strong class=
"command">msgcmp</strong></span>,
<span><strong class=
"command">msgattrib</strong></span>, and
<span><strong class=
"command">msgen</strong></span>) will not suffice
</p>
</td>
</tr>
<tr>
<td>
<a id="libgettextsrc" name=
"libgettextsrc"></a><span class="term"><tt class=
"filename">libgettextsrc</tt></span>
</td>
<td>
<p>
A private library containing common routines used
by the various Gettext programs; these are not
intended for general use
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-inetutils" name=
"ch-system-inetutils"></a>6.31.&nbsp;Inetutils-1.4.2
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Inetutils package contains programs for basic networking.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">8.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, Ncurses,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.31.1. Installation of Inetutils
</h3>
</div>
<p>
Inetutils has issues with the Linux 2.6 kernel series. Fix
these issues by applying the following patch:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../inetutils-1.4.2-kernel_headers-1.patch</kbd></pre>
<p>
All programs that come with Inetutils will not be installed.
However, the Inetutils build system will insist on installing
all the man pages anyway. The following patch will correct
this situation:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../inetutils-1.4.2-no_server_man_pages-1.patch</kbd></pre>
<p>
Prepare Inetutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --libexecdir=/usr/sbin \
--sysconfdir=/etc --localstatedir=/var \
--disable-logger --disable-syslogd \
--disable-whois --disable-servers</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-logger</tt></em></span>
</dt>
<dd>
<p>
This option prevents Inetutils from installing the
<span><strong class="command">logger</strong></span>
program, which is used by scripts to pass messages to
the System Log Daemon. Do not install it because
Util-linux installs a better version later.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-syslogd</tt></em></span>
</dt>
<dd>
<p>
This option prevents Inetutils from installing the
System Log Daemon, which is installed with the Sysklogd
package.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-whois</tt></em></span>
</dt>
<dd>
<p>
This option disables the building of the Inetutils
<span><strong class="command">whois</strong></span>
client, which is out of date. Instructions for a better
<span><strong class="command">whois</strong></span>
client are in the BLFS book.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-servers</tt></em></span>
</dt>
<dd>
<p>
This disables the installation of the various network
servers included as part of the Inetutils package.
These servers are deemed not appropriate in a basic LFS
system. Some are insecure by nature and are only
considered safe on trusted networks. More information
can be found at <a href=
"http://www.linuxfromscratch.org/blfs/view/svn/basicnet/inetutils.html">
<i>http://www.linuxfromscratch.org/blfs/view/svn/basicnet/inetutils.html</i></a>.
Note that better replacements are available for many of
these servers.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Move the <span><strong class="command">ping</strong></span>
program to its FHS-compliant place:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /usr/bin/ping /bin</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-inetutils" name="contents-inetutils"></a>
<h3 class="sect2">
6.31.2. Contents of Inetutils
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">ftp, ping,
rcp, rlogin, rsh, talk, telnet, and tftp</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3503064" name="id3503064"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="ftp" name="ftp"></a><span class=
"term"><span><strong class=
"command">ftp</strong></span></span>
</td>
<td>
<p>
Is the file transfer protocol program
</p>
</td>
</tr>
<tr>
<td>
<a id="ping" name="ping"></a><span class=
"term"><span><strong class=
"command">ping</strong></span></span>
</td>
<td>
<p>
Sends echo-request packets and reports how long the
replies take
</p>
</td>
</tr>
<tr>
<td>
<a id="rcp" name="rcp"></a><span class=
"term"><span><strong class=
"command">rcp</strong></span></span>
</td>
<td>
<p>
Performs remote file copy
</p>
</td>
</tr>
<tr>
<td>
<a id="rlogin" name="rlogin"></a><span class=
"term"><span><strong class=
"command">rlogin</strong></span></span>
</td>
<td>
<p>
Performs remote login
</p>
</td>
</tr>
<tr>
<td>
<a id="rsh" name="rsh"></a><span class=
"term"><span><strong class=
"command">rsh</strong></span></span>
</td>
<td>
<p>
Runs a remote shell
</p>
</td>
</tr>
<tr>
<td>
<a id="talk" name="talk"></a><span class=
"term"><span><strong class=
"command">talk</strong></span></span>
</td>
<td>
<p>
Is used to chat with another user
</p>
</td>
</tr>
<tr>
<td>
<a id="telnet" name="telnet"></a><span class=
"term"><span><strong class=
"command">telnet</strong></span></span>
</td>
<td>
<p>
An interface to the TELNET protocol
</p>
</td>
</tr>
<tr>
<td>
<a id="tftp" name="tftp"></a><span class=
"term"><span><strong class=
"command">tftp</strong></span></span>
</td>
<td>
<p>
A trivial file transfer program
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-iproute2" name=
"ch-system-iproute2"></a>6.32.&nbsp;IPRoute2-2.6.11-050330
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The IPRoute2 package contains programs for basic and advanced
IPV4-based networking.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">4.3 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">GCC, Glibc, Make,
Linux-Headers, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.32.1. Installation of IPRoute2
</h3>
</div>
<p>
The <span><strong class="command">arpd</strong></span> binary
included in this package is dependent on Berkeley DB. Because
<span><strong class="command">arpd</strong></span> is not a
very common requirement on a base Linux system, remove the
dependency on Berkeley DB by applying the
<span><strong class="command">sed</strong></span> command
below. If the <span><strong class=
"command">arpd</strong></span> binary is needed, instructions
for compiling Berkeley DB can be found in the BLFS Book at
<a href=
"http://www.linuxfromscratch.org/blfs/view/svn/server/databases.html#db">
<i>http://www.linuxfromscratch.org/blfs/view/svn/server/databases.html#db</i></a>.
</p>
<pre class="userinput"><kbd class=
"command">sed -i '/^TARGETS/s@arpd@@g' misc/Makefile</kbd></pre>
<p>
Prepare IPRoute2 for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure </kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class=
"command">make SBINDIR=/sbin</kbd></pre>
<p>
The meaning of the make option:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>SBINDIR=/sbin</tt></em></span>
</dt>
<dd>
<p>
This ensures that the IPRoute2 binaries will install
into <tt class="filename">/sbin</tt>. This is the
correct location according to the FHS, because some of
the IPRoute2 binaries are used by the LFS-Bootscripts
package.
</p>
</dd>
</dl>
</div>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make SBINDIR=/sbin install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-iproute2" name="contents-iproute2"></a>
<h3 class="sect2">
6.32.2. Contents of IPRoute2
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">ctstat (link
to lnstat), ifcfg, ifstat, ip, lnstat, nstat, routef,
routel, rtacct, rtmon, rtpr, rtstat (link to lnstat), ss,
and tc.</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3503327" name="id3503327"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="ctstat" name="ctstat"></a> <strong class=
"command">ctstat</strong>
</td>
<td>
<p>
Connection status utility
</p>
</td>
</tr>
<tr>
<td>
<a id="ifcfg" name="ifcfg"></a> <strong class=
"command">ifcfg</strong>
</td>
<td>
<p>
A shell script wrapper for the <span><strong class=
"command">ip</strong></span> command
</p>
</td>
</tr>
<tr>
<td>
<a id="ifstat" name="ifstat"></a> <strong class=
"command">ifstat</strong>
</td>
<td>
<p>
Shows the interface statistics, including the
amount of transmitted and received packets by
interface
</p>
</td>
</tr>
<tr>
<td>
<a id="ip" name="ip"></a> <strong class=
"command">ip</strong>
</td>
<td>
<p>
The main executable. It has several different
functions:
</p>
<p>
<span><strong class="command">ip link <em class=
"replaceable"><tt>[device]</tt></em></strong></span>
allows users to look at the state of devices and to
make changes
</p>
<p>
<span><strong class="command">ip
addr</strong></span> allows users to look at
addresses and their properties, add new addresses,
and delete old ones
</p>
<p>
<span><strong class="command">ip
neighbor</strong></span> allows users to look at
neighbor bindings and their properties, add new
neighbor entries, and delete old ones
</p>
<p>
<span><strong class="command">ip
rule</strong></span> allows users to look at the
routing policies and change them
</p>
<p>
<span><strong class="command">ip
route</strong></span> allows users to look at the
routing table and change routing table rules
</p>
<p>
<span><strong class="command">ip
tunnel</strong></span> allows users to look at the
IP tunnels and their properties, and change them
</p>
<p>
<span><strong class="command">ip
maddr</strong></span> allows users to look at the
multicast addresses and their properties, and
change them
</p>
<p>
<span><strong class="command">ip
mroute</strong></span> allows users to set, change,
or delete the multicast routing
</p>
<p>
<span><strong class="command">ip
monitor</strong></span> allows users to continously
monitor the state of devices, addresses and routes
</p>
</td>
</tr>
<tr>
<td>
<a id="lnstat" name="lnstat"></a> <strong class=
"command">lnstat</strong>
</td>
<td>
<p>
Provides Linux network statistics. It is a
generalized and more feature-complete replacement
for the old <span><strong class=
"command">rtstat</strong></span> program
</p>
</td>
</tr>
<tr>
<td>
<a id="nstat" name="nstat"></a> <strong class=
"command">nstat</strong>
</td>
<td>
<p>
Shows network statistics
</p>
</td>
</tr>
<tr>
<td>
<a id="routef" name="routef"></a> <strong class=
"command">routef</strong>
</td>
<td>
<p>
A component of <span><strong class="command">ip
route</strong></span>. This is for flushing the
routing tables
</p>
</td>
</tr>
<tr>
<td>
<a id="routel" name="routel"></a> <strong class=
"command">routel</strong>
</td>
<td>
<p>
A component of <span><strong class="command">ip
route</strong></span>. This is for listing the
routing tables
</p>
</td>
</tr>
<tr>
<td>
<a id="rtacct" name="rtacct"></a> <strong class=
"command">rtacct</strong>
</td>
<td>
<p>
Displays the contents of <tt class=
"filename">/proc/net/rt_acct</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="rtmon" name="rtmon"></a> <strong class=
"command">rtmon</strong>
</td>
<td>
<p>
Route monitoring utility
</p>
</td>
</tr>
<tr>
<td>
<a id="rtpr" name="rtpr"></a> <strong class=
"command">rtpr</strong>
</td>
<td>
<p>
Converts the output of <span><strong class=
"command">ip -o</strong></span> back into a
readable form
</p>
</td>
</tr>
<tr>
<td>
<a id="rtstat" name="rtstat"></a> <strong class=
"command">rtstat</strong>
</td>
<td>
<p>
Route status utility
</p>
</td>
</tr>
<tr>
<td>
<a id="ss" name="ss"></a> <strong class=
"command">ss</strong>
</td>
<td>
<p>
Similar to the <span><strong class=
"command">netstat</strong></span> command; shows
active connections
</p>
</td>
</tr>
<tr>
<td>
<a id="tc" name="tc"></a> <strong class=
"command">tc</strong>
</td>
<td>
<p>
Traffic Controlling Executable; this is for Quality
Of Service (QOS) and Class Of Service (COS)
implementations
</p>
<p>
<span><strong class="command">tc
qdisc</strong></span> allows users to setup the
queueing discipline
</p>
<p>
<span><strong class="command">tc
class</strong></span> allows users to setup classes
based on the queuing discipline scheduling
</p>
<p>
<span><strong class="command">tc
estimator</strong></span> allows users to estimate
the network flow into a network
</p>
<p>
<span><strong class="command">tc
filter</strong></span> allows users to setup the
QOS/COS packet filtering
</p>
<p>
<span><strong class="command">tc
policy</strong></span> allows users to setup the
QOS/COS policies
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-perl" name=
"ch-system-perl"></a>6.33.&nbsp;Perl-5.8.7
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Perl package contains the Practical Extraction and Report
Language.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">4.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">140 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.33.1. Installation of Perl
</h3>
</div>
<p>
To have full control over the way Perl is set up, run the
interactive <span><strong class=
"command">Configure</strong></span> script and hand-pick the
way this package is built. If the defaults it auto-detects
are suitable, prepare Perl for compilation with:
</p>
<pre class="userinput"><kbd class=
"command">./configure.gnu --prefix=/usr -Dpager="/bin/less -isR"</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>-Dpager="/bin/less -isR"</tt></em></span>
</dt>
<dd>
<p>
This corrects an error in the way that
<span><strong class="command">perldoc</strong></span>
invokes the <span><strong class=
"command">less</strong></span> program.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To run the test suite, first create a basic <tt class=
"filename">/etc/hosts</tt> file which is needed by a couple
of the tests to resolve the network name localhost:
</p>
<pre class="userinput"><kbd class=
"command">echo "127.0.0.1 localhost $(hostname)" &gt; /etc/hosts</kbd></pre>
<p>
Now run the tests, if desired:
</p>
<pre class="userinput"><kbd class=
"command">make test</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-perl" name="contents-perl"></a>
<h3 class="sect2">
6.33.2. Contents of Perl
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">a2p, c2ph,
dprofpp, enc2xs, find2perl, h2ph, h2xs, libnetcfg, perl,
perl5.8.7 (link to perl), perlbug, perlcc, perldoc,
perlivp, piconv, pl2pm, pod2html, pod2latex, pod2man,
pod2text, pod2usage, podchecker, podselect, psed (link to
s2p), pstruct (link to c2ph), s2p, splain, and
xsubpp</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class="seg">Several
hundred which cannot all be listed here</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3503918" name="id3503918"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="a2p" name="a2p"></a><span class=
"term"><span><strong class=
"command">a2p</strong></span></span>
</td>
<td>
<p>
Translates awk to Perl
</p>
</td>
</tr>
<tr>
<td>
<a id="c2ph" name="c2ph"></a><span class=
"term"><span><strong class=
"command">c2ph</strong></span></span>
</td>
<td>
<p>
Dumps C structures as generated from
<span><strong class="command">cc -g
-S</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="dprofpp" name="dprofpp"></a><span class=
"term"><span><strong class=
"command">dprofpp</strong></span></span>
</td>
<td>
<p>
Displays Perl profile data
</p>
</td>
</tr>
<tr>
<td>
<a id="en2cxs" name="en2cxs"></a><span class=
"term"><span><strong class=
"command">en2cxs</strong></span></span>
</td>
<td>
<p>
Builds a Perl extension for the Encode module from
either Unicode Character Mappings or Tcl Encoding
Files
</p>
</td>
</tr>
<tr>
<td>
<a id="find2perl" name="find2perl"></a><span class=
"term"><span><strong class=
"command">find2perl</strong></span></span>
</td>
<td>
<p>
Translates <span><strong class=
"command">find</strong></span> commands to Perl
</p>
</td>
</tr>
<tr>
<td>
<a id="h2ph" name="h2ph"></a><span class=
"term"><span><strong class=
"command">h2ph</strong></span></span>
</td>
<td>
<p>
Converts <tt class="filename">.h</tt> C header
files to <tt class="filename">.ph</tt> Perl header
files
</p>
</td>
</tr>
<tr>
<td>
<a id="h2xs" name="h2xs"></a><span class=
"term"><span><strong class=
"command">h2xs</strong></span></span>
</td>
<td>
<p>
Converts <tt class="filename">.h</tt> C header
files to Perl extensions
</p>
</td>
</tr>
<tr>
<td>
<a id="libnetcfg" name="libnetcfg"></a><span class=
"term"><span><strong class=
"command">libnetcfg</strong></span></span>
</td>
<td>
<p>
Can be used to configure the <tt class=
"filename">libnet</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="perl" name="perl"></a><span class=
"term"><span><strong class=
"command">perl</strong></span></span>
</td>
<td>
<p>
Combines some of the best features of C,
<span><strong class="command">sed</strong></span>,
<span><strong class="command">awk</strong></span>
and <span><strong class=
"command">sh</strong></span> into a single
swiss-army language
</p>
</td>
</tr>
<tr>
<td>
<a id="perl-version" name=
"perl-version"></a><span class=
"term"><span><strong class=
"command">perl5.8.7</strong></span></span>
</td>
<td>
<p>
A hard link to <span><strong class=
"command">perl</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="perlbug" name="perlbug"></a><span class=
"term"><span><strong class=
"command">perlbug</strong></span></span>
</td>
<td>
<p>
Used to generate bug reports about Perl, or the
modules that come with it, and mail them
</p>
</td>
</tr>
<tr>
<td>
<a id="perlcc" name="perlcc"></a><span class=
"term"><span><strong class=
"command">perlcc</strong></span></span>
</td>
<td>
<p>
Generates executables from Perl programs
</p>
</td>
</tr>
<tr>
<td>
<a id="perldoc" name="perldoc"></a><span class=
"term"><span><strong class=
"command">perldoc</strong></span></span>
</td>
<td>
<p>
Displays a piece of documentation in pod format
that is embedded in the Perl installation tree or
in a Perl script
</p>
</td>
</tr>
<tr>
<td>
<a id="perlivp" name="perlivp"></a><span class=
"term"><span><strong class=
"command">perlivp</strong></span></span>
</td>
<td>
<p>
The Perl Installation Verification Procedure; it
can be used to verify that Perl and its libraries
have been installed correctly
</p>
</td>
</tr>
<tr>
<td>
<a id="piconv" name="piconv"></a><span class=
"term"><span><strong class=
"command">piconv</strong></span></span>
</td>
<td>
<p>
A Perl version of the character encoding converter
<span><strong class="command">iconv</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="pl2pm" name="pl2pm"></a><span class=
"term"><span><strong class=
"command">pl2pm</strong></span></span>
</td>
<td>
<p>
A rough tool for converting Perl4 <tt class=
"filename">.pl</tt> files to Perl5 <tt class=
"filename">.pm</tt> modules
</p>
</td>
</tr>
<tr>
<td>
<a id="pod2html" name="pod2html"></a><span class=
"term"><span><strong class=
"command">pod2html</strong></span></span>
</td>
<td>
<p>
Converts files from pod format to HTML format
</p>
</td>
</tr>
<tr>
<td>
<a id="pod2latex" name="pod2latex"></a><span class=
"term"><span><strong class=
"command">pod2latex</strong></span></span>
</td>
<td>
<p>
Converts files from pod format to LaTeX format
</p>
</td>
</tr>
<tr>
<td>
<a id="pod2man" name="pod2man"></a><span class=
"term"><span><strong class=
"command">pod2man</strong></span></span>
</td>
<td>
<p>
Converts pod data to formatted *roff input
</p>
</td>
</tr>
<tr>
<td>
<a id="pod2text" name="pod2text"></a><span class=
"term"><span><strong class=
"command">pod2text</strong></span></span>
</td>
<td>
<p>
Converts pod data to formatted ASCII text
</p>
</td>
</tr>
<tr>
<td>
<a id="pod2usage" name="pod2usage"></a><span class=
"term"><span><strong class=
"command">pod2usage</strong></span></span>
</td>
<td>
<p>
Prints usage messages from embedded pod docs in
files
</p>
</td>
</tr>
<tr>
<td>
<a id="podchecker" name="podchecker"></a><span class=
"term"><span><strong class=
"command">podchecker</strong></span></span>
</td>
<td>
<p>
Checks the syntax of pod format documentation files
</p>
</td>
</tr>
<tr>
<td>
<a id="podselect" name="podselect"></a><span class=
"term"><span><strong class=
"command">podselect</strong></span></span>
</td>
<td>
<p>
Displays selected sections of pod documentation
</p>
</td>
</tr>
<tr>
<td>
<a id="psed" name="psed"></a><span class=
"term"><span><strong class=
"command">psed</strong></span></span>
</td>
<td>
<p>
A Perl version of the stream editor
<span><strong class="command">sed</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="pstruct" name="pstruct"></a><span class=
"term"><span><strong class=
"command">pstruct</strong></span></span>
</td>
<td>
<p>
Dumps C structures as generated from
<span><strong class="command">cc -g
-S</strong></span> stabs
</p>
</td>
</tr>
<tr>
<td>
<a id="s2p" name="s2p"></a><span class=
"term"><span><strong class=
"command">s2p</strong></span></span>
</td>
<td>
<p>
Translates <span><strong class=
"command">sed</strong></span> scripts to Perl
</p>
</td>
</tr>
<tr>
<td>
<a id="splain" name="splain"></a><span class=
"term"><span><strong class=
"command">splain</strong></span></span>
</td>
<td>
<p>
Is used to force verbose warning diagnostics in
Perl
</p>
</td>
</tr>
<tr>
<td>
<a id="xsubpp" name="xsubpp"></a><span class=
"term"><span><strong class=
"command">xsubpp</strong></span></span>
</td>
<td>
<p>
Converts Perl XS code into C code
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-texinfo" name=
"ch-system-texinfo"></a>6.34.&nbsp;Texinfo-4.8
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Texinfo package contains programs for reading, writing,
and converting info pages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">14.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Ncurses, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.34.1. Installation of Texinfo
</h3>
</div>
<p>
Texinfo allows local users to overwrite arbitrary files via a
symlink attack on temporary files. Apply the following patch
to fix this:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../texinfo-4.8-tempfile_fix-1.patch</kbd></pre>
<p>
Prepare Texinfo for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Optionally, install the components belonging in a TeX
installation:
</p>
<pre class="userinput"><kbd class=
"command">make TEXMF=/usr/share/texmf install-tex</kbd></pre>
<p>
The meaning of the make parameter:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>TEXMF=/usr/share/texmf</tt></em></span>
</dt>
<dd>
<p>
The <tt class="envar">TEXMF</tt> makefile variable
holds the location of the root of the TeX tree if, for
example, a TeX package will be installed later.
</p>
</dd>
</dl>
</div>
<p>
The Info documentation system uses a plain text file to hold
its list of menu entries. The file is located at <tt class=
"filename">/usr/share/info/dir</tt>. Unfortunately, due to
occasional problems in the Makefiles of various packages, it
can sometimes get out of sync with the info pages installed
on the system. If the <tt class=
"filename">/usr/share/info/dir</tt> file ever needs to be
recreated, the following optional commands will accomplish
the task:
</p>
<pre class="userinput"><kbd class="command">cd /usr/share/info
rm dir
for f in *
do install-info $f dir 2&gt;/dev/null
done</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-texinfo" name="contents-texinfo"></a>
<h3 class="sect2">
6.34.2. Contents of Texinfo
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">info,
infokey, install-info, makeinfo, texi2dvi, texi2pdf, and
texindex</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3504840" name="id3504840"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="info" name="info"></a><span class=
"term"><span><strong class=
"command">info</strong></span></span>
</td>
<td>
<p>
Used to read info pages which are similar to man
pages, but often go much deeper than just
explaining all the available command line options.
For example, compare <span><strong class=
"command">man bison</strong></span> and
<span><strong class="command">info
bison</strong></span>.
</p>
</td>
</tr>
<tr>
<td>
<a id="infokey" name="infokey"></a><span class=
"term"><span><strong class=
"command">infokey</strong></span></span>
</td>
<td>
<p>
Compiles a source file containing Info
customizations into a binary format
</p>
</td>
</tr>
<tr>
<td>
<a id="install-info" name=
"install-info"></a><span class=
"term"><span><strong class=
"command">install-info</strong></span></span>
</td>
<td>
<p>
Used to install info pages; it updates entries in
the <span><strong class=
"command">info</strong></span> index file
</p>
</td>
</tr>
<tr>
<td>
<a id="makeinfo" name="makeinfo"></a><span class=
"term"><span><strong class=
"command">makeinfo</strong></span></span>
</td>
<td>
<p>
Translates the given Texinfo source documents into
info pages, plain text, or HTML
</p>
</td>
</tr>
<tr>
<td>
<a id="texi2dvi" name="texi2dvi"></a><span class=
"term"><span><strong class=
"command">texi2dvi</strong></span></span>
</td>
<td>
<p>
Used to format the given Texinfo document into a
device-independent file that can be printed
</p>
</td>
</tr>
<tr>
<td>
<a id="texi2pdf" name="texi2pdf"></a><span class=
"term"><span><strong class=
"command">texi2pdf</strong></span></span>
</td>
<td>
<p>
Used to format the given Texinfo document into a
Portable Document Format (PDF) file
</p>
</td>
</tr>
<tr>
<td>
<a id="texindex" name="texindex"></a><span class=
"term"><span><strong class=
"command">texindex</strong></span></span>
</td>
<td>
<p>
Used to sort Texinfo index files
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-autoconf" name=
"ch-system-autoconf"></a>6.35.&nbsp;Autoconf-2.59
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Autoconf package contains programs for producing shell
scripts that can automatically configure source code.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.5 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">8.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Coreutils,
Diffutils, Grep, M4, Make, Perl, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.35.1. Installation of Autoconf
</h3>
</div>
<p>
Prepare Autoconf for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>. This takes a long
time, about 2 SBUs.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-autoconf" name="contents-autoconf"></a>
<h3 class="sect2">
6.35.2. Contents of Autoconf
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">autoconf,
autoheader, autom4te, autoreconf, autoscan, autoupdate,
and ifnames</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3505125" name="id3505125"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="autoconf" name="autoconf"></a><span class=
"term"><span><strong class=
"command">autoconf</strong></span></span>
</td>
<td>
<p>
Produces shell scripts that automatically configure
software source code packages to adapt to many
kinds of Unix-like systems. The configuration
scripts it produces are independent&mdash;running
them does not require the <span><strong class=
"command">autoconf</strong></span> program.
</p>
</td>
</tr>
<tr>
<td>
<a id="autoheader" name="autoheader"></a><span class=
"term"><span><strong class=
"command">autoheader</strong></span></span>
</td>
<td>
<p>
A tool for creating template files of C
<span class="emphasis"><em>#define</em></span>
statements for configure to use
</p>
</td>
</tr>
<tr>
<td>
<a id="autom4te" name="autom4te"></a><span class=
"term"><span><strong class=
"command">autom4te</strong></span></span>
</td>
<td>
<p>
A wrapper for the M4 macro processor
</p>
</td>
</tr>
<tr>
<td>
<a id="autoreconf" name="autoreconf"></a><span class=
"term"><span><strong class=
"command">autoreconf</strong></span></span>
</td>
<td>
<p>
Automatically runs <span><strong class=
"command">autoconf</strong></span>,
<span><strong class=
"command">autoheader</strong></span>,
<span><strong class=
"command">aclocal</strong></span>,
<span><strong class=
"command">automake</strong></span>,
<span><strong class=
"command">gettextize</strong></span>, and
<span><strong class=
"command">libtoolize</strong></span> in the correct
order to save time when changes are made to
<span><strong class=
"command">autoconf</strong></span> and
<span><strong class=
"command">automake</strong></span> template files
</p>
</td>
</tr>
<tr>
<td>
<a id="autoscan" name="autoscan"></a><span class=
"term"><span><strong class=
"command">autoscan</strong></span></span>
</td>
<td>
<p>
Helps to create a <tt class=
"filename">configure.in</tt> file for a software
package; it examines the source files in a
directory tree, searching them for common
portability issues, and creates a <tt class=
"filename">configure.scan</tt> file that serves as
as a preliminary <tt class=
"filename">configure.in</tt> file for the package
</p>
</td>
</tr>
<tr>
<td>
<a id="autoupdate" name="autoupdate"></a><span class=
"term"><span><strong class=
"command">autoupdate</strong></span></span>
</td>
<td>
<p>
Modifies a <tt class="filename">configure.in</tt>
file that still calls <span><strong class=
"command">autoconf</strong></span> macros by their
old names to use the current macro names
</p>
</td>
</tr>
<tr>
<td>
<a id="ifnames" name="ifnames"></a><span class=
"term"><span><strong class=
"command">ifnames</strong></span></span>
</td>
<td>
<p>
Helps when writing <tt class=
"filename">configure.in</tt> files for a software
package; it prints the identifiers that the package
uses in C preprocessor conditionals. If a package
has already been set up to have some portability,
this program can help determine what
<span><strong class=
"command">configure</strong></span> needs to check
for. It can also fill in gaps in a <tt class=
"filename">configure.in</tt> file generated by
<span><strong class=
"command">autoscan</strong></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-automake" name=
"ch-system-automake"></a>6.36.&nbsp;Automake-1.9.5
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Automake package contains programs for generating
Makefiles for use with Autoconf.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">8.8 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Autoconf, Bash,
Coreutils, Diffutils, Grep, M4, Make, Perl, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.36.1. Installation of Automake
</h3>
</div>
<p>
Prepare Automake for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>. This takes a long
time, about 5 SBUs.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-automake" name="contents-automake"></a>
<h3 class="sect2">
6.36.2. Contents of Automake
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">acinstall,
aclocal, aclocal-1.9.5, automake, automake-1.9.5,
compile, config.guess, config.sub, depcomp, elisp-comp,
install-sh, mdate-sh, missing, mkinstalldirs, py-compile,
symlink-tree, and ylwrap</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3505467" name="id3505467"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="acinstall" name="acinstall"></a><span class=
"term"><span><strong class=
"command">acinstall</strong></span></span>
</td>
<td>
<p>
A script that installs aclocal-style M4 files
</p>
</td>
</tr>
<tr>
<td>
<a id="aclocal" name="aclocal"></a><span class=
"term"><span><strong class=
"command">aclocal</strong></span></span>
</td>
<td>
<p>
Generates <tt class="filename">aclocal.m4</tt>
files based on the contents of <tt class=
"filename">configure.in</tt> files
</p>
</td>
</tr>
<tr>
<td>
<a id="aclocal-version" name=
"aclocal-version"></a><span class=
"term"><span><strong class=
"command">aclocal-1.9.5</strong></span></span>
</td>
<td>
<p>
A hard link to <span><strong class=
"command">aclocal</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="automake" name="automake"></a><span class=
"term"><span><strong class=
"command">automake</strong></span></span>
</td>
<td>
<p>
A tool for automatically generating <tt class=
"filename">Makefile.in</tt> files from <tt class=
"filename">Makefile.am</tt> files. To create all
the <tt class="filename">Makefile.in</tt> files for
a package, run this program in the top-level
directory. By scanning the <tt class=
"filename">configure.in</tt> file, it automatically
finds each appropriate <tt class=
"filename">Makefile.am</tt> file and generates the
corresponding <tt class="filename">Makefile.in</tt>
file
</p>
</td>
</tr>
<tr>
<td>
<a id="automake-version" name=
"automake-version"></a><span class=
"term"><span><strong class=
"command">automake-1.9.5</strong></span></span>
</td>
<td>
<p>
A hard link to <span><strong class=
"command">automake</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="compile" name="compile"></a><span class=
"term"><span><strong class=
"command">compile</strong></span></span>
</td>
<td>
<p>
A wrapper for compilers
</p>
</td>
</tr>
<tr>
<td>
<a id="config.guess" name=
"config.guess"></a><span class=
"term"><span><strong class=
"command">config.guess</strong></span></span>
</td>
<td>
<p>
A script that attempts to guess the canonical
triplet for the given build, host, or target
architecture
</p>
</td>
</tr>
<tr>
<td>
<a id="config.sub" name="config.sub"></a><span class=
"term"><span><strong class=
"command">config.sub</strong></span></span>
</td>
<td>
<p>
A configuration validation subroutine script
</p>
</td>
</tr>
<tr>
<td>
<a id="depcomp" name="depcomp"></a><span class=
"term"><span><strong class=
"command">depcomp</strong></span></span>
</td>
<td>
<p>
A script for compiling a program so that dependency
information is generated in addition to the desired
output
</p>
</td>
</tr>
<tr>
<td>
<a id="elisp-comp" name="elisp-comp"></a><span class=
"term"><span><strong class=
"command">elisp-comp</strong></span></span>
</td>
<td>
<p>
Byte-compiles Emacs Lisp code
</p>
</td>
</tr>
<tr>
<td>
<a id="install-sh" name="install-sh"></a><span class=
"term"><span><strong class=
"command">install-sh</strong></span></span>
</td>
<td>
<p>
A script that installs a program, script, or data
file
</p>
</td>
</tr>
<tr>
<td>
<a id="mdate-sh" name="mdate-sh"></a><span class=
"term"><span><strong class=
"command">mdate-sh</strong></span></span>
</td>
<td>
<p>
A script that prints the modification time of a
file or directory
</p>
</td>
</tr>
<tr>
<td>
<a id="missing" name="missing"></a><span class=
"term"><span><strong class=
"command">missing</strong></span></span>
</td>
<td>
<p>
A script acting as a common stub for missing GNU
programs during an installation
</p>
</td>
</tr>
<tr>
<td>
<a id="mkinstalldirs" name=
"mkinstalldirs"></a><span class=
"term"><span><strong class=
"command">mkinstalldirs</strong></span></span>
</td>
<td>
<p>
A script that creates a directory tree
</p>
</td>
</tr>
<tr>
<td>
<a id="py-compile" name="py-compile"></a><span class=
"term"><span><strong class=
"command">py-compile</strong></span></span>
</td>
<td>
<p>
Compiles a Python program
</p>
</td>
</tr>
<tr>
<td>
<a id="symlink-tree" name=
"symlink-tree"></a><span class=
"term"><span><strong class=
"command">symlink-tree</strong></span></span>
</td>
<td>
<p>
A script to create a symlink tree of a directory
tree
</p>
</td>
</tr>
<tr>
<td>
<a id="ylwrap" name="ylwrap"></a><span class=
"term"><span><strong class=
"command">ylwrap</strong></span></span>
</td>
<td>
<p>
A wrapper for <span><strong class=
"command">lex</strong></span> and
<span><strong class="command">yacc</strong></span>
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-bash" name=
"ch-system-bash"></a>6.37.&nbsp;Bash-3.0
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Bash package contains the Bourne-Again SHell.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">1.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">20.6 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Binutils,
Coreutils, Diffutils, Gawk, GCC, Glibc, Grep, Make,
Ncurses, and Sed.</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.37.1. Installation of Bash
</h3>
</div>
<p>
If you downloaded the Bash documentation tarball and wish to
install HTML documentation, issue the following commands:
</p>
<pre class="userinput"><kbd class=
"command">tar -xvf ../bash-doc-3.0.tar.gz &amp;&amp;
sed -i "s|htmldir = @htmldir@|htmldir = /usr/share/doc/bash-3.0|" \
Makefile.in</kbd></pre>
<p>
The following patch fixes various issues, including a problem
where Bash will sometimes only show 33 characters on a line,
then wrap to the next:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../bash-3.0-fixes-3.patch</kbd></pre>
<p>
Bash also has issues when compiled against newer versions of
Glibc. The following patch resolves this problem:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../bash-3.0-avoid_WCONTINUED-1.patch</kbd></pre>
<p>
Prepare Bash for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --bindir=/bin \
--without-bash-malloc --with-installed-readline</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-installed-readline</tt></em></span>
</dt>
<dd>
<p>
This option tells Bash to use the <tt class=
"filename">readline</tt> library that is already
installed on the system rather than using its own
readline version.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make tests</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Run the newly compiled <span><strong class=
"command">bash</strong></span> program (replacing the one
that is currently being executed):
</p>
<pre class="userinput"><kbd class=
"command">exec /bin/bash --login +h</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
The parameters used make the <span><strong class=
"command">bash</strong></span> process an interactive
login shell and continue to disable hashing so that new
programs are found as they become available.
</p>
</div>
</div>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-bash" name="contents-bash"></a>
<h3 class="sect2">
6.37.2. Contents of Bash
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">bash,
bashbug, and sh (link to bash)</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3506073" name="id3506073"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="bash" name="bash"></a><span class=
"term"><span><strong class=
"command">bash</strong></span></span>
</td>
<td>
<p>
A widely-used command interpreter; it performs many
types of expansions and substitutions on a given
command line before executing it, thus making this
interpreter a powerful tool
</p>
</td>
</tr>
<tr>
<td>
<a id="bashbug" name="bashbug"></a><span class=
"term"><span><strong class=
"command">bashbug</strong></span></span>
</td>
<td>
<p>
A shell script to help the user compose and mail
standard formatted bug reports concerning
<span><strong class="command">bash</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="sh" name="sh"></a><span class=
"term"><span><strong class=
"command">sh</strong></span></span>
</td>
<td>
<p>
A symlink to the <span><strong class=
"command">bash</strong></span> program; when
invoked as <span><strong class=
"command">sh</strong></span>, <span><strong class=
"command">bash</strong></span> tries to mimic the
startup behavior of historical versions of
<span><strong class="command">sh</strong></span> as
closely as possible, while conforming to the POSIX
standard as well
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-file" name=
"ch-system-file"></a>6.38.&nbsp;File-4.13
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The File package contains a utility for determining the type
of a given file or files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">6.2 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, Sed, and
Zlib</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.38.1. Installation of File
</h3>
</div>
<p>
Prepare File for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-file" name="contents-file"></a>
<h3 class="sect2">
6.38.2. Contents of File
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">file</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
library:</span></strong> <span class=
"seg">libmagic.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3506207" name="id3506207"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="file" name="file"></a><span class=
"term"><span><strong class=
"command">file</strong></span></span>
</td>
<td>
<p>
Tries to classify each given file; it does this by
performing several tests&mdash;file system tests,
magic number tests, and language tests
</p>
</td>
</tr>
<tr>
<td>
<a id="libmagic" name="libmagic"></a><span class=
"term"><tt class="filename">libmagic</tt></span>
</td>
<td>
<p>
Contains routines for magic number recognition,
used by the <span><strong class=
"command">file</strong></span> program
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-libtool" name=
"ch-system-libtool"></a>6.39.&nbsp;Libtool-1.5.14
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Libtool package contains the GNU generic library support
script. It wraps the complexity of using shared libraries in
a consistent, portable interface.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">1.5 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">19.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.39.1. Installation of Libtool
</h3>
</div>
<p>
Prepare Libtool for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-libtool" name="contents-libtool"></a>
<h3 class="sect2">
6.39.2. Contents of Libtool
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">libtool and
libtoolize</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libltdl.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3506269" name="id3506269"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="libtool" name="libtool"></a><span class=
"term"><span><strong class=
"command">libtool</strong></span></span>
</td>
<td>
<p>
Provides generalized library-building support
services
</p>
</td>
</tr>
<tr>
<td>
<a id="libtoolize" name="libtoolize"></a><span class=
"term"><span><strong class=
"command">libtoolize</strong></span></span>
</td>
<td>
<p>
Provides a standard way to add <span><strong class=
"command">libtool</strong></span> support to a
package
</p>
</td>
</tr>
<tr>
<td>
<a id="libltdl" name="libltdl"></a><span class=
"term"><tt class="filename">libltdl</tt></span>
</td>
<td>
<p>
Hides the various difficulties of dlopening
libraries
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-bzip2" name=
"ch-system-bzip2"></a>6.40.&nbsp;Bzip2-1.0.3
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Bzip2 package contains programs for compressing and
decompressing files. Compressing text files with
<span><strong class="command">bzip2</strong></span> yields a
much better compression percentage than with the traditional
<span><strong class="command">gzip</strong></span>.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">3.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, and Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.40.1. Installation of Bzip2
</h3>
</div>
<p>
Apply a patch to install the documentation for this package:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../bzip2-1.0.3-install_docs-1.patch</kbd></pre>
<p>
The <span><strong class="command">bzgrep</strong></span>
command does not escape '|' and '&amp;' in filenames passed
to it. This allows arbitrary commands to be executed with the
privileges of the user running <span><strong class=
"command">bzgrep</strong></span>. Apply the following to
address this:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../bzip2-1.0.3-bzgrep_security-1.patch</kbd></pre>
<p>
Prepare Bzip2 for compilation with:
</p>
<pre class="userinput"><kbd class=
"command">make -f Makefile-libbz2_so
make clean</kbd></pre>
<p>
The <em class="parameter"><tt>-f</tt></em> flag will cause
Bzip2 to be built using a different <tt class=
"filename">Makefile</tt> file, in this case the <tt class=
"filename">Makefile-libbz2_so</tt> file, which creates a
dynamic <tt class="filename">libbz2.so</tt> library and links
the Bzip2 utilities against it.
</p>
<p>
Compile and test the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
If reinstalling Bzip2, perform <strong class=
"userinput"><tt>rm -vf /usr/bin/bz*</tt></strong> first,
otherwise the following <span><strong class="command">make
install</strong></span> will fail.
</p>
<p>
Install the programs:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Install the shared <span><strong class=
"command">bzip2</strong></span> binary into the <tt class=
"filename">/bin</tt> directory, make some necessary symbolic
links, and clean up:
</p>
<pre class="userinput"><kbd class=
"command">cp -v bzip2-shared /bin/bzip2
cp -av libbz2.so* /lib
ln -sv ../../lib/libbz2.so.1.0 /usr/lib/libbz2.so
rm -v /usr/bin/{bunzip2,bzcat,bzip2}
ln -sv bzip2 /bin/bunzip2
ln -sv bzip2 /bin/bzcat</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-bzip2" name="contents-bzip2"></a>
<h3 class="sect2">
6.40.2. Contents of Bzip2
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">bunzip2 (link
to bzip2), bzcat (link to bzip2), bzcmp, bzdiff, bzegrep,
bzfgrep, bzgrep, bzip2, bzip2recover, bzless, and
bzmore</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libbz2.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3506649" name="id3506649"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="bunzip2" name="bunzip2"></a><span class=
"term"><span><strong class=
"command">bunzip2</strong></span></span>
</td>
<td>
<p>
Decompresses bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzcat" name="bzcat"></a><span class=
"term"><span><strong class=
"command">bzcat</strong></span></span>
</td>
<td>
<p>
Decompresses to standard output
</p>
</td>
</tr>
<tr>
<td>
<a id="bzcmp" name="bzcmp"></a><span class=
"term"><span><strong class=
"command">bzcmp</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">cmp</strong></span> on bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzdiff" name="bzdiff"></a><span class=
"term"><span><strong class=
"command">bzdiff</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">diff</strong></span> on bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzgrep" name="bzgrep"></a><span class=
"term"><span><strong class=
"command">bzgrep</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">grep</strong></span> on bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzegrep" name="bzegrep"></a><span class=
"term"><span><strong class=
"command">bzegrep</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">egrep</strong></span> on bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzfgrep" name="bzfgrep"></a><span class=
"term"><span><strong class=
"command">bzfgrep</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">fgrep</strong></span> on bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzip2" name="bzip2"></a><span class=
"term"><span><strong class=
"command">bzip2</strong></span></span>
</td>
<td>
<p>
Compresses files using the Burrows-Wheeler block
sorting text compression algorithm with Huffman
coding; the compression rate is better than that
achieved by more conventional compressors using
&ldquo;<span class="quote">Lempel-Ziv</span>&rdquo;
algorithms, like <span><strong class=
"command">gzip</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="bzip2recover" name=
"bzip2recover"></a><span class=
"term"><span><strong class=
"command">bzip2recover</strong></span></span>
</td>
<td>
<p>
Tries to recover data from damaged bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzless" name="bzless"></a><span class=
"term"><span><strong class=
"command">bzless</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">less</strong></span> on bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="bzmore" name="bzmore"></a><span class=
"term"><span><strong class=
"command">bzmore</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">more</strong></span> on bzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="libbz2" name="libbz2"></a><span class=
"term"><tt class="filename">libbz2*</tt></span>
</td>
<td>
<p>
The library implementing lossless, block-sorting
data compression, using the Burrows-Wheeler
algorithm
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-diffutils" name=
"ch-system-diffutils"></a>6.41.&nbsp;Diffutils-2.8.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Diffutils package contains programs that show the
differences between files or directories.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">5.6 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.41.1. Installation of Diffutils
</h3>
</div>
<p>
Prepare Diffutils for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-diffutils" name="contents-diffutils"></a>
<h3 class="sect2">
6.41.2. Contents of Diffutils
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">cmp, diff,
diff3, and sdiff</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3507052" name="id3507052"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="cmp" name="cmp"></a><span class=
"term"><span><strong class=
"command">cmp</strong></span></span>
</td>
<td>
<p>
Compares two files and reports whether or in which
bytes they differ
</p>
</td>
</tr>
<tr>
<td>
<a id="diff" name="diff"></a><span class=
"term"><span><strong class=
"command">diff</strong></span></span>
</td>
<td>
<p>
Compares two files or directories and reports which
lines in the files differ
</p>
</td>
</tr>
<tr>
<td>
<a id="diff3" name="diff3"></a><span class=
"term"><span><strong class=
"command">diff3</strong></span></span>
</td>
<td>
<p>
Compares three files line by line
</p>
</td>
</tr>
<tr>
<td>
<a id="sdiff" name="sdiff"></a><span class=
"term"><span><strong class=
"command">sdiff</strong></span></span>
</td>
<td>
<p>
Merges two files and interactively outputs the
results
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-kbd" name=
"ch-system-kbd"></a>6.42.&nbsp;Kbd-1.12
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Kbd package contains key-table files and keyboard
utilities.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">11.8 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Bison, Coreutils, Diffutils, Flex, GCC, Gettext, Glibc,
Grep, Gzip, M4, Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.42.1. Installation of Kbd
</h3>
</div>
<p>
Prepare Kbd for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-kbd" name="contents-kbd"></a>
<h3 class="sect2">
6.42.2. Contents of Kbd
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">chvt,
deallocvt, dumpkeys, fgconsole, getkeycodes, getunimap,
kbd_mode, kbdrate, loadkeys, loadunimap, mapscrn, openvt,
psfaddtable (link to psfxtable), psfgettable (link to
psfxtable), psfstriptable (link to psfxtable), psfxtable,
resizecons, setfont, setkeycodes, setleds, setlogcons,
setmetamode, setvesablank, showconsolefont, showkey,
unicode_start, and unicode_stop</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3507243" name="id3507243"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="chvt" name="chvt"></a><span class=
"term"><span><strong class=
"command">chvt</strong></span></span>
</td>
<td>
<p>
Changes the foreground virtual terminal
</p>
</td>
</tr>
<tr>
<td>
<a id="deallocvt" name="deallocvt"></a><span class=
"term"><span><strong class=
"command">deallocvt</strong></span></span>
</td>
<td>
<p>
Deallocates unused virtual terminals
</p>
</td>
</tr>
<tr>
<td>
<a id="dumpkeys" name="dumpkeys"></a><span class=
"term"><span><strong class=
"command">dumpkeys</strong></span></span>
</td>
<td>
<p>
Dumps the keyboard translation tables
</p>
</td>
</tr>
<tr>
<td>
<a id="fgconsole" name="fgconsole"></a><span class=
"term"><span><strong class=
"command">fgconsole</strong></span></span>
</td>
<td>
<p>
Prints the number of the active virtual terminal
</p>
</td>
</tr>
<tr>
<td>
<a id="getkeycodes" name=
"getkeycodes"></a><span class=
"term"><span><strong class=
"command">getkeycodes</strong></span></span>
</td>
<td>
<p>
Prints the kernel scancode-to-keycode mapping table
</p>
</td>
</tr>
<tr>
<td>
<a id="getunimap" name="getunimap"></a><span class=
"term"><span><strong class=
"command">getunimap</strong></span></span>
</td>
<td>
<p>
Prints the currently used unicode-to-font mapping
table
</p>
</td>
</tr>
<tr>
<td>
<a id="kbd_mode" name="kbd_mode"></a><span class=
"term"><span><strong class=
"command">kbd_mode</strong></span></span>
</td>
<td>
<p>
Reports or sets the keyboard mode
</p>
</td>
</tr>
<tr>
<td>
<a id="kbdrate" name="kbdrate"></a><span class=
"term"><span><strong class=
"command">kbdrate</strong></span></span>
</td>
<td>
<p>
Sets the keyboard repeat and delay rates
</p>
</td>
</tr>
<tr>
<td>
<a id="loadkeys" name="loadkeys"></a><span class=
"term"><span><strong class=
"command">loadkeys</strong></span></span>
</td>
<td>
<p>
Loads the keyboard translation tables
</p>
</td>
</tr>
<tr>
<td>
<a id="loadunimap" name="loadunimap"></a><span class=
"term"><span><strong class=
"command">loadunimap</strong></span></span>
</td>
<td>
<p>
Loads the kernel unicode-to-font mapping table
</p>
</td>
</tr>
<tr>
<td>
<a id="mapscrn" name="mapscrn"></a><span class=
"term"><span><strong class=
"command">mapscrn</strong></span></span>
</td>
<td>
<p>
An obsolete program that used to load a
user-defined output character mapping table into
the console driver; this is now done by
<span><strong class=
"command">setfont</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="openvt" name="openvt"></a><span class=
"term"><span><strong class=
"command">openvt</strong></span></span>
</td>
<td>
<p>
Starts a program on a new virtual terminal (VT)
</p>
</td>
</tr>
<tr>
<td>
<a id="psfaddtable" name=
"psfaddtable"></a><span class=
"term"><span><strong class=
"command">psfaddtable</strong></span></span>
</td>
<td>
<p>
A link to <span><strong class=
"command">psfxtable</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="psfgettable" name=
"psfgettable"></a><span class=
"term"><span><strong class=
"command">psfgettable</strong></span></span>
</td>
<td>
<p>
A link to <span><strong class=
"command">psfxtable</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="psfstriptable" name=
"psfstriptable"></a><span class=
"term"><span><strong class=
"command">psfstriptable</strong></span></span>
</td>
<td>
<p>
A link to <span><strong class=
"command">psfxtable</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="psfxtable" name="psfxtable"></a><span class=
"term"><span><strong class=
"command">psfxtable</strong></span></span>
</td>
<td>
<p>
Handle Unicode character tables for console fonts
</p>
</td>
</tr>
<tr>
<td>
<a id="resizecons" name="resizecons"></a><span class=
"term"><span><strong class=
"command">resizecons</strong></span></span>
</td>
<td>
<p>
Changes the kernel idea of the console size
</p>
</td>
</tr>
<tr>
<td>
<a id="setfont" name="setfont"></a><span class=
"term"><span><strong class=
"command">setfont</strong></span></span>
</td>
<td>
<p>
Changes the Enhanced Graphic Adapter (EGA) and
Video Graphics Array (VGA) fonts on the console
</p>
</td>
</tr>
<tr>
<td>
<a id="setkeycodes" name=
"setkeycodes"></a><span class=
"term"><span><strong class=
"command">setkeycodes</strong></span></span>
</td>
<td>
<p>
Loads kernel scancode-to-keycode mapping table
entries; this is useful if there are unusual keys
on the keyboard
</p>
</td>
</tr>
<tr>
<td>
<a id="setleds" name="setleds"></a><span class=
"term"><span><strong class=
"command">setleds</strong></span></span>
</td>
<td>
<p>
Sets the keyboard flags and Light Emitting Diodes
(LEDs)
</p>
</td>
</tr>
<tr>
<td>
<a id="setlogcons" name="setlogcons"></a><span class=
"term"><span><strong class=
"command">setlogcons</strong></span></span>
</td>
<td>
<p>
Sends kernel messages to the console
</p>
</td>
</tr>
<tr>
<td>
<a id="setmetamode" name=
"setmetamode"></a><span class=
"term"><span><strong class=
"command">setmetamode</strong></span></span>
</td>
<td>
<p>
Defines the keyboard meta-key handling
</p>
</td>
</tr>
<tr>
<td>
<a id="setvesablank" name=
"setvesablank"></a><span class=
"term"><span><strong class=
"command">setvesablank</strong></span></span>
</td>
<td>
<p>
Lets the user adjust the built-in hardware
screensaver (a blank screen)
</p>
</td>
</tr>
<tr>
<td>
<a id="showconsolefont" name=
"showconsolefont"></a><span class=
"term"><span><strong class=
"command">showconsolefont</strong></span></span>
</td>
<td>
<p>
Shows the current EGA/VGA console screen font
</p>
</td>
</tr>
<tr>
<td>
<a id="showkey" name="showkey"></a><span class=
"term"><span><strong class=
"command">showkey</strong></span></span>
</td>
<td>
<p>
Reports the scancodes, keycodes, and ASCII codes of
the keys pressed on the keyboard
</p>
</td>
</tr>
<tr>
<td>
<a id="unicode_start" name=
"unicode_start"></a><span class=
"term"><span><strong class=
"command">unicode_start</strong></span></span>
</td>
<td>
<p>
Puts the keyboard and console in UNICODE mode.
Never use it on LFS, because applications are not
configured to support UNICODE.
</p>
</td>
</tr>
<tr>
<td>
<a id="unicode_stop" name=
"unicode_stop"></a><span class=
"term"><span><strong class=
"command">unicode_stop</strong></span></span>
</td>
<td>
<p>
Reverts keyboard and console from UNICODE mode
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-e2fsprogs" name=
"ch-system-e2fsprogs"></a>6.43.&nbsp;E2fsprogs-1.37
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The E2fsprogs package contains the utilities for handling the
<tt class="systemitem">ext2</tt> file system. It also
supports the <tt class="systemitem">ext3</tt> journaling file
system.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.6 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">40.0 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, Gawk, GCC, Gettext, Glibc, Grep,
Make, Sed, and Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.43.1. Installation of E2fsprogs
</h3>
</div>
<p>
Fix a compilation error in E2fsprogs' testsuite:
</p>
<pre class="userinput"><kbd class=
"command">sed -i -e 's/-DTEST/$(ALL_CFLAGS) &amp;/' lib/e2p/Makefile.in</kbd></pre>
<p>
It is recommended that E2fsprogs be built in a subdirectory
of the source tree:
</p>
<pre class="userinput"><kbd class="command">mkdir -v build
cd build</kbd></pre>
<p>
Prepare E2fsprogs for compilation:
</p>
<pre class="userinput"><kbd class=
"command">../configure --prefix=/usr --with-root-prefix="" \
--enable-elf-shlibs --disable-evms</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--with-root-prefix=""</tt></em></span>
</dt>
<dd>
<p>
Certain programs (such as the <span><strong class=
"command">e2fsck</strong></span> program) are
considered essential programs. When, for example,
<tt class="filename">/usr</tt> is not mounted, these
programs still need to be available. They belong in
directories like <tt class="filename">/lib</tt> and
<tt class="filename">/sbin</tt>. If this option is not
passed to E2fsprogs' configure, the programs are
installed into the <tt class="filename">/usr</tt>
directory.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-elf-shlibs</tt></em></span>
</dt>
<dd>
<p>
This creates the shared libraries which some programs
in this package use.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>--disable-evms</tt></em></span>
</dt>
<dd>
<p>
This disables the building of the Enterprise Volume
Management System (EVMS) plugin. This plugin is not
up-to-date with the latest EVMS internal interfaces and
EVMS is not installed as part of a base LFS system, so
the plugin is not required. See the EVMS website at
<a href=
"http://evms.sourceforge.net/"><i>http://evms.sourceforge.net/</i></a>
for more information regarding EVMS.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the binaries and documentation:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Install the shared libraries:
</p>
<pre class="userinput"><kbd class=
"command">make install-libs</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-e2fsprogs" name="contents-e2fsprogs"></a>
<h3 class="sect2">
6.43.2. Contents of E2fsprogs
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">badblocks,
blkid, chattr, compile_et, debugfs, dumpe2fs, e2fsck,
e2image, e2label, findfs, fsck, fsck.ext2, fsck.ext3,
logsave, lsattr, mk_cmds, mke2fs, mkfs.ext2, mkfs.ext3,
mklost+found, resize2fs, tune2fs, and uuidgen.</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libblkid.[a,so], libcom_err.[a,so], libe2p.[a,so],
libext2fs.[a,so], libss.[a,so], and libuuid.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3507145" name="id3507145"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="badblocks" name="badblocks"></a><span class=
"term"><span><strong class=
"command">badblocks</strong></span></span>
</td>
<td>
<p>
Searches a device (usually a disk partition) for
bad blocks
</p>
</td>
</tr>
<tr>
<td>
<a id="blkid" name="blkid"></a><span class=
"term"><span><strong class=
"command">blkid</strong></span></span>
</td>
<td>
<p>
A command line utility to locate and print block
device attributes
</p>
</td>
</tr>
<tr>
<td>
<a id="chattr" name="chattr"></a><span class=
"term"><span><strong class=
"command">chattr</strong></span></span>
</td>
<td>
<p>
Changes the attributes of files on an <tt class=
"systemitem">ext2</tt> file system; it also changes
<tt class="systemitem">ext3</tt> file systems, the
journaling version of <tt class=
"systemitem">ext2</tt> file systems
</p>
</td>
</tr>
<tr>
<td>
<a id="compile_et" name="compile_et"></a><span class=
"term"><span><strong class=
"command">compile_et</strong></span></span>
</td>
<td>
<p>
An error table compiler; it converts a table of
error-code names and messages into a C source file
suitable for use with the <tt class=
"filename">com_err</tt> library
</p>
</td>
</tr>
<tr>
<td>
<a id="debugfs" name="debugfs"></a><span class=
"term"><span><strong class=
"command">debugfs</strong></span></span>
</td>
<td>
<p>
A file system debugger; it can be used to examine
and change the state of an <tt class=
"systemitem">ext2</tt> file system
</p>
</td>
</tr>
<tr>
<td>
<a id="dumpe2fs" name="dumpe2fs"></a><span class=
"term"><span><strong class=
"command">dumpe2fs</strong></span></span>
</td>
<td>
<p>
Prints the super block and blocks group information
for the file system present on a given device
</p>
</td>
</tr>
<tr>
<td>
<a id="e2fsck" name="e2fsck"></a><span class=
"term"><span><strong class=
"command">e2fsck</strong></span></span>
</td>
<td>
<p>
Is used to check, and optionally repair <tt class=
"systemitem">ext2</tt> file systems and <tt class=
"systemitem">ext3</tt> file systems
</p>
</td>
</tr>
<tr>
<td>
<a id="e2image" name="e2image"></a><span class=
"term"><span><strong class=
"command">e2image</strong></span></span>
</td>
<td>
<p>
Is used to save critical <tt class=
"systemitem">ext2</tt> file system data to a file
</p>
</td>
</tr>
<tr>
<td>
<a id="e2label" name="e2label"></a><span class=
"term"><span><strong class=
"command">e2label</strong></span></span>
</td>
<td>
<p>
Displays or changes the file system label on the
<tt class="systemitem">ext2</tt> file system
present on a given device
</p>
</td>
</tr>
<tr>
<td>
<a id="findfs" name="findfs"></a><span class=
"term"><span><strong class=
"command">findfs</strong></span></span>
</td>
<td>
<p>
Finds a file system by label or Universally Unique
Identifier (UUID)
</p>
</td>
</tr>
<tr>
<td>
<a id="fsck" name="fsck"></a><span class=
"term"><span><strong class=
"command">fsck</strong></span></span>
</td>
<td>
<p>
Is used to check, and optionally repair, file
systems
</p>
</td>
</tr>
<tr>
<td>
<a id="fsck.ext2" name="fsck.ext2"></a><span class=
"term"><span><strong class=
"command">fsck.ext2</strong></span></span>
</td>
<td>
<p>
By default checks <tt class="systemitem">ext2</tt>
file systems
</p>
</td>
</tr>
<tr>
<td>
<a id="fsck.ext3" name="fsck.ext3"></a><span class=
"term"><span><strong class=
"command">fsck.ext3</strong></span></span>
</td>
<td>
<p>
By default checks <tt class="systemitem">ext3</tt>
file systems
</p>
</td>
</tr>
<tr>
<td>
<a id="logsave" name="logsave"></a><span class=
"term"><span><strong class=
"command">logsave</strong></span></span>
</td>
<td>
<p>
Saves the output of a command in a log file
</p>
</td>
</tr>
<tr>
<td>
<a id="lsattr" name="lsattr"></a><span class=
"term"><span><strong class=
"command">lsattr</strong></span></span>
</td>
<td>
<p>
Lists the attributes of files on a second extended
file system
</p>
</td>
</tr>
<tr>
<td>
<a id="mk_cmds" name="mk_cmds"></a><span class=
"term"><span><strong class=
"command">mk_cmds</strong></span></span>
</td>
<td>
<p>
Converts a table of command names and help messages
into a C source file suitable for use with the
<tt class="filename">libss</tt> subsystem library
</p>
</td>
</tr>
<tr>
<td>
<a id="mke2fs" name="mke2fs"></a><span class=
"term"><span><strong class=
"command">mke2fs</strong></span></span>
</td>
<td>
<p>
Creates an ext2 or ext3 file system on the given
device
</p>
</td>
</tr>
<tr>
<td>
<a id="mkfs.ext2" name="mkfs.ext2"></a><span class=
"term"><span><strong class=
"command">mkfs.ext2</strong></span></span>
</td>
<td>
<p>
By default creates <tt class="systemitem">ext2</tt>
file systems
</p>
</td>
</tr>
<tr>
<td>
<a id="mkfs.ext3" name="mkfs.ext3"></a><span class=
"term"><span><strong class=
"command">mkfs.ext3</strong></span></span>
</td>
<td>
<p>
By default creates <tt class="systemitem">ext3</tt>
file systems
</p>
</td>
</tr>
<tr>
<td>
<a id="mklost-found" name=
"mklost-found"></a><span class=
"term"><span><strong class=
"command">mklost+found</strong></span></span>
</td>
<td>
<p>
Used to create a <tt class=
"filename">lost+found</tt> directory on an
<tt class="systemitem">ext2</tt> file system; it
pre-allocates disk blocks to this directory to
lighten the task of <span><strong class=
"command">e2fsck</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="resize2fs" name="resize2fs"></a><span class=
"term"><span><strong class=
"command">resize2fs</strong></span></span>
</td>
<td>
<p>
Can be used to enlarge or shrink an <tt class=
"systemitem">ext2</tt> file system
</p>
</td>
</tr>
<tr>
<td>
<a id="tune2fs" name="tune2fs"></a><span class=
"term"><span><strong class=
"command">tune2fs</strong></span></span>
</td>
<td>
<p>
Adjusts tunable file system parameters on an
<tt class="systemitem">ext2</tt> file system
</p>
</td>
</tr>
<tr>
<td>
<a id="uuidgen" name="uuidgen"></a><span class=
"term"><span><strong class=
"command">uuidgen</strong></span></span>
</td>
<td>
<p>
Creates new UUIDs. Each new UUID can reasonably be
considered unique among all UUIDs created, on the
local system and on other systems, in the past and
in the future
</p>
</td>
</tr>
<tr>
<td>
<a id="libblkid" name="libblkid"></a><span class=
"term"><tt class="filename">libblkid</tt></span>
</td>
<td>
<p>
Contains routines for device identification and
token extraction
</p>
</td>
</tr>
<tr>
<td>
<a id="libcom_err" name="libcom_err"></a><span class=
"term"><tt class="filename">libcom_err</tt></span>
</td>
<td>
<p>
The common error display routine
</p>
</td>
</tr>
<tr>
<td>
<a id="libe2p" name="libe2p"></a><span class=
"term"><tt class="filename">libe2p</tt></span>
</td>
<td>
<p>
Used by <span><strong class=
"command">dumpe2fs</strong></span>,
<span><strong class=
"command">chattr</strong></span>, and
<span><strong class=
"command">lsattr</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="libext2fs" name="libext2fs"></a><span class=
"term"><tt class="filename">libext2fs</tt></span>
</td>
<td>
<p>
Contains routines to enable user-level programs to
manipulate an <tt class="systemitem">ext2</tt> file
system
</p>
</td>
</tr>
<tr>
<td>
<a id="libss" name="libss"></a><span class=
"term"><tt class="filename">libss</tt></span>
</td>
<td>
<p>
Used by <span><strong class=
"command">debugfs</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="libuuid" name="libuuid"></a><span class=
"term"><tt class="filename">libuuid</tt></span>
</td>
<td>
<p>
Contains routines for generating unique identifiers
for objects that may be accessible beyond the local
system
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-grep" name=
"ch-system-grep"></a>6.44.&nbsp;Grep-2.5.1a
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Grep package contains programs for searching through
files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">4.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Make, Sed, and
Texinfo</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.44.1. Installation of Grep
</h3>
</div>
<p>
Prepare Grep for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --bindir=/bin</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-grep" name="contents-grep"></a>
<h3 class="sect2">
6.44.2. Contents of Grep
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">egrep (link
to grep), fgrep (link to grep), and grep</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3508916" name="id3508916"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="egrep" name="egrep"></a><span class=
"term"><span><strong class=
"command">egrep</strong></span></span>
</td>
<td>
<p>
Prints lines matching an extended regular
expression
</p>
</td>
</tr>
<tr>
<td>
<a id="fgrep" name="fgrep"></a><span class=
"term"><span><strong class=
"command">fgrep</strong></span></span>
</td>
<td>
<p>
Prints lines matching a list of fixed strings
</p>
</td>
</tr>
<tr>
<td>
<a id="grep" name="grep"></a><span class=
"term"><span><strong class=
"command">grep</strong></span></span>
</td>
<td>
<p>
Prints lines matching a basic regular expression
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-grub" name=
"ch-system-grub"></a>6.45.&nbsp;GRUB-0.96
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The GRUB package contains the GRand Unified Bootloader.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">10.0 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, Ncurses,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.45.1. Installation of GRUB
</h3>
</div>
<p>
This package is known to have issues when its default
optimization flags (including the <em class=
"parameter"><tt>-march</tt></em> and <em class=
"parameter"><tt>-mcpu</tt></em> options) are changed. If any
environment variables that override default optimizations
have been defined, such as <tt class="envar">CFLAGS</tt> and
<tt class="envar">CXXFLAGS</tt>, unset them when building
GRUB.
</p>
<p>
Prepare GRUB for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Note that the test results will always show the error
&ldquo;<span class="quote">ufs2_stage1_5 is too
big.</span>&rdquo; This is due to a compiler issue, but can
be ignored unless you plan to boot from an UFS partition. The
partitions are normally only used by Sun workstations.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class="command">make install
mkdir -v /boot/grub
cp -v /usr/lib/grub/i386-pc/stage{1,2} /boot/grub</kbd></pre>
<p>
Replace <tt class="filename">i386-pc</tt> with whatever
directory is appropriate for the hardware in use.
</p>
<p>
The <tt class="filename">i386-pc</tt> directory contains a
number of <tt class="filename">*stage1_5</tt> files,
different ones for different file systems. Review the files
available and copy the appropriate ones to the <tt class=
"filename">/boot/grub</tt> directory. Most users will copy
the <tt class="filename">e2fs_stage1_5</tt> and/or <tt class=
"filename">reiserfs_stage1_5</tt> files.
</p>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-gRUB" name="contents-gRUB"></a>
<h3 class="sect2">
6.45.2. Contents of GRUB
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">grub,
grub-install, grub-md5-crypt, grub-terminfo, and
mbchk</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3509151" name="id3509151"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="grub" name="grub"></a><span class=
"term"><span><strong class=
"command">grub</strong></span></span>
</td>
<td>
<p>
The Grand Unified Bootloader's command shell
</p>
</td>
</tr>
<tr>
<td>
<a id="grub-install" name=
"grub-install"></a><span class=
"term"><span><strong class=
"command">grub-install</strong></span></span>
</td>
<td>
<p>
Installs GRUB on the given device
</p>
</td>
</tr>
<tr>
<td>
<a id="grub-md5-crypt" name=
"grub-md5-crypt"></a><span class=
"term"><span><strong class=
"command">grub-md5-crypt</strong></span></span>
</td>
<td>
<p>
Encrypts a password in MD5 format
</p>
</td>
</tr>
<tr>
<td>
<a id="grub-terminfo" name=
"grub-terminfo"></a><span class=
"term"><span><strong class=
"command">grub-terminfo</strong></span></span>
</td>
<td>
<p>
Generates a terminfo command from a terminfo name;
it can be employed if an unknown terminal is being
used
</p>
</td>
</tr>
<tr>
<td>
<a id="mbchk" name="mbchk"></a><span class=
"term"><span><strong class=
"command">mbchk</strong></span></span>
</td>
<td>
<p>
Checks the format of a multi-boot kernel
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-gzip" name=
"ch-system-gzip"></a>6.46.&nbsp;Gzip-1.3.5
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Gzip package contains programs for compressing and
decompressing files.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">2.2 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.46.1. Installation of Gzip
</h3>
</div>
<p>
Gzip has 2 known security vulnerabilities. The following
patch addresses both of them:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../gzip-1.3.5-security_fixes-1.patch</kbd></pre>
<p>
Prepare Gzip for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
The <span><strong class="command">gzexe</strong></span>
script has the location of the <span><strong class=
"command">gzip</strong></span> binary hard-wired into it.
Because the location of the binary is changed later, the
following command ensures that the new location gets placed
into the script:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's@"BINDIR"@/bin@g' gzexe.in</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Move the <span><strong class="command">gzip</strong></span>
program to the <tt class="filename">/bin</tt> directory and
create some commonly used symlinks to it:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /usr/bin/gzip /bin
rm -v /usr/bin/{gunzip,zcat}
ln -sv gzip /bin/gunzip
ln -sv gzip /bin/zcat
ln -sv gzip /bin/compress
ln -sv gunzip /bin/uncompress</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-gzip" name="contents-gzip"></a>
<h3 class="sect2">
6.46.2. Contents of Gzip
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">compress
(link to gzip), gunzip (link to gzip), gzexe, gzip,
uncompress (link to gunzip), zcat (link to gzip), zcmp,
zdiff, zegrep, zfgrep, zforce, zgrep, zless, zmore, and
znew</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3509397" name="id3509397"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="compress" name="compress"></a><span class=
"term"><span><strong class=
"command">compress</strong></span></span>
</td>
<td>
<p>
Compresses and decompresses files
</p>
</td>
</tr>
<tr>
<td>
<a id="gunzip" name="gunzip"></a><span class=
"term"><span><strong class=
"command">gunzip</strong></span></span>
</td>
<td>
<p>
Decompresses gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="gzexe" name="gzexe"></a><span class=
"term"><span><strong class=
"command">gzexe</strong></span></span>
</td>
<td>
<p>
Creates self-decompressing executable files
</p>
</td>
</tr>
<tr>
<td>
<a id="gzip" name="gzip"></a><span class=
"term"><span><strong class=
"command">gzip</strong></span></span>
</td>
<td>
<p>
Compresses the given files using Lempel-Ziv (LZ77)
coding
</p>
</td>
</tr>
<tr>
<td>
<a id="uncompress" name="uncompress"></a><span class=
"term"><span><strong class=
"command">uncompress</strong></span></span>
</td>
<td>
<p>
Decompresses compressed files
</p>
</td>
</tr>
<tr>
<td>
<a id="zcat" name="zcat"></a><span class=
"term"><span><strong class=
"command">zcat</strong></span></span>
</td>
<td>
<p>
Decompresses the given gzipped files to standard
output
</p>
</td>
</tr>
<tr>
<td>
<a id="zcmp" name="zcmp"></a><span class=
"term"><span><strong class=
"command">zcmp</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">cmp</strong></span> on gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="zdiff" name="zdiff"></a><span class=
"term"><span><strong class=
"command">zdiff</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">diff</strong></span> on gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="zegrep" name="zegrep"></a><span class=
"term"><span><strong class=
"command">zegrep</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">egrep</strong></span> on gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="zfgrep" name="zfgrep"></a><span class=
"term"><span><strong class=
"command">zfgrep</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">fgrep</strong></span> on gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="zforce" name="zforce"></a><span class=
"term"><span><strong class=
"command">zforce</strong></span></span>
</td>
<td>
<p>
Forces a <tt class="filename">.gz</tt> extension on
all given files that are gzipped files, so that
<span><strong class="command">gzip</strong></span>
will not compress them again; this can be useful
when file names were truncated during a file
transfer
</p>
</td>
</tr>
<tr>
<td>
<a id="zgrep" name="zgrep"></a><span class=
"term"><span><strong class=
"command">zgrep</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">grep</strong></span> on gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="zless" name="zless"></a><span class=
"term"><span><strong class=
"command">zless</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">less</strong></span> on gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="zmore" name="zmore"></a><span class=
"term"><span><strong class=
"command">zmore</strong></span></span>
</td>
<td>
<p>
Runs <span><strong class=
"command">more</strong></span> on gzipped files
</p>
</td>
</tr>
<tr>
<td>
<a id="znew" name="znew"></a><span class=
"term"><span><strong class=
"command">znew</strong></span></span>
</td>
<td>
<p>
Re-compresses files from <span><strong class=
"command">compress</strong></span> format to
<span><strong class="command">gzip</strong></span>
format&mdash;<tt class="filename">.Z</tt> to
<tt class="filename">.gz</tt>
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-hotplug" name=
"ch-system-hotplug"></a>6.47.&nbsp;Hotplug-2004_09_23
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Hotplug package contains scripts that react upon hotplug
events generated by the kernel. Such events correspond to
every change in the kernel state visible in the <tt class=
"systemitem">sysfs</tt> filesystem, e.g., the addition and
removal of hardware. This package also detects existing
hardware during boot and inserts the relevant modules into
the running kernel.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.01 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">460 KB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Coreutils,
Find, Gawk, and Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.47.1. Installation of Hotplug
</h3>
</div>
<p>
Install the Hotplug package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
Copy a file that the &ldquo;<span class=
"quote">install</span>&rdquo; target omits.
</p>
<pre class="userinput"><kbd class=
"command">cp -v etc/hotplug/pnp.distmap /etc/hotplug</kbd></pre>
<p>
Remove the init script that Hotplug installs since we are
going to be using the script included in the LFS-Bootscripts
package:
</p>
<pre class="userinput"><kbd class=
"command">rm -rfv /etc/init.d</kbd></pre>
<p>
Network device hotplugging is not yet supported by the
LFS-Bootscripts package. For that reason, remove the network
hotplug agent:
</p>
<pre class="userinput"><kbd class=
"command">rm -fv /etc/hotplug/net.agent</kbd></pre>
<p>
Create a directory for storing firmware that can be loaded by
<span><strong class="command">hotplug</strong></span>:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v /lib/firmware</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-hotplug" name="contents-hotplug"></a>
<h3 class="sect2">
6.47.2. Contents of Hotplug
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
program:</span></strong> <span class="seg">hotplug</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
scripts:</span></strong> <span class=
"seg">/etc/hotplug/*.rc, /etc/hotplug/*.agent</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
files:</span></strong> <span class=
"seg">/etc/hotplug/hotplug.functions,
/etc/hotplug/blacklist, /etc/hotplug/{pci,usb},
/etc/hotplug/usb.usermap, /etc/hotplug.d, and
/var/log/hotplug/events</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3509909" name="id3509909"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="hotplug" name="hotplug"></a><span class=
"term"><span><strong class=
"command">hotplug</strong></span></span>
</td>
<td>
<p>
This script is called by default by the Linux
kernel when something changes in its internal state
(e.g., a new device is added or an existing device
is removed)
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-rc" name="hotplug-rc"></a><span class=
"term"><span><strong class=
"command">/etc/hotplug/*.rc</strong></span></span>
</td>
<td>
<p>
These scripts are used for cold plugging, i.e.,
detecting and acting upon hardware already present
during system startup. They are called by the
<tt class="filename">hotplug</tt> initscript
included in the LFS-Bootscripts package. The
<span><strong class="command">*.rc</strong></span>
scripts try to recover hotplug events that were
lost during system boot because, for example, the
root filesystem was not mounted by the kernel
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-agent" name=
"hotplug-agent"></a><span class=
"term"><span><strong class=
"command">/etc/hotplug/*.agent</strong></span></span>
</td>
<td>
<p>
These scripts are called by <span><strong class=
"command">hotplug</strong></span> in response to
different types of hotplug events generated by the
kernel. Their action is to insert corresponding
kernel modules and call any user-provided scripts
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-blacklist" name=
"hotplug-blacklist"></a><span class="term"><tt class=
"filename">/etc/hotplug/blacklist</tt></span>
</td>
<td>
<p>
This file contains the list of modules that should
never be inserted into the kernel by the Hotplug
scripts
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-functions" name=
"hotplug-functions"></a><span class="term"><tt class=
"filename">/etc/hotplug/hotplug.functions</tt></span>
</td>
<td>
<p>
This file contains common functions used by other
scripts in the Hotplug package
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-subdirs" name=
"hotplug-subdirs"></a><span class="term"><tt class=
"filename">/etc/hotplug/{pci,usb}</tt></span>
</td>
<td>
<p>
These directories contain user-written handlers for
hotplug events
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-usb.usermap" name=
"hotplug-usb.usermap"></a><span class=
"term"><tt class=
"filename">/etc/hotplug/usb.usermap</tt></span>
</td>
<td>
<p>
This file contains rules that determine which
user-defined handlers to call for each USB device,
based on its vendor ID and other attributes
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-hotplug.d" name=
"hotplug-hotplug.d"></a><span class="term"><tt class=
"filename">/etc/hotplug.d</tt></span>
</td>
<td>
<p>
This directory contains programs (or symlinks to
them) that are interested in receiving hotplug
events. For example, Udev puts its symlink here
during installation
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-firmware" name=
"hotplug-firmware"></a><span class="term"><tt class=
"filename">/lib/firmware</tt></span>
</td>
<td>
<p>
This directory contains the firmware for devices
that need to have their firmware loaded before use
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-events" name=
"hotplug-events"></a><span class="term"><tt class=
"filename">/var/log/hotplug/events</tt></span>
</td>
<td>
<p>
This file contains all the events that
<span><strong class=
"command">hotplug</strong></span> has called since
bootup
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-man" name=
"ch-system-man"></a>6.48.&nbsp;Man-1.5p
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Man package contains programs for finding and viewing man
pages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">2.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Gawk, GCC, Glibc, Grep, Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.48.1. Installation of Man
</h3>
</div>
<p>
Two adjustments need to be made to the sources of Man.
</p>
<p>
The first is a <span><strong class=
"command">sed</strong></span> substitution to add the
<em class="parameter"><tt>-R</tt></em> switch to the
<tt class="envar">PAGER</tt> variable so that escape
sequences are properly handled by Less:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's@-is@&amp;R@g' configure</kbd></pre>
<p>
The second is also a <span><strong class=
"command">sed</strong></span> substitution to comment out the
&ldquo;<span class="quote">MANPATH /usr/man</span>&rdquo;
line in the <tt class="filename">man.conf</tt> file to
prevent redundant results when using programs such as
<span><strong class="command">whatis</strong></span>:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's@MANPATH./usr/man@#&amp;@g' src/man.conf.in</kbd></pre>
<p>
Prepare Man for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure -confdir=/etc</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>-confdir=/etc</tt></em></span>
</dt>
<dd>
<p>
This tells the <span><strong class=
"command">man</strong></span> program to look for the
<tt class="filename">man.conf</tt> configuration file
in the <tt class="filename">/etc</tt> directory.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
If you will be working on a terminal that does not
support text attributes such as color and bold, you can
disable Select Graphic Rendition (SGR) escape sequences
by editing the <tt class="filename">man.conf</tt> file
and adding the <em class="parameter"><tt>-c</tt></em>
option to the <tt class="envar">NROFF</tt> variable. If
you use multiple terminal types for one computer it may
be better to selectively add the <tt class=
"envar">GROFF_NO_SGR</tt> environment variable for the
terminals that do not support SGR.
</p>
</div>
</div>
<p>
If the character set of the locale uses 8-bit characters,
search for the line beginning with &ldquo;<span class=
"quote">NROFF</span>&rdquo; in <tt class=
"filename">/etc/man.conf</tt>, and verify that it matches the
following:
</p>
<pre class="screen">
NROFF /usr/bin/nroff -Tlatin1 -mandoc</pre>
<p>
Note that &ldquo;<span class="quote">latin1</span>&rdquo;
should be used even if it is not the character set of the
locale. The reason is that, according to the specification,
<span><strong class="command">groff</strong></span> has no
means of typesetting characters outside International
Organization for Standards (ISO) 8859-1 without some strange
escape codes. When formatting man pages, <span><strong class=
"command">groff</strong></span> thinks that they are in the
ISO 8859-1 encoding and this <em class=
"parameter"><tt>-Tlatin1</tt></em> switch tells
<span><strong class="command">groff</strong></span> to use
the same encoding for output. Since <span><strong class=
"command">groff</strong></span> does no recoding of input
characters, the formatted result is really in the same
encoding as input, and therefore it is usable as the input
for a pager.
</p>
<p>
This does not solve the problem of a non-working
<span><strong class="command">man2dvi</strong></span> program
for localized man pages in non-ISO 8859-1 locales. Also, it
does not work with multibyte character sets. The first
problem does not currently have a solution. The second issue
is not of concern because the LFS installation does not
support multibyte character sets.
</p>
<p>
Additional information with regards to the compression of man
and info pages can be found in the BLFS book at <a href=
"http://www.linuxfromscratch.org/blfs/view/cvs/postlfs/compressdoc.html">
<i>http://www.linuxfromscratch.org/blfs/view/cvs/postlfs/compressdoc.html</i></a>.
</p>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-man" name="contents-man"></a>
<h3 class="sect2">
6.48.2. Contents of Man
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">apropos,
makewhatis, man, man2dvi, man2html, and whatis</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3510376" name="id3510376"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="apropos" name="apropos"></a><span class=
"term"><span><strong class=
"command">apropos</strong></span></span>
</td>
<td>
<p>
Searches the <span><strong class=
"command">whatis</strong></span> database and
displays the short descriptions of system commands
that contain a given string
</p>
</td>
</tr>
<tr>
<td>
<a id="makewhatis" name="makewhatis"></a><span class=
"term"><span><strong class=
"command">makewhatis</strong></span></span>
</td>
<td>
<p>
Builds the <span><strong class=
"command">whatis</strong></span> database; it reads
all the man pages in the <tt class=
"envar">MANPATH</tt> and writes the name and a
short description in the <span><strong class=
"command">whatis</strong></span> database for each
page
</p>
</td>
</tr>
<tr>
<td>
<a id="man" name="man"></a><span class=
"term"><span><strong class=
"command">man</strong></span></span>
</td>
<td>
<p>
Formats and displays the requested on-line man page
</p>
</td>
</tr>
<tr>
<td>
<a id="man2dvi" name="man2dvi"></a><span class=
"term"><span><strong class=
"command">man2dvi</strong></span></span>
</td>
<td>
<p>
Converts a man page into dvi format
</p>
</td>
</tr>
<tr>
<td>
<a id="man2html" name="man2html"></a><span class=
"term"><span><strong class=
"command">man2html</strong></span></span>
</td>
<td>
<p>
Converts a man page into HTML
</p>
</td>
</tr>
<tr>
<td>
<a id="whatis" name="whatis"></a><span class=
"term"><span><strong class=
"command">whatis</strong></span></span>
</td>
<td>
<p>
Searches the <span><strong class=
"command">whatis</strong></span> database and
displays the short descriptions of system commands
that contain the given keyword as a separate word
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-make" name=
"ch-system-make"></a>6.49.&nbsp;Make-3.80
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Make package contains a program for compiling packages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">7.1 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.49.1. Installation of Make
</h3>
</div>
<p>
Prepare Make for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-make" name="contents-make"></a>
<h3 class="sect2">
6.49.2. Contents of Make
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
program:</span></strong> <span class="seg">make</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3510685" name="id3510685"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="make" name="make"></a><span class=
"term"><span><strong class=
"command">make</strong></span></span>
</td>
<td>
<p>
Automatically determines which pieces of a package
need to be (re)compiled and then issues the
relevant commands
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-module-init-tools" name=
"ch-system-module-init-tools"></a>6.50.&nbsp;Module-Init-Tools-3.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Module-Init-Tools package contains programs for handling
kernel modules in Linux kernels greater than or equal to
version 2.5.47.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">4.9 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Bison, Coreutils, Diffutils, Flex, GCC, Glibc, Grep, M4,
Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.50.1. Installation of Module-Init-Tools
</h3>
</div>
<p>
Module-Init-Tools attempts to rewrite its <tt class=
"filename">modprobe.conf</tt> man page during the build
process. This is unnecessary and also relies on
<span><strong class="command">docbook2man</strong></span>
&mdash; which is not installed in LFS. Run the following
command to avoid this:
</p>
<pre class="userinput"><kbd class=
"command">touch modprobe.conf.5</kbd></pre>
<p>
If you wish to run the test suite for Module-Init-Tools, you
will need to download the separate testsuite tarball. Issue
the following commands to perform the tests (note that the
<span><strong class="command">make distclean</strong></span>
command is required to clean up the source tree, as the
source gets recompiled as part of the testing process):
</p>
<pre class="userinput"><kbd class=
"command">tar -xvf ../module-init-tools-testsuite-3.1.tar.bz2 --strip-path=1 &amp;&amp;
./configure &amp;&amp;
make check &amp;&amp;
make distclean</kbd></pre>
<p>
Prepare Module-Init-Tools for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix="" --enable-zlib</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--enable-zlib</tt></em></span>
</dt>
<dd>
<p>
This allows the Module-Init-Tools package to handle
compressed kernel modules.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-module-init-tools" name=
"contents-module-init-tools"></a>
<h3 class="sect2">
6.50.2. Contents of Module-Init-Tools
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">depmod,
insmod, insmod.static, lsmod (link to insmod), modinfo,
modprobe (link to insmod), and rmmod (link to
insmod)</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3510821" name="id3510821"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="depmod" name="depmod"></a><span class=
"term"><span><strong class=
"command">depmod</strong></span></span>
</td>
<td>
<p>
Creates a dependency file based on the symbols it
finds in the existing set of modules; this
dependency file is used by <span><strong class=
"command">modprobe</strong></span> to automatically
load the required modules
</p>
</td>
</tr>
<tr>
<td>
<a id="insmod" name="insmod"></a><span class=
"term"><span><strong class=
"command">insmod</strong></span></span>
</td>
<td>
<p>
Installs a loadable module in the running kernel
</p>
</td>
</tr>
<tr>
<td>
<a id="insmod.static" name=
"insmod.static"></a><span class=
"term"><span><strong class=
"command">insmod.static</strong></span></span>
</td>
<td>
<p>
A statically compiled version of
<span><strong class=
"command">insmod</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="lsmod" name="lsmod"></a><span class=
"term"><span><strong class=
"command">lsmod</strong></span></span>
</td>
<td>
<p>
Lists currently loaded modules
</p>
</td>
</tr>
<tr>
<td>
<a id="modinfo" name="modinfo"></a><span class=
"term"><span><strong class=
"command">modinfo</strong></span></span>
</td>
<td>
<p>
Examines an object file associated with a kernel
module and displays any information that it can
glean
</p>
</td>
</tr>
<tr>
<td>
<a id="modprobe" name="modprobe"></a><span class=
"term"><span><strong class=
"command">modprobe</strong></span></span>
</td>
<td>
<p>
Uses a dependency file, created by
<span><strong class=
"command">depmod</strong></span>, to automatically
load relevant modules
</p>
</td>
</tr>
<tr>
<td>
<a id="rmmod" name="rmmod"></a><span class=
"term"><span><strong class=
"command">rmmod</strong></span></span>
</td>
<td>
<p>
Unloads modules from the running kernel
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-patch" name=
"ch-system-patch"></a>6.51.&nbsp;Patch-2.5.4
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Patch package contains a program for modifying or
creating files by applying a &ldquo;<span class=
"quote">patch</span>&rdquo; file typically created by the
<span><strong class="command">diff</strong></span> program.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">1.5 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Glibc, Grep, Make, and
Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.51.1. Installation of Patch
</h3>
</div>
<p>
Prepare Patch for compilation. The preprocessor flag
<em class="parameter"><tt>-D_GNU_SOURCE</tt></em> is only
needed on the PowerPC platform. It can be left it out on
other architectures:
</p>
<pre class="userinput"><kbd class=
"command">CPPFLAGS=-D_GNU_SOURCE ./configure --prefix=/usr</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-patch" name="contents-patch"></a>
<h3 class="sect2">
6.51.2. Contents of Patch
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
program:</span></strong> <span class="seg">patch</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3511140" name="id3511140"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="patch" name="patch"></a><span class=
"term"><span><strong class=
"command">patch</strong></span></span>
</td>
<td>
<p>
Modifies files according to a patch file. A patch
file is normally a difference listing created with
the <span><strong class=
"command">diff</strong></span> program. By applying
these differences to the original files,
<span><strong class="command">patch</strong></span>
creates the patched versions.
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-procps" name=
"ch-system-procps"></a>6.52.&nbsp;Procps-3.2.5
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Procps package contains programs for monitoring
processes.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">2.3 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, GCC, Glibc, Make, and Ncurses</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.52.1. Installation of Procps
</h3>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-procps" name="contents-procps"></a>
<h3 class="sect2">
6.52.2. Contents of Procps
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">free, kill,
pgrep, pkill, pmap, ps, skill, snice, sysctl, tload, top,
uptime, vmstat, w, and watch</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
library:</span></strong> <span class=
"seg">libproc.so</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3511240" name="id3511240"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="free" name="free"></a><span class=
"term"><span><strong class=
"command">free</strong></span></span>
</td>
<td>
<p>
Reports the amount of free and used memory (both
physical and swap memory) in the system
</p>
</td>
</tr>
<tr>
<td>
<a id="kill" name="kill"></a><span class=
"term"><span><strong class=
"command">kill</strong></span></span>
</td>
<td>
<p>
Sends signals to processes
</p>
</td>
</tr>
<tr>
<td>
<a id="pgrep" name="pgrep"></a><span class=
"term"><span><strong class=
"command">pgrep</strong></span></span>
</td>
<td>
<p>
Looks up processes based on their name and other
attributes
</p>
</td>
</tr>
<tr>
<td>
<a id="pkill" name="pkill"></a><span class=
"term"><span><strong class=
"command">pkill</strong></span></span>
</td>
<td>
<p>
Signals processes based on their name and other
attributes
</p>
</td>
</tr>
<tr>
<td>
<a id="pmap" name="pmap"></a><span class=
"term"><span><strong class=
"command">pmap</strong></span></span>
</td>
<td>
<p>
Reports the memory map of the given process
</p>
</td>
</tr>
<tr>
<td>
<a id="ps" name="ps"></a><span class=
"term"><span><strong class=
"command">ps</strong></span></span>
</td>
<td>
<p>
Lists the current running processes
</p>
</td>
</tr>
<tr>
<td>
<a id="skill" name="skill"></a><span class=
"term"><span><strong class=
"command">skill</strong></span></span>
</td>
<td>
<p>
Sends signals to processes matching the given
criteria
</p>
</td>
</tr>
<tr>
<td>
<a id="snice" name="snice"></a><span class=
"term"><span><strong class=
"command">snice</strong></span></span>
</td>
<td>
<p>
Changes the scheduling priority of processes
matching the given criteria
</p>
</td>
</tr>
<tr>
<td>
<a id="sysctl" name="sysctl"></a><span class=
"term"><span><strong class=
"command">sysctl</strong></span></span>
</td>
<td>
<p>
Modifies kernel parameters at run time
</p>
</td>
</tr>
<tr>
<td>
<a id="tload" name="tload"></a><span class=
"term"><span><strong class=
"command">tload</strong></span></span>
</td>
<td>
<p>
Prints a graph of the current system load average
</p>
</td>
</tr>
<tr>
<td>
<a id="top" name="top"></a><span class=
"term"><span><strong class=
"command">top</strong></span></span>
</td>
<td>
<p>
Displays a list of the most CPU intensive
processes; it provides an ongoing look at processor
activity in real time
</p>
</td>
</tr>
<tr>
<td>
<a id="uptime" name="uptime"></a><span class=
"term"><span><strong class=
"command">uptime</strong></span></span>
</td>
<td>
<p>
Reports how long the system has been running, how
many users are logged on, and the system load
averages
</p>
</td>
</tr>
<tr>
<td>
<a id="vmstat" name="vmstat"></a><span class=
"term"><span><strong class=
"command">vmstat</strong></span></span>
</td>
<td>
<p>
Reports virtual memory statistics, giving
information about processes, memory, paging, block
Input/Output (IO), traps, and CPU activity
</p>
</td>
</tr>
<tr>
<td>
<a id="w" name="w"></a><span class=
"term"><span><strong class=
"command">w</strong></span></span>
</td>
<td>
<p>
Shows which users are currently logged on, where,
and since when
</p>
</td>
</tr>
<tr>
<td>
<a id="watch" name="watch"></a><span class=
"term"><span><strong class=
"command">watch</strong></span></span>
</td>
<td>
<p>
Runs a given command repeatedly, displaying the
first screen-full of its output; this allows a user
to watch the output change over time
</p>
</td>
</tr>
<tr>
<td>
<a id="libproc" name="libproc"></a><span class=
"term"><tt class="filename">libproc</tt></span>
</td>
<td>
<p>
Contains the functions used by most programs in
this package
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-psmisc" name=
"ch-system-psmisc"></a>6.53.&nbsp;Psmisc-21.6
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Psmisc package contains programs for displaying
information about running processes.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">1.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Ncurses, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.53.1. Installation of Psmisc
</h3>
</div>
<p>
Prepare Psmisc for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --exec-prefix=""</kbd></pre>
<p>
The meaning of the configure options:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>--exec-prefix=""</tt></em></span>
</dt>
<dd>
<p>
This ensures that the Psmisc binaries will install into
<tt class="filename">/bin</tt> instead of <tt class=
"filename">/usr/bin</tt>. This is the correct location
according to the FHS, because some of the Psmisc
binaries are used by the LFS-Bootscripts package.
</p>
</dd>
</dl>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
There is no reason for the <span><strong class=
"command">pstree</strong></span> and <span><strong class=
"command">pstree.x11</strong></span> programs to reside in
<tt class="filename">/bin</tt>. Therefore, move them to
<tt class="filename">/usr/bin</tt>:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /bin/pstree* /usr/bin</kbd></pre>
<p>
By default, Psmisc's <span><strong class=
"command">pidof</strong></span> program is not installed.
This usually is not a problem because it is installed later
in the Sysvinit package, which provides a better
<span><strong class="command">pidof</strong></span> program.
If Sysvinit will not be used for a particular system,
complete the installation of Psmisc by creating the following
symlink:
</p>
<pre class="userinput"><kbd class=
"command">ln -sv killall /bin/pidof</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-psmisc" name="contents-psmisc"></a>
<h3 class="sect2">
6.53.2. Contents of Psmisc
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">fuser,
killall, pstree, and pstree.x11 (link to pstree)</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3511297" name="id3511297"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="fuser" name="fuser"></a><span class=
"term"><span><strong class=
"command">fuser</strong></span></span>
</td>
<td>
<p>
Reports the Process IDs (PIDs) of processes that
use the given files or file systems
</p>
</td>
</tr>
<tr>
<td>
<a id="killall" name="killall"></a><span class=
"term"><span><strong class=
"command">killall</strong></span></span>
</td>
<td>
<p>
Kills processes by name; it sends a signal to all
processes running any of the given commands
</p>
</td>
</tr>
<tr>
<td>
<a id="pstree" name="pstree"></a><span class=
"term"><span><strong class=
"command">pstree</strong></span></span>
</td>
<td>
<p>
Displays running processes as a tree
</p>
</td>
</tr>
<tr>
<td>
<a id="pstree.x11" name="pstree.x11"></a><span class=
"term"><span><strong class=
"command">pstree.x11</strong></span></span>
</td>
<td>
<p>
Same as <span><strong class=
"command">pstree</strong></span>, except that it
waits for confirmation before exiting
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-shadow" name=
"ch-system-shadow"></a>6.54.&nbsp;Shadow-4.0.9
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Shadow package contains programs for handling passwords
in a secure way.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.4 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">13.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Bison, Coreutils, Diffutils, GCC, Gettext, Glibc, Grep,
Make, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.54.1. Installation of Shadow
</h3>
</div>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
If you would like to enforce the use of strong passwords,
refer to <a href=
"http://www.linuxfromscratch.org/blfs/view/svn/postlfs/cracklib.html">
<i>http://www.linuxfromscratch.org/blfs/view/svn/postlfs/cracklib.html</i></a>
for installing Cracklib prior to building Shadow. Then
add <em class="parameter"><tt>--with-libcrack</tt></em>
to the <span><strong class=
"command">configure</strong></span> command below.
</p>
</div>
</div>
<p>
Prepare Shadow for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --libdir=/lib --enable-shared</kbd></pre>
<p>
Disable the installation of the <span><strong class=
"command">groups</strong></span> program and its man page, as
Coreutils provides a better version:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's/groups$(EXEEXT) //' src/Makefile
sed -i '/groups/d' man/Makefile</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
<p>
<a id="shadow-limits-login_access" name=
"shadow-limits-login_access"></a>Shadow uses two files to
configure authentication settings for the system. Install
these two configuration files:
</p>
<pre class="userinput"><kbd class=
"command">cp -v etc/{limits,login.access} /etc</kbd></pre>
<p>
<a id="shadow-login_defs" name=
"shadow-login_defs"></a>Instead of using the default
<span class="emphasis"><em>crypt</em></span> method, use the
more secure <span class="emphasis"><em>MD5</em></span> method
of password encryption, which also allows passwords longer
than 8 characters. It is also necessary to change the
obsolete <tt class="filename">/var/spool/mail</tt> location
for user mailboxes that Shadow uses by default to the
<tt class="filename">/var/mail</tt> location used currently.
Both of these can be accomplished by changing the relevant
configuration file while copying it to its destination:
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
If you built Shadow with Cracklib support, insert the
following into the <span><strong class=
"command">sed</strong></span> given below:
</p>
<pre class="screen"><tt class=
"literal">-e 's@DICTPATH.*@DICTPATH\t/lib/cracklib/pw_dict@'</tt></pre>
</div>
</div>
<pre class="userinput"><kbd class=
"command">sed -e's@#MD5_CRYPT_ENAB.no@MD5_CRYPT_ENAB yes@' \
-e 's@/var/spool/mail@/var/mail@' \
etc/login.defs.linux &gt; /etc/login.defs</kbd></pre>
<p>
Move a misplaced program to its proper location:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /usr/bin/passwd /bin</kbd></pre>
<p>
Move Shadow's libraries to more appropriate locations:
</p>
<pre class="userinput"><kbd class=
"command">mv -v /lib/libshadow.*a /usr/lib
rm -v /lib/libshadow.so
ln -sfv ../../lib/libshadow.so.0 /usr/lib/libshadow.so</kbd></pre>
<p>
The <em class="parameter"><tt>-D</tt></em> option of the
<span><strong class="command">useradd</strong></span> program
requires the <tt class="filename">/etc/default</tt> directory
for it to work properly:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v /etc/default</kbd></pre>
</div>
<div class="configuration" lang="en" xml:lang="en">
<div class="titlepage">
<a id="conf-shadow" name="conf-shadow"></a>
<h3 class="sect2">
6.54.2. Configuring Shadow
</h3>
</div>
<p>
This package contains utilities to add, modify, and delete
users and groups; set and change their passwords; and perform
other administrative tasks. For a full explanation of what
<span class="emphasis"><em>password shadowing</em></span>
means, see the <tt class="filename">doc/HOWTO</tt> file
within the unpacked source tree. If using Shadow support,
keep in mind that programs which need to verify passwords
(display managers, FTP programs, pop3 daemons, etc.) must be
Shadow-compliant. That is, they need to be able to work with
shadowed passwords.
</p>
<p>
To enable shadowed passwords, run the following command:
</p>
<pre class="userinput"><kbd class="command">pwconv</kbd></pre>
<p>
To enable shadowed group passwords, run:
</p>
<pre class="userinput"><kbd class="command">grpconv</kbd></pre>
<p>
Under normal circumstances, passwords will not have been
created yet. However, if returning to this section later to
enable shadowing, reset any current user passwords with the
<span><strong class="command">passwd</strong></span> command
or any group passwords with the <span><strong class=
"command">gpasswd</strong></span> command.
</p>
</div>
<div class="configuration" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.54.3. Setting the root password
</h3>
</div>
<p>
Choose a password for user <span class=
"emphasis"><em>root</em></span> and set it by running:
</p>
<pre class="userinput"><kbd class=
"command">passwd root</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-shadow" name="contents-shadow"></a>
<h3 class="sect2">
6.54.4. Contents of Shadow
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">chage, chfn,
chpasswd, chsh, expiry, faillog, gpasswd, groupadd,
groupdel, groupmod, grpck, grpconv, grpunconv, lastlog,
login, logoutd, mkpasswd, newgrp, newusers, passwd, pwck,
pwconv, pwunconv, sg (link to newgrp), useradd, userdel,
usermod, vigr (link to vipw), and vipw</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
libraries:</span></strong> <span class=
"seg">libshadow.[a,so]</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3512204" name="id3512204"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="chage" name="chage"></a><span class=
"term"><span><strong class=
"command">chage</strong></span></span>
</td>
<td>
<p>
Used to change the maximum number of days between
obligatory password changes
</p>
</td>
</tr>
<tr>
<td>
<a id="chfn" name="chfn"></a><span class=
"term"><span><strong class=
"command">chfn</strong></span></span>
</td>
<td>
<p>
Used to change a user's full name and other
information
</p>
</td>
</tr>
<tr>
<td>
<a id="chpasswd" name="chpasswd"></a><span class=
"term"><span><strong class=
"command">chpasswd</strong></span></span>
</td>
<td>
<p>
Used to update the passwords of an entire series of
user accounts
</p>
</td>
</tr>
<tr>
<td>
<a id="chsh" name="chsh"></a><span class=
"term"><span><strong class=
"command">chsh</strong></span></span>
</td>
<td>
<p>
Used to change a user's default login shell
</p>
</td>
</tr>
<tr>
<td>
<a id="expiry" name="expiry"></a><span class=
"term"><span><strong class=
"command">expiry</strong></span></span>
</td>
<td>
<p>
Checks and enforces the current password expiration
policy
</p>
</td>
</tr>
<tr>
<td>
<a id="faillog" name="faillog"></a><span class=
"term"><span><strong class=
"command">faillog</strong></span></span>
</td>
<td>
<p>
Is used to examine the log of login failures, to
set a maximum number of failures before an account
is blocked, or to reset the failure count
</p>
</td>
</tr>
<tr>
<td>
<a id="gpasswd" name="gpasswd"></a><span class=
"term"><span><strong class=
"command">gpasswd</strong></span></span>
</td>
<td>
<p>
Is used to add and delete members and
administrators to groups
</p>
</td>
</tr>
<tr>
<td>
<a id="groupadd" name="groupadd"></a><span class=
"term"><span><strong class=
"command">groupadd</strong></span></span>
</td>
<td>
<p>
Creates a group with the given name
</p>
</td>
</tr>
<tr>
<td>
<a id="groupdel" name="groupdel"></a><span class=
"term"><span><strong class=
"command">groupdel</strong></span></span>
</td>
<td>
<p>
Deletes the group with the given name
</p>
</td>
</tr>
<tr>
<td>
<a id="groupmod" name="groupmod"></a><span class=
"term"><span><strong class=
"command">groupmod</strong></span></span>
</td>
<td>
<p>
Is used to modify the given group's name or GID
</p>
</td>
</tr>
<tr>
<td>
<a id="grpck" name="grpck"></a><span class=
"term"><span><strong class=
"command">grpck</strong></span></span>
</td>
<td>
<p>
Verifies the integrity of the group files
<tt class="filename">/etc/group</tt> and <tt class=
"filename">/etc/gshadow</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="grpconv" name="grpconv"></a><span class=
"term"><span><strong class=
"command">grpconv</strong></span></span>
</td>
<td>
<p>
Creates or updates the shadow group file from the
normal group file
</p>
</td>
</tr>
<tr>
<td>
<a id="grpunconv" name="grpunconv"></a><span class=
"term"><span><strong class=
"command">grpunconv</strong></span></span>
</td>
<td>
<p>
Updates <tt class="filename">/etc/group</tt> from
<tt class="filename">/etc/gshadow</tt> and then
deletes the latter
</p>
</td>
</tr>
<tr>
<td>
<a id="lastlog" name="lastlog"></a><span class=
"term"><span><strong class=
"command">lastlog</strong></span></span>
</td>
<td>
<p>
Reports the most recent login of all users or of a
given user
</p>
</td>
</tr>
<tr>
<td>
<a id="login" name="login"></a><span class=
"term"><span><strong class=
"command">login</strong></span></span>
</td>
<td>
<p>
Is used by the system to let users sign on
</p>
</td>
</tr>
<tr>
<td>
<a id="logoutd" name="logoutd"></a><span class=
"term"><span><strong class=
"command">logoutd</strong></span></span>
</td>
<td>
<p>
Is a daemon used to enforce restrictions on log-on
time and ports
</p>
</td>
</tr>
<tr>
<td>
<a id="mkpasswd" name="mkpasswd"></a><span class=
"term"><span><strong class=
"command">mkpasswd</strong></span></span>
</td>
<td>
<p>
Generates random passwords
</p>
</td>
</tr>
<tr>
<td>
<a id="newgrp" name="newgrp"></a><span class=
"term"><span><strong class=
"command">newgrp</strong></span></span>
</td>
<td>
<p>
Is used to change the current GID during a login
session
</p>
</td>
</tr>
<tr>
<td>
<a id="newusers" name="newusers"></a><span class=
"term"><span><strong class=
"command">newusers</strong></span></span>
</td>
<td>
<p>
Is used to create or update an entire series of
user accounts
</p>
</td>
</tr>
<tr>
<td>
<a id="passwd" name="passwd"></a><span class=
"term"><span><strong class=
"command">passwd</strong></span></span>
</td>
<td>
<p>
Is used to change the password for a user or group
account
</p>
</td>
</tr>
<tr>
<td>
<a id="pwck" name="pwck"></a><span class=
"term"><span><strong class=
"command">pwck</strong></span></span>
</td>
<td>
<p>
Verifies the integrity of the password files
<tt class="filename">/etc/passwd</tt> and
<tt class="filename">/etc/shadow</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="pwconv" name="pwconv"></a><span class=
"term"><span><strong class=
"command">pwconv</strong></span></span>
</td>
<td>
<p>
Creates or updates the shadow password file from
the normal password file
</p>
</td>
</tr>
<tr>
<td>
<a id="pwunconv" name="pwunconv"></a><span class=
"term"><span><strong class=
"command">pwunconv</strong></span></span>
</td>
<td>
<p>
Updates <tt class="filename">/etc/passwd</tt> from
<tt class="filename">/etc/shadow</tt> and then
deletes the latter
</p>
</td>
</tr>
<tr>
<td>
<a id="sg" name="sg"></a><span class=
"term"><span><strong class=
"command">sg</strong></span></span>
</td>
<td>
<p>
Executes a given command while the user's GID is
set to that of the given group
</p>
</td>
</tr>
<tr>
<td>
<a id="su" name="su"></a><span class=
"term"><span><strong class=
"command">su</strong></span></span>
</td>
<td>
<p>
Runs a shell with substitute user and group IDs
</p>
</td>
</tr>
<tr>
<td>
<a id="useradd" name="useradd"></a><span class=
"term"><span><strong class=
"command">useradd</strong></span></span>
</td>
<td>
<p>
Creates a new user with the given name, or updates
the default new-user information
</p>
</td>
</tr>
<tr>
<td>
<a id="userdel" name="userdel"></a><span class=
"term"><span><strong class=
"command">userdel</strong></span></span>
</td>
<td>
<p>
Deletes the given user account
</p>
</td>
</tr>
<tr>
<td>
<a id="usermod" name="usermod"></a><span class=
"term"><span><strong class=
"command">usermod</strong></span></span>
</td>
<td>
<p>
Is used to modify the given user's login name, User
Identification (UID), shell, initial group, home
directory, etc.
</p>
</td>
</tr>
<tr>
<td>
<a id="vigr" name="vigr"></a><span class=
"term"><span><strong class=
"command">vigr</strong></span></span>
</td>
<td>
<p>
Edits the <tt class="filename">/etc/group</tt> or
<tt class="filename">/etc/gshadow</tt> files
</p>
</td>
</tr>
<tr>
<td>
<a id="vipw" name="vipw"></a><span class=
"term"><span><strong class=
"command">vipw</strong></span></span>
</td>
<td>
<p>
Edits the <tt class="filename">/etc/passwd</tt> or
<tt class="filename">/etc/shadow</tt> files
</p>
</td>
</tr>
<tr>
<td>
<a id="libshadow" name="libshadow"></a><span class=
"term"><tt class="filename">libshadow</tt></span>
</td>
<td>
<p>
Contains functions used by most programs in this
package
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-sysklogd" name=
"ch-system-sysklogd"></a>6.55.&nbsp;Sysklogd-1.4.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Sysklogd package contains programs for logging system
messages, such as those given by the kernel when unusual
things happen.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">704 KB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Binutils,
Coreutils, GCC, Glibc, Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.55.1. Installation of Sysklogd
</h3>
</div>
<p>
The following patch fixes various issues, including a problem
building Sysklogd with Linux 2.6 series kernels
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../sysklogd-1.4.1-fixes-1.patch</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="configuration" lang="en" xml:lang="en">
<div class="titlepage">
<a id="conf-sysklogd" name="conf-sysklogd"></a>
<h3 class="sect2">
6.55.2. Configuring Sysklogd
</h3>
</div>
<p>
Create a new <tt class="filename">/etc/syslog.conf</tt> file
by running the following:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/syslog.conf &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/syslog.conf
auth,authpriv.* -/var/log/auth.log
*.*;auth,authpriv.none -/var/log/sys.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log
*.emerg *
# log the bootscript output:
local2.* -/var/log/boot.log
# End /etc/syslog.conf</tt>
EOF</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-sysklogd" name="contents-sysklogd"></a>
<h3 class="sect2">
6.55.3. Contents of Sysklogd
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">klogd and
syslogd</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3513078" name="id3513078"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="klogd" name="klogd"></a><span class=
"term"><span><strong class=
"command">klogd</strong></span></span>
</td>
<td>
<p>
A system daemon for intercepting and logging kernel
messages
</p>
</td>
</tr>
<tr>
<td>
<a id="syslogd" name="syslogd"></a><span class=
"term"><span><strong class=
"command">syslogd</strong></span></span>
</td>
<td>
<p>
Logs the messages that system programs offer for
logging. Every logged message contains at least a
date stamp and a hostname, and normally the
program's name too, but that depends on how
trusting the logging daemon is told to be
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-sysvinit" name=
"ch-system-sysvinit"></a>6.56.&nbsp;Sysvinit-2.86
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Sysvinit package contains programs for controlling the
startup, running, and shutdown of the system.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">1012 KB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Binutils,
Coreutils, GCC, Glibc, and Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.56.1. Installation of Sysvinit
</h3>
</div>
<p>
When run-levels are changed (for example, when halting the
system), <span><strong class="command">init</strong></span>
sends termination signals to those processes that
<span><strong class="command">init</strong></span> itself
started and that should not be running in the new run-level.
While doing this, <span><strong class=
"command">init</strong></span> outputs messages like
&ldquo;<span class="quote">Sending processes the TERM
signal</span>&rdquo; which seem to imply that it is sending
these signals to all currently running processes. To avoid
this misinterpretation, modify the source so that these
messages read like &ldquo;<span class="quote">Sending
processes started by init the TERM signal</span>&rdquo;
instead:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's@Sending processes@&amp; started by init@g' \
src/init.c</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class=
"command">make -C src</kbd></pre>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make -C src install</kbd></pre>
</div>
<div class="configuration" lang="en" xml:lang="en">
<div class="titlepage">
<a id="conf-sysvinit" name="conf-sysvinit"></a>
<h3 class="sect2">
6.56.2. Configuring Sysvinit
</h3>
</div>
<p>
Create a new file <tt class="filename">/etc/inittab</tt> by
running the following:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/inittab &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/inittab
id:3:initdefault:
si::sysinit:/etc/rc.d/init.d/rc sysinit
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
su:S016:once:/sbin/sulogin
1:2345:respawn:/sbin/agetty -I '\033(K' tty1 9600
2:2345:respawn:/sbin/agetty -I '\033(K' tty2 9600
3:2345:respawn:/sbin/agetty -I '\033(K' tty3 9600
4:2345:respawn:/sbin/agetty -I '\033(K' tty4 9600
5:2345:respawn:/sbin/agetty -I '\033(K' tty5 9600
6:2345:respawn:/sbin/agetty -I '\033(K' tty6 9600
# End /etc/inittab</tt>
EOF</kbd></pre>
<p>
The <em class="parameter"><tt>-I '\033(K'</tt></em> option
tells <span><strong class="command">agetty</strong></span> to
send this escape sequence to the terminal before doing
anything else. This escape sequence switches the console
character set to a user-defined one, which can be modified by
running the <span><strong class=
"command">setfont</strong></span> program. The
<span><strong class="command">console</strong></span>
initscript from the LFS-Bootscripts package calls the
<span><strong class="command">setfont</strong></span> program
during system startup. Sending this escape sequence is
necessary for people who use non-ISO 8859-1 screen fonts, but
it does not affect native English speakers.
</p>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-sysvinit" name="contents-sysvinit"></a>
<h3 class="sect2">
6.56.3. Contents of Sysvinit
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">halt, init,
killall5, last, lastb (link to last), mesg, pidof (link
to killall5), poweroff (link to halt), reboot (link to
halt), runlevel, shutdown, sulogin, telinit (link to
init), utmpdump, and wall</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3513326" name="id3513326"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="halt" name="halt"></a><span class=
"term"><span><strong class=
"command">halt</strong></span></span>
</td>
<td>
<p>
Normally invokes <span><strong class=
"command">shutdown</strong></span> with the
<em class="parameter"><tt>-h</tt></em> option,
except when already in run-level 0, then it tells
the kernel to halt the system; it notes in the file
<tt class="filename">/var/log/wtmp</tt> that the
system is being brought down
</p>
</td>
</tr>
<tr>
<td>
<a id="init" name="init"></a><span class=
"term"><span><strong class=
"command">init</strong></span></span>
</td>
<td>
<p>
The first process to be started when the kernel has
initialized the hardware which takes over the boot
process and starts all the proceses it is
instructed to
</p>
</td>
</tr>
<tr>
<td>
<a id="killall5" name="killall5"></a><span class=
"term"><span><strong class=
"command">killall5</strong></span></span>
</td>
<td>
<p>
Sends a signal to all processes, except the
processes in its own session so it will not kill
the shell running the script that called it
</p>
</td>
</tr>
<tr>
<td>
<a id="last" name="last"></a><span class=
"term"><span><strong class=
"command">last</strong></span></span>
</td>
<td>
<p>
Shows which users last logged in (and out),
searching back through the <tt class=
"filename">/var/log/wtmp</tt> file; it also shows
system boots, shutdowns, and run-level changes
</p>
</td>
</tr>
<tr>
<td>
<a id="lastb" name="lastb"></a><span class=
"term"><span><strong class=
"command">lastb</strong></span></span>
</td>
<td>
<p>
Shows the failed login attempts, as logged in
<tt class="filename">/var/log/btmp</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="mesg" name="mesg"></a><span class=
"term"><span><strong class=
"command">mesg</strong></span></span>
</td>
<td>
<p>
Controls whether other users can send messages to
the current user's terminal
</p>
</td>
</tr>
<tr>
<td>
<a id="mountpoint" name="mountpoint"></a><span class=
"term"><span><strong class=
"command">mountpoint</strong></span></span>
</td>
<td>
<p>
Checks if the directory is a mountpoint
</p>
</td>
</tr>
<tr>
<td>
<a id="pidof" name="pidof"></a><span class=
"term"><span><strong class=
"command">pidof</strong></span></span>
</td>
<td>
<p>
Reports the PIDs of the given programs
</p>
</td>
</tr>
<tr>
<td>
<a id="poweroff" name="poweroff"></a><span class=
"term"><span><strong class=
"command">poweroff</strong></span></span>
</td>
<td>
<p>
Tells the kernel to halt the system and switch off
the computer (see <span><strong class=
"command">halt</strong></span>)
</p>
</td>
</tr>
<tr>
<td>
<a id="reboot" name="reboot"></a><span class=
"term"><span><strong class=
"command">reboot</strong></span></span>
</td>
<td>
<p>
Tells the kernel to reboot the system (see
<span><strong class="command">halt</strong></span>)
</p>
</td>
</tr>
<tr>
<td>
<a id="runlevel" name="runlevel"></a><span class=
"term"><span><strong class=
"command">runlevel</strong></span></span>
</td>
<td>
<p>
Reports the previous and the current run-level, as
noted in the last run-level record in <tt class=
"filename">/var/run/utmp</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="shutdown" name="shutdown"></a><span class=
"term"><span><strong class=
"command">shutdown</strong></span></span>
</td>
<td>
<p>
Brings the system down in a secure way, signaling
all processes and notifying all logged-in users
</p>
</td>
</tr>
<tr>
<td>
<a id="sulogin" name="sulogin"></a><span class=
"term"><span><strong class=
"command">sulogin</strong></span></span>
</td>
<td>
<p>
Allows <span class="emphasis"><em>root</em></span>
to log in; it is normally invoked by
<span><strong class="command">init</strong></span>
when the system goes into single user mode
</p>
</td>
</tr>
<tr>
<td>
<a id="telinit" name="telinit"></a><span class=
"term"><span><strong class=
"command">telinit</strong></span></span>
</td>
<td>
<p>
Tells <span><strong class=
"command">init</strong></span> which run-level to
change to
</p>
</td>
</tr>
<tr>
<td>
<a id="utmpdump" name="utmpdump"></a><span class=
"term"><span><strong class=
"command">utmpdump</strong></span></span>
</td>
<td>
<p>
Displays the content of the given login file in a
more user-friendly format
</p>
</td>
</tr>
<tr>
<td>
<a id="wall" name="wall"></a><span class=
"term"><span><strong class=
"command">wall</strong></span></span>
</td>
<td>
<p>
Writes a message to all logged-in users
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-tar" name=
"ch-system-tar"></a>6.57.&nbsp;Tar-1.15.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Tar package contains an archiving program.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">12.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.57.1. Installation of Tar
</h3>
</div>
<p>
Tar has a bug when the <em class="parameter"><tt>-S</tt></em>
option is used with files larger than 4 GB. The following
patch properly fixes this issue:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../tar-1.15.1-sparse_fix-1.patch</kbd></pre>
<p>
Prepare Tar for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure --prefix=/usr --bindir=/bin --libexecdir=/usr/sbin</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make check</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-tar" name="contents-tar"></a>
<h3 class="sect2">
6.57.2. Contents of Tar
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">rmt and
tar</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3513838" name="id3513838"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="rmt" name="rmt"></a><span class=
"term"><span><strong class=
"command">rmt</strong></span></span>
</td>
<td>
<p>
Remotely manipulates a magnetic tape drive through
an interprocess communication connection
</p>
</td>
</tr>
<tr>
<td>
<a id="tar" name="tar"></a><span class=
"term"><span><strong class=
"command">tar</strong></span></span>
</td>
<td>
<p>
Creates, extracts files from, and lists the
contents of archives, also known as tarballs
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-udev" name=
"ch-system-udev"></a>6.58.&nbsp;Udev-056
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Udev package contains programs for dynamic creation of
device nodes.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">6.7 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Coreutils and
Make</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.58.1. Installation of Udev
</h3>
</div>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class=
"command">make udevdir=/dev</kbd></pre>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>udevdir=/dev</tt></em></span>
</dt>
<dd>
<p>
This tells <span><strong class=
"command">udev</strong></span> in which directory
devices nodes are to be created.
</p>
</dd>
</dl>
</div>
<p>
To test the results, issue: <strong class=
"userinput"><tt>make test</tt></strong>.
</p>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make DESTDIR=/ udevdir=/dev install</kbd></pre>
<p>
The meaning of the make option:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>DESTDIR=/</tt></em></span>
</dt>
<dd>
<p>
This prevents the Udev build process from killing any
<span><strong class="command">udevd</strong></span>
processes that may be running on the host system.
</p>
</dd>
</dl>
</div>
<p>
Udev's configuration is far from ideal by default, so install
the configuration files here:
</p>
<pre class="userinput"><kbd class=
"command">cp -v ../udev-config-4.rules /etc/udev/rules.d/25-lfs.rules</kbd></pre>
<p>
Run the <span><strong class=
"command">udevstart</strong></span> program to create our
full complement of device nodes.
</p>
<pre class="userinput"><kbd class=
"command">/sbin/udevstart</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-udev" name="contents-udev"></a>
<h3 class="sect2">
6.58.2. Contents of Udev
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">udev, udevd,
udevsend, udevstart, udevinfo, and udevtest</span>
</div>
<div class="seg">
<strong><span class="segtitle">Installed
directory:</span></strong> <span class=
"seg">/etc/udev</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3513868" name="id3513868"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="udev" name="udev"></a><span class=
"term"><span><strong class=
"command">udev</strong></span></span>
</td>
<td>
<p>
Creates device nodes in <tt class=
"filename">/dev</tt> or renames network interfaces
(not in LFS) in response to hotplug events
</p>
</td>
</tr>
<tr>
<td>
<a id="udevd" name="udevd"></a><span class=
"term"><span><strong class=
"command">udevd</strong></span></span>
</td>
<td>
<p>
A daemon that reorders hotplug events before
submitting them to <span><strong class=
"command">udev</strong></span>, thus avoiding
various race conditions
</p>
</td>
</tr>
<tr>
<td>
<a id="udevsend" name="udevsend"></a><span class=
"term"><span><strong class=
"command">udevsend</strong></span></span>
</td>
<td>
<p>
Delivers hotplug events to <span><strong class=
"command">udevd</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="udevstart" name="udevstart"></a><span class=
"term"><span><strong class=
"command">udevstart</strong></span></span>
</td>
<td>
<p>
Creates device nodes in <tt class=
"filename">/dev</tt> that correspond to drivers
compiled directly into the kernel; it performs that
task by simulating hotplug events presumably
dropped by the kernel before invocation of this
program (e.g., because the root filesystem has not
been mounted) and submitting such synthetic hotplug
events to <span><strong class=
"command">udev</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="udevinfo" name="udevinfo"></a><span class=
"term"><span><strong class=
"command">udevinfo</strong></span></span>
</td>
<td>
<p>
Allows users to query the <span><strong class=
"command">udev</strong></span> database for
information on any device currently present on the
system; it also provides a way to query any device
in the <tt class="systemitem">sysfs</tt> tree to
help create udev rules
</p>
</td>
</tr>
<tr>
<td>
<a id="udevtest" name="udevtest"></a><span class=
"term"><span><strong class=
"command">udevtest</strong></span></span>
</td>
<td>
<p>
Simulates a <span><strong class=
"command">udev</strong></span> run for the given
device, and prints out the name of the node the
real <span><strong class=
"command">udev</strong></span> would have created
or (not in LFS) the name of the renamed network
interface
</p>
</td>
</tr>
<tr>
<td>
<a id="etc-udev" name="etc-udev"></a><span class=
"term"><tt class="filename">/etc/udev</tt></span>
</td>
<td>
<p>
Contains <span><strong class=
"command">udev</strong></span> configuation files,
device permissions, and rules for device naming
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-util-linux" name=
"ch-system-util-linux"></a>6.59.&nbsp;Util-linux-2.12q
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Util-linux package contains miscellaneous utility
programs. Among them are utilities for handling file systems,
consoles, partitions, and messages.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.2 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">11.6 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Diffutils, GCC, Gettext, Glibc, Grep, Make,
Ncurses, Sed, and Zlib</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.59.1. FHS compliance notes
</h3>
</div>
<p>
The FHS recommends using the <tt class=
"filename">/var/lib/hwclock</tt> directory instead of the
usual <tt class="filename">/etc</tt> directory as the
location for the <tt class="filename">adjtime</tt> file. To
make the <span><strong class=
"command">hwclock</strong></span> program FHS-compliant, run
the following:
</p>
<pre class="userinput"><kbd class=
"command">sed -i 's@etc/adjtime@var/lib/hwclock/adjtime@g' \
hwclock/hwclock.c
mkdir -p /var/lib/hwclock</kbd></pre>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
6.59.2. Installation of Util-linux
</h3>
</div>
<p>
Util-linux fails to compile against newer versions of
Linux-Libc-Headers. The following patch properly fixes this
issue:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../util-linux-2.12q-cramfs-1.patch</kbd></pre>
<p>
Util-linux has a security vulnerability that could allow a
user to remount a volume without the <tt class=
"option">nosuid</tt> option. The following patch fixes this
issue:
</p>
<pre class="userinput"><kbd class=
"command">patch -Np1 -i ../util-linux-2.12q-umount_fix-1.patch</kbd></pre>
<p>
Prepare Util-linux for compilation:
</p>
<pre class="userinput"><kbd class=
"command">./configure</kbd></pre>
<p>
Compile the package:
</p>
<pre class="userinput"><kbd class=
"command">make HAVE_KILL=yes HAVE_SLN=yes</kbd></pre>
<p>
The meaning of the make parameters:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>HAVE_KILL=yes</tt></em></span>
</dt>
<dd>
<p>
This prevents the <span><strong class=
"command">kill</strong></span> program (already
installed by Procps) from being built and installed
again.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>HAVE_SLN=yes</tt></em></span>
</dt>
<dd>
<p>
This prevents the <span><strong class=
"command">sln</strong></span> program (a statically
linked version of <span><strong class=
"command">ln</strong></span> already installed by
Glibc) from being built and installed again.
</p>
</dd>
</dl>
</div>
<p>
This package does not come with a test suite.
</p>
<p>
Install the package and move the <span><strong class=
"command">logger</strong></span> binary to <tt class=
"filename">/bin</tt> as it is needed by the LFS-Bootscripts
package:
</p>
<pre class="userinput"><kbd class=
"command">make HAVE_KILL=yes HAVE_SLN=yes install
mv /usr/bin/logger /bin</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-utillinux" name="contents-utillinux"></a>
<h3 class="sect2">
6.59.3. Contents of Util-linux
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
programs:</span></strong> <span class="seg">agetty, arch,
blockdev, cal, cfdisk, chkdupexe, col, colcrt, colrm,
column, ctrlaltdel, cytune, ddate, dmesg, elvtune,
fdformat, fdisk, fsck.cramfs, fsck.minix, getopt,
hexdump, hwclock, ipcrm, ipcs, isosize, line, logger,
look, losetup, mcookie, mkfs, mkfs.bfs, mkfs.cramfs,
mkfs.minix, mkswap, more, mount, namei, pg, pivot_root,
ramsize (link to rdev), raw, rdev, readprofile, rename,
renice, rev, rootflags (link to rdev), script, setfdprm,
setsid, setterm, sfdisk, swapdev, swapoff (link to
swapon), swapon, tunelp, ul, umount, vidmode (link to
rdev), whereis, and write</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3515150" name="id3515150"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="agetty" name="agetty"></a><span class=
"term"><span><strong class=
"command">agetty</strong></span></span>
</td>
<td>
<p>
Opens a tty port, prompts for a login name, and
then invokes the <span><strong class=
"command">login</strong></span> program
</p>
</td>
</tr>
<tr>
<td>
<a id="arch" name="arch"></a><span class=
"term"><span><strong class=
"command">arch</strong></span></span>
</td>
<td>
<p>
Reports the machine's architecture
</p>
</td>
</tr>
<tr>
<td>
<a id="blockdev" name="blockdev"></a><span class=
"term"><span><strong class=
"command">blockdev</strong></span></span>
</td>
<td>
<p>
Allows users to call block device ioctls from the
command line
</p>
</td>
</tr>
<tr>
<td>
<a id="cal" name="cal"></a><span class=
"term"><span><strong class=
"command">cal</strong></span></span>
</td>
<td>
<p>
Displays a simple calendar
</p>
</td>
</tr>
<tr>
<td>
<a id="cfdisk" name="cfdisk"></a><span class=
"term"><span><strong class=
"command">cfdisk</strong></span></span>
</td>
<td>
<p>
Manipulates the partition table of the given device
</p>
</td>
</tr>
<tr>
<td>
<a id="chkdupexe" name="chkdupexe"></a><span class=
"term"><span><strong class=
"command">chkdupexe</strong></span></span>
</td>
<td>
<p>
Finds duplicate executables
</p>
</td>
</tr>
<tr>
<td>
<a id="col" name="col"></a><span class=
"term"><span><strong class=
"command">col</strong></span></span>
</td>
<td>
<p>
Filters out reverse line feeds
</p>
</td>
</tr>
<tr>
<td>
<a id="colcrt" name="colcrt"></a><span class=
"term"><span><strong class=
"command">colcrt</strong></span></span>
</td>
<td>
<p>
Filters <span><strong class=
"command">nroff</strong></span> output for
terminals that lack some capabilities, such as
overstriking and half-lines
</p>
</td>
</tr>
<tr>
<td>
<a id="colrm" name="colrm"></a><span class=
"term"><span><strong class=
"command">colrm</strong></span></span>
</td>
<td>
<p>
Filters out the given columns
</p>
</td>
</tr>
<tr>
<td>
<a id="column" name="column"></a><span class=
"term"><span><strong class=
"command">column</strong></span></span>
</td>
<td>
<p>
Formats a given file into multiple columns
</p>
</td>
</tr>
<tr>
<td>
<a id="ctrlaltdel" name="ctrlaltdel"></a><span class=
"term"><span><strong class=
"command">ctrlaltdel</strong></span></span>
</td>
<td>
<p>
Sets the function of the Ctrl+Alt+Del key
combination to a hard or a soft reset
</p>
</td>
</tr>
<tr>
<td>
<a id="cytune" name="cytune"></a><span class=
"term"><span><strong class=
"command">cytune</strong></span></span>
</td>
<td>
<p>
Tunes the parameters of the serial line drivers for
Cyclades cards
</p>
</td>
</tr>
<tr>
<td>
<a id="ddate" name="ddate"></a><span class=
"term"><span><strong class=
"command">ddate</strong></span></span>
</td>
<td>
<p>
Gives the Discordian date or converts the given
Gregorian date to a Discordian one
</p>
</td>
</tr>
<tr>
<td>
<a id="dmesg" name="dmesg"></a><span class=
"term"><span><strong class=
"command">dmesg</strong></span></span>
</td>
<td>
<p>
Dumps the kernel boot messages
</p>
</td>
</tr>
<tr>
<td>
<a id="elvtune" name="elvtune"></a><span class=
"term"><span><strong class=
"command">elvtune</strong></span></span>
</td>
<td>
<p>
Tunes the performance and interactivity of a block
device
</p>
</td>
</tr>
<tr>
<td>
<a id="fdformat" name="fdformat"></a><span class=
"term"><span><strong class=
"command">fdformat</strong></span></span>
</td>
<td>
<p>
Low-level formats a floppy disk
</p>
</td>
</tr>
<tr>
<td>
<a id="fdisk" name="fdisk"></a><span class=
"term"><span><strong class=
"command">fdisk</strong></span></span>
</td>
<td>
<p>
Manipulates the partition table of the given device
</p>
</td>
</tr>
<tr>
<td>
<a id="fsck.cramfs" name=
"fsck.cramfs"></a><span class=
"term"><span><strong class=
"command">fsck.cramfs</strong></span></span>
</td>
<td>
<p>
Performs a consistency check on the Cramfs file
system on the given device
</p>
</td>
</tr>
<tr>
<td>
<a id="fsck.minix" name="fsck.minix"></a><span class=
"term"><span><strong class=
"command">fsck.minix</strong></span></span>
</td>
<td>
<p>
Performs a consistency check on the Minix file
system on the given device
</p>
</td>
</tr>
<tr>
<td>
<a id="getopt" name="getopt"></a><span class=
"term"><span><strong class=
"command">getopt</strong></span></span>
</td>
<td>
<p>
Parses options in the given command line
</p>
</td>
</tr>
<tr>
<td>
<a id="hexdump" name="hexdump"></a><span class=
"term"><span><strong class=
"command">hexdump</strong></span></span>
</td>
<td>
<p>
Dumps the given file in hexadecimal or in another
given format
</p>
</td>
</tr>
<tr>
<td>
<a id="hwclock" name="hwclock"></a><span class=
"term"><span><strong class=
"command">hwclock</strong></span></span>
</td>
<td>
<p>
Reads or sets the system's hardware clock, also
called the Real-Time Clock (RTC) or Basic
Input-Output System (BIOS) clock
</p>
</td>
</tr>
<tr>
<td>
<a id="ipcrm" name="ipcrm"></a><span class=
"term"><span><strong class=
"command">ipcrm</strong></span></span>
</td>
<td>
<p>
Removes the given Inter-Process Communication (IPC)
resource
</p>
</td>
</tr>
<tr>
<td>
<a id="ipcs" name="ipcs"></a><span class=
"term"><span><strong class=
"command">ipcs</strong></span></span>
</td>
<td>
<p>
Provides IPC status information
</p>
</td>
</tr>
<tr>
<td>
<a id="isosize" name="isosize"></a><span class=
"term"><span><strong class=
"command">isosize</strong></span></span>
</td>
<td>
<p>
Reports the size of an iso9660 file system
</p>
</td>
</tr>
<tr>
<td>
<a id="line" name="line"></a><span class=
"term"><span><strong class=
"command">line</strong></span></span>
</td>
<td>
<p>
Copies a single line
</p>
</td>
</tr>
<tr>
<td>
<a id="logger" name="logger"></a><span class=
"term"><span><strong class=
"command">logger</strong></span></span>
</td>
<td>
<p>
Enters the given message into the system log
</p>
</td>
</tr>
<tr>
<td>
<a id="look" name="look"></a><span class=
"term"><span><strong class=
"command">look</strong></span></span>
</td>
<td>
<p>
Displays lines that begin with the given string
</p>
</td>
</tr>
<tr>
<td>
<a id="losetup" name="losetup"></a><span class=
"term"><span><strong class=
"command">losetup</strong></span></span>
</td>
<td>
<p>
Sets up and controls loop devices
</p>
</td>
</tr>
<tr>
<td>
<a id="mcookie" name="mcookie"></a><span class=
"term"><span><strong class=
"command">mcookie</strong></span></span>
</td>
<td>
<p>
Generates magic cookies (128-bit random hexadecimal
numbers) for <span><strong class=
"command">xauth</strong></span>
</p>
</td>
</tr>
<tr>
<td>
<a id="mkfs" name="mkfs"></a><span class=
"term"><span><strong class=
"command">mkfs</strong></span></span>
</td>
<td>
<p>
Builds a file system on a device (usually a hard
disk partition)
</p>
</td>
</tr>
<tr>
<td>
<a id="mkfs.bfs" name="mkfs.bfs"></a><span class=
"term"><span><strong class=
"command">mkfs.bfs</strong></span></span>
</td>
<td>
<p>
Creates a Santa Cruz Operations (SCO) bfs file
system
</p>
</td>
</tr>
<tr>
<td>
<a id="mkfs.cramfs" name=
"mkfs.cramfs"></a><span class=
"term"><span><strong class=
"command">mkfs.cramfs</strong></span></span>
</td>
<td>
<p>
Creates a cramfs file system
</p>
</td>
</tr>
<tr>
<td>
<a id="mkfs.minix" name="mkfs.minix"></a><span class=
"term"><span><strong class=
"command">mkfs.minix</strong></span></span>
</td>
<td>
<p>
Creates a Minix file system
</p>
</td>
</tr>
<tr>
<td>
<a id="mkswap" name="mkswap"></a><span class=
"term"><span><strong class=
"command">mkswap</strong></span></span>
</td>
<td>
<p>
Initializes the given device or file to be used as
a swap area
</p>
</td>
</tr>
<tr>
<td>
<a id="more" name="more"></a><span class=
"term"><span><strong class=
"command">more</strong></span></span>
</td>
<td>
<p>
A filter for paging through text one screen at a
time
</p>
</td>
</tr>
<tr>
<td>
<a id="mount" name="mount"></a><span class=
"term"><span><strong class=
"command">mount</strong></span></span>
</td>
<td>
<p>
Attaches the file system on the given device to a
specified directory in the file-system tree
</p>
</td>
</tr>
<tr>
<td>
<a id="namei" name="namei"></a><span class=
"term"><span><strong class=
"command">namei</strong></span></span>
</td>
<td>
<p>
Shows the symbolic links in the given pathnames
</p>
</td>
</tr>
<tr>
<td>
<a id="pg" name="pg"></a><span class=
"term"><span><strong class=
"command">pg</strong></span></span>
</td>
<td>
<p>
Displays a text file one screen full at a time
</p>
</td>
</tr>
<tr>
<td>
<a id="pivot_root" name="pivot_root"></a><span class=
"term"><span><strong class=
"command">pivot_root</strong></span></span>
</td>
<td>
<p>
Makes the given file system the new root file
system of the current process
</p>
</td>
</tr>
<tr>
<td>
<a id="ramsize" name="ramsize"></a><span class=
"term"><span><strong class=
"command">ramsize</strong></span></span>
</td>
<td>
<p>
Sets the size of the RAM disk in a bootable image
</p>
</td>
</tr>
<tr>
<td>
<a id="raw" name="raw"></a><span class=
"term"><span><strong class=
"command">raw</strong></span></span>
</td>
<td>
<p>
Used to bind a Linux raw character device to a
block device
</p>
</td>
</tr>
<tr>
<td>
<a id="rdev" name="rdev"></a><span class=
"term"><span><strong class=
"command">rdev</strong></span></span>
</td>
<td>
<p>
Queries and sets the root device, among other
things, in a bootable image
</p>
</td>
</tr>
<tr>
<td>
<a id="readprofile" name=
"readprofile"></a><span class=
"term"><span><strong class=
"command">readprofile</strong></span></span>
</td>
<td>
<p>
Reads kernel profiling information
</p>
</td>
</tr>
<tr>
<td>
<a id="rename" name="rename"></a><span class=
"term"><span><strong class=
"command">rename</strong></span></span>
</td>
<td>
<p>
Renames the given files, replacing a given string
with another
</p>
</td>
</tr>
<tr>
<td>
<a id="renice" name="renice"></a><span class=
"term"><span><strong class=
"command">renice</strong></span></span>
</td>
<td>
<p>
Alters the priority of running processes
</p>
</td>
</tr>
<tr>
<td>
<a id="rev" name="rev"></a><span class=
"term"><span><strong class=
"command">rev</strong></span></span>
</td>
<td>
<p>
Reverses the lines of a given file
</p>
</td>
</tr>
<tr>
<td>
<a id="rootflags" name="rootflags"></a><span class=
"term"><span><strong class=
"command">rootflags</strong></span></span>
</td>
<td>
<p>
Sets the rootflags in a bootable image
</p>
</td>
</tr>
<tr>
<td>
<a id="script" name="script"></a><span class=
"term"><span><strong class=
"command">script</strong></span></span>
</td>
<td>
<p>
Makes a typescript of a terminal session
</p>
</td>
</tr>
<tr>
<td>
<a id="setfdprm" name="setfdprm"></a><span class=
"term"><span><strong class=
"command">setfdprm</strong></span></span>
</td>
<td>
<p>
Sets user-provided floppy disk parameters
</p>
</td>
</tr>
<tr>
<td>
<a id="setsid" name="setsid"></a><span class=
"term"><span><strong class=
"command">setsid</strong></span></span>
</td>
<td>
<p>
Runs the given program in a new session
</p>
</td>
</tr>
<tr>
<td>
<a id="setterm" name="setterm"></a><span class=
"term"><span><strong class=
"command">setterm</strong></span></span>
</td>
<td>
<p>
Sets terminal attributes
</p>
</td>
</tr>
<tr>
<td>
<a id="sfdisk" name="sfdisk"></a><span class=
"term"><span><strong class=
"command">sfdisk</strong></span></span>
</td>
<td>
<p>
A disk partition table manipulator
</p>
</td>
</tr>
<tr>
<td>
<a id="swapdev" name="swapdev"></a><span class=
"term"><span><strong class=
"command">swapdev</strong></span></span>
</td>
<td>
<p>
Sets the swap device in a bootable image
</p>
</td>
</tr>
<tr>
<td>
<a id="swapoff" name="swapoff"></a><span class=
"term"><span><strong class=
"command">swapoff</strong></span></span>
</td>
<td>
<p>
Disables devices and files for paging and swapping
</p>
</td>
</tr>
<tr>
<td>
<a id="swapon" name="swapon"></a><span class=
"term"><span><strong class=
"command">swapon</strong></span></span>
</td>
<td>
<p>
Enables devices and files for paging and swapping
and lists the devices and files currently in use
</p>
</td>
</tr>
<tr>
<td>
<a id="tunelp" name="tunelp"></a><span class=
"term"><span><strong class=
"command">tunelp</strong></span></span>
</td>
<td>
<p>
Tunes the parameters of the line printer
</p>
</td>
</tr>
<tr>
<td>
<a id="ul" name="ul"></a><span class=
"term"><span><strong class=
"command">ul</strong></span></span>
</td>
<td>
<p>
A filter for translating underscores into escape
sequences indicating underlining for the terminal
in use
</p>
</td>
</tr>
<tr>
<td>
<a id="umount" name="umount"></a><span class=
"term"><span><strong class=
"command">umount</strong></span></span>
</td>
<td>
<p>
Disconnects a file system from the system's file
tree
</p>
</td>
</tr>
<tr>
<td>
<a id="vidmode" name="vidmode"></a><span class=
"term"><span><strong class=
"command">vidmode</strong></span></span>
</td>
<td>
<p>
Sets the video mode in a bootable image
</p>
</td>
</tr>
<tr>
<td>
<a id="whereis" name="whereis"></a><span class=
"term"><span><strong class=
"command">whereis</strong></span></span>
</td>
<td>
<p>
Reports the location of the binary, source, and man
page for the given command
</p>
</td>
</tr>
<tr>
<td>
<a id="write" name="write"></a><span class=
"term"><span><strong class=
"command">write</strong></span></span>
</td>
<td>
<p>
Sends a message to the given user <span class=
"emphasis"><em>if</em></span> that user has not
disabled receipt of such messages
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-aboutdebug" name=
"ch-system-aboutdebug"></a>6.60.&nbsp;About Debugging
Symbols
</h2>
</div>
</div>
</div>
<p>
Most programs and libraries are, by default, compiled with
debugging symbols included (with <span><strong class=
"command">gcc</strong></span>'s <em class=
"parameter"><tt>-g</tt></em> option). This means that when
debugging a program or library that was compiled with debugging
information included, the debugger can provide not only memory
addresses, but also the names of the routines and variables.
</p>
<p>
However, the inclusion of these debugging symbols enlarges a
program or library significantly. The following is an example
of the amount of space these symbols occupy:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
a bash binary with debugging symbols: 1200 KB
</p>
</li>
<li>
<p>
a bash binary without debugging symbols: 480 KB
</p>
</li>
<li>
<p>
Glibc and GCC files (<tt class="filename">/lib</tt> and
<tt class="filename">/usr/lib</tt>) with debugging
symbols: 87 MB
</p>
</li>
<li>
<p>
Glibc and GCC files without debugging symbols: 16 MB
</p>
</li>
</ul>
</div>
<p>
Sizes may vary depending on which compiler and C library were
used, but when comparing programs with and without debugging
symbols, the difference will usually be a factor between two
and five.
</p>
<p>
Because most users will never use a debugger on their system
software, a lot of disk space can be regained by removing these
symbols. The next section shows how to strip all debugging
symbols from the programs and libraries. Additional information
on system optimization can be found at <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/optimization.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/optimization.txt</i></a>.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-strippingagain" name=
"ch-system-strippingagain"></a>6.61.&nbsp;Stripping Again
</h2>
</div>
</div>
</div>
<p>
If the intended user is not a programmer and does not plan to
do any debugging on the system software, the system size can be
decreased by about 200 MB by removing the debugging symbols
from binaries and libraries. This causes no inconvenience other
than not being able to debug the software fully anymore.
</p>
<p>
Most people who use the command mentioned below do not
experience any difficulties. However, it is easy to make a typo
and render the new system unusable, so before running the
<span><strong class="command">strip</strong></span> command, it
is a good idea to make a backup of the current situation.
</p>
<p>
Before performing the stripping, take special care to ensure
that none of the binaries that are about to be stripped are
running. If unsure whether the user entered chroot with the
command given in <a href="#ch-system-chroot" title=
"6.3.&nbsp;Entering the Chroot Environment">Section&nbsp;6.3,
&ldquo;Entering the Chroot Environment,&rdquo;</a> first exit
from chroot:
</p>
<pre class="userinput"><kbd class="command">logout</kbd></pre>
<p>
Then reenter it with:
</p>
<pre class="userinput"><kbd class=
"command">chroot $LFS /tools/bin/env -i \
HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin \
/tools/bin/bash --login</kbd></pre>
<p>
Now the binaries and libraries can be safely stripped:
</p>
<pre class="userinput"><kbd class=
"command">/tools/bin/find /{,usr/}{bin,lib,sbin} -type f \
-exec /tools/bin/strip --strip-debug '{}' ';'</kbd></pre>
<p>
A large number of files will be reported as having their file
format not recognized. These warnings can be safely ignored.
These warnings indicate that those files are scripts instead of
binaries.
</p>
<p>
If disk space is very tight, the <em class=
"parameter"><tt>--strip-all</tt></em> option can be used on the
binaries in <tt class="filename">/{,usr/}{bin,sbin}</tt> to
gain several more megabytes. Do not use this option on
libraries&mdash;they will be destroyed.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-system-revisedchroot" name=
"ch-system-revisedchroot"></a>6.62.&nbsp;Cleaning Up
</h2>
</div>
</div>
</div>
<p>
From now on, when reentering the chroot environment after
exiting, use the following modified chroot command:
</p>
<pre class="userinput"><kbd class=
"command">chroot "$LFS" /usr/bin/env -i \
HOME=/root TERM="$TERM" PS1='\u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin \
/bin/bash --login</kbd></pre>
<p>
The reason for this is that the programs in <tt class=
"filename">/tools</tt> are no longer needed. Since they are no
longer needed you can delete the <tt class=
"filename">/tools</tt> directory if so desired or tar it up and
keep it to build another final system.
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
Removing <tt class="filename">/tools</tt> will also remove
the temporary copies of Tcl, Expect, and DejaGNU which were
used for running the toolchain tests. If you need these
programs later on, they will need to be recompiled and
re-installed. The BLFS book has instructions for this (see
<a href=
"http://www.linuxfromscratch.org/blfs/"><i>http://www.linuxfromscratch.org/blfs/</i></a>).
</p>
</div>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-bootscripts" name=
"chapter-bootscripts"></a>Chapter&nbsp;7.&nbsp;Setting Up
System Bootscripts
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-introduction" name=
"ch-scripts-introduction"></a>7.1.&nbsp;Introduction
</h2>
</div>
</div>
</div>
<p>
This chapter details how to install and configure the
LFS-Bootscripts package. Most of these scripts will work
without modification, but a few require additional
configuration files because they deal with hardware-dependent
information.
</p>
<p>
System-V style init scripts are employed in this book because
they are widely used. For additional options, a hint detailing
the BSD style init setup is available at <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/bsd-init.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/bsd-init.txt</i></a>.
Searching the LFS mailing lists for &ldquo;<span class=
"quote">depinit</span>&rdquo; will also offer additional
choices.
</p>
<p>
If using an alternative style of init scripts, skip this
chapter and move on to <a href="#chapter-bootable">Chapter
8</a>.
</p>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-bootscripts" name=
"ch-scripts-bootscripts"></a>7.2.&nbsp;LFS-Bootscripts-3.2.1
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The LFS-Bootscripts package contains a set of scripts to
start/stop the LFS system at bootup/shutdown.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">0.1 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">0.3 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash and
Coreutils</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
7.2.1. Installation of LFS-Bootscripts
</h3>
</div>
<p>
Install the package:
</p>
<pre class="userinput"><kbd class=
"command">make install</kbd></pre>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-bootscripts" name="contents-bootscripts"></a>
<h3 class="sect2">
7.2.2. Contents of LFS-Bootscripts
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
scripts:</span></strong> <span class="seg">checkfs,
cleanfs, console, functions, halt, hotplug, ifdown, ifup,
localnet, mountfs, mountkernfs, network, rc, reboot,
sendsignals, setclock, static, swap, sysklogd, template,
and udev</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3516725" name="id3516725"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="checkfs-bootscripts" name=
"checkfs-bootscripts"></a><span class=
"term"><span><strong class=
"command">checkfs</strong></span></span>
</td>
<td>
<p>
Checks the integrity of the file systems before
they are mounted (with the exception of journal and
network based file systems)
</p>
</td>
</tr>
<tr>
<td>
<a id="cleanfs-bootscripts" name=
"cleanfs-bootscripts"></a><span class=
"term"><span><strong class=
"command">cleanfs</strong></span></span>
</td>
<td>
<p>
Removes files that should not be preserved between
reboots, such as those in <tt class=
"filename">/var/run/</tt> and <tt class=
"filename">/var/lock/</tt>; it re-creates
<tt class="filename">/var/run/utmp</tt> and removes
the possibly present <tt class=
"filename">/etc/nologin</tt>, <tt class=
"filename">/fastboot</tt>, and <tt class=
"filename">/forcefsck</tt> files
</p>
</td>
</tr>
<tr>
<td>
<a id="console-bootscripts" name=
"console-bootscripts"></a><span class=
"term"><span><strong class=
"command">console</strong></span></span>
</td>
<td>
<p>
Loads the correct keymap table for the desired
keyboard layout; it also sets the screen font
</p>
</td>
</tr>
<tr>
<td>
<a id="functions-bootscripts" name=
"functions-bootscripts"></a><span class=
"term"><span><strong class=
"command">functions</strong></span></span>
</td>
<td>
<p>
Contains common functions, such as error and status
checking, that are used by several bootscripts
</p>
</td>
</tr>
<tr>
<td>
<a id="halt-bootscripts" name=
"halt-bootscripts"></a><span class=
"term"><span><strong class=
"command">halt</strong></span></span>
</td>
<td>
<p>
Halts the system
</p>
</td>
</tr>
<tr>
<td>
<a id="hotplug-bootscripts" name=
"hotplug-bootscripts"></a><span class=
"term"><span><strong class=
"command">hotplug</strong></span></span>
</td>
<td>
<p>
Loads modules for system devices
</p>
</td>
</tr>
<tr>
<td>
<a id="ifdown-bootscripts" name=
"ifdown-bootscripts"></a><span class=
"term"><span><strong class=
"command">ifdown</strong></span></span>
</td>
<td>
<p>
Assists the network script with stopping network
devices
</p>
</td>
</tr>
<tr>
<td>
<a id="ifup-bootscripts" name=
"ifup-bootscripts"></a><span class=
"term"><span><strong class=
"command">ifup</strong></span></span>
</td>
<td>
<p>
Assists the network script with starting network
devices
</p>
</td>
</tr>
<tr>
<td>
<a id="localnet-bootscripts" name=
"localnet-bootscripts"></a><span class=
"term"><span><strong class=
"command">localnet</strong></span></span>
</td>
<td>
<p>
Sets up the system's hostname and local loopback
device
</p>
</td>
</tr>
<tr>
<td>
<a id="mountfs-bootscripts" name=
"mountfs-bootscripts"></a><span class=
"term"><span><strong class=
"command">mountfs</strong></span></span>
</td>
<td>
<p>
Mounts all file systems, except ones that are
marked <span class=
"emphasis"><em>noauto</em></span> or are network
based
</p>
</td>
</tr>
<tr>
<td>
<a id="mountkernfs-bootscripts" name=
"mountkernfs-bootscripts"></a><span class=
"term"><span><strong class=
"command">mountkernfs</strong></span></span>
</td>
<td>
<p>
Mounts virtual kernel file systems, such as
<tt class="systemitem">proc</tt>
</p>
</td>
</tr>
<tr>
<td>
<a id="network-bootscripts" name=
"network-bootscripts"></a><span class=
"term"><span><strong class=
"command">network</strong></span></span>
</td>
<td>
<p>
Sets up network interfaces, such as network cards,
and sets up the default gateway (where applicable)
</p>
</td>
</tr>
<tr>
<td>
<a id="rc-bootscripts" name=
"rc-bootscripts"></a><span class=
"term"><span><strong class=
"command">rc</strong></span></span>
</td>
<td>
<p>
The master run-level control script; it is
responsible for running all the other bootscripts
one-by-one, in a sequence determined by the name of
the symbolic links being processed
</p>
</td>
</tr>
<tr>
<td>
<a id="reboot-bootscripts" name=
"reboot-bootscripts"></a><span class=
"term"><span><strong class=
"command">reboot</strong></span></span>
</td>
<td>
<p>
Reboots the system
</p>
</td>
</tr>
<tr>
<td>
<a id="sendsignals-bootscripts" name=
"sendsignals-bootscripts"></a><span class=
"term"><span><strong class=
"command">sendsignals</strong></span></span>
</td>
<td>
<p>
Makes sure every process is terminated before the
system reboots or halts
</p>
</td>
</tr>
<tr>
<td>
<a id="setclock-bootscripts" name=
"setclock-bootscripts"></a><span class=
"term"><span><strong class=
"command">setclock</strong></span></span>
</td>
<td>
<p>
Resets the kernel clock to local time in case the
hardware clock is not set to UTC time
</p>
</td>
</tr>
<tr>
<td>
<a id="static-bootscripts" name=
"static-bootscripts"></a><span class=
"term"><span><strong class=
"command">static</strong></span></span>
</td>
<td>
<p>
Provides the functionality needed to assign a
static Internet Protocol (IP) address to a network
interface
</p>
</td>
</tr>
<tr>
<td>
<a id="swap-bootscripts" name=
"swap-bootscripts"></a><span class=
"term"><span><strong class=
"command">swap</strong></span></span>
</td>
<td>
<p>
Enables and disables swap files and partitions
</p>
</td>
</tr>
<tr>
<td>
<a id="sysklogd-bootscripts" name=
"sysklogd-bootscripts"></a><span class=
"term"><span><strong class=
"command">sysklogd</strong></span></span>
</td>
<td>
<p>
Starts and stops the system and kernel log daemons
</p>
</td>
</tr>
<tr>
<td>
<a id="template-bootscripts" name=
"template-bootscripts"></a><span class=
"term"><span><strong class=
"command">template</strong></span></span>
</td>
<td>
<p>
A template to create custom bootscripts for other
daemons
</p>
</td>
</tr>
<tr>
<td>
<a id="udev-bootscripts" name=
"udev-bootscripts"></a><span class=
"term"><span><strong class=
"command">udev</strong></span></span>
</td>
<td>
<p>
Prepares the <tt class="filename">/dev</tt>
directory and starts Udev
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-usage" name=
"ch-scripts-usage"></a>7.3.&nbsp;How Do These Bootscripts
Work?
</h2>
</div>
</div>
</div>
<p>
Linux uses a special booting facility named SysVinit that is
based on a concept of <span class=
"emphasis"><em>run-levels</em></span>. It can be quite
different from one system to another, so it cannot be assumed
that because things worked in one particular Linux
distribution, they should work the same in LFS too. LFS has its
own way of doing things, but it respects generally accepted
standards.
</p>
<p>
SysVinit (which will be referred to as &ldquo;<span class=
"quote">init</span>&rdquo; from now on) works using a
run-levels scheme. There are seven (numbered 0 to 6) run-levels
(actually, there are more run-levels, but they are for special
cases and are generally not used. See <tt class=
"filename">init(8)</tt> for more details), and each one of
those corresponds to the actions the computer is supposed to
perform when it starts up. The default run-level is 3. Here are
the descriptions of the different run-levels as they are
implemented:
</p>
<div class="literallayout">
<p>
0:&nbsp;halt&nbsp;the&nbsp;computer<br />
1:&nbsp;single-user&nbsp;mode<br />
2:&nbsp;multi-user&nbsp;mode&nbsp;without&nbsp;networking<br />
3:&nbsp;multi-user&nbsp;mode&nbsp;with&nbsp;networking<br />
4:&nbsp;reserved&nbsp;for&nbsp;customization,&nbsp;otherwise&nbsp;does&nbsp;the&nbsp;same&nbsp;as&nbsp;3<br />
5:&nbsp;same&nbsp;as&nbsp;4,&nbsp;it&nbsp;is&nbsp;usually&nbsp;used&nbsp;for&nbsp;GUI&nbsp;login&nbsp;(like&nbsp;X's&nbsp;<span>
<strong class=
"command">xdm</strong></span>&nbsp;or&nbsp;KDE's&nbsp;<span><strong class="command">
kdm</strong></span>)<br />
6:&nbsp;reboot&nbsp;the&nbsp;computer
</p>
</div>
<p>
The command used to change run-levels is <span><strong class=
"command">init <em class=
"replaceable"><tt>[runlevel]</tt></em></strong></span>, where
<em class="replaceable"><tt>[runlevel]</tt></em> is the target
run-level. For example, to reboot the computer, a user could
issue the <span><strong class="command">init 6</strong></span>
command, which is an alias for the <span><strong class=
"command">reboot</strong></span> command. Likewise,
<span><strong class="command">init 0</strong></span> is an
alias for the <span><strong class=
"command">halt</strong></span> command.
</p>
<p>
There are a number of directories under <tt class=
"filename">/etc/rc.d</tt> that look like <tt class=
"filename">rc?.d</tt> (where ? is the number of the run-level)
and <tt class="filename">rcsysinit.d</tt>, all containing a
number of symbolic links. Some begin with a <span class=
"emphasis"><em>K</em></span>, the others begin with an
<span class="emphasis"><em>S</em></span>, and all of them have
two numbers following the initial letter. The K means to stop
(kill) a service and the S means to start a service. The
numbers determine the order in which the scripts are run, from
00 to 99&mdash;the lower the number the earlier it gets
executed. When <span><strong class=
"command">init</strong></span> switches to another run-level,
the appropriate services are either started or stopped,
depending on the runlevel chosen.
</p>
<p>
The real scripts are in <tt class=
"filename">/etc/rc.d/init.d</tt>. They do the actual work, and
the symlinks all point to them. Killing links and starting
links point to the same script in <tt class=
"filename">/etc/rc.d/init.d</tt>. This is because the scripts
can be called with different parameters like <em class=
"parameter"><tt>start</tt></em>, <em class=
"parameter"><tt>stop</tt></em>, <em class=
"parameter"><tt>restart</tt></em>, <em class=
"parameter"><tt>reload</tt></em>, and <em class=
"parameter"><tt>status</tt></em>. When a K link is encountered,
the appropriate script is run with the <em class=
"parameter"><tt>stop</tt></em> argument. When an S link is
encountered, the appropriate script is run with the <em class=
"parameter"><tt>start</tt></em> argument.
</p>
<p>
There is one exception to this explanation. Links that start
with an <span class="emphasis"><em>S</em></span> in the
<tt class="filename">rc0.d</tt> and <tt class=
"filename">rc6.d</tt> directories will not cause anything to be
started. They will be called with the parameter <em class=
"parameter"><tt>stop</tt></em> to stop something. The logic
behind this is that when a user is going to reboot or halt the
system, nothing needs to be started. The system only needs to
be stopped.
</p>
<p>
These are descriptions of what the arguments make the scripts
do:
</p>
<div class="variablelist">
<dl>
<dt>
<span class="term"><em class=
"parameter"><tt>start</tt></em></span>
</dt>
<dd>
<p>
The service is started.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>stop</tt></em></span>
</dt>
<dd>
<p>
The service is stopped.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>restart</tt></em></span>
</dt>
<dd>
<p>
The service is stopped and then started again.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>reload</tt></em></span>
</dt>
<dd>
<p>
The configuration of the service is updated. This is used
after the configuration file of a service was modified,
when the service does not need to be restarted.
</p>
</dd>
<dt>
<span class="term"><em class=
"parameter"><tt>status</tt></em></span>
</dt>
<dd>
<p>
Tells if the service is running and with which PIDs.
</p>
</dd>
</dl>
</div>
<p>
Feel free to modify the way the boot process works (after all,
it is your own LFS system). The files given here are an example
of how it can be done.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-udev" name=
"ch-scripts-udev"></a>7.4.&nbsp;Device and Module
Handling on an LFS System
</h2>
</div>
</div>
</div>
<p>
In <a href="#chapter-building-system">Chapter 6</a>, we
installed the Udev package. Before we go into the details
regarding how this works, a brief history of previous methods
of handling devices is in order.
</p>
<p>
Linux systems in general traditionally use a static device
creation method, whereby a great many device nodes are created
under <tt class="filename">/dev</tt> (sometimes literally
thousands of nodes), regardless of whether the corresponding
hardware devices actually exist. This is typically done via a
<span><strong class="command">MAKEDEV</strong></span> script,
which contains a number of calls to the <span><strong class=
"command">mknod</strong></span> program with the relevant major
and minor device numbers for every possible device that might
exist in the world. Using the Udev method, only those devices
which are detected by the kernel get device nodes created for
them. Because these device nodes will be created each time the
system boots, they will be stored on a <tt class=
"systemitem">tmpfs</tt> file system (a virtual file system that
resides entirely in system memory). Device nodes do not require
much space, so the memory that is used is negligible.
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
7.4.1. History
</h3>
</div>
<p>
In February 2000, a new filesystem called <tt class=
"systemitem">devfs</tt> was merged into the 2.3.46 kernel and
was made available during the 2.4 series of stable kernels.
Although it was present in the kernel source itself, this
method of creating devices dynamically never received
overwhelming support from the core kernel developers.
</p>
<p>
The main problem with the approach adopted by <tt class=
"systemitem">devfs</tt> was the way it handled device
detection, creation, and naming. The latter issue, that of
device node naming, was perhaps the most critical. It is
generally accepted that if device names are allowed to be
configurable, then the device naming policy should be up to a
system administrator, not imposed on them by any particular
developer(s). The <tt class="systemitem">devfs</tt> file
system also suffers from race conditions that are inherent in
its design and cannot be fixed without a substantial revision
to the kernel. It has also been marked as deprecated due to a
lack of recent maintenance.
</p>
<p>
With the development of the unstable 2.5 kernel tree, later
released as the 2.6 series of stable kernels, a new virtual
filesystem called <tt class="systemitem">sysfs</tt> came to
be. The job of <tt class="systemitem">sysfs</tt> is to export
a view of the system's hardrware configuration to userspace
processes. With this userspace-visible representation, the
possibility of seeing a userspace replacement for <tt class=
"systemitem">devfs</tt> became much more realistic.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
7.4.2. Udev Implementation
</h3>
</div>
<p>
The <tt class="systemitem">sysfs</tt> filesystem was
mentioned briefly above. One may wonder how <tt class=
"systemitem">sysfs</tt> knows about the devices present on a
system and what device numbers should be used for them.
Drivers that have been compiled into the kernel directly
register their objects with <tt class="systemitem">sysfs</tt>
as they are detected by the kernel. For drivers compiled as
modules, this registration will happen when the module is
loaded. Once the <tt class="systemitem">sysfs</tt> filesystem
is mounted (on <tt class="filename">/sys</tt>), data which
the built-in drivers registered with <tt class=
"systemitem">sysfs</tt> are available to userspace processes
and to <span><strong class="command">udev</strong></span> for
device node creation.
</p>
<p>
The <span><strong class="command">S10udev</strong></span>
initscript takes care of creating these device nodes when
Linux is booted. This script starts by registering
<span><strong class="command">/sbin/udevsend</strong></span>
as a hotplug event handler. Hotplug events (discussed below)
are not usually generated during this stage, but
<span><strong class="command">udev</strong></span> is
registered just in case they do occur. The
<span><strong class="command">udevstart</strong></span>
program then walks through the <tt class=
"systemitem">/sys</tt> filesystem and creates devices under
<tt class="filename">/dev</tt> that match the descriptions.
For example, <tt class="filename">/sys/class/tty/vcs/dev</tt>
contains the string &ldquo;<span class=
"quote">7:0</span>&rdquo; This string is used by
<span><strong class="command">udevstart</strong></span> to
create <tt class="filename">/dev/vcs</tt> with major number
<span class="emphasis"><em>7</em></span> and minor
<span class="emphasis"><em>0</em></span>. The names and
permissions of the nodes created under the <tt class=
"filename">/dev</tt> directory are configured according to
the rules specified in the files within the <tt class=
"filename">/etc/udev/rules.d/</tt> directory. These are
numbered in a similar fashion to the LFS-Bootscripts package.
If <span><strong class="command">udev</strong></span> can't
find a rule for the device it is creating, it will default
permissions to <span class="emphasis"><em>660</em></span> and
ownership to <span class=
"emphasis"><em>root:root</em></span>.
</p>
<p>
Once the above stage is complete, all devices that were
already present and have compiled-in drivers will be
available for use. This leads us to the devices that have
modular drivers.
</p>
<p>
Earlier, we mentioned the concept of a &ldquo;<span class=
"quote">hotplug event handler.</span>&rdquo; When a new
device connection is detected by the kernel, the kernel will
generate a hotplug event and look at the file <tt class=
"filename">/proc/sys/kernel/hotplug</tt> to determine the
userspace program that handles the device's connection. The
<span><strong class="command">udev</strong></span> bootscript
registered <span><strong class=
"command">udevsend</strong></span> as this handler. When
these hotplug events are generated, the kernel will tell
<span><strong class="command">udev</strong></span> to check
the <tt class="filename">/sys</tt> filesystem for the
information pertaining to this new device and create the
<tt class="filename">/dev</tt> entry for it.
</p>
<p>
This brings us to one problem that exists with
<span><strong class="command">udev</strong></span>, and
likewise with <tt class="systemitem">devfs</tt> before it. It
is commonly referred to as the &ldquo;<span class=
"quote">chicken and egg</span>&rdquo; problem. Most Linux
distributions handle loading modules via entries in
<tt class="filename">/etc/modules.conf</tt>. Access to a
device node causes the appropriate kernel module to load.
With <span><strong class="command">udev</strong></span>, this
method will not work because the device node does not exist
until the module is loaded. To solve this, the
<span><strong class="command">S05modules</strong></span>
bootscript was added to the LFS-Bootscripts package, along
with the <tt class="filename">/etc/sysconfig/modules</tt>
file. By adding module names to the <tt class=
"filename">modules</tt> file, these modules will be loaded
when the computer starts up. This allows <span><strong class=
"command">udev</strong></span> to detect the devices and
create the appropriate device nodes.
</p>
<p>
Note that on slower machines or for drivers that create a lot
of device nodes, the process of creating devices may take a
few seconds to complete. This means that some device nodes
may not be immediately accessible.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
7.4.3. Handling Hotpluggable/Dynamic Devices
</h3>
</div>
<p>
When you plug in a device, such as a Universal Serial Bus
(USB) MP3 player, the kernel recognizes that the device is
now connected and generates a hotplug event. If the driver is
already loaded (either because it was compiled into the
kernel or because it was loaded via the <span><strong class=
"command">S05modules</strong></span> bootscript),
<span><strong class="command">udev</strong></span> will be
called upon to create the relevant device node(s) according
to the <tt class="systemitem">sysfs</tt> data available in
<tt class="filename">/sys</tt>.
</p>
<p>
If the driver for the just plugged in device is available as
a module but currently unloaded, the Hotplug package will
load the appropriate module and make this device available by
creating the device node(s) for it.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
7.4.4. Problems with Creating Devices
</h3>
</div>
<p>
There are a few known problems when it comes to automatically
creating device nodes:
</p>
<p>
1) A kernel driver may not export its data to <tt class=
"systemitem">sysfs</tt>.
</p>
<p>
This is most common with third party drivers from outside the
kernel tree. Udev will be unable to automatically create
device nodes for such drivers. Use the <tt class=
"filename">/etc/sysconfig/createfiles</tt> configuration file
to manually create the devices. Consult the <tt class=
"filename">devices.txt</tt> file inside the kernel
documentation or the documentation for that driver to find
the proper major/minor numbers.
</p>
<p>
2) A non-hardware device is required. This is most common
with the Advanced Linux Sound Architecture (ALSA) project's
Open Sound System (OSS) compatibility module. These types of
devices can be handled in one of two ways:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
Adding the module names to <tt class=
"filename">/etc/sysconfig/modules</tt>
</p>
</li>
<li>
<p>
Using an &ldquo;<span class=
"quote">install</span>&rdquo; line in <tt class=
"filename">/etc/modprobe.conf</tt>. This tells the
<span><strong class="command">modprobe</strong></span>
command &ldquo;<span class="quote">when loading this
module, also load this other module, at the same
time.</span>&rdquo; For example:
</p>
<pre class="userinput"><kbd class=
"command">install snd-pcm modprobe -i snd-pcm ; modprobe \
snd-pcm-oss ; true</kbd></pre>
<p>
This will cause the system to load both the
<span class="emphasis"><em>snd-pcm</em></span> and
<span class="emphasis"><em>snd-pcm-oss</em></span>
modules when any request is made to load the driver
<span class="emphasis"><em>snd-pcm</em></span>.
</p>
</li>
</ul>
</div>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
7.4.5. Useful Reading
</h3>
</div>
<p>
Additional helpful documentation is available at the
following sites:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
A Userspace Implementation of <tt class=
"systemitem">devfs</tt> <a href=
"http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf">
<i>http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf</i></a>
</p>
</li>
<li>
<p>
udev FAQ <a href=
"http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ">
<i>http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ</i></a>
</p>
</li>
<li>
<p>
The Linux Kernel Driver Model <a href=
"http://public.planetmirror.com/pub/lca/2003/proceedings/papers/Patrick_Mochel/Patrick_Mochel.pdf">
<i>http://public.planetmirror.com/pub/lca/2003/proceedings/papers/Patrick_Mochel/Patrick_Mochel.pdf</i></a>
</p>
</li>
</ul>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-setclock" name=
"ch-scripts-setclock"></a>7.5.&nbsp;Configuring the
setclock Script
</h2>
</div>
</div>
</div>
<p>
The <span><strong class="command">setclock</strong></span>
script reads the time from the hardware clock, also known as
the BIOS or the Complementary Metal Oxide Semiconductor (CMOS)
clock. If the hardware clock is set to UTC, this script will
convert the hardware clock's time to the local time using the
<tt class="filename">/etc/localtime</tt> file (which tells the
<span><strong class="command">hwclock</strong></span> program
which timezone the user is in). There is no way to detect
whether or not the hardware clock is set to UTC, so this needs
to be configured manually.
</p>
<p>
If you cannot remember whether or not the hardware clock is set
to UTC, find out by running the <strong class=
"userinput"><tt>hwclock --localtime --show</tt></strong>
command. This will display what the current time is according
to the hardware clock. If this time matches whatever your watch
says, then the hardware clock is set to local time. If the
output from <span><strong class=
"command">hwclock</strong></span> is not local time, chances
are it is set to UTC time. Verify this by adding or subtracting
the proper amount of hours for the timezone to the time shown
by <span><strong class="command">hwclock</strong></span>. For
example, if you are currently in the MST timezone, which is
also known as GMT -0700, add seven hours to the local time.
</p>
<p>
Change the value of the <tt class="envar">UTC</tt> variable
below to a value of <em class="parameter"><tt>0</tt></em>
(zero) if the hardware clock is <span class=
"emphasis"><em>not</em></span> set to UTC time.
</p>
<p>
Create a new file <tt class=
"filename">/etc/sysconfig/clock</tt> by running the following:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/sysconfig/clock
UTC=1
# End /etc/sysconfig/clock</tt>
EOF</kbd></pre>
<p>
A good hint explaining how to deal with time on LFS is
available at <a href=
"http://www.linuxfromscratch.org/hints/downloads/files/time.txt">
<i>http://www.linuxfromscratch.org/hints/downloads/files/time.txt</i></a>.
It explains issues such as time zones, UTC, and the <tt class=
"envar">TZ</tt> environment variable.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-console" name=
"ch-scripts-console"></a>7.6.&nbsp;Configuring the Linux
Console
</h2>
</div>
</div>
</div>
<p>
This section discusses how to configure the
<span><strong class="command">console</strong></span>
bootscript that sets up the keyboard map and the console font.
If non-ASCII characters (e.g., the British pound sign and Euro
character) will not be used and the keyboard is a U.S. one,
skip this section. Without the configuration file, the
<span><strong class="command">console</strong></span>
bootscript will do nothing.
</p>
<p>
The <span><strong class="command">console</strong></span>
script reads the <tt class=
"filename">/etc/sysconfig/console</tt> file for configuration
information. Decide which keymap and screen font will be used.
Various language-specific HOWTO's can also help with this (see
<a href=
"http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"><i>http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html</i></a>.
A pre-made <tt class="filename">/etc/sysconfig/console</tt>
file with known settings for several countries was installed
with the LFS-Bootscripts package, so the relevant section can
be uncommented if the country is supported. If still in doubt,
look in the <tt class="filename">/usr/share/kbd</tt> directory
for valid keymaps and screen fonts. Read <tt class=
"filename">loadkeys(1)</tt> and <tt class=
"filename">setfont(8)</tt> to determine the correct arguments
for these programs. Once decided, create the configuration file
with the following command:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"
<tt class="literal">KEYMAP="<em class=
"replaceable"><tt>[arguments for loadkeys]</tt></em>"
FONT="<em class="replaceable"><tt>[arguments for setfont]</tt></em>"</tt>
EOF</kbd></pre>
<p>
For example, for Spanish users who also want to use the Euro
character (accessible by pressing AltGr+E), the following
settings are correct:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt;/etc/sysconfig/console &lt;&lt;"EOF"
<tt class="literal">KEYMAP="es euro2"
FONT="lat9-16 -u iso01"</tt>
EOF</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
The <tt class="envar">FONT</tt> line above is correct only
for the ISO 8859-15 character set. If using ISO 8859-1 and,
therefore, a pound sign instead of Euro, the correct
<tt class="envar">FONT</tt> line would be:
</p>
<pre class="userinput"><kbd class=
"command">FONT="lat1-16"</kbd></pre>
</div>
</div>
<p>
If the <tt class="envar">KEYMAP</tt> or <tt class=
"envar">FONT</tt> variable is not set, the <span><strong class=
"command">console</strong></span> initscript will not run the
corresponding program.
</p>
<p>
In some keymaps, the Backspace and Delete keys send characters
different from ones in the default keymap built into the
kernel. This confuses some applications. For example, Emacs
displays its help (instead of erasing the character before the
cursor) when Backspace is pressed. To check if the keymap in
use is affected (this works only for i386 keymaps):
</p>
<pre class="userinput"><kbd class=
"command">zgrep '\W14\W' <em class=
"replaceable"><tt>[/path/to/your/keymap]</tt></em></kbd></pre>
<p>
If the keycode 14 is Backspace instead of Delete, create the
following keymap snippet to fix this issue:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -pv /etc/kbd &amp;&amp; cat &gt; /etc/kbd/bs-sends-del &lt;&lt;"EOF"
<tt class=
"literal"> keycode 14 = Delete Delete Delete Delete
alt keycode 14 = Meta_Delete
altgr alt keycode 14 = Meta_Delete
keycode 111 = Remove
altgr control keycode 111 = Boot
control alt keycode 111 = Boot
altgr control alt keycode 111 = Boot</tt>
EOF</kbd></pre>
<p>
Tell the <span><strong class="command">console</strong></span>
script to load this snippet after the main keymap:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt;&gt;/etc/sysconfig/console &lt;&lt;"EOF"
<tt class="literal">KEYMAP_CORRECTIONS="/etc/kbd/bs-sends-del"</tt>
EOF</kbd></pre>
<p>
To compile the keymap directly into the kernel instead of
setting it every time from the <span><strong class=
"command">console</strong></span> bootscript, follow the
instructions given in <a href="#ch-bootable-kernel" title=
"8.3.&nbsp;Linux-2.6.11.12">Section 8.3,
&ldquo;Linux-2.6.11.12.&rdquo;</a> Doing this ensures that the
keyboard will always work as expected, even when booting into
maintenance mode (by passing <em class=
"parameter"><tt>init=/bin/sh</tt></em> to the kernel), because
the <span><strong class="command">console</strong></span>
bootscript will not be run in that situation. Additionally, the
kernel will not set the screen font automatically. This should
not pose many problems because ASCII characters will be handled
correctly, and it is unlikely that a user would need to rely on
non-ASCII characters while in maintenance mode.
</p>
<p>
Since the kernel will set up the keymap, it is possible to omit
the <tt class="envar">KEYMAP</tt> variable from the <tt class=
"filename">/etc/sysconfig/console</tt> configuration file. It
can also be left in place, if desired, without consequence.
Keeping it could be beneficial if running several different
kernels where it is difficult to ensure that the keymap is
compiled into every one of them.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-sysklogd" name=
"ch-scripts-sysklogd"></a>7.7.&nbsp;Configuring the
sysklogd script
</h2>
</div>
</div>
</div>
<p>
The <tt class="filename">sysklogd</tt> script invokes the
<span><strong class="command">syslogd</strong></span> program
with the <em class="parameter"><tt>-m 0</tt></em> option. This
option turns off the periodic timestamp mark that
<span><strong class="command">syslogd</strong></span> writes to
the log files every 20 minutes by default. If you want to turn
on this periodic timestamp mark, edit the <tt class=
"filename">sysklogd</tt> script and make the changes
accordingly. See <strong class="userinput"><tt>man
syslogd</tt></strong> for more information.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-inputrc" name=
"ch-scripts-inputrc"></a>7.8.&nbsp;Creating the
/etc/inputrc File
</h2>
</div>
</div>
</div>
<p>
The <tt class="filename">inputrc</tt> file handles keyboard
mapping for specific situations. This file is the startup file
used by Readline &mdash; the input-related library &mdash; used
by Bash and most other shells.
</p>
<p>
Most people do not need user-specific keyboard mappings so the
command below creates a global <tt class=
"filename">/etc/inputrc</tt> used by everyone who logs in. If
you later decide you need to override the defaults on a
per-user basis, you can create a <tt class=
"filename">.inputrc</tt> file in the user's home directory with
the modified mappings.
</p>
<p>
For more information on how to edit the <tt class=
"filename">inputrc</tt> file, see <span><strong class=
"command">info bash</strong></span> under the <span class=
"emphasis"><em>Readline Init File</em></span> section.
<span><strong class="command">info readline</strong></span> is
also a good source of information.
</p>
<p>
Below is a generic global <tt class="filename">inputrc</tt>
along with comments to explain what the various options do.
Note that comments cannot be on the same line as commands.
Create the file using the following command:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/inputrc &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/inputrc
# Modified by Chris Lynn &lt;roryo@roryo.dynup.net&gt;
# Allow the command prompt to wrap to the next line
set horizontal-scroll-mode Off
# Enable 8bit input
set meta-flag On
set input-meta On
# Turns off 8th bit stripping
set convert-meta Off
# Keep the 8th bit for display
set output-meta On
# none, visible or audible
set bell-style none
# All of the following map the escape sequence of the
# value contained inside the 1st argument to the
# readline specific functions
"\eOd": backward-word
"\eOc": forward-word
# for linux console
"\e[1~": beginning-of-line
"\e[4~": end-of-line
"\e[5~": beginning-of-history
"\e[6~": end-of-history
"\e[3~": delete-char
"\e[2~": quoted-insert
# for xterm
"\eOH": beginning-of-line
"\eOF": end-of-line
# for Konsole
"\e[H": beginning-of-line
"\e[F": end-of-line
# End /etc/inputrc</tt>
EOF</kbd></pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-profile" name=
"ch-scripts-profile"></a>7.9.&nbsp;The Bash Shell Startup
Files
</h2>
</div>
</div>
</div>
<p>
The shell program <span><strong class=
"command">/bin/bash</strong></span> (hereafter referred to as
&ldquo;<span class="quote">the shell</span>&rdquo;) uses a
collection of startup files to help create an environment to
run in. Each file has a specific use and may affect login and
interactive environments differently. The files in the
<tt class="filename">/etc</tt> directory provide global
settings. If an equivalent file exists in the home directory,
it may override the global settings.
</p>
<p>
An interactive login shell is started after a successful login,
using <span><strong class="command">/bin/login</strong></span>,
by reading the <tt class="filename">/etc/passwd</tt> file. An
interactive non-login shell is started at the command-line
(e.g., <tt class="prompt">[prompt]$</tt><span><strong class=
"command">/bin/bash</strong></span>). A non-interactive shell
is usually present when a shell script is running. It is
non-interactive because it is processing a script and not
waiting for user input between commands.
</p>
<p>
For more information, see <span><strong class="command">info
bash</strong></span> under the <span class="emphasis"><em>Bash
Startup Files and Interactive Shells</em></span> section.
</p>
<p>
The files <tt class="filename">/etc/profile</tt> and <tt class=
"filename">~/.bash_profile</tt> are read when the shell is
invoked as an interactive login shell.
</p>
<p>
The base <tt class="filename">/etc/profile</tt> below sets some
environment variables necessary for native language support.
Setting them properly results in:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
The output of programs translated into the native
language
</p>
</li>
<li>
<p>
Correct classification of characters into letters, digits
and other classes. This is necessary for
<span><strong class="command">bash</strong></span> to
properly accept non-ASCII characters in command lines in
non-English locales
</p>
</li>
<li>
<p>
The correct alphabetical sorting order for the country
</p>
</li>
<li>
<p>
Appropriate default paper size
</p>
</li>
<li>
<p>
Correct formatting of monetary, time, and date values
</p>
</li>
</ul>
</div>
<p>
This script also sets the <tt class="envar">INPUTRC</tt>
environment variable that makes Bash and Readline use the
<tt class="filename">/etc/inputrc</tt> file created earlier.
</p>
<p>
Replace <em class="replaceable"><tt>[ll]</tt></em> below with
the two-letter code for the desired language (e.g.,
&ldquo;<span class="quote">en</span>&rdquo;) and <em class=
"replaceable"><tt>[CC]</tt></em> with the two-letter code for
the appropriate country (e.g., &ldquo;<span class=
"quote">GB</span>&rdquo;). <em class=
"replaceable"><tt>[charmap]</tt></em> should be replaced with
the canonical charmap for your chosen locale.
</p>
<p>
The list of all locales supported by Glibc can be obtained by
running the following command:
</p>
<pre class="userinput"><kbd class="command">locale -a</kbd></pre>
<p>
Locales can have a number of synonyms, e.g. &ldquo;<span class=
"quote">ISO-8859-1</span>&rdquo; is also referred to as
&ldquo;<span class="quote">iso8859-1</span>&rdquo; and
&ldquo;<span class="quote">iso88591</span>&rdquo;. Some
applications cannot handle the various synonyms correctly, so
it is safest to choose the canonical name for a particular
locale. To determine the canonical name, run the following
command, where <em class="replaceable"><tt>[locale
name]</tt></em> is the output given by <span><strong class=
"command">locale -a</strong></span> for your preferred locale
(&ldquo;<span class="quote">en_GB.iso88591</span>&rdquo; in our
example).
</p>
<pre class="userinput"><kbd class="command">LC_ALL=<em class=
"replaceable"><tt>[locale name]</tt></em> locale charmap</kbd></pre>
<p>
For the &ldquo;<span class="quote">en_GB.iso88591</span>&rdquo;
locale, the above command will print:
</p>
<pre class="screen">ISO-8859-1</pre>
<p>
This results in a final locale setting of &ldquo;<span class=
"quote">en_GB.ISO-8859-1</span>&rdquo;. It is important that
the locale found using the heuristic above is tested prior to
it being added to the Bash startup files:
</p>
<pre class="userinput"><kbd class=
"command">LC_ALL=[locale name] locale country
LC_ALL=[locale name] locale language
LC_ALL=[locale name] locale charmap
LC_ALL=[locale name] locale int_curr_symbol
LC_ALL=[locale name] locale int_prefix</kbd></pre>
<p>
The above commands should print the country and language names,
the character encoding used by the locale, the local currency
and the prefix to dial before the telephone number in order to
get into the country. If any of the commands above fail with a
message similar to the one shown below, this means that your
locale was either not installed in Chapter 6 or is not
supported by the default installation of Glibc.
</p>
<pre class="screen"><tt class=
"computeroutput">locale: Cannot set LC_* to default locale: No such file or directory</tt></pre>
<p>
If this happens, you should either install the desired locale
using the <span><strong class=
"command">localedef</strong></span> command, or consider
choosing a different locale. Further instructions assume that
there are no such error messages from Glibc.
</p>
<p>
Some packages beyond LFS may also lack support for your chosen
locale. One example is the X library (part of the X Window
System), which outputs the following error message:
</p>
<pre class="screen"><tt class=
"computeroutput">Warning: locale not supported by Xlib, locale set to C</tt></pre>
<p>
Sometimes it is possible to fix this by removing the charmap
part of the locale specification, as long as that does not
change the character map that Glibc associates with the locale
(this can be checked by running the <span><strong class=
"command">locale charmap</strong></span> command in both
locales). For example, one would have to change
"de_DE.ISO-8859-15@euro" to "de_DE@euro" in order to get this
locale recognized by Xlib.
</p>
<p>
Other packages can also function incorrectly (but may not
necessarily display any error messages) if the locale name does
not meet their expectations. In those cases, investigating how
other Linux distributions support your locale might provide
some useful information.
</p>
<p>
Once the proper locale settings have been determined, create
the <tt class="filename">/etc/profile</tt> file:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/profile &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/profile
export LANG=<em class="replaceable"><tt>[ll]</tt></em>_<em class=
"replaceable"><tt>[CC]</tt></em>.<em class=
"replaceable"><tt>[charmap]</tt></em>
export INPUTRC=/etc/inputrc
# End /etc/profile</tt>
EOF</kbd></pre>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
The &ldquo;<span class="quote">C</span>&rdquo; (default)
and &ldquo;<span class="quote">en_US</span>&rdquo; (the
recommended one for United States English users) locales
are different.
</p>
</div>
</div>
<p>
Setting the keyboard layout, screen font, and locale-related
environment variables are the only internationalization steps
needed to support locales that use ordinary single-byte
encodings and left-to-right writing direction. More complex
cases (including UTF-8 based locales) require additional steps
and additional patches because many applications tend to not
work properly under such conditions. These steps and patches
are not included in the LFS book and such locales are not yet
supported by LFS.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-hostname" name=
"ch-scripts-hostname"></a>7.10.&nbsp;Configuring the
localnet Script
</h2>
</div>
</div>
</div>
<p>
Part of the job of the <span><strong class=
"command">localnet</strong></span> script is setting the
system's hostname. This needs to be configured in the
<tt class="filename">/etc/sysconfig/network</tt> file.
</p>
<p>
Create the <tt class="filename">/etc/sysconfig/network</tt>
file and enter a hostname by running:
</p>
<pre class="userinput"><kbd class=
"command">echo "HOSTNAME=<em class=
"replaceable"><tt>[lfs]</tt></em>" &gt; /etc/sysconfig/network</kbd></pre>
<p>
<em class="replaceable"><tt>[lfs]</tt></em> needs to be
replaced with the name given to the computer. Do not enter the
Fully Qualified Domain Name (FQDN) here. That information will
be put in the <tt class="filename">/etc/hosts</tt> file in the
next section.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-hosts" name=
"ch-scripts-hosts"></a>7.11.&nbsp;Creating the /etc/hosts
File
</h2>
</div>
</div>
</div>
<p>
If a network card is to be configured, decide on the IP
address, FQDN, and possible aliases for use in the <tt class=
"filename">/etc/hosts</tt> file. The syntax is:
</p>
<pre class="screen">
&lt;IP address&gt; myhost.example.org aliases</pre>
<p>
Unless the computer is to be visible to the Internet (i.e.,
there is a registered domain and a valid block of assigned IP
addresses&mdash;most users do not have this), make sure that
the IP address is in the private network IP address range.
Valid ranges are:
</p>
<pre class="screen"> Class Networks
A 10.0.0.0
B 172.16.0.0 through 172.31.0.255
C 192.168.0.0 through 192.168.255.255</pre>
<p>
A valid IP address could be 192.168.1.1. A valid FQDN for this
IP could be www.linuxfromscratch.org (not recommended because
this is a valid registered domain address and could cause
domain name server issues).
</p>
<p>
Even if not using a network card, an FQDN is still required.
This is necessary for certain programs to operate correctly.
</p>
<p>
Create the <tt class="filename">/etc/hosts</tt> file by
running:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/hosts &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/hosts (network card version)
127.0.0.1 localhost
<em class="replaceable"><tt>[192.168.1.1]</tt></em> <em class=
"replaceable"><tt>[&lt;HOSTNAME&gt;.example.org]</tt></em> <em class=
"replaceable"><tt>[HOSTNAME]</tt></em>
# End /etc/hosts (network card version)</tt>
EOF</kbd></pre>
<p>
The <em class="replaceable"><tt>[192.168.1.1]</tt></em> and
<em class=
"replaceable"><tt>[&lt;HOSTNAME&gt;.example.org]</tt></em>
values need to be changed for specific users or requirements
(if assigned an IP address by a network/system administrator
and the machine will be connected to an existing network).
</p>
<p>
If a network card is not going to be configured, create the
<tt class="filename">/etc/hosts</tt> file by running:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/hosts &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/hosts (no network card version)
127.0.0.1 <em class=
"replaceable"><tt>[&lt;HOSTNAME&gt;.example.org]</tt></em> <em class=
"replaceable"><tt>[HOSTNAME]</tt></em> localhost
# End /etc/hosts (no network card version)</tt>
EOF</kbd></pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-scripts-network" name=
"ch-scripts-network"></a>7.12.&nbsp;Configuring the
network Script
</h2>
</div>
</div>
</div>
<p>
This section only applies if a network card is to be
configured.
</p>
<p>
If a network card will not be used, there is likely no need to
create any configuration files relating to network cards. If
that is the case, remove the <tt class="filename">network</tt>
symlinks from all run-level directories (<tt class=
"filename">/etc/rc.d/rc*.d</tt>).
</p>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
7.12.1. Creating Network Interface Configuration Files
</h3>
</div>
<p>
Which interfaces are brought up and down by the network
script depends on the files and directories in the <tt class=
"filename">/etc/sysconfig/network-devices</tt> hierarchy.
This directory should contain a sub-directory for each
interface to be configured, such as <tt class=
"filename">ifconfig.xyz</tt>, where &ldquo;<span class=
"quote">xyz</span>&rdquo; is a network interface name. Inside
this directory would be files defining the attributes to this
interface, such as its IP address(es), subnet masks, and so
forth.
</p>
<p>
The following command creates a sample <tt class=
"filename">ipv4</tt> file for the <span class=
"emphasis"><em>eth0</em></span> device:
</p>
<pre class="userinput"><kbd class=
"command">cd /etc/sysconfig/network-devices &amp;&amp;
mkdir -v ifconfig.eth0 &amp;&amp;
cat &gt; ifconfig.eth0/ipv4 &lt;&lt; "EOF"
<tt class="literal">ONBOOT=yes
SERVICE=ipv4-static
IP=192.168.1.1
GATEWAY=192.168.1.2
PREFIX=24
BROADCAST=192.168.1.255</tt>
EOF</kbd></pre>
<p>
The values of these variables must be changed in every file
to match the proper setup. If the <tt class=
"envar">ONBOOT</tt> variable is set to &ldquo;<span class=
"quote">yes</span>&rdquo; the network script will bring up
the Network Interface Card (NIC) during booting of the
system. If set to anything but &ldquo;<span class=
"quote">yes</span>&rdquo; the NIC will be ignored by the
network script and not be brought up.
</p>
<p>
The <tt class="envar">SERVICE</tt> variable defines the
method used for obtaining the IP address. The LFS-Bootscripts
package has a modular IP assignment format, and creating
additional files in the <tt class=
"filename">/etc/sysconfig/network-devices/services</tt>
directory allows other IP assignment methods. This is
commonly used for Dynamic Host Configuration Protocol (DHCP),
which is addressed in the BLFS book.
</p>
<p>
The <tt class="envar">GATEWAY</tt> variable should contain
the default gateway IP address, if one is present. If not,
then comment out the variable entirely.
</p>
<p>
The <tt class="envar">PREFIX</tt> variable needs to contain
the number of bits used in the subnet. Each octet in an IP
address is 8 bits. If the subnet's netmask is 255.255.255.0,
then it is using the first three octets (24 bits) to specify
the network number. If the netmask is 255.255.255.240, it
would be using the first 28 bits. Prefixes longer than 24
bits are commonly used by DSL and cable-based Internet
Service Providers (ISPs). In this example (PREFIX=24), the
netmask is 255.255.255.0. Adjust the <tt class=
"envar">PREFIX</tt> variable according to your specific
subnet.
</p>
</div>
<div class="sect2" lang="en" xml:lang="en">
<div class="titlepage">
<a id="resolv.conf" name="resolv.conf"></a>
<h3 class="sect2">
7.12.2. Creating the /etc/resolv.conf File
</h3>
</div>
<p>
If the system is going to be connected to the Internet, it
will need some means of Domain Name Service (DNS) name
resolution to resolve Internet domain names to IP addresses,
and vice versa. This is best achieved by placing the IP
address of the DNS server, available from the ISP or network
administrator, into <tt class=
"filename">/etc/resolv.conf</tt>. Create the file by running
the following:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/resolv.conf
domain {<em class="replaceable"><tt>[Your Domain Name]</tt></em>}
nameserver <em class=
"replaceable"><tt>[IP address of your primary nameserver]</tt></em>
nameserver <em class=
"replaceable"><tt>[IP address of your secondary nameserver]</tt></em>
# End /etc/resolv.conf</tt>
EOF</kbd></pre>
<p>
Replace <em class="replaceable"><tt>[IP address of the
nameserver]</tt></em> with the IP address of the DNS most
appropriate for the setup. There will often be more than one
entry (requirements demand secondary servers for fallback
capability). If you only need or want one DNS server, remove
the second <span class="emphasis"><em>nameserver</em></span>
line from the file. The IP address may also be a router on
the local network.
</p>
</div>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-bootable" name=
"chapter-bootable"></a>Chapter&nbsp;8.&nbsp;Making the LFS
System Bootable
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-bootable-introduction" name=
"ch-bootable-introduction"></a>8.1.&nbsp;Introduction
</h2>
</div>
</div>
</div>
<p>
It is time to make the LFS system bootable. This chapter
discusses creating an <tt class="filename">fstab</tt> file,
building a kernel for the new LFS system, and installing the
GRUB boot loader so that the LFS system can be selected for
booting at startup.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-bootable-fstab" name=
"ch-bootable-fstab"></a>8.2.&nbsp;Creating the /etc/fstab
File
</h2>
</div>
</div>
</div>
<p>
The <tt class="filename">/etc/fstab</tt> file is used by some
programs to determine where file systems are to be mounted by
default, in which order, and which must be checked (for
integrity errors) prior to mounting. Create a new file systems
table like this:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /etc/fstab &lt;&lt; "EOF"
<tt class="literal"># Begin /etc/fstab
# file system mount-point type options dump fsck
# order
/dev/<em class="replaceable"><tt>[xxx]</tt></em> / <em class=
"replaceable"><tt>[fff]</tt></em> defaults 1 1
/dev/<em class=
"replaceable"><tt>[yyy]</tt></em> swap swap pri=1 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
devpts /dev/pts devpts gid=4,mode=620 0 0
shm /dev/shm tmpfs defaults 0 0
# End /etc/fstab</tt>
EOF</kbd></pre>
<p>
Replace <em class="replaceable"><tt>[xxx]</tt></em>, <em class=
"replaceable"><tt>[yyy]</tt></em>, and <em class=
"replaceable"><tt>[fff]</tt></em> with the values appropriate
for the system, for example, <tt class="filename">hda2</tt>,
<tt class="filename">hda5</tt>, and <tt class=
"systemitem">ext2</tt>. For details on the six fields in this
file, see <span><strong class="command">man 5
fstab</strong></span>.
</p>
<p>
When using a journalling file system, the <em class=
"parameter"><tt>1 1</tt></em> at the end of the line should be
replaced with <em class="parameter"><tt>0 0</tt></em> because
such a partition does not need to be dumped or checked.
</p>
<p>
The <tt class="filename">/dev/shm</tt> mount point for
<tt class="systemitem">tmpfs</tt> is included to allow enabling
POSIX-shared memory. The kernel must have the required support
built into it for this to work (more about this is in the next
section). Please note that very little software currently uses
POSIX-shared memory. Therefore, consider the <tt class=
"filename">/dev/shm</tt> mount point optional. For more
information, see <tt class=
"filename">Documentation/filesystems/tmpfs.txt</tt> in the
kernel source tree.
</p>
<p>
There are other lines which may be added to the <tt class=
"filename">/etc/fstab</tt> file. One example is a line for USB
devices:
</p>
<pre class="screen">
usbfs /proc/bus/usb usbfs devgid=14,devmode=0660 0 0 </pre>
<p>
This option will only work if &ldquo;<span class=
"quote">Support for Host-side USB</span>&rdquo; and
&ldquo;<span class="quote">USB device filesystem</span>&rdquo;
are configured in the kernel. If &ldquo;<span class=
"quote">Support for Host-side USB</span>&rdquo; is compiled as
a module, then <tt class="filename">usbcore</tt> must be listed
in <tt class="filename">/etc/sysconfig/modules</tt>.
</p>
</div>
<div class="wrap" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-bootable-kernel" name=
"ch-bootable-kernel"></a>8.3.&nbsp;Linux-2.6.11.12
</h2>
</div>
</div>
</div>
<div class="package" lang="en" xml:lang="en">
<p>
The Linux package contains the Linux kernel.
</p>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Approximate build
time:</span></strong> <span class="seg">4.20 SBU</span>
</div>
<div class="seg">
<strong><span class="segtitle">Required disk
space:</span></strong> <span class="seg">181 MB</span>
</div>
</div>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installation depends
on:</span></strong> <span class="seg">Bash, Binutils,
Coreutils, Findutils, GCC, Glibc, Grep, Gzip, Make,
Modutils, Perl, and Sed</span>
</div>
</div>
</div>
</div>
<div class="installation" lang="en" xml:lang="en">
<div class="titlepage">
<h3 class="sect2">
8.3.1. Installation of the kernel
</h3>
</div>
<p>
Building the kernel involves a few steps&mdash;configuration,
compilation, and installation. Read the <tt class=
"filename">README</tt> file in the kernel source tree for
alternative methods to the way this book configures the
kernel.
</p>
<p>
Prepare for compilation by running the following command:
</p>
<pre class="userinput"><kbd class=
"command">make mrproper</kbd></pre>
<p>
This ensures that the kernel tree is absolutely clean. The
kernel team recommends that this command be issued prior to
each kernel compilation. Do not rely on the source tree being
clean after un-tarring.
</p>
<p>
If, in <a href="#ch-scripts-console" title=
"7.6.&nbsp;Configuring the Linux Console">Section 7.6,
&ldquo;Configuring the Linux Console,&rdquo;</a> it was
decided to compile the keymap into the kernel, issue the
command below:
</p>
<pre class="userinput"><kbd class=
"command">loadkeys -m /usr/share/kbd/keymaps/<em class=
"replaceable"><tt>[path to keymap]</tt></em> &gt; \
drivers/char/defkeymap.c</kbd></pre>
<p>
For example, if using a Dutch keyboard, use <tt class=
"filename">/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</tt>.
</p>
<p>
Configure the kernel via a menu-driven interface. BLFS has
some information regarding particular kernel configuration
requirements of packages outside of LFS at <a href=
"http://www.linuxfromscratch.org/blfs/view/svn/longindex.html#kernel-config-index">
<i>http://www.linuxfromscratch.org/blfs/view/svn/longindex.html#kernel-config-index</i></a>:
</p>
<pre class="userinput"><kbd class=
"command">make menuconfig</kbd></pre>
<p>
Alternatively, <span><strong class="command">make
oldconfig</strong></span> may be more appropriate in some
situations. See the <tt class="filename">README</tt> file for
more information.
</p>
<p>
If desired, skip kernel configuration by copying the kernel
config file, <tt class="filename">.config</tt>, from the host
system (assuming it is available) to the unpacked <tt class=
"filename">linux-2.6.11.12</tt> directory. However, we do not
recommend this option. It is often better to explore all the
configuration menus and create the kernel configuration from
scratch.
</p>
<div class="note">
<div class="admonhead">
<h3 class="admontitle">
Note
</h3>
</div>
<div class="admonbody">
<p>
NPTL requires the kernel to be compiled with GCC-3.x or
later, in this case 3.4.3. It is not recommended to
compile the kernel with GCC-2.95.x, as this causes
failures in the Glibc test suite. Normally, this wouldn't
be mentioned as LFS doesn't build GCC-2.95.x.
Unfortunately, the kernel documentation is outdated and
still claims GCC-2.95.3 is the recommended compiler.
</p>
</div>
</div>
<p>
Compile the kernel image and modules:
</p>
<pre class="userinput"><kbd class="command">make</kbd></pre>
<p>
If using kernel modules, an <tt class=
"filename">/etc/modprobe.conf</tt> file may be needed.
Information pertaining to modules and kernel configuration is
located in the kernel documentation in the <tt class=
"filename">linux-2.6.11.12/Documentation</tt> directory.
Also, <tt class="filename">modprobe.conf(5)</tt> may be of
interest.
</p>
<p>
Be very careful when reading other documentation relating to
kernel modules because it usually applies to 2.4.x kernels
only. As far as we know, kernel configuration issues specific
to Hotplug and Udev are not documented. The problem is that
Udev will create a device node only if Hotplug or a
user-written script inserts the corresponding module into the
kernel, and not all modules are detectable by Hotplug. Note
that statements like the one below in the <tt class=
"filename">/etc/modprobe.conf</tt> file do not work with
Udev:
</p>
<pre class="screen">alias char-major-XXX some-module</pre>
<p>
Because of the complications with Hotplug, Udev, and modules,
we strongly recommend starting with a completely non-modular
kernel configuration, especially if this is the first time
using Udev.
</p>
<p>
Install the modules, if the kernel configuration uses them:
</p>
<pre class="userinput"><kbd class=
"command">make modules_install</kbd></pre>
<p>
After kernel compilation is complete, additional steps are
required to complete the installation. Some files need to be
copied to the <tt class="filename">/boot</tt> directory.
</p>
<p>
The path to the kernel image may vary depending on the
platform being used. The following command assumes an x86
architecture:
</p>
<pre class="userinput"><kbd class=
"command">cp -v arch/i386/boot/bzImage /boot/lfskernel-2.6.11.12</kbd></pre>
<p>
<tt class="filename">System.map</tt> is a symbol file for the
kernel. It maps the function entry points of every function
in the kernel API, as well as the addresses of the kernel
data structures for the running kernel. Issue the following
command to install the map file:
</p>
<pre class="userinput"><kbd class=
"command">cp -v System.map /boot/System.map-2.6.11.12</kbd></pre>
<p>
The kernel configuration file <tt class=
"filename">.config</tt> produced by the <span><strong class=
"command">make menuconfig</strong></span> step above contains
all the configuration selections for the kernel that was just
compiled. It is a good idea to keep this file for future
reference:
</p>
<pre class="userinput"><kbd class=
"command">cp -v .config /boot/config-2.6.11.12</kbd></pre>
<p>
It is important to note that the files in the kernel source
directory are not owned by <span class=
"emphasis"><em>root</em></span>. Whenever a package is
unpacked as user <span class="emphasis"><em>root</em></span>
(like we did inside chroot), the files have the user and
group IDs of whatever they were on the packager's computer.
This is usually not a problem for any other package to be
installed because the source tree is removed after the
installation. However, the Linux source tree is often
retained for a long time. Because of this, there is a chance
that whatever user ID the packager used will be assigned to
somebody on the machine. That person would then have write
access to the kernel source.
</p>
<p>
If the kernel source tree is going to be retained, run
<span><strong class="command">chown -R 0:0</strong></span> on
the <tt class="filename">linux-2.6.11.12</tt> directory to
ensure all files are owned by user <span class=
"emphasis"><em>root</em></span>.
</p>
<div class="warning">
<div class="admonhead">
<h3 class="admontitle">
Warning
</h3>
</div>
<div class="admonbody">
<p>
Some kernel documentation recommends creating a symlink
from <tt class="filename">/usr/src/linux</tt> pointing to
the kernel source directory. This is specific to kernels
prior to the 2.6 series and <span class=
"emphasis"><em>must not</em></span> be created on an LFS
system as it can cause problems for packages you may wish
to build once your base LFS system is complete.
</p>
<p>
Also, the headers in the system's <tt class=
"filename">include</tt> directory should <span class=
"emphasis"><em>always</em></span> be the ones against
which Glibc was compiled, that is, the ones from the
Linux-Libc-Headers package, and therefore, should
<span class="emphasis"><em>never</em></span> be replaced
by the kernel headers.
</p>
</div>
</div>
</div>
<div class="content" lang="en" xml:lang="en">
<div class="titlepage">
<a id="contents-kernel" name="contents-kernel"></a>
<h3 class="sect2">
8.3.2. Contents of Linux
</h3>
</div>
<div class="segmentedlist">
<div class="seglistitem">
<div class="seg">
<strong><span class="segtitle">Installed
files:</span></strong> <span class=
"seg">config-2.6.11.12, lfskernel-2.6.11.12, and
System.map-2.6.11.12</span>
</div>
</div>
</div>
<div class="variablelist">
<h3>
<a id="id3519511" name="id3519511"></a>Short Descriptions
</h3>
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<a id="config" name="config"></a><span class=
"term"><tt class=
"filename">config-2.6.11.12</tt></span>
</td>
<td>
<p>
Contains all the configuration selections for the
kernel
</p>
</td>
</tr>
<tr>
<td>
<a id="lfskernel" name="lfskernel"></a><span class=
"term"><tt class=
"filename">lfskernel-2.6.11.12</tt></span>
</td>
<td>
<p>
The engine of the Linux system. When turning on the
computer, the kernel is the first part of the
operating system that gets loaded. It detects and
initializes all components of the computer's
hardware, then makes these components available as
a tree of files to the software and turns a single
CPU into a multitasking machine capable of running
scores of programs seemingly at the same time
</p>
</td>
</tr>
<tr>
<td>
<a id="System.map" name="System.map"></a><span class=
"term"><tt class=
"filename">System.map-2.6.11.12</tt></span>
</td>
<td>
<p>
A list of addresses and symbols; it maps the entry
points and addresses of all the functions and data
structures in the kernel
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-bootable-grub" name=
"ch-bootable-grub"></a>8.4.&nbsp;Making the LFS System
Bootable
</h2>
</div>
</div>
</div>
<p>
Your shiny new LFS system is almost complete. One of the last
things to do is to ensure that the system can be properly
booted. The instructions below apply only to computers of IA-32
architecture, meaning mainstream PCs. Information on
&ldquo;<span class="quote">boot loading</span>&rdquo; for other
architectures should be available in the usual
resource-specific locations for those architectures.
</p>
<p>
Boot loading can be a complex area, so a few cautionary words
are in order. Be familiar with the current boot loader and any
other operating systems present on the hard drive(s) that need
to be bootable. Make sure that an emergency boot disk is ready
to &ldquo;<span class="quote">rescue</span>&rdquo; the computer
if the computer becomes unusable (un-bootable).
</p>
<p>
Earlier, we compiled and installed the GRUB boot loader
software in preparation for this step. The procedure involves
writing some special GRUB files to specific locations on the
hard drive. We highly recommend creating a GRUB boot floppy
diskette as a backup. Insert a blank floppy diskette and run
the following commands:
</p>
<pre class="userinput"><kbd class=
"command">dd if=/boot/grub/stage1 of=/dev/fd0 bs=512 count=1
dd if=/boot/grub/stage2 of=/dev/fd0 bs=512 seek=1</kbd></pre>
<p>
Remove the diskette and store it somewhere safe. Now, run the
<span><strong class="command">grub</strong></span> shell:
</p>
<pre class="userinput"><kbd class="command">grub</kbd></pre>
<p>
GRUB uses its own naming structure for drives and partitions in
the form of <span class="emphasis"><em>(hdn,m)</em></span>,
where <span class="emphasis"><em>n</em></span> is the hard
drive number and <span class="emphasis"><em>m</em></span> is
the partition number, both starting from zero. For example,
partition <tt class="filename">hda1</tt> is <span class=
"emphasis"><em>(hd0,0)</em></span> to GRUB and <tt class=
"filename">hdb3</tt> is <span class=
"emphasis"><em>(hd1,2)</em></span>. In contrast to Linux, GRUB
does not consider CD-ROM drives to be hard drives. For example,
if using a CD on <tt class="filename">hdb</tt> and a second
hard drive on <tt class="filename">hdc</tt>, that second hard
drive would still be <span class=
"emphasis"><em>(hd1)</em></span>.
</p>
<p>
Using the above information, determine the appropriate
designator for the root partition (or boot partition, if a
separate one is used). For the following example, it is assumed
that the root (or separate boot) partition is <tt class=
"filename">hda4</tt>.
</p>
<p>
Tell GRUB where to search for its <tt class=
"filename">stage{1,2}</tt> files. The Tab key can be used
everywhere to make GRUB show the alternatives:
</p>
<pre class="userinput"><kbd class=
"command">root (hd0,3)</kbd></pre>
<div class="warning">
<div class="admonhead">
<h3 class="admontitle">
Warning
</h3>
</div>
<div class="admonbody">
<p>
The following command will overwrite the current boot
loader. Do not run the command if this is not desired, for
example, if using a third party boot manager to manage the
Master Boot Record (MBR). In this scenario, it would make
more sense to install GRUB into the &ldquo;<span class=
"quote">boot sector</span>&rdquo; of the LFS partition. In
this case, this next command would become <strong class=
"userinput"><tt>setup (hd0,3)</tt></strong>.
</p>
</div>
</div>
<p>
Tell GRUB to install itself into the MBR of <tt class=
"filename">hda</tt>:
</p>
<pre class="userinput"><kbd class=
"command">setup (hd0)</kbd></pre>
<p>
If all went well, GRUB will have reported finding its files in
<tt class="filename">/boot/grub</tt>. That's all there is to
it. Quit the <span><strong class="command">grub</strong></span>
shell:
</p>
<pre class="userinput"><kbd class="command">quit</kbd></pre>
<p>
Create a &ldquo;<span class="quote">menu list</span>&rdquo;
file defining GRUB's boot menu:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt; /boot/grub/menu.lst &lt;&lt; "EOF"
<tt class="literal"># Begin /boot/grub/menu.lst
# By default boot the first menu entry.
default 0
# Allow 30 seconds before booting the default.
timeout 30
# Use prettier colors.
color green/black light-green/black
# The first entry is for LFS.
title LFS 6.1.1
root (hd0,3)
kernel /boot/lfskernel-2.6.11.12 root=/dev/hda4</tt>
EOF</kbd></pre>
<p>
Add an entry for the host distribution if desired. It might
look like this:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt;&gt; /boot/grub/menu.lst &lt;&lt; "EOF"
<tt class="literal">title Red Hat
root (hd0,2)
kernel /boot/kernel-2.6.5 root=/dev/hda3
initrd /boot/initrd-2.6.5</tt>
EOF</kbd></pre>
<p>
If dual-booting Windows, the following entry will allow booting
it:
</p>
<pre class="userinput"><kbd class=
"command">cat &gt;&gt; /boot/grub/menu.lst &lt;&lt; "EOF"
<tt class="literal">title Windows
rootnoverify (hd0,0)
chainloader +1</tt>
EOF</kbd></pre>
<p>
If <span><strong class="command">info grub</strong></span> does
not provide all necessary material, additional information
regarding GRUB is located on its website at: <a href=
"http://www.gnu.org/software/grub/"><i>http://www.gnu.org/software/grub/</i></a>.
</p>
<p>
The FHS stipulates that GRUB's <tt class=
"filename">menu.lst</tt> file should be symlinked to <tt class=
"filename">/etc/grub/menu.lst</tt>. To satisfy this
requirement, issue the following command:
</p>
<pre class="userinput"><kbd class=
"command">mkdir -v /etc/grub &amp;&amp;
ln -sv /boot/grub/menu.lst /etc/grub</kbd></pre>
</div>
</div>
<div class="chapter" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="chapter-finalizing" name=
"chapter-finalizing"></a>Chapter&nbsp;9.&nbsp;The End
</h2>
</div>
</div>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-finish-theend" name=
"ch-finish-theend"></a>9.1.&nbsp;The End
</h2>
</div>
</div>
</div>
<p>
Well done! The new LFS system is installed! We wish you much
success with your shiny new custom-built Linux system.
</p>
<p>
It may be a good idea to create an <tt class=
"filename">/etc/lfs-release</tt> file. By having this file, it
is very easy for you (and for us if you need to ask for help at
some point) to find out which LFS version is installed on the
system. Create this file by running:
</p>
<pre class="userinput"><kbd class=
"command">echo 6.1.1 &gt; /etc/lfs-release</kbd></pre>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-finish-getcounted" name=
"ch-finish-getcounted"></a>9.2.&nbsp;Get Counted
</h2>
</div>
</div>
</div>
<p>
Now that you have finished the book, do you want to be counted
as an LFS user? Head over to <a href=
"http://www.linuxfromscratch.org/cgi-bin/lfscounter.cgi"><i>http://www.linuxfromscratch.org/cgi-bin/lfscounter.cgi</i></a>
and register as an LFS user by entering your name and the first
LFS version you have used.
</p>
<p>
Let's reboot into LFS now.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-finish-reboot" name=
"ch-finish-reboot"></a>9.3.&nbsp;Rebooting the System
</h2>
</div>
</div>
</div>
<p>
Now that all of the software has been installed, it is time to
reboot your computer. However, you should be aware of a few
things. The system you have created in this book is quite
minimal, and most likely will not have the functionality you
would need to be able to continue forward. By installing a few
extra packages from the BLFS book while still in our current
chroot environment, you can leave yourself in a much better
position to continue on once you reboot into your new LFS
installation. Installing a text mode web browser, such as Lynx,
you can easily view the BLFS book in one virtual terminal,
while building packages in another. The GPM package will also
allow you to perform copy/paste actions in your virtual
terminals. Lastly, if you are in a situation where static IP
configuration does not meet your networking requirements,
installing packages such as Dhcpcd or PPP at this point might
also be useful.
</p>
<p>
Now that we have said that, lets move on to booting our shiny
new LFS installation for the first time! First exit from the
chroot environment:
</p>
<pre class="userinput"><kbd class="command">logout</kbd></pre>
<p>
Then unmount the virtual files systems:
</p>
<pre class="userinput"><kbd class=
"command">umount -v $LFS/dev/pts
umount -v $LFS/dev/shm
umount -v $LFS/dev
umount -v $LFS/proc
umount -v $LFS/sys</kbd></pre>
<p>
Unmount the LFS file system itself:
</p>
<pre class="userinput"><kbd class=
"command">umount -v $LFS</kbd></pre>
<p>
If multiple partitions were created, unmount the other
partitions before unmounting the main one, like this:
</p>
<pre class="userinput"><kbd class="command">umount -v $LFS/usr
umount -v $LFS/home
umount -v $LFS</kbd></pre>
<p>
Now, reboot the system with:
</p>
<pre class="userinput"><kbd class=
"command">shutdown -r now</kbd></pre>
<p>
Assuming the GRUB boot loader was set up as outlined earlier,
the menu is set to boot <span class="emphasis"><em>LFS
6.1.1</em></span> automatically.
</p>
<p>
When the reboot is complete, the LFS system is ready for use
and more software may be added to suit your needs.
</p>
</div>
<div class="sect1" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="ch-finish-whatnow" name=
"ch-finish-whatnow"></a>9.4.&nbsp;What Now?
</h2>
</div>
</div>
</div>
<p>
Thank you for reading this LFS book. We hope that you have
found this book helpful and have learned more about the system
creation process.
</p>
<p>
Now that the LFS system is installed, you may be wondering
&ldquo;<span class="quote">What next?</span>&rdquo; To answer
that question, we have compiled a list of resources for you.
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
Maintenance
</p>
<p>
Bugs and security notices are reported regularly for all
software. Since an LFS system is compiled from source, it
is up to you to keep abreast of such reports. There are
several online resources that track such reports, some of
which are shown below:
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
Freshmeat.net (<a href=
"http://freshmeat.net/"><i>http://freshmeat.net/</i></a>)
</p>
<p>
Freshmeat can notify you (via email) of new
versions of packages installed on your system.
</p>
</li>
<li>
<p>
<a href="http://www.cert.org/"><i>CERT</i></a>
(Computer Emergency Response Team)
</p>
<p>
CERT has a mailing list that publishes security
alerts concerning various operating systems and
applications. Subscription information is available
at <a href=
"http://www.us-cert.gov/cas/signup.html"><i>http://www.us-cert.gov/cas/signup.html</i></a>.
</p>
</li>
<li>
<p>
Bugtraq
</p>
<p>
Bugtraq is a full-disclosure computer security
mailing list. It publishes newly discovered
security issues, and occasionally potential fixes
for them. Subscription information is available at
<a href=
"http://www.securityfocus.com/archive"><i>http://www.securityfocus.com/archive</i></a>.
</p>
</li>
</ul>
</div>
</li>
<li>
<p>
Beyond Linux From Scratch
</p>
<p>
The Beyond Linux From Scratch book covers installation
procedures for a wide range of software beyond the scope
of the LFS Book. The BLFS project is located at <a href=
"http://www.linuxfromscratch.org/blfs/"><i>http://www.linuxfromscratch.org/blfs/</i></a>.
</p>
</li>
<li>
<p>
LFS Hints
</p>
<p>
The LFS Hints are a collection of educational documents
submitted by volunteers in the LFS community. The hints
are available at <a href=
"http://www.linuxfromscratch.org/hints/list.html"><i>http://www.linuxfromscratch.org/hints/list.html</i></a>.
</p>
</li>
<li>
<p>
Mailing lists
</p>
<p>
There are several LFS mailing lists you may subscribe to
if you are in need of help, want to stay current with the
latest developments, want to contribute to the project,
and more. See <a href="#ch-scatter-maillists">Chapter 1 -
Mailing Lists</a> for more information.
</p>
</li>
<li>
<p>
The Linux Documentation Project
</p>
<p>
The goal of The Linux Documentation Project (TLDP) is to
collaborate on all of the issues of Linux documentation.
The TLDP features a large collection of HOWTOs, guides,
and man pages. It is located at <a href=
"http://www.tldp.org/"><i>http://www.tldp.org/</i></a>.
</p>
</li>
</ul>
</div>
</div>
</div>
</div>
<div class="part" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h1 class="title">
<a id="part4" name="part4"></a>Part&nbsp;IV.&nbsp;Appendices
</h1>
</div>
</div>
</div>
<div class="toc">
<h3>
Table of Contents
</h3>
<ul>
<li class="appendix">
<a href="#appendixa">A. Acronyms and Terms</a>
</li>
<li class="appendix">
<a href="#appendixb">B. Acknowledgments</a>
</li>
</ul>
</div>
<div class="appendix" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="appendixa" name=
"appendixa"></a>Appendix&nbsp;A.&nbsp;Acronyms and Terms
</h2>
</div>
</div>
</div>
<div class="variablelist">
<table border="0">
<col align="left" valign="top" />
<tbody>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ABI</strong></span></span>
</td>
<td>
<p>
Application Binary Interface
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ALFS</strong></span></span>
</td>
<td>
<p>
Automated Linux From Scratch
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ALSA</strong></span></span>
</td>
<td>
<p>
Advanced Linux Sound Architecture
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>API</strong></span></span>
</td>
<td>
<p>
Application Programming Interface
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ASCII</strong></span></span>
</td>
<td>
<p>
American Standard Code for Information Interchange
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>BIOS</strong></span></span>
</td>
<td>
<p>
Basic Input/Output System
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>BLFS</strong></span></span>
</td>
<td>
<p>
Beyond Linux From Scratch
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>BSD</strong></span></span>
</td>
<td>
<p>
Berkeley Software Distribution
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>chroot</strong></span></span>
</td>
<td>
<p>
change root
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>CMOS</strong></span></span>
</td>
<td>
<p>
Complementary Metal Oxide Semiconductor
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>COS</strong></span></span>
</td>
<td>
<p>
Class Of Service
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>CPU</strong></span></span>
</td>
<td>
<p>
Central Processing Unit
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>CRC</strong></span></span>
</td>
<td>
<p>
Cyclic Redundancy Check
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>CVS</strong></span></span>
</td>
<td>
<p>
Concurrent Versions System
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>DHCP</strong></span></span>
</td>
<td>
<p>
Dynamic Host Configuration Protocol
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>DNS</strong></span></span>
</td>
<td>
<p>
Domain Name Service
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>EGA</strong></span></span>
</td>
<td>
<p>
Enhanced Graphics Adapter
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ELF</strong></span></span>
</td>
<td>
<p>
Executable and Linkable Format
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>EOF</strong></span></span>
</td>
<td>
<p>
End of File
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>EQN</strong></span></span>
</td>
<td>
<p>
equation
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>EVMS</strong></span></span>
</td>
<td>
<p>
Enterprise Volume Management System
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ext2</strong></span></span>
</td>
<td>
<p>
second extended file system
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>FAQ</strong></span></span>
</td>
<td>
<p>
Frequently Asked Questions
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>FHS</strong></span></span>
</td>
<td>
<p>
Filesystem Hierarchy Standard
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>FIFO</strong></span></span>
</td>
<td>
<p>
First-In, First Out
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>FQDN</strong></span></span>
</td>
<td>
<p>
Fully Qualified Domain Name
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>FTP</strong></span></span>
</td>
<td>
<p>
File Transfer Protocol
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>GB</strong></span></span>
</td>
<td>
<p>
Gibabytes
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>GCC</strong></span></span>
</td>
<td>
<p>
GNU Compiler Collection
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>GID</strong></span></span>
</td>
<td>
<p>
Group Identifier
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>GMT</strong></span></span>
</td>
<td>
<p>
Greenwich Mean Time
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>GPG</strong></span></span>
</td>
<td>
<p>
GNU Privacy Guard
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>HTML</strong></span></span>
</td>
<td>
<p>
Hypertext Markup Language
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>IDE</strong></span></span>
</td>
<td>
<p>
Integrated Drive Electronics
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>IEEE</strong></span></span>
</td>
<td>
<p>
Institute of Electrical and Electronic Engineers
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>IO</strong></span></span>
</td>
<td>
<p>
Input/Output
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>IP</strong></span></span>
</td>
<td>
<p>
Internet Protocol
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>IPC</strong></span></span>
</td>
<td>
<p>
Inter-Process Communication
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>IRC</strong></span></span>
</td>
<td>
<p>
Internet Relay Chat
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ISO</strong></span></span>
</td>
<td>
<p>
International Organization for Standardization
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>ISP</strong></span></span>
</td>
<td>
<p>
Internet Service Provider
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>KB</strong></span></span>
</td>
<td>
<p>
Kilobytes
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>LED</strong></span></span>
</td>
<td>
<p>
Light Emitting Diode
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>LFS</strong></span></span>
</td>
<td>
<p>
Linux From Scratch
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>LSB</strong></span></span>
</td>
<td>
<p>
Linux Standards Base
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>MB</strong></span></span>
</td>
<td>
<p>
Megabytes
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>MBR</strong></span></span>
</td>
<td>
<p>
Master Boot Record
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>MD5</strong></span></span>
</td>
<td>
<p>
Message Digest 5
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>NIC</strong></span></span>
</td>
<td>
<p>
Network Interface Card
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>NLS</strong></span></span>
</td>
<td>
<p>
Native Language Support
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>NNTP</strong></span></span>
</td>
<td>
<p>
Network News Transport Protocol
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>NPTL</strong></span></span>
</td>
<td>
<p>
Native POSIX Threading Library
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>OSS</strong></span></span>
</td>
<td>
<p>
Open Sound System
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>PCH</strong></span></span>
</td>
<td>
<p>
Pre-Compiled Headers
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>PCRE</strong></span></span>
</td>
<td>
<p>
Perl Compatible Regular Expression
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>PID</strong></span></span>
</td>
<td>
<p>
Process Identifier
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>PLFS</strong></span></span>
</td>
<td>
<p>
Pure Linux From Scratch
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>PTY</strong></span></span>
</td>
<td>
<p>
pseudo terminal
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>QA</strong></span></span>
</td>
<td>
<p>
Quality Assurance
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>QOS</strong></span></span>
</td>
<td>
<p>
Quality Of Service
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>RAM</strong></span></span>
</td>
<td>
<p>
Random Access Memory
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>RPC</strong></span></span>
</td>
<td>
<p>
Remote Procedure Call
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>RTC</strong></span></span>
</td>
<td>
<p>
Real Time Clock
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>SBU</strong></span></span>
</td>
<td>
<p>
Standard Build Unit
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>SCO</strong></span></span>
</td>
<td>
<p>
The Santa Cruz Operation
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>SGR</strong></span></span>
</td>
<td>
<p>
Select Graphic Rendition
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>SHA1</strong></span></span>
</td>
<td>
<p>
Secure-Hash Algorithm 1
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>SMP</strong></span></span>
</td>
<td>
<p>
Symmetric Multi-Processor
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>TLDP</strong></span></span>
</td>
<td>
<p>
The Linux Documentation Project
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>TFTP</strong></span></span>
</td>
<td>
<p>
Trivial File Transfer Protocol
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>TLS</strong></span></span>
</td>
<td>
<p>
Thread-Local Storage
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>UID</strong></span></span>
</td>
<td>
<p>
User Identifier
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>umask</strong></span></span>
</td>
<td>
<p>
user file-creation mask
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>USB</strong></span></span>
</td>
<td>
<p>
Universal Serial Bus
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>UTC</strong></span></span>
</td>
<td>
<p>
Coordinated Universal Time
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>UUID</strong></span></span>
</td>
<td>
<p>
Universally Unique Identifier
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>VC</strong></span></span>
</td>
<td>
<p>
Virtual Console
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>VGA</strong></span></span>
</td>
<td>
<p>
Video Graphics Array
</p>
</td>
</tr>
<tr>
<td>
<span class="term"><span class=
"bold"><strong>VT</strong></span></span>
</td>
<td>
<p>
Virtual Terminal
</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="appendix" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h2 class="title">
<a id="appendixb" name=
"appendixb"></a>Appendix&nbsp;B.&nbsp;Acknowledgments
</h2>
</div>
</div>
</div>
<p>
We would like to thank the following people and organizations for
their contributions to the Linux From Scratch Project.
</p>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#103;&#101;&#114;&#97;&#114;&#100;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Gerard
Beekmans</i></a> &lt;gerard AT linuxfromscratch D0T org&gt;
&ndash; LFS Creator, LFS Project Leader
</p>
</li>
<li>
<p>
<a href="mailto:&#109;&#97;&#116;&#116;&#104;&#101;&#119;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Matthew
Burgess</i></a> &lt;matthew AT linuxfromscratch D0T org&gt;
&ndash; LFS Project Leader, LFS Technical Writer/Editor,
LFS Release Manager
</p>
</li>
<li>
<p>
<a href=
"mailto:&#97;&#114;&#99;&#104;&#97;&#105;&#99;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Archaic</i></a>
&lt;archaic AT linuxfromscratch D0T org&gt; &ndash; LFS Technical
Writer/Editor, HLFS Project Leader, BLFS Editor, Hints and
Patches Project Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#110;&#97;&#116;&#104;&#97;&#110;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Nathan
Coulson</i></a> &lt;nathan AT linuxfromscratch D0T org&gt; &ndash;
LFS-Bootscripts Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#98;&#100;&#117;&#98;&#98;&#115;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Bruce
Dubbs</i></a> &lt;bdubbs AT linuxfromscratch D0T org&gt; &ndash;
BLFS Project Leader
</p>
</li>
<li>
<p>
<a href="mailto:&#109;&#97;&#110;&#117;&#101;&#108;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Manuel
Canales Esparcia</i></a>
&lt;manuel AT linuxfromscratch D0T org&gt; &ndash; LFS/BLFS/HLFS
XML and XSL Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#105;&#109;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Jim
Gifford</i></a> &lt;jim AT linuxfromscratch D0T org&gt; &ndash;
LFS Technical Writer, Patches Project Leader
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#104;&#117;&#110;&#116;&#119;&#111;&#114;&#107;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Jeremy
Huntwork</i></a> &lt;jhuntwork AT linuxfromscratch D0T org&gt;
&ndash; LFS Technical Writer, LFS LiveCD Maintainer, ALFS
Project Leader
</p>
</li>
<li>
<p>
<a href="mailto:&#108;&#105;&#122;&#97;&#114;&#100;&#111;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Anderson
Lizardo</i></a> &lt;lizardo AT linuxfromscratch D0T org&gt;
&ndash; Website Backend-Scripts Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#114;&#121;&#97;&#110;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Ryan
Oliver</i></a> &lt;ryan AT linuxfromscratch D0T org&gt; &ndash;
LFS Toolchain Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#119;&#114;&#111;&#98;&#101;&#114;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>James
Robertson</i></a> &lt;jwrober AT linuxfromscratch D0T org&gt;
&ndash; Bugzilla Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#116;&#117;&#115;&#104;&#97;&#114;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Tushar
Teredesai</i></a> &lt;tushar AT linuxfromscratch D0T org&gt;
&ndash; BLFS Book Editor, Hints and Patches Project Leader
</p>
</li>
<li>
<p>
Countless other people on the various LFS and BLFS mailing
lists who helped make this book possible by giving their
suggestions, testing the book, and submitting bug reports,
instructions, and their experiences with installing various
packages.
</p>
</li>
</ul>
</div>
<h2>
<a id="id3521335" name="id3521335"></a>Translators
</h2>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#109;&#97;&#99;&#97;&#110;&#97;&#64;&#108;&#102;&#115;&#45;&#101;&#115;&#46;&#99;&#111;&#109;"><i>Manuel Canales
Esparcia</i></a> &lt;macana AT lfs-es D0T com&gt; &ndash; Spanish
LFS translation project
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#111;&#104;&#97;&#110;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Johan
Lenglet</i></a> &lt;johan AT linuxfromscratch D0T org&gt; &ndash;
French LFS translation project
</p>
</li>
<li>
<p>
<a href="mailto:&#108;&#105;&#122;&#97;&#114;&#100;&#111;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Anderson
Lizardo</i></a> &lt;lizardo AT linuxfromscratch D0T org&gt;
&ndash; Portuguese LFS translation project
</p>
</li>
<li>
<p>
<a href="mailto:&#116;&#114;&#64;&#101;&#114;&#100;&#102;&#117;&#110;&#107;&#115;&#116;&#101;&#108;&#108;&#101;&#46;&#100;&#101;"><i>Thomas
Reitelbach</i></a> &lt;tr AT erdfunkstelle D0T de&gt; &ndash;
German LFS translation project
</p>
</li>
</ul>
</div>
<h2>
<a id="id3519782" name="id3519782"></a>Mirror Maintainers
</h2>
<h3>
<a id="id3521213" name="id3521213"></a>North American Mirrors
</h3>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#115;&#99;&#111;&#116;&#116;&#64;&#111;&#115;&#117;&#111;&#115;&#108;&#46;&#111;&#114;&#103;"><i>Scott Kveton</i></a>
&lt;scott AT osuosl D0T org&gt; &ndash; lfs.oregonstate.edu mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#109;&#105;&#104;&#97;&#64;&#120;&#117;&#121;&#46;&#98;&#105;&#122;"><i>Mikhail Pastukhov</i></a>
&lt;miha AT xuy D0T biz&gt; &ndash; lfs.130th.net mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#108;&#111;&#115;&#116;&#64;&#108;&#45;&#119;&#46;&#110;&#101;&#116;"><i>William Astle</i></a>
&lt;lost AT l-w D0T net&gt; &ndash; ca.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#112;&#111;&#108;&#101;&#110;&#64;&#114;&#97;&#99;&#107;&#115;&#112;&#97;&#99;&#101;&#46;&#99;&#111;&#109;"><i>Jeremy
Polen</i></a> &lt;jpolen AT rackspace D0T com&gt; &ndash;
us2.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#116;&#105;&#109;&#64;&#105;&#100;&#103;&#101;&#46;&#110;&#101;&#116;"><i>Tim Jackson</i></a>
&lt;tim AT idge D0T net&gt; &ndash; linuxfromscratch.idge.net
mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#101;&#114;&#101;&#109;&#121;&#64;&#108;&#105;&#110;&#117;&#120;&#45;&#112;&#104;&#114;&#101;&#97;&#107;&#46;&#110;&#101;&#116;"><i>Jeremy
Utley</i></a> &lt;jeremy AT linux-phreak D0T net&gt; &ndash;
lfs.linux-phreak.net mirror
</p>
</li>
</ul>
</div>
<h3>
<a id="id3521210" name="id3521210"></a>South American Mirrors
</h3>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#115;&#121;&#115;&#111;&#112;&#64;&#109;&#101;&#115;&#105;&#46;&#99;&#111;&#109;&#46;&#97;&#114;"><i>Andres
Meggiotto</i></a> &lt;sysop AT mesi D0T com D0T ar&gt; &ndash;
lfs.mesi.com.ar mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#109;&#97;&#110;&#117;&#101;&#108;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Manuel
Canales Esparcia</i></a>
&lt;manuel AT linuxfromscratch D0T org&gt; &ndash;
lfsmirror.lfs-es.info mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#101;&#98;&#102;&#64;&#97;&#101;&#100;&#115;&#111;&#108;&#117;&#99;&#111;&#101;&#115;&#46;&#99;&#111;&#109;&#46;&#98;&#114;"><i>Eduardo B.
Fonseca</i></a> &lt;ebf AT aedsolucoes D0T com D0T br&gt; &ndash;
br.linuxfromscratch.org mirror
</p>
</li>
</ul>
</div>
<h3>
<a id="id3521363" name="id3521363"></a>European Mirrors
</h3>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#98;&#97;&#114;&#110;&#97;&#64;&#115;&#105;&#107;&#101;&#114;&#46;&#104;&#117;"><i>Barna Koczka</i></a>
&lt;barna AT siker D0T hu&gt; &ndash; hu.linuxfromscratch.org
mirror
</p>
</li>
<li>
<p>
<a href="http://www.mirror.ac.uk"><i>UK Mirror
Service</i></a> &ndash; linuxfromscratch.mirror.ac.uk
mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#77;&#97;&#114;&#116;&#105;&#110;&#46;&#86;&#111;&#115;&#115;&#64;&#97;&#100;&#97;&#46;&#100;&#101;"><i>Martin Voss</i></a>
&lt;Martin D0T Voss AT ada D0T de&gt; &ndash; lfs.linux-matrix.net
mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#103;&#117;&#105;&#100;&#111;&#64;&#112;&#114;&#105;&#109;&#101;&#114;&#101;&#108;&#97;&#121;&#46;&#110;&#101;&#116;"><i>Guido
Passet</i></a> &lt;guido AT primerelay D0T net&gt; &ndash;
nl.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#98;&#97;&#97;&#102;&#105;&#101;&#64;&#112;&#108;&#97;&#110;&#101;&#116;&#46;&#110;&#108;"><i>Bastiaan
Jacques</i></a> &lt;baafie AT planet D0T nl&gt; &ndash;
lfs.pagefault.net mirror
</p>
</li>
<li>
<p>
<a href=
"mailto:&#108;&#102;&#115;&#45;&#109;&#105;&#114;&#114;&#111;&#114;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#114;&#97;&#118;&#101;&#46;&#111;&#114;&#103;"><i>Roel
Neefs</i></a> &lt;lfs-mirror AT linuxfromscratch D0T rave D0T org&gt;
&ndash; linuxfromscratch.rave.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#117;&#115;&#116;&#105;&#110;&#64;&#106;&#114;&#107;&#110;&#105;&#101;&#114;&#105;&#109;&#46;&#100;&#101;"><i>Justin
Knierim</i></a> &lt;justin AT jrknierim D0T de&gt; &ndash;
www.lfs-matrix.de mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#115;&#116;&#101;&#118;&#105;&#101;&#64;&#115;&#116;&#101;&#118;&#105;&#101;&#50;&#48;&#46;&#100;&#101;"><i>Stephan
Brendel</i></a> &lt;stevie AT stevie20 D0T de&gt; &ndash;
lfs.netservice-neuss.de mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#65;&#110;&#116;&#111;&#110;&#105;&#110;&#46;&#83;&#112;&#114;&#105;&#110;&#122;&#108;&#64;&#116;&#117;&#119;&#105;&#101;&#110;&#46;&#97;&#99;&#46;&#97;&#116;"><i>Antonin
Sprinzl</i></a> &lt;Antonin D0T Sprinzl AT tuwien D0T ac D0T at&gt;
&ndash; at.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#102;&#114;&#101;&#100;&#97;&#110;&#45;&#108;&#102;&#115;&#64;&#102;&#114;&#101;&#100;&#97;&#110;&#46;&#111;&#114;&#103;"><i>Fredrik
Danerklint</i></a> &lt;fredan-lfs AT fredan D0T org&gt; &ndash;
se.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#97;&#114;&#99;&#104;&#105;&#118;&#101;&#64;&#100;&#111;&#99;&#46;&#99;&#115;&#46;&#117;&#110;&#105;&#118;&#45;&#112;&#97;&#114;&#105;&#115;&#56;&#46;&#102;&#114;"><i>Parisian
sysadmins</i></a> &lt;archive AT doc D0T cs D0T univ-paris8 D0T fr&gt;
&ndash; www2.fr.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#118;&#101;&#108;&#105;&#110;&#64;&#122;&#97;&#100;&#110;&#105;&#107;&#46;&#111;&#114;&#103;"><i>Alexander
Velin</i></a> &lt;velin AT zadnik D0T org&gt; &ndash;
bg.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#100;&#105;&#114;&#107;&#64;&#115;&#101;&#99;&#117;&#114;&#101;&#119;&#101;&#98;&#115;&#101;&#114;&#118;&#105;&#99;&#101;&#115;&#46;&#99;&#111;&#46;&#117;&#107;"><i>Dirk
Webster</i></a> &lt;dirk AT securewebservices D0T co D0T uk&gt;
&ndash; lfs.securewebservices.co.uk mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#116;&#104;&#111;&#109;&#97;&#115;&#64;&#115;&#111;&#102;&#97;&#103;&#97;&#110;&#103;&#46;&#100;&#107;"><i>Thomas Skyt</i></a>
&lt;thomas AT sofagang D0T dk&gt; &ndash; dk.linuxfromscratch.org
mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#115;&#105;&#109;&#101;&#64;&#100;&#111;&#116;&#45;&#115;&#105;&#109;&#101;&#46;&#99;&#111;&#109;"><i>Simon Nicoll</i></a>
&lt;sime AT dot-sime D0T com&gt; &ndash; uk.linuxfromscratch.org
mirror
</p>
</li>
</ul>
</div>
<h3>
<a id="id3521387" name="id3521387"></a>Asian Mirrors
</h3>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#112;&#121;&#110;&#103;&#64;&#115;&#112;&#97;&#109;&#46;&#97;&#118;&#101;&#114;&#115;&#101;&#46;&#110;&#101;&#116;"><i>Pui Yong</i></a>
&lt;pyng AT spam D0T averse D0T net&gt; &ndash;
sg.linuxfromscratch.org mirror
</p>
</li>
<li>
<p>
<a href="mailto:&#115;&#116;&#117;&#97;&#114;&#116;&#64;&#97;&#108;&#116;&#104;&#97;&#108;&#117;&#115;&#46;&#109;&#101;&#46;&#117;&#107;"><i>Stuart
Harris</i></a> &lt;stuart AT althalus D0T me D0T uk&gt; &ndash;
lfs.mirror.intermedia.com.sg mirror
</p>
</li>
</ul>
</div>
<h3>
<a id="id3521223" name="id3521223"></a>Australian Mirrors
</h3>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#106;&#97;&#115;&#111;&#110;&#64;&#100;&#115;&#116;&#99;&#46;&#101;&#100;&#117;&#46;&#97;&#117;"><i>Jason Andrade</i></a>
&lt;jason AT dstc D0T edu D0T au&gt; &ndash; au.linuxfromscratch.org
mirror
</p>
</li>
</ul>
</div>
<h2>
<a id="id3520240" name="id3520240"></a>Former Project Team
Members
</h2>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href=
"mailto:&#116;&#104;&#101;&#108;&#97;&#100;&#121;&#115;&#107;&#121;&#101;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Christine
Barczak</i></a> &lt;theladyskye AT linuxfromscratch D0T org&gt;
&ndash; LFS Book Editor
</p>
</li>
<li>
<p>
Timothy Bauscher
</p>
</li>
<li>
<p>
Robert Briggs
</p>
</li>
<li>
<p>
Ian Chilton
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#101;&#114;&#111;&#101;&#110;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Jeroen
Coumans</i></a> &lt;jeroen AT linuxfromscratch D0T org&gt; &ndash;
Website Developer, FAQ Maintainer
</p>
</li>
<li>
<p>
Alex Groenewoud &ndash; LFS Technical Writer
</p>
</li>
<li>
<p>
Marc Heerdink
</p>
</li>
<li>
<p>
Mark Hymers
</p>
</li>
<li>
<p>
Seth W. Klein &ndash; FAQ maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#110;&#105;&#99;&#104;&#111;&#108;&#97;&#115;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Nicholas
Leippe</i></a> &lt;nicholas AT linuxfromscratch D0T org&gt;
&ndash; Wiki Maintainer
</p>
</li>
<li>
<p>
Simon Perreault
</p>
</li>
<li>
<p>
<a href="mailto:&#115;&#99;&#111;&#116;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Scot Mc
Pherson</i></a> &lt;scot AT linuxfromscratch D0T org&gt; &ndash;
LFS NNTP Gateway Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#115;&#101;&#109;&#122;&#120;&#64;&#110;&#101;&#119;&#109;&#97;&#105;&#108;&#46;&#114;&#117;"><i>Alexander
Patrakov</i></a> &lt;semzx AT newmail D0T ru&gt; &ndash; LFS
Technical Writer
</p>
</li>
<li>
<p>
<a href="mailto:&#103;&#115;&#99;&#104;&#97;&#102;&#101;&#114;&#64;&#122;&#105;&#112;&#46;&#99;&#111;&#109;&#46;&#97;&#117;"><i>Greg
Schafer</i></a> &lt;gschafer AT zip D0T com D0T au&gt; &ndash; LFS
Technical Writer
</p>
</li>
<li>
<p>
Jesse Tie-Ten-Quee &ndash; LFS Technical Writer
</p>
</li>
<li>
<p>
<a href="mailto:&#106;&#101;&#114;&#101;&#109;&#121;&#64;&#108;&#105;&#110;&#117;&#120;&#102;&#114;&#111;&#109;&#115;&#99;&#114;&#97;&#116;&#99;&#104;&#46;&#111;&#114;&#103;"><i>Jeremy
Utley</i></a> &lt;jeremy AT linuxfromscratch D0T org&gt; &ndash;
LFS Technical Writer, Bugzilla Maintainer, LFS-Bootscripts
Maintainer
</p>
</li>
<li>
<p>
<a href="mailto:&#122;&#119;&#105;&#110;&#107;&#108;&#101;&#115;&#64;&#103;&#109;&#97;&#105;&#108;&#46;&#99;&#111;&#109;"><i>Zack Winkles</i></a>
&lt;zwinkles AT gmail D0T com&gt; &ndash; LFS Technical Writer
</p>
</li>
</ul>
</div>
<h2>
<a id="id3521620" name="id3521620"></a>A very special thank you
to our donators
</h2>
<div class="itemizedlist">
<ul>
<li>
<p>
<a href="mailto:&#100;&#101;&#97;&#110;&#64;&#118;&#105;&#112;&#101;&#114;&#115;&#111;&#102;&#116;&#46;&#99;&#111;&#46;&#117;&#107;"><i>Dean
Benson</i></a> &lt;dean AT vipersoft D0T co D0T uk&gt; for several
monetary contributions
</p>
</li>
<li>
<p>
<a href="mailto:&#104;&#114;&#120;&#64;&#104;&#114;&#120;&#110;&#101;&#116;&#46;&#100;&#101;"><i>Hagen Herrschaft</i></a>
&lt;hrx AT hrxnet D0T de&gt; for donating a 2.2 GHz P4 system, now
running under the name of Lorien
</p>
</li>
<li>
<p>
<a href="http://www.vasoftware.com"><i>VA Software</i></a>
who, on behalf of <a href=
"http://www.linux.com"><i>Linux.com</i></a>, donated a VA
Linux 420 (former StartX SP2) workstation
</p>
</li>
<li>
<p>
Mark Stone for donating Belgarath, the linuxfromscratch.org
server
</p>
</li>
</ul>
</div>
</div>
</div>
<div class="index">
<div class="titlepage">
<h1 class="index">
Index
</h1>
</div>
<div class="index">
<div class="indexdiv">
<h2>
Packages
</h2>
<ul>
<li>
<strong class="item">Autoconf:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a>
</li>
<li>
<strong class="item">Automake:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a>
</li>
<li>
<strong class="item">Bash:</strong> <a href=
"#ch-system-bash">Bash-3.0</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-bash">Bash-3.0</a>
</li>
</ul>
</li>
<li>
<strong class="item">Binutils:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a>
<ul>
<li>
<strong class="secitem">tools, pass 1:</strong> <a href=
"#ch-tools-binutils-pass1">Binutils-2.15.94.0.2.2 - Pass
1</a>
</li>
<li>
<strong class="secitem">tools, pass 2:</strong> <a href=
"#ch-tools-binutils-pass2">Binutils-2.15.94.0.2.2 - Pass
2</a>
</li>
</ul>
</li>
<li>
<strong class="item">Bison:</strong> <a href=
"#ch-system-bison">Bison-2.0</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-bison">Bison-2.0</a>
</li>
</ul>
</li>
<li>
<strong class="item">Bootscripts:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a>
<ul>
<li>
<strong class="secitem">usage:</strong> <a href=
"#ch-scripts-usage">How Do These Bootscripts Work?</a>
</li>
</ul>
</li>
<li>
<strong class="item">Bzip2:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-bzip2">Bzip2-1.0.3</a>
</li>
</ul>
</li>
<li>
<strong class="item">Coreutils:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-coreutils">Coreutils-5.2.1</a>
</li>
</ul>
</li>
<li>
<strong class="item">DejaGNU:</strong> <a href=
"#ch-tools-dejagnu">DejaGNU-1.4.4</a>
</li>
<li>
<strong class="item">Diffutils:</strong> <a href=
"#ch-system-diffutils">Diffutils-2.8.1</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-diffutils">Diffutils-2.8.1</a>
</li>
</ul>
</li>
<li>
<strong class="item">E2fsprogs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a>
</li>
<li>
<strong class="item">Expect:</strong> <a href=
"#ch-tools-expect">Expect-5.43.0</a>
</li>
<li>
<strong class="item">File:</strong> <a href=
"#ch-system-file">File-4.13</a>
</li>
<li>
<strong class="item">Findutils:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-findutils">Findutils-4.2.23</a>
</li>
</ul>
</li>
<li>
<strong class="item">Flex:</strong> <a href=
"#ch-system-flex">Flex-2.5.31</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-flex">Flex-2.5.31</a>
</li>
</ul>
</li>
<li>
<strong class="item">Gawk:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-gawk">Gawk-3.1.4</a>
</li>
</ul>
</li>
<li>
<strong class="item">GCC:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a>
<ul>
<li>
<strong class="secitem">tools, pass 1:</strong> <a href=
"#ch-tools-gcc-pass1">GCC-3.4.3 - Pass 1</a>
</li>
<li>
<strong class="secitem">tools, pass 2:</strong> <a href=
"#ch-tools-gcc-pass2">GCC-3.4.3 - Pass 2</a>
</li>
</ul>
</li>
<li>
<strong class="item">Gettext:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-gettext">Gettext-0.14.3</a>
</li>
</ul>
</li>
<li>
<strong class="item">Glibc:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-glibc">Glibc-2.3.4</a>
</li>
</ul>
</li>
<li>
<strong class="item">Grep:</strong> <a href=
"#ch-system-grep">Grep-2.5.1a</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-grep">Grep-2.5.1a</a>
</li>
</ul>
</li>
<li>
<strong class="item">Groff:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a>
</li>
<li>
<strong class="item">GRUB:</strong> <a href=
"#ch-system-grub">GRUB-0.96</a>
<ul>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#ch-bootable-grub">Making the LFS System Bootable</a>
</li>
</ul>
</li>
<li>
<strong class="item">Gzip:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-gzip">Gzip-1.3.5</a>
</li>
</ul>
</li>
<li>
<strong class="item">Hotplug:</strong> <a href=
"#ch-system-hotplug">Hotplug-2004_09_23</a>
</li>
<li>
<strong class="item">Iana-Etc:</strong> <a href=
"#ch-system-iana-etc">Iana-Etc-1.04</a>
</li>
<li>
<strong class="item">Inetutils:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a>
</li>
<li>
<strong class="item">IPRoute2:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a>
</li>
<li>
<strong class="item">Kbd:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a>
</li>
<li>
<strong class="item">Less:</strong> <a href=
"#ch-system-less">Less-382</a>
</li>
<li>
<strong class="item">Libtool:</strong> <a href=
"#ch-system-libtool">Libtool-1.5.14</a>
</li>
<li>
<strong class="item">Linux:</strong> <a href=
"#ch-bootable-kernel">Linux-2.6.11.12</a>
</li>
<li>
<strong class="item">Linux-Libc-Headers:</strong> <a href=
"#ch-system-linux-libc-headers">Linux-Libc-Headers-2.6.11.2</a>
<ul>
<li>
<strong class="secitem">tools, headers:</strong> <a href=
"#ch-tools-linux-libc-headers">Linux-Libc-Headers-2.6.11.2</a>
</li>
</ul>
</li>
<li>
<strong class="item">M4:</strong> <a href=
"#ch-system-m4">M4-1.4.3</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-m4">M4-1.4.3</a>
</li>
</ul>
</li>
<li>
<strong class="item">Make:</strong> <a href=
"#ch-system-make">Make-3.80</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-make">Make-3.80</a>
</li>
</ul>
</li>
<li>
<strong class="item">Man:</strong> <a href=
"#ch-system-man">Man-1.5p</a>
</li>
<li>
<strong class="item">Man-pages:</strong> <a href=
"#ch-system-man-pages">Man-pages-2.01</a>
</li>
<li>
<strong class="item">Mktemp:</strong> <a href=
"#ch-system-mktemp">Mktemp-1.5</a>
</li>
<li>
<strong class="item">Module-Init-Tools:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a>
</li>
<li>
<strong class="item">Ncurses:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-ncurses">Ncurses-5.4</a>
</li>
</ul>
</li>
<li>
<strong class="item">Patch:</strong> <a href=
"#ch-system-patch">Patch-2.5.4</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-patch">Patch-2.5.4</a>
</li>
</ul>
</li>
<li>
<strong class="item">Perl:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-perl">Perl-5.8.7</a>
</li>
</ul>
</li>
<li>
<strong class="item">Procps:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a>
</li>
<li>
<strong class="item">Psmisc:</strong> <a href=
"#ch-system-psmisc">Psmisc-21.6</a>
</li>
<li>
<strong class="item">Readline:</strong> <a href=
"#ch-system-readline">Readline-5.0</a>
</li>
<li>
<strong class="item">Sed:</strong> <a href=
"#ch-system-sed">Sed-4.1.4</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-sed">Sed-4.1.4</a>
</li>
</ul>
</li>
<li>
<strong class="item">Shadow:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a>
<ul>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#conf-shadow">Configuring Shadow</a>
</li>
</ul>
</li>
<li>
<strong class="item">Sysklogd:</strong> <a href=
"#ch-system-sysklogd">Sysklogd-1.4.1</a>
<ul>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#conf-sysklogd">Configuring Sysklogd</a>
</li>
</ul>
</li>
<li>
<strong class="item">Sysvinit:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a>
<ul>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#conf-sysvinit">Configuring Sysvinit</a>
</li>
</ul>
</li>
<li>
<strong class="item">Tar:</strong> <a href=
"#ch-system-tar">Tar-1.15.1</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-tar">Tar-1.15.1</a>
</li>
</ul>
</li>
<li>
<strong class="item">Tcl:</strong> <a href=
"#ch-tools-tcl">Tcl-8.4.9</a>
</li>
<li>
<strong class="item">Texinfo:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-texinfo">Texinfo-4.8</a>
</li>
</ul>
</li>
<li>
<strong class="item">Udev:</strong> <a href=
"#ch-system-udev">Udev-056</a>
<ul>
<li>
<strong class="secitem">usage:</strong> <a href=
"#ch-scripts-udev">Device and Module Handling on an LFS
System</a>
</li>
</ul>
</li>
<li>
<strong class="item">Util-linux:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a>
<ul>
<li>
<strong class="secitem">tools:</strong> <a href=
"#ch-tools-util-linux">Util-linux-2.12q</a>
</li>
</ul>
</li>
<li>
<strong class="item">Vim:</strong> <a href=
"#ch-system-vim">Vim-6.3</a>
</li>
<li>
<strong class="item">Zlib:</strong> <a href=
"#ch-system-zlib">Zlib-1.2.3</a>
</li>
</ul>
</div>
<div class="indexdiv">
<h2>
Programs
</h2>
<ul>
<li>
<strong class="item">a2p:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#a2p">description</a>
</li>
<li>
<strong class="item">acinstall:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#acinstall">description</a>
</li>
<li>
<strong class="item">aclocal:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#aclocal">description</a>
</li>
<li>
<strong class="item">aclocal-1.9.5:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#aclocal-version">description</a>
</li>
<li>
<strong class="item">addftinfo:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#addftinfo">description</a>
</li>
<li>
<strong class="item">addr2line:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#addr2line">description</a>
</li>
<li>
<strong class="item">afmtodit:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#afmtodit">description</a>
</li>
<li>
<strong class="item">agetty:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#agetty">description</a>
</li>
<li>
<strong class="item">apropos:</strong> <a href=
"#ch-system-man">Man-1.5p</a> -- <a href=
"#apropos">description</a>
</li>
<li>
<strong class="item">ar:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#ar">description</a>
</li>
<li>
<strong class="item">arch:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#arch">description</a>
</li>
<li>
<strong class="item">as:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#as">description</a>
</li>
<li>
<strong class="item">autoconf:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a> -- <a href=
"#autoconf">description</a>
</li>
<li>
<strong class="item">autoheader:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a> -- <a href=
"#autoheader">description</a>
</li>
<li>
<strong class="item">autom4te:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a> -- <a href=
"#autom4te">description</a>
</li>
<li>
<strong class="item">automake:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#automake">description</a>
</li>
<li>
<strong class="item">automake-1.9.5:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#automake-version">description</a>
</li>
<li>
<strong class="item">autopoint:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#autopoint">description</a>
</li>
<li>
<strong class="item">autoreconf:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a> -- <a href=
"#autoreconf">description</a>
</li>
<li>
<strong class="item">autoscan:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a> -- <a href=
"#autoscan">description</a>
</li>
<li>
<strong class="item">autoupdate:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a> -- <a href=
"#autoupdate">description</a>
</li>
<li>
<strong class="item">awk:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#awk">description</a>
</li>
<li>
<strong class="item">badblocks:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#badblocks">description</a>
</li>
<li>
<strong class="item">basename:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#basename">description</a>
</li>
<li>
<strong class="item">bash:</strong> <a href=
"#ch-system-bash">Bash-3.0</a> -- <a href=
"#bash">description</a>
</li>
<li>
<strong class="item">bashbug:</strong> <a href=
"#ch-system-bash">Bash-3.0</a> -- <a href=
"#bashbug">description</a>
</li>
<li>
<strong class="item">bigram:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a> -- <a href=
"#bigram">description</a>
</li>
<li>
<strong class="item">bison:</strong> <a href=
"#ch-system-bison">Bison-2.0</a> -- <a href=
"#bison">description</a>
</li>
<li>
<strong class="item">blkid:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#blkid">description</a>
</li>
<li>
<strong class="item">blockdev:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#blockdev">description</a>
</li>
<li>
<strong class="item">bunzip2:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bunzip2">description</a>
</li>
<li>
<strong class="item">bzcat:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzcat">description</a>
</li>
<li>
<strong class="item">bzcmp:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzcmp">description</a>
</li>
<li>
<strong class="item">bzdiff:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzdiff">description</a>
</li>
<li>
<strong class="item">bzegrep:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzegrep">description</a>
</li>
<li>
<strong class="item">bzfgrep:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzfgrep">description</a>
</li>
<li>
<strong class="item">bzgrep:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzgrep">description</a>
</li>
<li>
<strong class="item">bzip2:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzip2">description</a>
</li>
<li>
<strong class="item">bzip2recover:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzip2recover">description</a>
</li>
<li>
<strong class="item">bzless:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzless">description</a>
</li>
<li>
<strong class="item">bzmore:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#bzmore">description</a>
</li>
<li>
<strong class="item">c++:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#c">description</a>
</li>
<li>
<strong class="item">c++filt:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#c-filt">description</a>
</li>
<li>
<strong class="item">c2ph:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#c2ph">description</a>
</li>
<li>
<strong class="item">cal:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#cal">description</a>
</li>
<li>
<strong class="item">captoinfo:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#captoinfo">description</a>
</li>
<li>
<strong class="item">cat:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#cat">description</a>
</li>
<li>
<strong class="item">catchsegv:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#catchsegv">description</a>
</li>
<li>
<strong class="item">cc:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#cc">description</a>
</li>
<li>
<strong class="item">cfdisk:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#cfdisk">description</a>
</li>
<li>
<strong class="item">chage:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#chage">description</a>
</li>
<li>
<strong class="item">chattr:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#chattr">description</a>
</li>
<li>
<strong class="item">chfn:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#chfn">description</a>
</li>
<li>
<strong class="item">chgrp:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#chgrp">description</a>
</li>
<li>
<strong class="item">chkdupexe:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#chkdupexe">description</a>
</li>
<li>
<strong class="item">chmod:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#chmod">description</a>
</li>
<li>
<strong class="item">chown:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#chown">description</a>
</li>
<li>
<strong class="item">chpasswd:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#chpasswd">description</a>
</li>
<li>
<strong class="item">chroot:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#chroot">description</a>
</li>
<li>
<strong class="item">chsh:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#chsh">description</a>
</li>
<li>
<strong class="item">chvt:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#chvt">description</a>
</li>
<li>
<strong class="item">cksum:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#cksum">description</a>
</li>
<li>
<strong class="item">clear:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#clear">description</a>
</li>
<li>
<strong class="item">cmp:</strong> <a href=
"#ch-system-diffutils">Diffutils-2.8.1</a> -- <a href=
"#cmp">description</a>
</li>
<li>
<strong class="item">code:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a> -- <a href=
"#code">description</a>
</li>
<li>
<strong class="item">col:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#col">description</a>
</li>
<li>
<strong class="item">colcrt:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#colcrt">description</a>
</li>
<li>
<strong class="item">colrm:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#colrm">description</a>
</li>
<li>
<strong class="item">column:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#column">description</a>
</li>
<li>
<strong class="item">comm:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#comm">description</a>
</li>
<li>
<strong class="item">compile:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#compile">description</a>
</li>
<li>
<strong class="item">compile_et:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#compile_et">description</a>
</li>
<li>
<strong class="item">compress:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#compress">description</a>
</li>
<li>
<strong class="item">config.charset:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#config.charset">description</a>
</li>
<li>
<strong class="item">config.guess:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#config.guess">description</a>
</li>
<li>
<strong class="item">config.rpath:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#config.rpath">description</a>
</li>
<li>
<strong class="item">config.sub:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#config.sub">description</a>
</li>
<li>
<strong class="item">cp:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#cp">description</a>
</li>
<li>
<strong class="item">cpp:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#cpp">description</a>
</li>
<li>
<strong class="item">csplit:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#csplit">description</a>
</li>
<li>
<strong class="item">ctrlaltdel:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#ctrlaltdel">description</a>
</li>
<li>
<strong class="item">ctstat:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#ctstat">description</a>
</li>
<li>
<strong class="item">cut:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#cut">description</a>
</li>
<li>
<strong class="item">cytune:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#cytune">description</a>
</li>
<li>
<strong class="item">date:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#date">description</a>
</li>
<li>
<strong class="item">dd:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#dd">description</a>
</li>
<li>
<strong class="item">ddate:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#ddate">description</a>
</li>
<li>
<strong class="item">deallocvt:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#deallocvt">description</a>
</li>
<li>
<strong class="item">debugfs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#debugfs">description</a>
</li>
<li>
<strong class="item">depcomp:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#depcomp">description</a>
</li>
<li>
<strong class="item">depmod:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a> --
<a href="#depmod">description</a>
</li>
<li>
<strong class="item">df:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#df">description</a>
</li>
<li>
<strong class="item">diff:</strong> <a href=
"#ch-system-diffutils">Diffutils-2.8.1</a> -- <a href=
"#diff">description</a>
</li>
<li>
<strong class="item">diff3:</strong> <a href=
"#ch-system-diffutils">Diffutils-2.8.1</a> -- <a href=
"#diff3">description</a>
</li>
<li>
<strong class="item">dir:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#dir">description</a>
</li>
<li>
<strong class="item">dircolors:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#dircolors">description</a>
</li>
<li>
<strong class="item">dirname:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#dirname">description</a>
</li>
<li>
<strong class="item">dmesg:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#dmesg">description</a>
</li>
<li>
<strong class="item">dprofpp:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#dprofpp">description</a>
</li>
<li>
<strong class="item">du:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#du">description</a>
</li>
<li>
<strong class="item">dumpe2fs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#dumpe2fs">description</a>
</li>
<li>
<strong class="item">dumpkeys:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#dumpkeys">description</a>
</li>
<li>
<strong class="item">e2fsck:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#e2fsck">description</a>
</li>
<li>
<strong class="item">e2image:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#e2image">description</a>
</li>
<li>
<strong class="item">e2label:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#e2label">description</a>
</li>
<li>
<strong class="item">echo:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#echo">description</a>
</li>
<li>
<strong class="item">efm_filter.pl:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#efm_filter.pl">description</a>
</li>
<li>
<strong class="item">efm_perl.pl:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#efm_perl.pl">description</a>
</li>
<li>
<strong class="item">egrep:</strong> <a href=
"#ch-system-grep">Grep-2.5.1a</a> -- <a href=
"#egrep">description</a>
</li>
<li>
<strong class="item">elisp-comp:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#elisp-comp">description</a>
</li>
<li>
<strong class="item">elvtune:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#elvtune">description</a>
</li>
<li>
<strong class="item">en2cxs:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#en2cxs">description</a>
</li>
<li>
<strong class="item">env:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#env">description</a>
</li>
<li>
<strong class="item">envsubst:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#envsubst">description</a>
</li>
<li>
<strong class="item">eqn:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#eqn">description</a>
</li>
<li>
<strong class="item">eqn2graph:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#eqn2graph">description</a>
</li>
<li>
<strong class="item">ex:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href="#ex">description</a>
</li>
<li>
<strong class="item">expand:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#expand">description</a>
</li>
<li>
<strong class="item">expect:</strong> <a href=
"#ch-tools-expect">Expect-5.43.0</a> -- <a href=
"#expect">description</a>
</li>
<li>
<strong class="item">expiry:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#expiry">description</a>
</li>
<li>
<strong class="item">expr:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#expr">description</a>
</li>
<li>
<strong class="item">factor:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#factor">description</a>
</li>
<li>
<strong class="item">faillog:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#faillog">description</a>
</li>
<li>
<strong class="item">false:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#false">description</a>
</li>
<li>
<strong class="item">fdformat:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#fdformat">description</a>
</li>
<li>
<strong class="item">fdisk:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#fdisk">description</a>
</li>
<li>
<strong class="item">fgconsole:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#fgconsole">description</a>
</li>
<li>
<strong class="item">fgrep:</strong> <a href=
"#ch-system-grep">Grep-2.5.1a</a> -- <a href=
"#fgrep">description</a>
</li>
<li>
<strong class="item">file:</strong> <a href=
"#ch-system-file">File-4.13</a> -- <a href=
"#file">description</a>
</li>
<li>
<strong class="item">find:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a> -- <a href=
"#find">description</a>
</li>
<li>
<strong class="item">find2perl:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#find2perl">description</a>
</li>
<li>
<strong class="item">findfs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#findfs">description</a>
</li>
<li>
<strong class="item">flex:</strong> <a href=
"#ch-system-flex">Flex-2.5.31</a> -- <a href=
"#flex">description</a>
</li>
<li>
<strong class="item">fmt:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#fmt">description</a>
</li>
<li>
<strong class="item">fold:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#fold">description</a>
</li>
<li>
<strong class="item">frcode:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a> -- <a href=
"#frcode">description</a>
</li>
<li>
<strong class="item">free:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#free">description</a>
</li>
<li>
<strong class="item">fsck:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#fsck">description</a>
</li>
<li>
<strong class="item">fsck.cramfs:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#fsck.cramfs">description</a>
</li>
<li>
<strong class="item">fsck.ext2:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#fsck.ext2">description</a>
</li>
<li>
<strong class="item">fsck.ext3:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#fsck.ext3">description</a>
</li>
<li>
<strong class="item">fsck.minix:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#fsck.minix">description</a>
</li>
<li>
<strong class="item">ftp:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#ftp">description</a>
</li>
<li>
<strong class="item">fuser:</strong> <a href=
"#ch-system-psmisc">Psmisc-21.6</a> -- <a href=
"#fuser">description</a>
</li>
<li>
<strong class="item">g++:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#g">description</a>
</li>
<li>
<strong class="item">gawk:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#gawk">description</a>
</li>
<li>
<strong class="item">gawk-3.1.4:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#gawk-version">description</a>
</li>
<li>
<strong class="item">gcc:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#gcc">description</a>
</li>
<li>
<strong class="item">gccbug:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#gccbug">description</a>
</li>
<li>
<strong class="item">gcov:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#gcov">description</a>
</li>
<li>
<strong class="item">gencat:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#gencat">description</a>
</li>
<li>
<strong class="item">geqn:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#geqn">description</a>
</li>
<li>
<strong class="item">getconf:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#getconf">description</a>
</li>
<li>
<strong class="item">getent:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#getent">description</a>
</li>
<li>
<strong class="item">getkeycodes:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#getkeycodes">description</a>
</li>
<li>
<strong class="item">getopt:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#getopt">description</a>
</li>
<li>
<strong class="item">gettext:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#gettext">description</a>
</li>
<li>
<strong class="item">gettextize:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#gettextize">description</a>
</li>
<li>
<strong class="item">getunimap:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#getunimap">description</a>
</li>
<li>
<strong class="item">gpasswd:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#gpasswd">description</a>
</li>
<li>
<strong class="item">gprof:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#gprof">description</a>
</li>
<li>
<strong class="item">grcat:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#grcat">description</a>
</li>
<li>
<strong class="item">grep:</strong> <a href=
"#ch-system-grep">Grep-2.5.1a</a> -- <a href=
"#grep">description</a>
</li>
<li>
<strong class="item">grn:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#grn">description</a>
</li>
<li>
<strong class="item">grodvi:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#grodvi">description</a>
</li>
<li>
<strong class="item">groff:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#groff">description</a>
</li>
<li>
<strong class="item">groffer:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#groffer">description</a>
</li>
<li>
<strong class="item">grog:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#grog">description</a>
</li>
<li>
<strong class="item">grolbp:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#grolbp">description</a>
</li>
<li>
<strong class="item">grolj4:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#grolj4">description</a>
</li>
<li>
<strong class="item">grops:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#grops">description</a>
</li>
<li>
<strong class="item">grotty:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#grotty">description</a>
</li>
<li>
<strong class="item">groupadd:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#groupadd">description</a>
</li>
<li>
<strong class="item">groupdel:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#groupdel">description</a>
</li>
<li>
<strong class="item">groupmod:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#groupmod">description</a>
</li>
<li>
<strong class="item">groups:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#groups">description</a>
</li>
<li>
<strong class="item">grpck:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#grpck">description</a>
</li>
<li>
<strong class="item">grpconv:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#grpconv">description</a>
</li>
<li>
<strong class="item">grpunconv:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#grpunconv">description</a>
</li>
<li>
<strong class="item">grub:</strong> <a href=
"#ch-system-grub">GRUB-0.96</a> -- <a href=
"#grub">description</a>
</li>
<li>
<strong class="item">grub-install:</strong> <a href=
"#ch-system-grub">GRUB-0.96</a> -- <a href=
"#grub-install">description</a>
</li>
<li>
<strong class="item">grub-md5-crypt:</strong> <a href=
"#ch-system-grub">GRUB-0.96</a> -- <a href=
"#grub-md5-crypt">description</a>
</li>
<li>
<strong class="item">grub-terminfo:</strong> <a href=
"#ch-system-grub">GRUB-0.96</a> -- <a href=
"#grub-terminfo">description</a>
</li>
<li>
<strong class="item">gtbl:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#gtbl">description</a>
</li>
<li>
<strong class="item">gunzip:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#gunzip">description</a>
</li>
<li>
<strong class="item">gzexe:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#gzexe">description</a>
</li>
<li>
<strong class="item">gzip:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#gzip">description</a>
</li>
<li>
<strong class="item">h2ph:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#h2ph">description</a>
</li>
<li>
<strong class="item">h2xs:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#h2xs">description</a>
</li>
<li>
<strong class="item">halt:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#halt">description</a>
</li>
<li>
<strong class="item">head:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#head">description</a>
</li>
<li>
<strong class="item">hexdump:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#hexdump">description</a>
</li>
<li>
<strong class="item">hostid:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#hostid">description</a>
</li>
<li>
<strong class="item">hostname:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#hostname">description</a>
</li>
<li>
<strong class="item">hostname:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#hostname-gettext">description</a>
</li>
<li>
<strong class="item">hotplug:</strong> <a href=
"#ch-system-hotplug">Hotplug-2004_09_23</a> -- <a href=
"#hotplug">description</a>
</li>
<li>
<strong class="item">hpftodit:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#hpftodit">description</a>
</li>
<li>
<strong class="item">hwclock:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#hwclock">description</a>
</li>
<li>
<strong class="item">iconv:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#iconv">description</a>
</li>
<li>
<strong class="item">iconvconfig:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#iconvconfig">description</a>
</li>
<li>
<strong class="item">id:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#id">description</a>
</li>
<li>
<strong class="item">ifcfg:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#ifcfg">description</a>
</li>
<li>
<strong class="item">ifnames:</strong> <a href=
"#ch-system-autoconf">Autoconf-2.59</a> -- <a href=
"#ifnames">description</a>
</li>
<li>
<strong class="item">ifstat:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#ifstat">description</a>
</li>
<li>
<strong class="item">igawk:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#igawk">description</a>
</li>
<li>
<strong class="item">indxbib:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#indxbib">description</a>
</li>
<li>
<strong class="item">info:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a> -- <a href=
"#info">description</a>
</li>
<li>
<strong class="item">infocmp:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#infocmp">description</a>
</li>
<li>
<strong class="item">infokey:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a> -- <a href=
"#infokey">description</a>
</li>
<li>
<strong class="item">infotocap:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#infotocap">description</a>
</li>
<li>
<strong class="item">init:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#init">description</a>
</li>
<li>
<strong class="item">insmod:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a> --
<a href="#insmod">description</a>
</li>
<li>
<strong class="item">insmod.static:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a> --
<a href="#insmod.static">description</a>
</li>
<li>
<strong class="item">install:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#install">description</a>
</li>
<li>
<strong class="item">install-info:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a> -- <a href=
"#install-info">description</a>
</li>
<li>
<strong class="item">install-sh:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#install-sh">description</a>
</li>
<li>
<strong class="item">ip:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#ip">description</a>
</li>
<li>
<strong class="item">ipcrm:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#ipcrm">description</a>
</li>
<li>
<strong class="item">ipcs:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#ipcs">description</a>
</li>
<li>
<strong class="item">isosize:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#isosize">description</a>
</li>
<li>
<strong class="item">join:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#join">description</a>
</li>
<li>
<strong class="item">kbdrate:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#kbdrate">description</a>
</li>
<li>
<strong class="item">kbd_mode:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#kbd_mode">description</a>
</li>
<li>
<strong class="item">kill:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#kill">description</a>
</li>
<li>
<strong class="item">killall:</strong> <a href=
"#ch-system-psmisc">Psmisc-21.6</a> -- <a href=
"#killall">description</a>
</li>
<li>
<strong class="item">killall5:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#killall5">description</a>
</li>
<li>
<strong class="item">klogd:</strong> <a href=
"#ch-system-sysklogd">Sysklogd-1.4.1</a> -- <a href=
"#klogd">description</a>
</li>
<li>
<strong class="item">last:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#last">description</a>
</li>
<li>
<strong class="item">lastb:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#lastb">description</a>
</li>
<li>
<strong class="item">lastlog:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#lastlog">description</a>
</li>
<li>
<strong class="item">ld:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#ld">description</a>
</li>
<li>
<strong class="item">ldconfig:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#ldconfig">description</a>
</li>
<li>
<strong class="item">ldd:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#ldd">description</a>
</li>
<li>
<strong class="item">lddlibc4:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#lddlibc4">description</a>
</li>
<li>
<strong class="item">less:</strong> <a href=
"#ch-system-less">Less-382</a> -- <a href=
"#less">description</a>
</li>
<li>
<strong class="item">less.sh:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#less.sh">description</a>
</li>
<li>
<strong class="item">lessecho:</strong> <a href=
"#ch-system-less">Less-382</a> -- <a href=
"#lessecho">description</a>
</li>
<li>
<strong class="item">lesskey:</strong> <a href=
"#ch-system-less">Less-382</a> -- <a href=
"#lesskey">description</a>
</li>
<li>
<strong class="item">lex:</strong> <a href=
"#ch-system-flex">Flex-2.5.31</a> -- <a href=
"#lex">description</a>
</li>
<li>
<strong class="item">lfskernel-2.6.11.12:</strong> <a href=
"#ch-bootable-kernel">Linux-2.6.11.12</a> -- <a href=
"#lfskernel">description</a>
</li>
<li>
<strong class="item">libnetcfg:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#libnetcfg">description</a>
</li>
<li>
<strong class="item">libtool:</strong> <a href=
"#ch-system-libtool">Libtool-1.5.14</a> -- <a href=
"#libtool">description</a>
</li>
<li>
<strong class="item">libtoolize:</strong> <a href=
"#ch-system-libtool">Libtool-1.5.14</a> -- <a href=
"#libtoolize">description</a>
</li>
<li>
<strong class="item">line:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#line">description</a>
</li>
<li>
<strong class="item">link:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#link">description</a>
</li>
<li>
<strong class="item">lkbib:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#lkbib">description</a>
</li>
<li>
<strong class="item">ln:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#ln">description</a>
</li>
<li>
<strong class="item">lnstat:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#lnstat">description</a>
</li>
<li>
<strong class="item">loadkeys:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#loadkeys">description</a>
</li>
<li>
<strong class="item">loadunimap:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#loadunimap">description</a>
</li>
<li>
<strong class="item">locale:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#locale">description</a>
</li>
<li>
<strong class="item">localedef:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#localedef">description</a>
</li>
<li>
<strong class="item">locate:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a> -- <a href=
"#locate">description</a>
</li>
<li>
<strong class="item">logger:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#logger">description</a>
</li>
<li>
<strong class="item">login:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#login">description</a>
</li>
<li>
<strong class="item">logname:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#logname">description</a>
</li>
<li>
<strong class="item">logoutd:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#logoutd">description</a>
</li>
<li>
<strong class="item">logsave:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#logsave">description</a>
</li>
<li>
<strong class="item">look:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#look">description</a>
</li>
<li>
<strong class="item">lookbib:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#lookbib">description</a>
</li>
<li>
<strong class="item">losetup:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#losetup">description</a>
</li>
<li>
<strong class="item">ls:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#ls">description</a>
</li>
<li>
<strong class="item">lsattr:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#lsattr">description</a>
</li>
<li>
<strong class="item">lsmod:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a> --
<a href="#lsmod">description</a>
</li>
<li>
<strong class="item">m4:</strong> <a href=
"#ch-system-m4">M4-1.4.3</a> -- <a href="#m4">description</a>
</li>
<li>
<strong class="item">make:</strong> <a href=
"#ch-system-make">Make-3.80</a> -- <a href=
"#make">description</a>
</li>
<li>
<strong class="item">makeinfo:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a> -- <a href=
"#makeinfo">description</a>
</li>
<li>
<strong class="item">makewhatis:</strong> <a href=
"#ch-system-man">Man-1.5p</a> -- <a href=
"#makewhatis">description</a>
</li>
<li>
<strong class="item">man:</strong> <a href=
"#ch-system-man">Man-1.5p</a> -- <a href=
"#man">description</a>
</li>
<li>
<strong class="item">man2dvi:</strong> <a href=
"#ch-system-man">Man-1.5p</a> -- <a href=
"#man2dvi">description</a>
</li>
<li>
<strong class="item">man2html:</strong> <a href=
"#ch-system-man">Man-1.5p</a> -- <a href=
"#man2html">description</a>
</li>
<li>
<strong class="item">mapscrn:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#mapscrn">description</a>
</li>
<li>
<strong class="item">mbchk:</strong> <a href=
"#ch-system-grub">GRUB-0.96</a> -- <a href=
"#mbchk">description</a>
</li>
<li>
<strong class="item">mcookie:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#mcookie">description</a>
</li>
<li>
<strong class="item">md5sum:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#md5sum">description</a>
</li>
<li>
<strong class="item">mdate-sh:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#mdate-sh">description</a>
</li>
<li>
<strong class="item">mesg:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#mesg">description</a>
</li>
<li>
<strong class="item">missing:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#missing">description</a>
</li>
<li>
<strong class="item">mkdir:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#mkdir">description</a>
</li>
<li>
<strong class="item">mke2fs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#mke2fs">description</a>
</li>
<li>
<strong class="item">mkfifo:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#mkfifo">description</a>
</li>
<li>
<strong class="item">mkfs:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#mkfs">description</a>
</li>
<li>
<strong class="item">mkfs.bfs:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#mkfs.bfs">description</a>
</li>
<li>
<strong class="item">mkfs.cramfs:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#mkfs.cramfs">description</a>
</li>
<li>
<strong class="item">mkfs.ext2:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#mkfs.ext2">description</a>
</li>
<li>
<strong class="item">mkfs.ext3:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#mkfs.ext3">description</a>
</li>
<li>
<strong class="item">mkfs.minix:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#mkfs.minix">description</a>
</li>
<li>
<strong class="item">mkinstalldirs:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#mkinstalldirs">description</a>
</li>
<li>
<strong class="item">mklost+found:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#mklost-found">description</a>
</li>
<li>
<strong class="item">mknod:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#mknod">description</a>
</li>
<li>
<strong class="item">mkpasswd:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#mkpasswd">description</a>
</li>
<li>
<strong class="item">mkswap:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#mkswap">description</a>
</li>
<li>
<strong class="item">mktemp:</strong> <a href=
"#ch-system-mktemp">Mktemp-1.5</a> -- <a href=
"#mktemp">description</a>
</li>
<li>
<strong class="item">mk_cmds:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#mk_cmds">description</a>
</li>
<li>
<strong class="item">mmroff:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#mmroff">description</a>
</li>
<li>
<strong class="item">modinfo:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a> --
<a href="#modinfo">description</a>
</li>
<li>
<strong class="item">modprobe:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a> --
<a href="#modprobe">description</a>
</li>
<li>
<strong class="item">more:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#more">description</a>
</li>
<li>
<strong class="item">mount:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#mount">description</a>
</li>
<li>
<strong class="item">mountpoint:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#mountpoint">description</a>
</li>
<li>
<strong class="item">msgattrib:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgattrib">description</a>
</li>
<li>
<strong class="item">msgcat:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgcat">description</a>
</li>
<li>
<strong class="item">msgcmp:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgcmp">description</a>
</li>
<li>
<strong class="item">msgcomm:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgcomm">description</a>
</li>
<li>
<strong class="item">msgconv:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgconv">description</a>
</li>
<li>
<strong class="item">msgen:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgen">description</a>
</li>
<li>
<strong class="item">msgexec:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgexec">description</a>
</li>
<li>
<strong class="item">msgfilter:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgfilter">description</a>
</li>
<li>
<strong class="item">msgfmt:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgfmt">description</a>
</li>
<li>
<strong class="item">msggrep:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msggrep">description</a>
</li>
<li>
<strong class="item">msginit:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msginit">description</a>
</li>
<li>
<strong class="item">msgmerge:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgmerge">description</a>
</li>
<li>
<strong class="item">msgunfmt:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msgunfmt">description</a>
</li>
<li>
<strong class="item">msguniq:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#msguniq">description</a>
</li>
<li>
<strong class="item">mtrace:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#mtrace">description</a>
</li>
<li>
<strong class="item">mv:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#mv">description</a>
</li>
<li>
<strong class="item">mve.awk:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#mve.awk">description</a>
</li>
<li>
<strong class="item">namei:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#namei">description</a>
</li>
<li>
<strong class="item">neqn:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#neqn">description</a>
</li>
<li>
<strong class="item">newgrp:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#newgrp">description</a>
</li>
<li>
<strong class="item">newusers:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#newusers">description</a>
</li>
<li>
<strong class="item">ngettext:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#ngettext">description</a>
</li>
<li>
<strong class="item">nice:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#nice">description</a>
</li>
<li>
<strong class="item">nl:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#nl">description</a>
</li>
<li>
<strong class="item">nm:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#nm">description</a>
</li>
<li>
<strong class="item">nohup:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#nohup">description</a>
</li>
<li>
<strong class="item">nroff:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#nroff">description</a>
</li>
<li>
<strong class="item">nscd:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#nscd">description</a>
</li>
<li>
<strong class="item">nscd_nischeck:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#nscd_nischeck">description</a>
</li>
<li>
<strong class="item">nstat:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#nstat">description</a>
</li>
<li>
<strong class="item">objcopy:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#objcopy">description</a>
</li>
<li>
<strong class="item">objdump:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#objdump">description</a>
</li>
<li>
<strong class="item">od:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#od">description</a>
</li>
<li>
<strong class="item">openvt:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#openvt">description</a>
</li>
<li>
<strong class="item">passwd:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#passwd">description</a>
</li>
<li>
<strong class="item">paste:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#paste">description</a>
</li>
<li>
<strong class="item">patch:</strong> <a href=
"#ch-system-patch">Patch-2.5.4</a> -- <a href=
"#patch">description</a>
</li>
<li>
<strong class="item">pathchk:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#pathchk">description</a>
</li>
<li>
<strong class="item">pcprofiledump:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#pcprofiledump">description</a>
</li>
<li>
<strong class="item">perl:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#perl">description</a>
</li>
<li>
<strong class="item">perl5.8.7:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#perl-version">description</a>
</li>
<li>
<strong class="item">perlbug:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#perlbug">description</a>
</li>
<li>
<strong class="item">perlcc:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#perlcc">description</a>
</li>
<li>
<strong class="item">perldoc:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#perldoc">description</a>
</li>
<li>
<strong class="item">perlivp:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#perlivp">description</a>
</li>
<li>
<strong class="item">pfbtops:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#pfbtops">description</a>
</li>
<li>
<strong class="item">pg:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#pg">description</a>
</li>
<li>
<strong class="item">pgawk:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#pgawk">description</a>
</li>
<li>
<strong class="item">pgawk-3.1.4:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#pgawk-version">description</a>
</li>
<li>
<strong class="item">pgrep:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#pgrep">description</a>
</li>
<li>
<strong class="item">pic:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#pic">description</a>
</li>
<li>
<strong class="item">pic2graph:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#pic2graph">description</a>
</li>
<li>
<strong class="item">piconv:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#piconv">description</a>
</li>
<li>
<strong class="item">pidof:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#pidof">description</a>
</li>
<li>
<strong class="item">ping:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#ping">description</a>
</li>
<li>
<strong class="item">pinky:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#pinky">description</a>
</li>
<li>
<strong class="item">pivot_root:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#pivot_root">description</a>
</li>
<li>
<strong class="item">pkill:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#pkill">description</a>
</li>
<li>
<strong class="item">pl2pm:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#pl2pm">description</a>
</li>
<li>
<strong class="item">pltags.pl:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#pltags.pl">description</a>
</li>
<li>
<strong class="item">pmap:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#pmap">description</a>
</li>
<li>
<strong class="item">pod2html:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#pod2html">description</a>
</li>
<li>
<strong class="item">pod2latex:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#pod2latex">description</a>
</li>
<li>
<strong class="item">pod2man:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#pod2man">description</a>
</li>
<li>
<strong class="item">pod2text:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#pod2text">description</a>
</li>
<li>
<strong class="item">pod2usage:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#pod2usage">description</a>
</li>
<li>
<strong class="item">podchecker:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#podchecker">description</a>
</li>
<li>
<strong class="item">podselect:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#podselect">description</a>
</li>
<li>
<strong class="item">post-grohtml:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#post-grohtml">description</a>
</li>
<li>
<strong class="item">poweroff:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#poweroff">description</a>
</li>
<li>
<strong class="item">pr:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#pr">description</a>
</li>
<li>
<strong class="item">pre-grohtml:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#pre-grohtml">description</a>
</li>
<li>
<strong class="item">printenv:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#printenv">description</a>
</li>
<li>
<strong class="item">printf:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#printf">description</a>
</li>
<li>
<strong class="item">ps:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#ps">description</a>
</li>
<li>
<strong class="item">psed:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#psed">description</a>
</li>
<li>
<strong class="item">psfaddtable:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#psfaddtable">description</a>
</li>
<li>
<strong class="item">psfgettable:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#psfgettable">description</a>
</li>
<li>
<strong class="item">psfstriptable:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#psfstriptable">description</a>
</li>
<li>
<strong class="item">psfxtable:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#psfxtable">description</a>
</li>
<li>
<strong class="item">pstree:</strong> <a href=
"#ch-system-psmisc">Psmisc-21.6</a> -- <a href=
"#pstree">description</a>
</li>
<li>
<strong class="item">pstree.x11:</strong> <a href=
"#ch-system-psmisc">Psmisc-21.6</a> -- <a href=
"#pstree.x11">description</a>
</li>
<li>
<strong class="item">pstruct:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#pstruct">description</a>
</li>
<li>
<strong class="item">ptx:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#ptx">description</a>
</li>
<li>
<strong class="item">pt_chown:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#pt_chown">description</a>
</li>
<li>
<strong class="item">pwcat:</strong> <a href=
"#ch-system-gawk">Gawk-3.1.4</a> -- <a href=
"#pwcat">description</a>
</li>
<li>
<strong class="item">pwck:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#pwck">description</a>
</li>
<li>
<strong class="item">pwconv:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#pwconv">description</a>
</li>
<li>
<strong class="item">pwd:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#pwd">description</a>
</li>
<li>
<strong class="item">pwunconv:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#pwunconv">description</a>
</li>
<li>
<strong class="item">py-compile:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#py-compile">description</a>
</li>
<li>
<strong class="item">ramsize:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#ramsize">description</a>
</li>
<li>
<strong class="item">ranlib:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#ranlib">description</a>
</li>
<li>
<strong class="item">raw:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#raw">description</a>
</li>
<li>
<strong class="item">rcp:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#rcp">description</a>
</li>
<li>
<strong class="item">rdev:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#rdev">description</a>
</li>
<li>
<strong class="item">readelf:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#readelf">description</a>
</li>
<li>
<strong class="item">readlink:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#readlink">description</a>
</li>
<li>
<strong class="item">readprofile:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#readprofile">description</a>
</li>
<li>
<strong class="item">reboot:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#reboot">description</a>
</li>
<li>
<strong class="item">ref:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#ref">description</a>
</li>
<li>
<strong class="item">refer:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#refer">description</a>
</li>
<li>
<strong class="item">rename:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#rename">description</a>
</li>
<li>
<strong class="item">renice:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#renice">description</a>
</li>
<li>
<strong class="item">reset:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#reset">description</a>
</li>
<li>
<strong class="item">resize2fs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#resize2fs">description</a>
</li>
<li>
<strong class="item">resizecons:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#resizecons">description</a>
</li>
<li>
<strong class="item">rev:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#rev">description</a>
</li>
<li>
<strong class="item">rlogin:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#rlogin">description</a>
</li>
<li>
<strong class="item">rm:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#rm">description</a>
</li>
<li>
<strong class="item">rmdir:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#rmdir">description</a>
</li>
<li>
<strong class="item">rmmod:</strong> <a href=
"#ch-system-module-init-tools">Module-Init-Tools-3.1</a> --
<a href="#rmmod">description</a>
</li>
<li>
<strong class="item">rmt:</strong> <a href=
"#ch-system-tar">Tar-1.15.1</a> -- <a href=
"#rmt">description</a>
</li>
<li>
<strong class="item">rootflags:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#rootflags">description</a>
</li>
<li>
<strong class="item">routef:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#routef">description</a>
</li>
<li>
<strong class="item">routel:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#routel">description</a>
</li>
<li>
<strong class="item">rpcgen:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#rpcgen">description</a>
</li>
<li>
<strong class="item">rpcinfo:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#rpcinfo">description</a>
</li>
<li>
<strong class="item">rsh:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#rsh">description</a>
</li>
<li>
<strong class="item">rtacct:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#rtacct">description</a>
</li>
<li>
<strong class="item">rtmon:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#rtmon">description</a>
</li>
<li>
<strong class="item">rtpr:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#rtpr">description</a>
</li>
<li>
<strong class="item">rtstat:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#rtstat">description</a>
</li>
<li>
<strong class="item">runlevel:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#runlevel">description</a>
</li>
<li>
<strong class="item">runtest:</strong> <a href=
"#ch-tools-dejagnu">DejaGNU-1.4.4</a> -- <a href=
"#runtest">description</a>
</li>
<li>
<strong class="item">rview:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#rview">description</a>
</li>
<li>
<strong class="item">rvim:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#rvim">description</a>
</li>
<li>
<strong class="item">s2p:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#s2p">description</a>
</li>
<li>
<strong class="item">script:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#script">description</a>
</li>
<li>
<strong class="item">sdiff:</strong> <a href=
"#ch-system-diffutils">Diffutils-2.8.1</a> -- <a href=
"#sdiff">description</a>
</li>
<li>
<strong class="item">sed:</strong> <a href=
"#ch-system-sed">Sed-4.1.4</a> -- <a href=
"#sed">description</a>
</li>
<li>
<strong class="item">seq:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#seq">description</a>
</li>
<li>
<strong class="item">setfdprm:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#setfdprm">description</a>
</li>
<li>
<strong class="item">setfont:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#setfont">description</a>
</li>
<li>
<strong class="item">setkeycodes:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#setkeycodes">description</a>
</li>
<li>
<strong class="item">setleds:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#setleds">description</a>
</li>
<li>
<strong class="item">setlogcons:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#setlogcons">description</a>
</li>
<li>
<strong class="item">setmetamode:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#setmetamode">description</a>
</li>
<li>
<strong class="item">setsid:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#setsid">description</a>
</li>
<li>
<strong class="item">setterm:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#setterm">description</a>
</li>
<li>
<strong class="item">setvesablank:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#setvesablank">description</a>
</li>
<li>
<strong class="item">sfdisk:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#sfdisk">description</a>
</li>
<li>
<strong class="item">sg:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#sg">description</a>
</li>
<li>
<strong class="item">sh:</strong> <a href=
"#ch-system-bash">Bash-3.0</a> -- <a href=
"#sh">description</a>
</li>
<li>
<strong class="item">sha1sum:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#sha1sum">description</a>
</li>
<li>
<strong class="item">showconsolefont:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#showconsolefont">description</a>
</li>
<li>
<strong class="item">showkey:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#showkey">description</a>
</li>
<li>
<strong class="item">shred:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#shred">description</a>
</li>
<li>
<strong class="item">shtags.pl:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#shtags.pl">description</a>
</li>
<li>
<strong class="item">shutdown:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#shutdown">description</a>
</li>
<li>
<strong class="item">size:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#size">description</a>
</li>
<li>
<strong class="item">skill:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#skill">description</a>
</li>
<li>
<strong class="item">sleep:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#sleep">description</a>
</li>
<li>
<strong class="item">sln:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#sln">description</a>
</li>
<li>
<strong class="item">snice:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#snice">description</a>
</li>
<li>
<strong class="item">soelim:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#soelim">description</a>
</li>
<li>
<strong class="item">sort:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#sort">description</a>
</li>
<li>
<strong class="item">splain:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#splain">description</a>
</li>
<li>
<strong class="item">split:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#split">description</a>
</li>
<li>
<strong class="item">sprof:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#sprof">description</a>
</li>
<li>
<strong class="item">ss:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#ss">description</a>
</li>
<li>
<strong class="item">stat:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#stat">description</a>
</li>
<li>
<strong class="item">strings:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#strings">description</a>
</li>
<li>
<strong class="item">strip:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#strip">description</a>
</li>
<li>
<strong class="item">stty:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#stty">description</a>
</li>
<li>
<strong class="item">su:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#su">description</a>
</li>
<li>
<strong class="item">sulogin:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#sulogin">description</a>
</li>
<li>
<strong class="item">sum:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#sum">description</a>
</li>
<li>
<strong class="item">swapdev:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#swapdev">description</a>
</li>
<li>
<strong class="item">swapoff:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#swapoff">description</a>
</li>
<li>
<strong class="item">swapon:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#swapon">description</a>
</li>
<li>
<strong class="item">symlink-tree:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#symlink-tree">description</a>
</li>
<li>
<strong class="item">sync:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#sync">description</a>
</li>
<li>
<strong class="item">sysctl:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#sysctl">description</a>
</li>
<li>
<strong class="item">syslogd:</strong> <a href=
"#ch-system-sysklogd">Sysklogd-1.4.1</a> -- <a href=
"#syslogd">description</a>
</li>
<li>
<strong class="item">tac:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#tac">description</a>
</li>
<li>
<strong class="item">tack:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#tack">description</a>
</li>
<li>
<strong class="item">tail:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#tail">description</a>
</li>
<li>
<strong class="item">talk:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#talk">description</a>
</li>
<li>
<strong class="item">tar:</strong> <a href=
"#ch-system-tar">Tar-1.15.1</a> -- <a href=
"#tar">description</a>
</li>
<li>
<strong class="item">tbl:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#tbl">description</a>
</li>
<li>
<strong class="item">tc:</strong> <a href=
"#ch-system-iproute2">IPRoute2-2.6.11-050330</a> -- <a href=
"#ss">description</a>
</li>
<li>
<strong class="item">tclsh:</strong> <a href=
"#ch-tools-tcl">Tcl-8.4.9</a> -- <a href=
"#tclsh">description</a>
</li>
<li>
<strong class="item">tclsh8.4:</strong> <a href=
"#ch-tools-tcl">Tcl-8.4.9</a> -- <a href=
"#tclsh8.4">description</a>
</li>
<li>
<strong class="item">tcltags:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#tcltags">description</a>
</li>
<li>
<strong class="item">tee:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#tee">description</a>
</li>
<li>
<strong class="item">telinit:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#telinit">description</a>
</li>
<li>
<strong class="item">telnet:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#telnet">description</a>
</li>
<li>
<strong class="item">tempfile:</strong> <a href=
"#ch-system-mktemp">Mktemp-1.5</a> -- <a href=
"#tempfile">description</a>
</li>
<li>
<strong class="item">test:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#test">description</a>
</li>
<li>
<strong class="item">texi2dvi:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a> -- <a href=
"#texi2dvi">description</a>
</li>
<li>
<strong class="item">texi2pdf:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a> -- <a href=
"#texi2pdf">description</a>
</li>
<li>
<strong class="item">texindex:</strong> <a href=
"#ch-system-texinfo">Texinfo-4.8</a> -- <a href=
"#texindex">description</a>
</li>
<li>
<strong class="item">tfmtodit:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#tfmtodit">description</a>
</li>
<li>
<strong class="item">tftp:</strong> <a href=
"#ch-system-inetutils">Inetutils-1.4.2</a> -- <a href=
"#tftp">description</a>
</li>
<li>
<strong class="item">tic:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#tic">description</a>
</li>
<li>
<strong class="item">tload:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#tload">description</a>
</li>
<li>
<strong class="item">toe:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#toe">description</a>
</li>
<li>
<strong class="item">top:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#top">description</a>
</li>
<li>
<strong class="item">touch:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#touch">description</a>
</li>
<li>
<strong class="item">tput:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#tput">description</a>
</li>
<li>
<strong class="item">tr:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#tr">description</a>
</li>
<li>
<strong class="item">troff:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#troff">description</a>
</li>
<li>
<strong class="item">true:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#true">description</a>
</li>
<li>
<strong class="item">tset:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#tset">description</a>
</li>
<li>
<strong class="item">tsort:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#tsort">description</a>
</li>
<li>
<strong class="item">tty:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#tty">description</a>
</li>
<li>
<strong class="item">tune2fs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#tune2fs">description</a>
</li>
<li>
<strong class="item">tunelp:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#tunelp">description</a>
</li>
<li>
<strong class="item">tzselect:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#tzselect">description</a>
</li>
<li>
<strong class="item">udev:</strong> <a href=
"#ch-system-udev">Udev-056</a> -- <a href=
"#udev">description</a>
</li>
<li>
<strong class="item">udevd:</strong> <a href=
"#ch-system-udev">Udev-056</a> -- <a href=
"#udevd">description</a>
</li>
<li>
<strong class="item">udevinfo:</strong> <a href=
"#ch-system-udev">Udev-056</a> -- <a href=
"#udevinfo">description</a>
</li>
<li>
<strong class="item">udevsend:</strong> <a href=
"#ch-system-udev">Udev-056</a> -- <a href=
"#udevsend">description</a>
</li>
<li>
<strong class="item">udevstart:</strong> <a href=
"#ch-system-udev">Udev-056</a> -- <a href=
"#udevstart">description</a>
</li>
<li>
<strong class="item">udevtest:</strong> <a href=
"#ch-system-udev">Udev-056</a> -- <a href=
"#udevtest">description</a>
</li>
<li>
<strong class="item">ul:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#ul">description</a>
</li>
<li>
<strong class="item">umount:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#umount">description</a>
</li>
<li>
<strong class="item">uname:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#uname">description</a>
</li>
<li>
<strong class="item">uncompress:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#uncompress">description</a>
</li>
<li>
<strong class="item">unexpand:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#unexpand">description</a>
</li>
<li>
<strong class="item">unicode_start:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#unicode_start">description</a>
</li>
<li>
<strong class="item">unicode_stop:</strong> <a href=
"#ch-system-kbd">Kbd-1.12</a> -- <a href=
"#unicode_stop">description</a>
</li>
<li>
<strong class="item">uniq:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#uniq">description</a>
</li>
<li>
<strong class="item">unlink:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#unlink">description</a>
</li>
<li>
<strong class="item">updatedb:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a> -- <a href=
"#updatedb">description</a>
</li>
<li>
<strong class="item">uptime:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#uptime">description</a>
</li>
<li>
<strong class="item">useradd:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#useradd">description</a>
</li>
<li>
<strong class="item">userdel:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#userdel">description</a>
</li>
<li>
<strong class="item">usermod:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#usermod">description</a>
</li>
<li>
<strong class="item">users:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#users">description</a>
</li>
<li>
<strong class="item">utmpdump:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#utmpdump">description</a>
</li>
<li>
<strong class="item">uuidgen:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#uuidgen">description</a>
</li>
<li>
<strong class="item">vdir:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#vdir">description</a>
</li>
<li>
<strong class="item">vi:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href="#vi">description</a>
</li>
<li>
<strong class="item">vidmode:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#vidmode">description</a>
</li>
<li>
<strong class="item">view:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#view">description</a>
</li>
<li>
<strong class="item">vigr:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#vigr">description</a>
</li>
<li>
<strong class="item">vim:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#vim">description</a>
</li>
<li>
<strong class="item">vim132:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#vim132">description</a>
</li>
<li>
<strong class="item">vim2html.pl:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#vim2html.pl">description</a>
</li>
<li>
<strong class="item">vimdiff:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#vimdiff">description</a>
</li>
<li>
<strong class="item">vimm:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#vimm">description</a>
</li>
<li>
<strong class="item">vimspell.sh:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#vimspell.sh">description</a>
</li>
<li>
<strong class="item">vimtutor:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#vimtutor">description</a>
</li>
<li>
<strong class="item">vipw:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#vipw">description</a>
</li>
<li>
<strong class="item">vmstat:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#vmstat">description</a>
</li>
<li>
<strong class="item">w:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#w">description</a>
</li>
<li>
<strong class="item">wall:</strong> <a href=
"#ch-system-sysvinit">Sysvinit-2.86</a> -- <a href=
"#wall">description</a>
</li>
<li>
<strong class="item">watch:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#watch">description</a>
</li>
<li>
<strong class="item">wc:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#wc">description</a>
</li>
<li>
<strong class="item">whatis:</strong> <a href=
"#ch-system-man">Man-1.5p</a> -- <a href=
"#whatis">description</a>
</li>
<li>
<strong class="item">whereis:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#whereis">description</a>
</li>
<li>
<strong class="item">who:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#who">description</a>
</li>
<li>
<strong class="item">whoami:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#whoami">description</a>
</li>
<li>
<strong class="item">write:</strong> <a href=
"#ch-system-util-linux">Util-linux-2.12q</a> -- <a href=
"#write">description</a>
</li>
<li>
<strong class="item">xargs:</strong> <a href=
"#ch-system-findutils">Findutils-4.2.23</a> -- <a href=
"#xargs">description</a>
</li>
<li>
<strong class="item">xgettext:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#xgettext">description</a>
</li>
<li>
<strong class="item">xsubpp:</strong> <a href=
"#ch-system-perl">Perl-5.8.7</a> -- <a href=
"#xsubpp">description</a>
</li>
<li>
<strong class="item">xtrace:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#xtrace">description</a>
</li>
<li>
<strong class="item">xxd:</strong> <a href=
"#ch-system-vim">Vim-6.3</a> -- <a href=
"#xxd">description</a>
</li>
<li>
<strong class="item">yacc:</strong> <a href=
"#ch-system-bison">Bison-2.0</a> -- <a href=
"#yacc">description</a>
</li>
<li>
<strong class="item">yes:</strong> <a href=
"#ch-system-coreutils">Coreutils-5.2.1</a> -- <a href=
"#yes">description</a>
</li>
<li>
<strong class="item">ylwrap:</strong> <a href=
"#ch-system-automake">Automake-1.9.5</a> -- <a href=
"#ylwrap">description</a>
</li>
<li>
<strong class="item">zcat:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zcat">description</a>
</li>
<li>
<strong class="item">zcmp:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zcmp">description</a>
</li>
<li>
<strong class="item">zdiff:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zdiff">description</a>
</li>
<li>
<strong class="item">zdump:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#zdump">description</a>
</li>
<li>
<strong class="item">zegrep:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zegrep">description</a>
</li>
<li>
<strong class="item">zfgrep:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zfgrep">description</a>
</li>
<li>
<strong class="item">zforce:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zforce">description</a>
</li>
<li>
<strong class="item">zgrep:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zgrep">description</a>
</li>
<li>
<strong class="item">zic:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#zic">description</a>
</li>
<li>
<strong class="item">zless:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zless">description</a>
</li>
<li>
<strong class="item">zmore:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#zmore">description</a>
</li>
<li>
<strong class="item">znew:</strong> <a href=
"#ch-system-gzip">Gzip-1.3.5</a> -- <a href=
"#znew">description</a>
</li>
<li>
<strong class="item">zsoelim:</strong> <a href=
"#ch-system-groff">Groff-1.19.1</a> -- <a href=
"#zsoelim">description</a>
</li>
</ul>
</div>
<div class="indexdiv">
<h2>
Libraries
</h2>
<ul>
<li>
<strong class="item">ld.so:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#ld.so">description</a>
</li>
<li>
<strong class="item">libanl:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libanl">description</a>
</li>
<li>
<strong class="item">libasprintf:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#libasprintf">description</a>
</li>
<li>
<strong class="item">libbfd:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#libbfd">description</a>
</li>
<li>
<strong class="item">libblkid:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#libblkid">description</a>
</li>
<li>
<strong class="item">libBrokenLocale:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libBrokenLocale">description</a>
</li>
<li>
<strong class="item">libbsd-compat:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libbsd-compat">description</a>
</li>
<li>
<strong class="item">libbz2*:</strong> <a href=
"#ch-system-bzip2">Bzip2-1.0.3</a> -- <a href=
"#libbz2">description</a>
</li>
<li>
<strong class="item">libc:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libc">description</a>
</li>
<li>
<strong class="item">libcom_err:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#libcom_err">description</a>
</li>
<li>
<strong class="item">libcrypt:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libcrypt">description</a>
</li>
<li>
<strong class="item">libcurses:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#libcurses">description</a>
</li>
<li>
<strong class="item">libdl:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libdl">description</a>
</li>
<li>
<strong class="item">libe2p:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#libe2p">description</a>
</li>
<li>
<strong class="item">libexpect-5.43:</strong> <a href=
"#ch-tools-expect">Expect-5.43.0</a> -- <a href=
"#libexpect">description</a>
</li>
<li>
<strong class="item">libext2fs:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#libext2fs">description</a>
</li>
<li>
<strong class="item">libfl.a:</strong> <a href=
"#ch-system-flex">Flex-2.5.31</a> -- <a href=
"#libfl.a">description</a>
</li>
<li>
<strong class="item">libform:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#libform">description</a>
</li>
<li>
<strong class="item">libg:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libg">description</a>
</li>
<li>
<strong class="item">libgcc*:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#libgcc">description</a>
</li>
<li>
<strong class="item">libgettextlib:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#libgettextlib">description</a>
</li>
<li>
<strong class="item">libgettextpo:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#libgettextpo">description</a>
</li>
<li>
<strong class="item">libgettextsrc:</strong> <a href=
"#ch-system-gettext">Gettext-0.14.3</a> -- <a href=
"#libgettextsrc">description</a>
</li>
<li>
<strong class="item">libhistory:</strong> <a href=
"#ch-system-readline">Readline-5.0</a> -- <a href=
"#libhistory">description</a>
</li>
<li>
<strong class="item">libiberty:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#libiberty">description</a>
</li>
<li>
<strong class="item">libieee:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libieee">description</a>
</li>
<li>
<strong class="item">libltdl:</strong> <a href=
"#ch-system-libtool">Libtool-1.5.14</a> -- <a href=
"#libltdl">description</a>
</li>
<li>
<strong class="item">libm:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libm">description</a>
</li>
<li>
<strong class="item">libmagic:</strong> <a href=
"#ch-system-file">File-4.13</a> -- <a href=
"#libmagic">description</a>
</li>
<li>
<strong class="item">libmcheck:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libmcheck">description</a>
</li>
<li>
<strong class="item">libmemusage:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libmemusage">description</a>
</li>
<li>
<strong class="item">libmenu:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#libmenu">description</a>
</li>
<li>
<strong class="item">libncurses:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#libncurses">description</a>
</li>
<li>
<strong class="item">libnsl:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libnsl">description</a>
</li>
<li>
<strong class="item">libnss:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libnss">description</a>
</li>
<li>
<strong class="item">libopcodes:</strong> <a href=
"#ch-system-binutils">Binutils-2.15.94.0.2.2</a> -- <a href=
"#libopcodes">description</a>
</li>
<li>
<strong class="item">libpanel:</strong> <a href=
"#ch-system-ncurses">Ncurses-5.4</a> -- <a href=
"#libpanel">description</a>
</li>
<li>
<strong class="item">libpcprofile:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libpcprofile">description</a>
</li>
<li>
<strong class="item">libproc:</strong> <a href=
"#ch-system-procps">Procps-3.2.5</a> -- <a href=
"#libproc">description</a>
</li>
<li>
<strong class="item">libpthread:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libpthread">description</a>
</li>
<li>
<strong class="item">libreadline:</strong> <a href=
"#ch-system-readline">Readline-5.0</a> -- <a href=
"#libreadline">description</a>
</li>
<li>
<strong class="item">libresolv:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libresolv">description</a>
</li>
<li>
<strong class="item">librpcsvc:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#librpcsvc">description</a>
</li>
<li>
<strong class="item">librt:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#librt">description</a>
</li>
<li>
<strong class="item">libSegFault:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libSegFault">description</a>
</li>
<li>
<strong class="item">libshadow:</strong> <a href=
"#ch-system-shadow">Shadow-4.0.9</a> -- <a href=
"#libshadow">description</a>
</li>
<li>
<strong class="item">libss:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#libss">description</a>
</li>
<li>
<strong class="item">libstdc++:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#libstdc">description</a>
</li>
<li>
<strong class="item">libsupc++:</strong> <a href=
"#ch-system-gcc">GCC-3.4.3</a> -- <a href=
"#libsupc">description</a>
</li>
<li>
<strong class="item">libtcl8.4.so:</strong> <a href=
"#ch-tools-tcl">Tcl-8.4.9</a> -- <a href=
"#libtcl8.4.so">description</a>
</li>
<li>
<strong class="item">libthread_db:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libthread_db">description</a>
</li>
<li>
<strong class="item">libutil:</strong> <a href=
"#ch-system-glibc">Glibc-2.3.4</a> -- <a href=
"#libutil">description</a>
</li>
<li>
<strong class="item">libuuid:</strong> <a href=
"#ch-system-e2fsprogs">E2fsprogs-1.37</a> -- <a href=
"#libuuid">description</a>
</li>
<li>
<strong class="item">liby.a:</strong> <a href=
"#ch-system-bison">Bison-2.0</a> -- <a href=
"#liby.a">description</a>
</li>
<li>
<strong class="item">libz:</strong> <a href=
"#ch-system-zlib">Zlib-1.2.3</a> -- <a href=
"#libz">description</a>
</li>
</ul>
</div>
<div class="indexdiv">
<h2>
Scripts
</h2>
<ul>
<li>
<strong class="item">/etc/hotplug/*.agent:</strong> <a href=
"#ch-system-hotplug">Hotplug-2004_09_23</a> -- <a href=
"#hotplug-agent">description</a>
</li>
<li>
<strong class="item">/etc/hotplug/*.rc:</strong> <a href=
"#ch-system-hotplug">Hotplug-2004_09_23</a> -- <a href=
"#hotplug-rc">description</a>
</li>
<li>
<strong class="item">checkfs:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#checkfs-bootscripts">description</a>
</li>
<li>
<strong class="item">cleanfs:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#cleanfs-bootscripts">description</a>
</li>
<li>
<strong class="item">console:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#console-bootscripts">description</a>
<ul>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#ch-scripts-console">Configuring the Linux Console</a>
</li>
</ul>
</li>
<li>
<strong class="item">functions:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#functions-bootscripts">description</a>
</li>
<li>
<strong class="item">halt:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#halt-bootscripts">description</a>
</li>
<li>
<strong class="item">hotplug:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#hotplug-bootscripts">description</a>
</li>
<li>
<strong class="item">ifdown:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#ifdown-bootscripts">description</a>
</li>
<li>
<strong class="item">ifup:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#ifup-bootscripts">description</a>
</li>
<li>
<strong class="item">localnet:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#localnet-bootscripts">description</a>
<ul>
<li>
<strong class="secitem">/etc/hosts:</strong> <a href=
"#ch-scripts-hosts">Creating the /etc/hosts File</a>
</li>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#ch-scripts-hostname">Configuring the localnet
Script</a>
</li>
</ul>
</li>
<li>
<strong class="item">mountfs:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#mountfs-bootscripts">description</a>
</li>
<li>
<strong class="item">mountkernfs:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#mountkernfs-bootscripts">description</a>
</li>
<li>
<strong class="item">network:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#network-bootscripts">description</a>
<ul>
<li>
<strong class="secitem">/etc/hosts:</strong> <a href=
"#ch-scripts-hosts">Creating the /etc/hosts File</a>
</li>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#ch-scripts-network">Configuring the network Script</a>
</li>
</ul>
</li>
<li>
<strong class="item">rc:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#rc-bootscripts">description</a>
</li>
<li>
<strong class="item">reboot:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#reboot-bootscripts">description</a>
</li>
<li>
<strong class="item">sendsignals:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#sendsignals-bootscripts">description</a>
</li>
<li>
<strong class="item">setclock:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#setclock-bootscripts">description</a>
<ul>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#ch-scripts-setclock">Configuring the setclock
Script</a>
</li>
</ul>
</li>
<li>
<strong class="item">static:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#static-bootscripts">description</a>
</li>
<li>
<strong class="item">swap:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#swap-bootscripts">description</a>
</li>
<li>
<strong class="item">sysklogd:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#sysklogd-bootscripts">description</a>
<ul>
<li>
<strong class="secitem">configuring:</strong> <a href=
"#ch-scripts-sysklogd">Configuring the sysklogd
script</a>
</li>
</ul>
</li>
<li>
<strong class="item">template:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#template-bootscripts">description</a>
</li>
<li>
<strong class="item">udev:</strong> <a href=
"#ch-scripts-bootscripts">LFS-Bootscripts-3.2.1</a> --
<a href="#udev-bootscripts">description</a>
</li>
</ul>
</div>
<div class="indexdiv">
<h2>
Others
</h2>
<ul>
<li>
<strong class="item">/boot/config-2.6.11.12:</strong>
<a href="#ch-bootable-kernel">Linux-2.6.11.12</a> -- <a href=
"#config">description</a>
</li>
<li>
<strong class="item">/boot/System.map-2.6.11.12:</strong>
<a href="#ch-bootable-kernel">Linux-2.6.11.12</a> -- <a href=
"#System.map">description</a>
</li>
<li>
<strong class="item">/dev/*:</strong> <a href=
"#ch-system-devices">Populating /dev</a>
</li>
<li>
<strong class="item">/etc/fstab:</strong> <a href=
"#ch-bootable-fstab">Creating the /etc/fstab File</a>
</li>
<li>
<strong class="item">/etc/group:</strong> <a href=
"#ch-system-pwdgroup">Creating the passwd, group, and log
Files</a>
</li>
<li>
<strong class="item">/etc/hosts:</strong> <a href=
"#ch-scripts-hosts">Creating the /etc/hosts File</a>
</li>
<li>
<strong class="item">/etc/hotplug.d:</strong> <a href=
"#ch-system-hotplug">Hotplug-2004_09_23</a> -- <a href=
"#hotplug-hotplug.d">description</a>
</li>
<li>
<strong class="item">/etc/hotplug/blacklist:</strong>
<a href="#ch-system-hotplug">Hotplug-2004_09_23</a> --
<a href="#hotplug-blacklist">description</a>
</li>
<li>
<strong class="item">/etc/hotplug/hotplug.functions:</strong>
<a href="#ch-system-hotplug">Hotplug-2004_09_23</a> --
<a href="#hotplug-functions">description</a>
</li>
<li>
<strong class="item">/etc/hotplug/usb.usermap:</strong>
<a href="#ch-system-hotplug">Hotplug-2004_09_23</a> --
<a href="#hotplug-usb.usermap">description</a>
</li>
<li>
<strong class="item">/etc/hotplug/{pci,usb}:</strong>
<a href="#ch-system-hotplug">Hotplug-2004_09_23</a> --
<a href="#hotplug-subdirs">description</a>
</li>
<li>
<strong class="item">/etc/inittab:</strong> <a href=
"#conf-sysvinit">Configuring Sysvinit</a>
</li>
<li>
<strong class="item">/etc/inputrc:</strong> <a href=
"#ch-scripts-inputrc">Creating the /etc/inputrc File</a>
</li>
<li>
<strong class="item">/etc/ld.so.conf:</strong> <a href=
"#conf-ld">Configuring Dynamic Loader</a>
</li>
<li>
<strong class="item">/etc/lfs-release:</strong> <a href=
"#ch-finish-theend">The End</a>
</li>
<li>
<strong class="item">/etc/limits:</strong> <a href=
"#shadow-limits-login_access">Installation of Shadow</a>
</li>
<li>
<strong class="item">/etc/localtime:</strong> <a href=
"#conf-glibc">Configuring Glibc</a>
</li>
<li>
<strong class="item">/etc/login.access:</strong> <a href=
"#shadow-limits-login_access">Installation of Shadow</a>
</li>
<li>
<strong class="item">/etc/login.defs:</strong> <a href=
"#shadow-login_defs">Installation of Shadow</a>
</li>
<li>
<strong class="item">/etc/nsswitch.conf:</strong> <a href=
"#conf-glibc">Configuring Glibc</a>
</li>
<li>
<strong class="item">/etc/passwd:</strong> <a href=
"#ch-system-pwdgroup">Creating the passwd, group, and log
Files</a>
</li>
<li>
<strong class="item">/etc/profile:</strong> <a href=
"#ch-scripts-profile">The Bash Shell Startup Files</a>
</li>
<li>
<strong class="item">/etc/protocols:</strong> <a href=
"#ch-system-iana-etc">Iana-Etc-1.04</a>
</li>
<li>
<strong class="item">/etc/resolv.conf:</strong> <a href=
"#resolv.conf">Creating the /etc/resolv.conf File</a>
</li>
<li>
<strong class="item">/etc/services:</strong> <a href=
"#ch-system-iana-etc">Iana-Etc-1.04</a>
</li>
<li>
<strong class="item">/etc/syslog.conf:</strong> <a href=
"#conf-sysklogd">Configuring Sysklogd</a>
</li>
<li>
<strong class="item">/etc/udev:</strong> <a href=
"#ch-system-udev">Udev-056</a> -- <a href=
"#etc-udev">description</a>
</li>
<li>
<strong class="item">/etc/vim:</strong> <a href=
"#conf-vim">Configuring Vim</a>
</li>
<li>
<strong class="item">/lib/firmware:</strong> <a href=
"#ch-system-hotplug">Hotplug-2004_09_23</a> -- <a href=
"#hotplug-firmware">description</a>
</li>
<li>
<strong class="item">/usr/include/{asm,linux}/*.h:</strong>
<a href=
"#ch-system-linux-libc-headers">Linux-Libc-Headers-2.6.11.2</a>
-- <a href="#linux-libc-headers">description</a>
</li>
<li>
<strong class="item">/var/log/btmp:</strong> <a href=
"#ch-system-pwdgroup">Creating the passwd, group, and log
Files</a>
</li>
<li>
<strong class="item">/var/log/hotplug/events:</strong>
<a href="#ch-system-hotplug">Hotplug-2004_09_23</a> --
<a href="#hotplug-events">description</a>
</li>
<li>
<strong class="item">/var/log/lastlog:</strong> <a href=
"#ch-system-pwdgroup">Creating the passwd, group, and log
Files</a>
</li>
<li>
<strong class="item">/var/log/wtmp:</strong> <a href=
"#ch-system-pwdgroup">Creating the passwd, group, and log
Files</a>
</li>
<li>
<strong class="item">/var/run/utmp:</strong> <a href=
"#ch-system-pwdgroup">Creating the passwd, group, and log
Files</a>
</li>
<li>
<strong class="item">man pages:</strong> <a href=
"#ch-system-man-pages">Man-pages-2.01</a> -- <a href=
"#man-pages">description</a>
</li>
</ul>
</div>
</div>
</div>
</div>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink