Changeset 2c094d6


Ignore:
Timestamp:
09/28/2002 09:08:29 PM (22 years ago)
Author:
Timothy Bauscher <timothy@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
4d46e012
Parents:
f5cc1c17
Message:

Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2138 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
75 edited

Legend:

Unmodified
Added
Removed
  • appendixa/autoconf-desc.xml

    rf5cc1c17 r2c094d6  
    1212<para>autoconf is a tool for producing shell scripts that automatically
    1313configure software source code packages to adapt to many kinds of
    14 Unix-like systems.  The configuration scripts produced by autoconf are
     14Unix-like systems. The configuration scripts produced by autoconf are
    1515independent of autoconf when they are run, so their users do not need to
    1616have autoconf.</para></sect4>
     
    2525<sect4><title>autoreconf</title>
    2626<para>If there are a lot of autoconf-generated configure scripts, the
    27 autoreconf program can save some work.  It runs autoconf (and
    28 autoheader, where appropriate) repeatedly to remake the autoconf
     27autoreconf program can save some work. It runs autoconf and
     28autoheader (where appropriate) repeatedly to remake the autoconf
    2929configure scripts and configuration header templates in the directory
    3030tree rooted at the current directory.</para></sect4>
     
    3232<sect4><title>autoscan</title>
    3333<para>The autoscan program can help to create a configure.in file for
    34 a software package. autoscan examines source files in the directory
    35 tree rooted at a directory given as a command line argument, or the
    36 current directory if none is given.  It searches the source files for
    37 common portability problems and creates a file configure.scan which
    38 is a preliminary configure.in for that package.</para></sect4>
     34a software package. autoscan examines the source files in a directory
     35tree. If a directory is not specified on the command line, then the
     36current working directory is used. The source files are searched for
     37common portability problems and a configure.scan file is created to
     38serve as the preliminary configure.in for that package.</para></sect4>
    3939
    4040<sect4><title>autoupdate</title>
     
    4747package. It prints the identifiers that the package already uses in C
    4848preprocessor conditionals. If a package has already been set up to
    49 have some portability, this program can help to figure out what its
    50 configure needs to check for. It may help fill in some gaps in a
    51 configure.in generated by autoscan.</para></sect4>
     49have some portability, this program can help to determine what configure
     50needs to check. It may fill in some gaps in a configure.in file generated
     51by autoscan.</para></sect4>
    5252
    5353</sect3>
  • appendixa/automake-desc.xml

    rf5cc1c17 r2c094d6  
    1515<sect4><title>aclocal, aclocal-1.6</title>
    1616<para>automake includes a number of autoconf macros which can be used in
    17 packages; some of them are actually required by automake in certain
    18 situations. These macros must be defined in the aclocal.m4-file;
    19 otherwise they will not be seen by autoconf.</para>
     17packages, some of which are needed by automake in certain
     18situations. These macros must be defined in the aclocal.m4-file
     19or they will not be seen by autoconf.</para>
    2020
    2121<para>The aclocal program will automatically generate aclocal.m4 files
    22 based on the contents of configure.in.  This provides a convenient
    23 way to get automake-provided macros, without having to search around.
     22based on the contents of configure.in. This provides a convenient
     23way to get automake-provided macros without having to search around.
    2424Also, the aclocal mechanism is extensible for use
    2525by other packages.</para></sect4>
     
    2727<sect4><title>automake, automake-1.6</title>
    2828<para>To create all the Makefile.in's for a package, run the automake
    29 program in the top level directory, with no arguments.  automake will
     29program in the top level directory, with no arguments. automake will
    3030automatically find each appropriate Makefile.am (by scanning
    3131configure.in) and generate the corresponding Makefile.in.</para></sect4>
  • appendixa/bash-desc.xml

    rf5cc1c17 r2c094d6  
    2020
    2121<sect4><title>sh</title>
    22 <para>sh is a symlink to the bash program.  When invoked as sh, bash
     22<para>sh is a symlink to the bash program. When invoked as sh, bash
    2323tries to mimic the startup behavior of historical versions of sh as closely
    2424as possible, while conforming to the POSIX standard as
  • appendixa/bin86-desc.xml

    rf5cc1c17 r2c094d6  
    1919
    2020<sect4><title>ld86</title>
    21 <para>ld86 understands only the object files produced by the as86 assembler, it
     21<para>ld86 understands only the object files produced by the as86 assembler. It
    2222can link them into either an impure or a
    2323separate I&amp;D executable.</para></sect4>
  • appendixa/binutils-desc.xml

    rf5cc1c17 r2c094d6  
    1212<sect4><title>addr2line</title>
    1313<para>addr2line translates program addresses into file names and line numbers.
    14 Given an address and an executable, it uses the  debugging information in
     14Given an address and an executable, it uses the debugging information in
    1515the executable to figure out which file name and line number are associated
    1616with a given address.</para></sect4>
     
    1919<para>The ar program creates, modifies, and extracts from archives. An archive
    2020is a single file holding a collection of other files in a structure that makes
    21 it  possible to retrieve the original individual files (called members of
     21it possible to retrieve the original individual files (called members of
    2222the archive).</para></sect4>
    2323
     
    3333
    3434<sect4><title>ld</title>
    35 <para>ld combines a number of object and archive files,  relocates their data
     35<para>ld combines a number of object and archive files, relocates their data
    3636and ties up symbol references. Often the last step in building a new compiled
    3737program to run is a call to ld.</para></sect4>
     
    5454<sect4><title>ranlib</title>
    5555<para>ranlib generates an index to the contents of an archive, and stores it in
    56 the archive.  The index lists each symbol defined by a member of an archive
     56the archive. The index lists each symbol defined by an archive member
    5757that is a relocatable object file.</para></sect4>
    5858
     
    6666
    6767<sect4><title>strings</title>
    68 <para>For each  file given, strings prints the printable character sequences
    69 that are at least  4  characters long (or the number specified with an
     68<para>For each file given, strings prints the printable character sequences
     69that are at least 4 characters long (or the number specified with an
    7070option to the program) and are followed by an unprintable character. By
    7171default, it only prints the strings from the initialized and loaded
     
    9393<sect4><title>libopcodes</title>
    9494<para>libopcodes is a native library for dealing with opcodes and is
    95 used in the course of building utilities such as objdump.  Opcodes are
     95used in the course of building utilities such as objdump. Opcodes are
    9696actually "readable text" versions of instructions for the
    9797processor.</para></sect4>
  • appendixa/bison-desc.xml

    rf5cc1c17 r2c094d6  
    1616writing the actual program a user specifies how things should be connected
    1717and with those rules a program is constructed that analyzes the
    18 text file.  There are a lot of examples where structure is needed and
     18text file. There are a lot of examples where structure is needed and
    1919one of them is the calculator.</para>
    2020
     
    4040the next thing that the computer sees is the result of 2*3 and the
    4141number 1 which are joined by the add symbol. Adding 1 to the previous
    42 result makes 7. In calculating the most complex calculations can be
     42result makes 7. In calculating, the most complex calculations can be
    4343broken down in this tree format and the computer just starts at the
    4444bottom and works its way up to the top and comes with the correct
  • appendixa/bzip2-desc.xml

    rf5cc1c17 r2c094d6  
    2727<sect4><title>bzip2</title>
    2828<para>bzip2 compresses files using the Burrows-Wheeler block sorting text
    29 compression algorithm, and Huffman coding. Compression is generally
    30 considerably  better than that achieved by more conventional LZ77/LZ78-based
    31 compressors, and approaches the performance of the PPM family of statistical
     29compression algorithm and Huffman coding. Compression is generally
     30considerably better than that achieved by more conventional LZ77/LZ78-based
     31compressors and approaches the performance of the PPM family of statistical
    3232compressors.</para></sect4>
    3333
     
    3737<sect4><title>bzless</title>
    3838<para>bzless is a filter which allows examination of compressed
    39 or plain text files one screenful at a time on a soft-copy
     39or plain text files, one screenful at a time on a soft-copy
    4040terminal, like less.</para></sect4>
    4141
    4242<sect4><title>bzmore</title>
    4343<para>bzmore is a filter which allows examination of compressed
    44 or plain text files one screenful at a time on a soft-copy
     44or plain text files, one screenful at a time on a soft-copy
    4545terminal, like more.</para></sect4>
    4646
     
    5353<sect4><title>libbz2</title>
    5454<para>libbz2 is the library for implementing lossless, block-sorting data
    55 compression using the Burrows-Wheeler algorithm.</para></sect4>
     55compression, using the Burrows-Wheeler algorithm.</para></sect4>
    5656
    5757</sect3>
  • appendixa/e2fsprogs-desc.xml

    rf5cc1c17 r2c094d6  
    2121
    2222<sect4><title>compile_et</title>
    23 <para>compile_et is used to convert a table listing error-code names
    24 and associated messages into a C source file suitable for use with the
    25 com_err library.</para></sect4>
     23<para>compile_et is used to convert a table, listing error-code names
     24and associated messages, into a C source file that is suitable for use
     25with the com_err library.</para></sect4>
    2626
    2727<sect4><title>debugfs</title>
    28 <para>The debugfs program is a file system debugger. It can be used  to examine
     28<para>The debugfs program is a file system debugger. It can be used to examine
    2929and change the state of an ext2 file system.</para></sect4>
    3030
     
    3434
    3535<sect4><title>e2fsck and fsck.ext2</title>
    36 <para>e2fsck is used to check and optionally repair Linux second
    37 extended filesystems. fsck.ext2 does the same as e2fsck.</para></sect4>
     36<para>e2fsck and fsck.ext2 are used to check, and optionally repair, Linux
     37second extended filesystems.</para></sect4>
    3838
    3939<sect4><title>e2image</title>
    40 <para>e2image is used to save critical ext2 filesystem data to 
     40<para>e2image is used to save critical ext2 filesystem data to
    4141a file.</para></sect4>
    4242
     
    4646
    4747<sect4><title>fsck</title>
    48 <para>fsck is used to check and optionally repair a Linux
    49 file system.</para></sect4>
     48<para>fsck is used to check, and optionally repair, a Linux file
     49system.</para></sect4>
    5050
    5151<sect4><title>fsck.ext3</title>
    52 <para>fsck.ext3 is used to check and optionally repair a Linux ext3
     52<para>fsck.ext3 is used to check, and optionally repair, a Linux ext3
    5353filesystems.</para></sect4>
    5454
     
    5959<sect4><title>mk_cmds</title>
    6060<para>The mk_cmds utility takes a command table file as input and produces
    61 a C source file as output which is intended to be used with the subsystem
     61a C source file as output, which is intended to be used with the subsystem
    6262library, libss.</para></sect4>
    6363
     
    8585<para>The uuidgen program creates a new universally unique identifier (UUID)
    8686using the libuuid library. The new UUID can reasonably be considered unique
    87 among all UUIDs created on the local system, and among UUIDs created on other
    88 systems in the past and in the future.</para></sect4>
     87among all UUIDs created, on the local system and on other
     88systems, in the past and in the future.</para></sect4>
    8989
    9090</sect3>
  • appendixa/ed-desc.xml

    rf5cc1c17 r2c094d6  
    99
    1010<sect4><title>ed</title>
    11 <para>ed is a line-oriented text editor.  It is used to create, display,
     11<para>ed is a line-oriented text editor. It is used to create, display,
    1212modify and otherwise manipulate text files.</para></sect4>
    1313
  • appendixa/file-desc.xml

    rf5cc1c17 r2c094d6  
    1010<sect4><title>file</title>
    1111<para>file tests each specified file in an attempt to classify it. There are
    12 three sets  of  tests, performed in this order: filesystem tests,
    13 magic number tests, and language tests. The first test that succeeds
     12three sets of tests, performed in this order: filesystem tests,
     13magic number tests and language tests. The first test that succeeds
    1414causes the file type to be printed.</para></sect4>
    1515
  • appendixa/fileutils-desc.xml

    rf5cc1c17 r2c094d6  
    1616<sect4><title>chmod</title>
    1717<para>chmod changes the permissions of each given file according to mode, which
    18 can be either a symbolic representation of changes to make, or an octal
     18can be either a symbolic representation of changes to make or an octal
    1919number representing the bit pattern for the new permissions.</para></sect4>
    2020
     
    3939<para>dir and vdir are versions of ls with different default output formats.
    4040These programs list each given file or directory name. Directory contents
    41 are sorted alphabetically.  For ls, files are by default listed in columns,
    42 sorted  vertically, if the standard output is a terminal; otherwise they
    43 are listed one per  line. For dir, files are by default listed in columns,
    44 sorted vertically. For vdir, files are by default listed in
     41are sorted alphabetically. For ls, files are, by default, listed in columns
     42sorted vertically if the standard output is a terminal; otherwise they
     43are listed one per line. For dir, files are, by default, listed in columns
     44sorted vertically. For vdir, files are, by default, listed in
    4545long format.</para></sect4>
    4646
    4747<sect4><title>dircolors</title>
    48 <para>dircolors  outputs commands to set the LS_COLOR environment variable.
     48<para>dircolors outputs commands to set the LS_COLOR environment variable.
    4949The LS_COLOR variable is use to change the default color scheme used by
    5050ls and related utilities.</para></sect4>
    5151
    5252<sect4><title>du</title>
    53 <para>du displays the amount of disk space used by each argument and for each
    54 subdirectory of directory arguments.</para></sect4>
     53<para>du displays the amount of disk space used by each file or directory
     54listed on the command-line and by each of their subdirectories.</para></sect4>
    5555
    5656<sect4><title>install</title>
  • appendixa/flex-desc.xml

    rf5cc1c17 r2c094d6  
    1010<sect4><title>flex</title>
    1111<para>flex is a tool for generating programs which recognize
    12 patterns in text.  Pattern recognition is very useful in many applications.
    13 A user sets up rules
    14 what to look for and flex will make a program that looks for those
    15 patterns. The reason people use flex is that it is much easier to set up
    16 rules for what to look for than to write the actual program which finds
    17 the text.</para></sect4>
     12patterns in text. Pattern recognition is very useful in many applications.
     13A user sets up rules about what to look for and flex will make a program
     14that looks for those patterns. The reason people use flex is that it is
     15much easier to set up rules for what to look for than to write the actual
     16program which finds the text.</para></sect4>
    1817
    1918<sect4><title>flex++</title>
  • appendixa/gcc-desc.xml

    rf5cc1c17 r2c094d6  
    1010
    1111<sect4><title>cc, cc1, cc1plus, gcc</title>
    12 <para>These are the C compiler.  A compiler translates source code in
     12<para>These are the C compiler. A compiler translates source code in
    1313text format to a format that a computer understands. After a source code
    1414file is compiled into an object file, a linker will create an executable
     
    2222<para>The C++ language provides function overloading, which means that it is
    2323possible to write many functions with the same name (providing each takes
    24 parameters of different types).  All C++ function names are encoded into
     24parameters of different types). All C++ function names are encoded into
    2525a low-level assembly label (this process is known as mangling). The c++filt
    2626program does the inverse mapping: it decodes (demangles) low-level names
     
    6464
    6565<sect4><title>libstdc++</title>
    66 <para>libstdc++ is the C++ library.  It is used by C++ programs and contains
     66<para>libstdc++ is the C++ library. It is used by C++ programs and contains
    6767functions that are frequently used in C++ programs. This way the
    6868programmer doesn't have to write certain functions (such as writing a
  • appendixa/gettext-desc.xml

    rf5cc1c17 r2c094d6  
    1212
    1313<sect4><title>config.charset</title>
    14 <para>The config.charset script outputs a system dependent table of
     14<para>The config.charset script outputs a system-dependent table of
    1515character encoding aliases.</para></sect4>
    1616
    1717<sect4><title>config.rpath</title>
    18 <para>The config.rpath script outputs a system dependent set of variables,
     18<para>The config.rpath script outputs a system-dependent set of variables,
    1919describing how to set the run time search path of shared libraries in an
    2020executable.</para></sect4>
     
    2424i18n) and for localization (also known as l10n). Programs can be
    2525compiled with Native Language Support (NLS) which enable them to output
    26 messages in the users native language rather than in the default English
     26messages in the user's native language rather than in the default English
    2727language.</para></sect4>
    2828
     
    3737<sect4><title>msgattrib</title>
    3838<para>The msgattrib program filters the messages of a translation catalog
    39 according to their attributes, and manipulates the attributes.</para></sect4>
     39according to their attributes and manipulates the attributes.</para></sect4>
    4040
    4141<sect4><title>msgcat</title>
  • appendixa/glibc-desc.xml

    rf5cc1c17 r2c094d6  
    7373<para>pt_chown sets the owner, group and access permission of the
    7474slave pseudo terminal corresponding to the master pseudo terminal passed
    75 on file descriptor `3'.  This is the helper program for the `grantpt'
    76 function.  It is not intended to be run directly from the command
     75on file descriptor `3'. This is the helper program for the `grantpt'
     76function. It is not intended to be run directly from the command
    7777line.</para></sect4>
    7878
     
    8484
    8585<sect4><title>sln</title>
    86 <para>sln symbolically links dest to source.  It is statically linked,
    87 needing no dynamic linking at all.  Thus sln is useful to make symbolic
     86<para>sln symbolically links dest to source. It is statically linked,
     87needing no dynamic linking at all. Thus sln is useful to make symbolic
    8888links to dynamic libraries if the dynamic linking system for some reason
    8989is nonfunctional.</para></sect4>
     
    140140
    141141<sect4><title>libc, libc_nonshared, libc_p</title>
    142 <para>These files constitute the main C library.  The C library is a
     142<para>These files constitute the main C library. The C library is a
    143143collection of commonly used functions in programs.
    144144This way a programmer doesn't need to create his own functions for every
     
    150150library, the code from the C library is copied into the executable file.
    151151When a program uses a dynamic library, the executable will not
    152 contain the code from the C library, but  instead a routine that loads
     152contain the code from the C library, but instead a routine that loads
    153153the functions from the library at the time the program is run. This
    154154means a significant decrease in the file size of a program. The
  • appendixa/groff-desc.xml

    rf5cc1c17 r2c094d6  
    5454<sect4><title>grotty</title>
    5555<para>grotty translates the output of GNU troff into a form suitable for
    56 typewriter-like  devices.</para></sect4>
     56typewriter-like devices.</para></sect4>
    5757
    5858<sect4><title>gtbl</title>
     
    6060
    6161<sect4><title>hpftodit</title>
    62 <para>hpftodit creates a font file for use with groff -Tlj4 from an  HP
     62<para>hpftodit creates a font file for use with groff -Tlj4 from an HP
    6363tagged font metric file.</para></sect4>
    6464
     
    7575<para>lookbib prints a prompt on the standard error (unless the standard input
    7676is not a terminal), reads from the standard input a line containing a set
    77 of keywords, searches the bibliographic databases in a specified file for 
     77of keywords, searches the bibliographic databases in a specified file for
    7878references containing those keywords, prints any references found on the
    79 standard output, and repeats this process until the end of input.</para></sect4>
     79standard output and repeats this process until the end of input.</para></sect4>
    8080
    8181<sect4><title>mmroff</title>
     
    9494<sect4><title>pic</title>
    9595<para>pic compiles descriptions of pictures embedded within troff or TeX input
    96 files into commands that are understood by TeX or  troff.</para></sect4>
     96files into commands that are understood by TeX or troff.</para></sect4>
    9797
    9898<sect4><title>pre-grohtml and post-grohtml</title>
     
    103103<para>refer copies the contents of a file to the standard output, except that
    104104lines between .[ and .] are interpreted as citations, and lines between .R1
    105 and  .R2  are interpreted as commands about how citations are to be
     105and .R2 are interpreted as commands about how citations are to be
    106106processed.</para></sect4>
    107107
    108108<sect4><title>soelim</title>
    109109<para>soelim reads files and replaces lines of the form
    110 <emphasis>.so file</emphasis> by  the contents of
     110<emphasis>.so file</emphasis> by the contents of
    111111<emphasis>file</emphasis>.</para></sect4>
    112112
    113113<sect4><title>tbl</title>
    114114<para>tbl compiles descriptions of tables embedded within troff input files
    115 into commands that are understood  by troff.</para></sect4>
     115into commands that are understood by troff.</para></sect4>
    116116
    117117<sect4><title>tfmtodit</title>
  • appendixa/gzip-desc.xml

    rf5cc1c17 r2c094d6  
    2424
    2525<sect4><title>zcat</title>
    26 <para>zcat uncompresses either a list of files on the command line or a
    27 file being read from its standard input. Then, that uncompressed data is
    28 written to standard output.</para></sect4>
     26<para>zcat uncompresses, and writes to standard output, either a list of files
     27on the command line or a file being read from standard input.</para></sect4>
    2928
    3029<sect4><title>zcmp</title>
     
    3635<sect4><title>zforce</title>
    3736<para>zforce forces a .gz extension on all gzip files so that gzip will not
    38 compress them twice.  This can be useful for files with names truncated
     37compress them twice. This can be useful for files with names truncated
    3938after a file transfer.</para></sect4>
    4039
     
    4443<sect4><title>zmore</title>
    4544<para>zmore is a filter which allows examination of compressed or plain text
    46 files one screen at a time on a soft-copy terminal (similar to the
     45files, one screen at a time on a soft-copy terminal (similar to the
    4746more program).</para></sect4>
    4847
  • appendixa/introduction.xml

    rf5cc1c17 r2c094d6  
    2929packages than about others. If you think anything should be added to the
    3030following descriptions, please don't hesitate to email the mailing
    31 lists.  We intend that the list should contain an in-depth description
     31lists. We intend that the list should contain an in-depth description
    3232of every package installed, but we can't do it without help.</para>
    3333
    3434<para>Please note that currently only what a package does is described and not
    35 why it needs to be installed.  This may be added later.</para>
     35why it needs to be installed. This may be added later.</para>
    3636
    3737<para>Also listed are all of the installation dependencies for all the
  • appendixa/kbd-desc.xml

    rf5cc1c17 r2c094d6  
    6969<sect4><title>setleds</title>
    7070<para>setleds sets the keyboard LEDs. Many people find it useful to have numlock
    71 enabled by default, and it is by using this program that you can
     71enabled by default and, by using this program, you can
    7272achieve this.</para></sect4>
    7373
     
    8484<sect4><title>showfont</title>
    8585<para>showfont displays data about a font. The information shown includes font
    86 information, font properties, character metrics, and
     86information, font properties, character metrics and
    8787character bitmaps.</para></sect4>
    8888
  • appendixa/kernel-desc.xml

    rf5cc1c17 r2c094d6  
    1919<sect4><title>linux kernel headers</title>
    2020<para>These are the files we copy to
    21 <filename>/usr/include/{linux,asm}</filename> in Chapter 5.  They should
     21<filename>/usr/include/{linux,asm}</filename> in Chapter 5. They should
    2222match those which glibc was compiled against and therefore should
    2323<emphasis>not</emphasis> be replaced when upgrading the kernel. They are
  • appendixa/less-desc.xml

    rf5cc1c17 r2c094d6  
    1010<sect4><title>less</title>
    1111<para>The less program is a file pager (or text viewer). It
    12 displays the contents of a file with the ability to scroll. Less is an
     12displays the contents of a file and has the ability to scroll. Less is an
    1313improvement on the common pager called <quote>more</quote>. Less has
    1414the ability to scroll backwards through files as well and it doesn't need
  • appendixa/libtool-desc.xml

    rf5cc1c17 r2c094d6  
    2525
    2626<sect4><title>libltdl, libltdl.so.3, libltdl.so.3.1.0</title>
    27 <para>A small library that aims at hiding from programmers
     27<para>A small library that aims at hiding, from programmers,
    2828the various difficulties of dlopening libraries.</para></sect4>
    2929
  • appendixa/m4-desc.xml

    rf5cc1c17 r2c094d6  
    99
    1010<sect4><title>m4</title>
    11 <para>m4 is a macro processor. It copies input to output expanding macros as it
     11<para>m4 is a macro processor. It copies input to output, expanding macros as it
    1212goes. Macros are either built-in or user-defined and can take any number
    1313of arguments. Besides just doing macro expansion, m4 has built-in functions
  • appendixa/man-desc.xml

    rf5cc1c17 r2c094d6  
    1010
    1111<sect4><title>apropos</title>
    12 <para>apropos searches a set of database files containing short descriptions
    13 of system commands for keywords and displays the result on the standard
     12<para>apropos searches for keywords in a set of database files, containing
     13short descriptions of system commands, and displays the result on the standard
    1414output.</para></sect4>
    1515
     
    1717<para>makewhatis reads all the manual pages contained in given sections of
    1818manpath or the pre-formatted pages contained in the given sections of
    19 catpath. For  each  page, it writes a line in the whatis database; each
    20 line consists of the name of the page  and  a  short description,
    21 separated  by a dash. The description is extracted using the content of
     19catpath. For each page, it writes a line in the whatis database. Each
     20line consists of the name of the page and a short description,
     21separated by a dash. The description is extracted using the content of
    2222the NAME section of the manual page.</para></sect4>
    2323
     
    3232
    3333<sect4><title>whatis</title>
    34 <para>whatis searches a set of database files containing short descriptions
    35 of system commands for keywords and displays the result on the standard
     34<para>
     35whatis searches for keywords in a set of database files, containing short
     36descriptions of system commands, and displays the result on the standard
    3637output. Only complete word matches are displayed.</para></sect4>
    3738
  • appendixa/modutils-desc.xml

    rf5cc1c17 r2c094d6  
    1515
    1616<sect4><title>genksyms</title>
    17 <para>genksyms reads (on standard input) the output from gcc  -E source.c
     17<para>genksyms reads (on standard input) the output from gcc -E source.c
    1818and generates a file containing version information.</para></sect4>
    1919
     
    4040<sect4><title>modinfo</title>
    4141<para>modinfo examines an object file associated with a kernel module and
    42 displays any  information that it can glean.</para></sect4>
     42displays any information that it can glean.</para></sect4>
    4343
    4444<sect4><title>modprobe</title>
  • appendixa/ncurses-desc.xml

    rf5cc1c17 r2c094d6  
    1414
    1515<sect4><title>clear</title>
    16 <para>clear clears the screen if this is possible.  It looks in
     16<para>clear clears the screen if this is possible. It looks in
    1717the environment for the terminal type and then in the terminfo database
    1818to figure out how to clear the screen.</para></sect4>
     
    2121<para>infocmp can be used to compare a binary terminfo entry with
    2222other terminfo entries, rewrite a terminfo description to
    23 take advantage of the use=  terminfo field, or print  out  a 
    24 terminfo  description from the binary file (term) in a variety of
     23take advantage of the use= terminfo field, or print out a
     24terminfo description from the binary file (term) in a variety of
    2525formats (the opposite of what tic does).</para></sect4>
    2626
     
    3131<sect4><title>reset</title>
    3232<para>reset sets cooked and echo modes, turns off cbreak and raw modes,
    33 turns on new-line translation  and resets any unset special characters to
     33turns on new-line translation and resets any unset special characters to
    3434their default values before doing terminal initialization the same way
    3535as tset.</para></sect4>
  • appendixa/nettools-desc.xml

    rf5cc1c17 r2c094d6  
    3737<sect4><title>netstat</title>
    3838<para>netstat is a multi-purpose tool used to print the network connections,
    39 routing tables, interface statistics, masquerade connections, and multicast
     39routing tables, interface statistics, masquerade connections and multicast
    4040memberships.</para></sect4>
    4141
  • appendixa/perl-desc.xml

    rf5cc1c17 r2c094d6  
    2929
    3030<sect4><title>perl, perl5.6.1</title>
    31 <para>perl is the Practical Extraction and Report Language.  It combines
    32 some of the best features of C, sed, awk, and sh into one powerful
     31<para>perl is the Practical Extraction and Report Language. It combines
     32some of the best features of C, sed, awk and sh into one powerful
    3333language.</para></sect4>
    3434
     
    4242<sect4><title>perldoc</title>
    4343<para>perldoc looks up a piece of documentation in .pod format that is
    44 embedded in the perl installation tree or in a perl script, and displays it
     44embedded in the perl installation tree or in a perl script and displays it
    4545via "pod2man | nroff -man | $PAGER".</para></sect4>
    4646
  • appendixa/shadowpwd-desc.xml

    rf5cc1c17 r2c094d6  
    66<para>chage, chfn, chpasswd, chsh, dpasswd, expiry, faillog, gpasswd,
    77groupadd, groupdel, groupmod, groups, grpck, grpconv, grpunconv, lastlog,
    8 login,  logoutd, mkpasswd, newgrp, newusers, passwd, pwck, pwconv, pwunconv,
     8login, logoutd, mkpasswd, newgrp, newusers, passwd, pwck, pwconv, pwunconv,
    99sg (link to newgrp), useradd, userdel, usermod, vigr (link to vipw) and
    1010vipw</para></sect3>
     
    2727
    2828<sect4><title>chsh</title>
    29 <para>chsh  changes the user login shell.</para></sect4>
     29<para>chsh changes the user login shell.</para></sect4>
    3030
    3131<sect4><title>dpasswd</title>
     
    129129<para>vipw and vigr will edit the files /etc/passwd and /etc/group,
    130130respectively. With the -s flag, they will edit the shadow versions of
    131 those files, /etc/shadow  and /etc/gshadow, respectively.</para></sect4>
     131those files, /etc/shadow and /etc/gshadow, respectively.</para></sect4>
    132132
    133133</sect3>
  • appendixa/shellutils-desc.xml

    rf5cc1c17 r2c094d6  
    4343
    4444<sect4><title>groups</title>
    45 <para>groups prints the groups a user is in.</para></sect4>
     45<para>groups prints a user's group memberships.</para></sect4>
    4646
    4747<sect4><title>hostid</title>
     
    6161<sect4><title>nohup</title>
    6262<para>nohup runs a command immune to hangups, with output to a
    63 non-tty.</para></sect4>
     63log file.</para></sect4>
    6464
    6565<sect4><title>pathchk</title>
     
    7474
    7575<sect4><title>printf</title>
    76 <para>printf formats and prints data (the same as the printf C
     76<para>printf formats and prints data (the same as the C printf
    7777function).</para></sect4>
    7878
  • appendixa/sysvinit-desc.xml

    rf5cc1c17 r2c094d6  
    2020<sect4><title>init</title>
    2121<para>init is the parent of all processes. Its primary role is to create
    22 processes from  a  script  stored  in  the  file /etc/inittab. This 
     22processes from a script stored in the file /etc/inittab. This
    2323file usually has entries which cause init to spawn gettys on each line that
    2424users can log in. It also controls autonomous processes required by any
     
    3232<sect4><title>last</title>
    3333<para>last searches back through the file /var/log/wtmp (or the file designated
    34 by the -f flag) and displays a list of all users logged in (and  out)
     34by the -f flag) and displays a list of all users logged in (and out)
    3535since that file was created.</para></sect4>
    3636
     
    5959<para>runlevel reads the system utmp file (typically /var/run/utmp) to locate
    6060the runlevel record, and then prints the previous and current system
    61 runlevel on its standard  output, separated by a single space.</para></sect4>
     61runlevel on its standard output, separated by a single space.</para></sect4>
    6262
    6363<sect4><title>shutdown</title>
  • appendixa/texinfo-desc.xml

    rf5cc1c17 r2c094d6  
    1212<para>The info program reads Info documents, usually contained in the
    1313/usr/share/info directory. Info documents are like man(ual) pages, but
    14 they tend to be more in depth than just explaining the options to a
     14they tend to go deeper than just explaining the options to a
    1515program.</para></sect4>
    1616
     
    2323program is run, a list with available topics (ie: available info documents)
    2424will be presented. The install-info program is used to maintain this list of
    25 available topics. If info files are removed manually, it is also necessary
    26 to delete the topic in the index file as well. This program is used for
     25available topics. If info files are removed manually, you must also delete
     26the topic in the index file. This program is used for
    2727that. It also works the other way around when info documents are
    2828added.</para></sect4>
     
    3030<sect4><title>makeinfo</title>
    3131<para>The makeinfo program translates Texinfo source documents into various
    32 formats.  Available formats are: info files, plain text and HTML.</para></sect4>
     32formats. Available formats are: info files, plain text and HTML.</para></sect4>
    3333
    3434<sect4><title>texi2dvi</title>
  • appendixa/textutils-desc.xml

    rf5cc1c17 r2c094d6  
    2222
    2323<sect4><title>csplit</title>
    24 <para>csplit outputs pieces of a file separated  by (a) pattern(s) to files
     24<para>csplit outputs pieces of a file separated by (a) pattern(s) to files
    2525xx01, xx02, ..., and outputs byte counts of each piece to standard
    2626output.</para></sect4>
     
    3131
    3232<sect4><title>expand</title>
    33 <para>expand converts  tabs in files to spaces, writing to standard
     33<para>expand converts tabs in files to spaces, writing to standard
    3434output.</para></sect4>
    3535
     
    107107
    108108<sect4><title>wc</title>
    109 <para>wc prints line, word, and byte counts for each specified file, and a
    110 total line if more than one file is specified.</para></sect4>
     109<para>wc prints line, word and byte counts for each specified file and a
     110total line, if more than one file is specified.</para></sect4>
    111111
    112112</sect3>
  • chapter01/blfssupport.xml

    rf5cc1c17 r2c094d6  
    33
    44<para>The blfs-support list handles support requests for any software
    5 that is not built or installed in the LFS book.  Any software beyond what is
     5that is not built or installed in the LFS book. Any software beyond what is
    66installed as part of the base LFS system can be discussed here.</para>
    77
  • chapter01/changelog.xml

    rf5cc1c17 r2c094d6  
    6060</para></listitem>
    6161
     62<listitem><para>September 28th, 2002 [timothy]: Applied Bill Maltby's
     63grammatic-fixes patch. Changed "$LFS" to "LFS" when speaking of the LFS
     64environment variable.</para></listitem>
     65
    6266<listitem><para>September 23rd, 2002 [timothy]: Applied Bill Maltby's
    6367grammatic-related patches.</para></listitem>
  • chapter01/conventions.xml

    rf5cc1c17 r2c094d6  
    44
    55<para>To make things easy to follow, there are a number of conventions used
    6 throughout the book.  Following are some examples:</para>
     6throughout the book. Following are some examples:</para>
    77
    88<para><userinput>./configure --prefix=/usr</userinput></para>
    99
    1010<blockquote><para>This form of text is designed to be typed exactly
    11 as seen unless otherwise noted in the surrounding text.  It is also used
     11as seen unless otherwise noted in the surrounding text. It is also used
    1212in the explanation sections to identify which of the commands is being
    1313referenced.</para></blockquote>
     
    4141
    4242<blockquote><para>This type of section is used mainly when creating
    43 configuration files.  The first command (in bold) tells the system to create
     43configuration files. The first command (in bold) tells the system to create
    4444the file $LFS/etc/group from whatever is typed on the following lines until
    4545the sequence EOF is encountered. Therefore, this whole section is generally
  • chapter01/lfssupport.xml

    rf5cc1c17 r2c094d6  
    33
    44<para>The lfs-support mailing list provides support to users building an
    5 LFS system as far as the end of the main book.  Requests for help with
     5LFS system as far as the end of the main book. Requests for help with
    66installing software beyond the base system should go to the blfs-support
    77list.</para>
  • chapter01/unsubscribe.xml

    rf5cc1c17 r2c094d6  
    1919unsubscribe alfs-discuss</literallayout></blockquote>
    2020
    21 <para>After the email is sent, the Listar program will reply with an 
     21<para>After the email is sent, the Listar program will reply with an
    2222email requesting a confirmation of the unsubscription
    2323request. After this confirmation email is sent back, Listar will
  • chapter02/aboutlfs.xml

    rf5cc1c17 r2c094d6  
    44
    55<para>Please read the following carefully: throughout this book
    6 the variable $LFS will be used frequently. $LFS must at all times be
     6the variable LFS will be used frequently. $LFS must at all times be
    77replaced with the directory where the partition that contains the LFS system
    88is mounted. How to create and where to mount the partition will be
     
    2929command).</para>
    3030
    31 <para>If you plan to use $LFS, do not forget to set the $LFS variable at all
     31<para>If you plan to use $LFS, do not forget to set the LFS variable at all
    3232times. If the variable is not set and is used in a command, $LFS will
    3333be ignored and whatever is left will be executed. A command like
    3434<userinput>echo "root:x:0:0:root:/root:/bin/bash" &gt;
    35 $LFS/etc/passwd</userinput> without the $LFS variable set will
     35$LFS/etc/passwd</userinput> without the LFS variable set will
    3636re-create your host system's /etc/passwd file. Simply put: it will
    3737destroy your current password database file.</para>
     
    4040the /root/.bash_profile and /root/.bashrc files so that every time
    4141you login as user root, or you <userinput>su</userinput> to user root,
    42 the $LFS variable is set.</para>
     42the LFS variable is set.</para>
    4343
    4444</sect1>
  • chapter02/askforhelp.xml

    rf5cc1c17 r2c094d6  
    2525
    2626<para>(Note that saying that you've deviated from the book doesn't mean
    27 that we won't help you.  After all, LFS is about choice. It'll just
     27that we won't help you. After all, LFS is about choice. It'll just
    2828help us to see other possible causes of your problem.)</para>
    2929
     
    4646<para>To help us find the cause of the problem, both screen output and
    4747the contents of various files are useful. The screen output from both
    48 the ./configure script and the make run can be useful.  Don't blindly
     48the ./configure script and the make run can be useful. Don't blindly
    4949include the whole thing but on the other hand, don't include too little.
    5050As an example, here is some screen output from make:</para>
    5151
    52 <para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" 
    53 -DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\" 
    54 -DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.   
     52<para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
     53-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\"
     54-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
    5555-g -O2 -c getopt1.c
    56 gcc  -g -O2 -static -o make  ar.o arscan.o commands.o dir.o expand.o file.o
    57 function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o 
    58 signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o   
     56gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o
     57function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o
     58signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o
    5959-lutil job.o: In function `load_too_high':
    6060/lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg'
     
    6767
    6868<para>In this case, many people just include the bottom section where it
    69 says <screen>make [2]: *** [make] Error 1</screen> and onwards.  This
     69says <screen>make [2]: *** [make] Error 1</screen> and onwards. This
    7070isn't enough for us to diagnose the problem because it only tells us
    7171that <emphasis>something</emphasis> went wrong, not
    72 <emphasis>what</emphasis> went wrong.  The whole section, as
     72<emphasis>what</emphasis> went wrong. The whole section, as
    7373in the example above, is what should be included to be helpful, because it
    7474includes the command that was executed and the command's error
     
    7676
    7777<para>An excellent article on asking for help on the Internet in general
    78 has been written by Eric S. Raymond.  It is available online at <ulink
     78has been written by Eric S. Raymond. It is available online at <ulink
    7979url="http://www.tuxedo.org/~esr/faqs/smart-questions.html"/>.
    8080Read and follow the hints in that document and you are much more likely
  • chapter02/install.xml

    rf5cc1c17 r2c094d6  
    44
    55<para>Before you start using the LFS book, we should point out that all
    6 of the commands here assume that you are using the bash shell.  If you
    7 aren't, the commands may work, but we can't guarantee it.  If you want a
     6of the commands here assume that you are using the bash shell. If you
     7aren't, the commands may work, but we can't guarantee it. If you want a
    88simple life, use bash.</para>
    99
     
    3232
    3333<para>Nowadays most tar programs, but not all, are
    34 patched to be able to use bzip2 files directly.  They use either
     34patched to be able to use bzip2 files directly. They use either
    3535the -I, the -y, or the -j parameter, which work the same as the -z
    3636parameter for handling gzip files. The above construction, however,
     
    7777<para>There is one exception; the kernel source tree. Keep it around as you
    7878will need it later in this book when building a kernel. Nothing before then
    79 will use the kernel tree, so the source tree won't be in your way.  If,
     79will use the kernel tree, so the source tree won't be in your way. If,
    8080however, you are short of disk space, you can remove the kernel tree and
    8181re-untar it later when required.</para>
  • chapter02/platform.xml

    rf5cc1c17 r2c094d6  
    66said that, the main LFS development work occurs on the x86 platform. We
    77attempt to include information where possible on differences for other
    8 platforms such as PPC.  If you come across a problem compiling which is
     8platforms such as PPC. If you come across a problem compiling which is
    99not related to the x86 platform, still feel free to ask for help on the
    10 mailing lists.  Even better, if you come up with a solution to a
     10mailing lists. Even better, if you come up with a solution to a
    1111particular problem related to one of the other platforms, please let us
    12 know at the lfs-dev mailing list.  We will then (subject to confirming
     12know at the lfs-dev mailing list. We will then (subject to confirming
    1313it works) include that in the book.</para>
    1414
  • chapter03/mounting.xml

    rf5cc1c17 r2c094d6  
    2020<para>Replace <quote>xxx</quote> by the partition's designation (like hda11).</para>
    2121
    22 <para>This directory (/mnt/lfs) is the $LFS variable you have read about
    23 back in Chapter 2. If you were planning to make use of the $LFS environment
     22<para>This directory (/mnt/lfs) is the LFS variable you have read about
     23back in Chapter 2. If you were planning to make use of the LFS environment
    2424variable, <userinput>export LFS=/mnt/lfs</userinput> has to be executed
    2525now.</para>
  • chapter05/binutils-inst.xml

    rf5cc1c17 r2c094d6  
    44<para>This package is known to behave badly when you have changed its default
    55optimization flags (including the -march and -mcpu options). Binutils is
    6 best left alone.  Therefore, if you have defined any environment variables
     6best left alone. Therefore, if you have defined any environment variables
    77that override default optimizations, such as CFLAGS and CXXFLAGS, we
    8 recommend unsetting or modifying them when building binutils.  You have been
     8recommend unsetting or modifying them when building binutils. You have been
    99warned.</para>
    1010
  • chapter05/gcc-exp.xml

    rf5cc1c17 r2c094d6  
    77<ulink url="http://www.zipworld.com.au/~gschafer/lfs-tweaks.html"/>.</para>
    88
    9 <para><userinput>--prefix=/static:</userinput> This is NOT a typo.  GCC hard
     9<para><userinput>--prefix=/static:</userinput> This is NOT a typo. GCC hard
    1010codes some paths while compiling and so we need to pass /static as the
    11 prefix during ./configure.  We pass the real install prefix during the
     11prefix during ./configure. We pass the real install prefix during the
    1212make install command later.</para>
    1313
  • chapter05/gcc-inst.xml

    rf5cc1c17 r2c094d6  
    88<para>This package is known to behave badly when you have changed its
    99default optimization flags (including the -march and -mcpu options). GCC is
    10 best left alone.  Therefore, if you have defined any environment variables
     10best left alone. Therefore, if you have defined any environment variables
    1111that override default optimizations, such as CFLAGS and CXXFLAGS, we
    12 recommend unsetting or modifying them when building GCC.  You have
     12recommend unsetting or modifying them when building GCC. You have
    1313been warned.</para>
    1414
  • chapter05/patch-exp.xml

    rf5cc1c17 r2c094d6  
    44<para><userinput>CPPFLAGS=-D_GNU_SOURCE: </userinput>
    55This flag fixes installation problems of this package on PPC and m68k
    6 platforms (that we know of).  It doesn't hurt compilation on other
     6platforms (that we know of). It doesn't hurt compilation on other
    77platforms, such as x86, so we do it by default.</para>
    88
  • chapter05/whystatic.xml

    rf5cc1c17 r2c094d6  
    3030that we only need one copy of the library. If <filename>ls</filename> and
    3131<filename>rm</filename> both use the same library, then we don't need two
    32 copies of the library, as they can both get the code from the same file. 
     32copies of the library, as they can both get the code from the same file.
    3333Even when in memory, the two programs share the same code, rather than loading
    3434duplicates into memory. So not only are we saving hard disk space, but also
     
    3636
    3737<para>If dynamic linking saves so much room, then why are we making everything
    38 statically linked?  Well, that's because when you chroot into your brand new
     38statically linked? Well, that's because when you chroot into your brand new
    3939(but very incomplete) LFS environment, these dynamic libraries won't be
    4040available because they are somewhere else in your old directory tree
     
    5353
    5454<para>And there you have it, that's why you need to use those weird
    55 <userinput>-static</userinput> flags.  If you try building everything
     55<userinput>-static</userinput> flags. If you try building everything
    5656without them, you'll see very quickly what
    5757happens when you chroot into your newly crippled LFS system.</para>
  • chapter06/aboutdebug.xml

    rf5cc1c17 r2c094d6  
    33<?dbhtml filename="aboutdebug.html" dir="chapter06"?>
    44
    5 <para>Most programs and libraries are by default compiled with debugging
     5<para>Most programs and libraries are, by default, compiled with debugging
    66symbols included (with gcc option -g).</para>
    77
     
    4444<para>For your convenience, Chapter 9 includes one simple command to strip
    4545all debugging symbols from all programs and libraries on your system.
    46 Additional information on optimization you can find in the hint at
     46Additional information on optimization can be found in the hint at
    4747<ulink url="&hints-root;optimization.txt"/>.</para>
    4848
  • chapter06/binutils-exp.xml

    rf5cc1c17 r2c094d6  
    33
    44<para><userinput>tooldir=/usr:</userinput> Normally, the tooldir (the
    5 directory where the executables from binutils end up in) is set to
     5directory where the executables from binutils end up) is set to
    66$(exec_prefix)/$(target_alias) which expands into, for example,
    77/usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
  • chapter06/binutils-inst.xml

    rf5cc1c17 r2c094d6  
    33<para>This package is known to behave badly when you have changed its
    44default optimization flags (including the -march and -mcpu options). Binutils
    5 is best left alone.  Therefore, if you have defined any environment variables
     5is best left alone. Therefore, if you have defined any environment variables
    66that override default optimizations, such as CFLAGS and CXXFLAGS, we
    7 recommend unsetting or modifying them when building binutils.  You have
     7recommend unsetting or modifying them when building binutils. You have
    88been warned.</para>
    99
  • chapter06/bzip2-exp.xml

    rf5cc1c17 r2c094d6  
    44<para><userinput>make -f Makefile-libbz2_so:</userinput> This will cause bzip2
    55to be built using a different Makefile file, in this case the
    6 Makefile-libbz2_so file which creates a dynamic libbz2.so library and
     6Makefile-libbz2_so file, which creates a dynamic libbz2.so library and
    77links the bzip2 utilities against it.</para>
    88
  • chapter06/bzip2-inst.xml

    rf5cc1c17 r2c094d6  
    1717ln -s bzip2 /bin/bzcat</userinput></screen></para>
    1818
    19 <para>Although it's not strictly a part of a basic LFS system it's worth
     19<para>Although it's not strictly a part of a basic LFS system, it's worth
    2020mentioning that a patch for Tar can be downloaded which enables the tar
    2121program to compress and uncompress using bzip2/bunzip2 easily. With a
  • chapter06/chroot.xml

    rf5cc1c17 r2c094d6  
    11<sect1 id="ch06-chroot">
    2 <title>Entering the chroot'ed environment</title>
     2<title>Entering the chroot environment</title>
    33<?dbhtml filename="chroot.html" dir="chapter06"?>
    44
    5 <para>It is time to enter the chroot'ed environment in order to begin installing
     5<para>It is time to enter the chroot environment in order to begin installing
    66the packages we need. Before you can chroot, however, you need to become
    77<emphasis>root</emphasis>, since only <emphasis>root</emphasis>
     
    99
    1010<para>Become <emphasis>root</emphasis> and run the following command
    11 to enter the chroot'ed environment:</para>
     11to enter the chroot environment:</para>
    1212
    1313<para><screen><userinput>chroot $LFS /static/bin/env -i \
     
    1818
    1919<para>The <userinput>-i</userinput> option given to the
    20 <userinput>env</userinput> command will clear all variables of the chroot'ed
     20<userinput>env</userinput> command will clear all variables of the chroot
    2121environment. After that, only the HOME, TERM, PS1 and PATH variables are
    2222set again. The TERM=$TERM construct will set the TERM variable inside chroot
     
    2525such as CFLAGS or CXXFLAGS, this is a good place to set them again.</para>
    2626
    27 <para>From this point on there's no need anymore to use the $LFS variable,
     27<para>From this point on there's no need anymore to use the LFS variable,
    2828because everything you do will be restricted to the LFS file system -- since
    2929what the shell thinks is <filename class="directory">/</filename> is actually
     
    3131
    3232<para>You have to make sure all the commands in the rest of this chapter and
    33 in the following chapters are run from within the chroot'ed environment.
     33in the following chapters are run from within the chroot environment.
    3434If you ever leave this environment for any reason (rebooting for example),
    3535you must remember to again enter chroot and mount proc (discussed later)
  • chapter06/creatingdirs.xml

    rf5cc1c17 r2c094d6  
    33<?dbhtml filename="creatingdirs.html" dir="chapter06"?>
    44
    5 <para>Let's now create some structure in our LFS file system, let's create
     5<para>Let's now create some structure in our LFS file system. Let's create
    66a directory tree. Issuing the following commands will create a more or less
    77standard tree:</para>
     
    2323ln -s ../var/tmp /usr</userinput></screen></para>
    2424
    25 <para>Directories are by default created with permission mode 755, but this
     25<para>Directories are, by default, created with permission mode 755, but this
    2626isn't desirable for all directories. We will make two changes: one to the home
    2727directory of root, and another to the directories for temporary files.</para>
     
    3232<para>The first mode change ensures that not just everybody can enter the
    3333<filename class="directory">/root</filename> directory -- the same
    34 a normal user would do with his or her home directory.
     34as a normal user would do with his or her home directory.
    3535The second mode change makes sure that any user can write to the
    3636<filename class="directory">/tmp</filename> and
    3737<filename class="directory">/var/tmp</filename> directories, but
    38 cannot remove other users's files from them. The latter is prohibited
     38cannot remove other users' files from them. The latter is prohibited
    3939by the so-called "sticky bit" -- the highest bit in the 1777 bit mask.</para>
    4040
     
    5454much like these for a base system. However, feel free to make your system
    5555FHS-compliant. As to the structure of the
    56 <filename class="directory">/usr/local/share</filename> subdirectory the FHS
     56<filename class="directory">/usr/local/share</filename> subdirectory, the FHS
    5757isn't precise, so we created here the directories that we think are needed.</para>
    5858
  • chapter06/e2fsprogs-exp.xml

    rf5cc1c17 r2c094d6  
    55reason for supplying this option is because of the setup of the
    66e2fsprogs Makefile. Some programs are essential for system use when,
    7 for example, /usr isn't mounted (like the e2fsck program).  These
    8 programs and libraries therefore belong in directories like /lib and
     7for example, /usr isn't mounted (like the e2fsck program). These
     8programs and libraries, therefore, belong in directories like /lib and
    99/sbin. If this option isn't passed to E2fsprogs's configure, it places
    10 these programs in /usr which is not what we want.</para>
     10these programs in /usr, which is not what we want.</para>
    1111
    1212<para><userinput>--enable-elf-shlibs:</userinput> This creates shared
  • chapter06/findutils-inst.xml

    rf5cc1c17 r2c094d6  
    1919<para>By default, the location of the updatedb database is in /usr/var.
    2020If you would rather be FHS compliant, you may wish to use another
    21 location.  The following commands use the database file
     21location. The following commands use the database file
    2222<filename>/var/lib/misc/locatedb</filename> which is FHS compliant.</para>
    2323
  • chapter06/gcc-inst.xml

    rf5cc1c17 r2c094d6  
    88<para>This package is known to behave badly when you have changed its
    99default optimization flags (including the -march and -mcpu options). GCC is
    10 best left alone.  Therefore, if you have defined any environment variables
     10best left alone. Therefore, if you have defined any environment variables
    1111that override default optimizations, such as CFLAGS and CXXFLAGS, we
    12 recommend unsetting or modifying them when building Gcc.  You have
     12recommend unsetting or modifying them when building Gcc. You have
    1313been warned.</para>
    1414
  • chapter06/glibc-exp.xml

    rf5cc1c17 r2c094d6  
    3131
    3232<para><userinput>--enable-add-ons:</userinput> This enables the add-on that
    33 we install with Glibc: linuxthreads</para>
     33we install with Glibc, linuxthreads</para>
    3434
    3535<para><userinput>--libexecdir=/usr/bin:</userinput> This will cause the
  • chapter06/glibc-inst.xml

    rf5cc1c17 r2c094d6  
    1313<para>This package is known to behave badly when you have changed its
    1414default optimization flags (including the -march and -mcpu options). Glibc
    15 is best left alone.  Therefore, if you have defined any environment variables
     15is best left alone. Therefore, if you have defined any environment variables
    1616that override default optimizations, such as CFLAGS and CXXFLAGS, we
    17 recommend unsetting or modifying them when building Glibc.  You have
     17recommend unsetting or modifying them when building Glibc. You have
    1818been warned.</para>
    1919
     
    4141<para>An alternative to running <userinput>make
    4242localedata/install-locales</userinput> is to only install those locales
    43 which you need or want.  This can be achieved using the localedef
    44 command.  Information on this can be found in the INSTALL
     43which you need or want. This can be achieved using the localedef
     44command. Information on this can be found in the INSTALL
    4545file in the glibc-&glibc-version; tree. One thing to note is that the
    4646<userinput>localedef</userinput> program assumes that the <filename
     
    5050<para>The Linux Threads man pages are not going to be installed at this
    5151point because it requires a working Perl installation. We'll install Perl
    52 later on in this chapter so we'll come back to the Linux Threads man page
     52later on in this chapter, so we'll come back to the Linux Threads man page
    5353installation after that.</para>
    5454
  • chapter06/groff-exp.xml

    rf5cc1c17 r2c094d6  
    33
    44<para><userinput>make PROCESSEDEXAMPLEFILES="":</userinput> Groff has a few
    5 extra dependencies that we don't install with LFS. This option disable the
     5extra dependencies that we don't install with LFS. This option disables the
    66need for those tools.</para>
    77
  • chapter06/introduction.xml

    rf5cc1c17 r2c094d6  
    44
    55<para>In this chapter we enter the building site, and start
    6 constructing our LFS system in earnest.  That is, we chroot into
     6constructing our LFS system in earnest. That is, we chroot into
    77our temporary mini Linux system, create some auxiliary things,
    88and then start installing all the packages, one by one.</para>
     
    2222may also cause compilation difficulties. If a package refuses
    2323to compile when using optimization, try to compile it without
    24 optimization and see if  the problem goes away.</para>
     24optimization and see if the problem goes away.</para>
    2525
    2626<para>The order in which packages are installed in this chapter has
     
    2828to <filename class="directory">/static</filename> hard-wired into it.
    2929For the same reason, <emphasis>do not </emphasis> compile packages
    30 in parallel.  Compiling in parallel may save you some time (especially on
     30in parallel. Compiling in parallel may save you some time (especially on
    3131dual-CPU machines), but it could result in a program containing a
    3232hard-wired path to <filename class="directory">/static</filename>,
  • chapter06/kbd-exp.xml

    rf5cc1c17 r2c094d6  
    44<para><userinput>patch -Np1 -i ../kbd-&kbd-patch-version;.patch</userinput>:
    55This patch fixes two problems. The first one is the <userinput>loadkeys -d</userinput>
    6 behaviour which is broken in current kbd versions. It is necessary to fix this,
     6behaviour, which is broken in current kbd versions. It is necessary to fix this,
    77because the boot scripts rely on a proper <userinput>loadkeys -d</userinput>.
    8 The second part of the patch changes a Makefile so some utilities (setlogcons,
    9 setvesablank and getunimap) that are not installed by default, are installed as
    10 well.</para>
     8The second part of the patch changes a Makefile so some utilities that are
     9not installed by default (setlogcons, setvesablank and getunimap) are also
     10installed.</para>
    1111
    1212</sect2>
  • chapter06/kernel-exp-headers.xml

    rf5cc1c17 r2c094d6  
    2727
    2828<para>The essential part is where Linus states that the header files should be
    29 <emphasis>the ones which glibc was compiled against</emphasis>.  These are
     29<emphasis>the ones which glibc was compiled against</emphasis>. These are
    3030the headers that should be used when you later compile other packages, as they
    3131are the ones that match the object-code library files. By copying the headers,
  • chapter06/kernel-exp.xml

    rf5cc1c17 r2c094d6  
    99<para><userinput>make mrproper</userinput>: This ensures that the kernel
    1010tree is absolutely clean. The kernel team recommends that this command be
    11 issued prior to <emphasis>each</emphasis> kernel compilation, and that you
     11issued prior to <emphasis>each</emphasis> kernel compilation and that you
    1212shouldn't rely on the source tree being clean after untarring.</para>
    1313
  • chapter06/lilo-inst.xml

    rf5cc1c17 r2c094d6  
    2222
    2323<para>The standard LILO prompt, or menu, may be replaced by the
    24 LFS logo, or any logo you like. Martin Imobersteg has written a
     24LFS logo or any logo you like. Martin Imobersteg has written a
    2525hint about this, which is located at
    2626<ulink url="&hints-root;bootlogo.txt"/>.</para>
  • chapter06/makedev-exp.xml

    rf5cc1c17 r2c094d6  
    55bunch of devices. Normally, these are all the devices you will need. But it
    66is possible that some special devices needed for your hardware configuration
    7 are missing. Create these with ./MAKEDEV -v &lt;device&gt;. 
     7are missing. Create these with ./MAKEDEV -v &lt;device&gt;.
    88The <userinput>generic-nopty</userinput> option mostly creates the same
    9 devices as <userinput>generic-nopty</userinput>, but skips those that aren't
     9devices as <userinput>generic</userinput>, but skips those that aren't
    1010needed if you are using devpts.</para>
    1111
  • chapter06/makedev-inst.xml

    rf5cc1c17 r2c094d6  
    22<title>Creating devices</title>
    33
    4 <para>(Note that unpacking the MAKEDEV-&makedev-version;.bz2 file doesn't create
    5 a directory for you to cd into, as the file only contains a script.)</para>
     4<para>Note that unpacking the MAKEDEV-&makedev-version;.bz2 file doesn't create
     5a directory for you to cd into, as the file only contains a script.</para>
    66
    77<para>Prepare for the creation of the device files by running the
  • chapter06/man-inst.xml

    rf5cc1c17 r2c094d6  
    1818
    1919<para>You may want to take a look at the man hint
    20 at <ulink url="&hints-root;man.txt"/> which deals with formatting
     20at <ulink url="&hints-root;man.txt"/>, which deals with formatting
    2121and compression issues for man pages.</para>
    2222
  • chapter06/mountproc.xml

    rf5cc1c17 r2c094d6  
    44
    55<para>In order for certain programs to function properly, the proc file
    6 system must be available within the chroot'ed environment.
     6system must be available within the chroot environment.
    77As a file system can be mounted as many times and in as many places
    88as you like, it's not a problem that the proc file system is already
     
    2222not enough memory</screen></blockquote>
    2323
    24 <para>Ignore these, they're just caused due to the fact that the system
     24<para>Ignore these, they're just due to the fact that the system
    2525isn't installed completely yet and some files are missing. The mount itself
    2626will be successful and that's all we care about at this point.</para>
  • chapter06/ncurses-exp.xml

    rf5cc1c17 r2c094d6  
    1010
    1111<para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
    12 executable.  Ncurses install routine doesn't set the permissions
     12executable. Ncurses's install routine doesn't set the permissions
    1313properly so we do it manually instead.</para>
    1414
    1515<para><userinput>ln -sf libncurses.a libcurses.a:</userinput> Some
    16 programs try to link using -lcurses instead of -lncurses.  This symlink
     16programs try to link using -lcurses instead of -lncurses. This symlink
    1717ensures that such programs will link without errors.</para>
    1818
  • chapter06/nettools-inst.xml

    rf5cc1c17 r2c094d6  
    1515<para>If you don't know what to answer to all the questions asked during
    1616the <userinput>make</userinput> phase, then just accept the defaults, which
    17 will be just in fine in the majority of the cases. What you are asked here
     17will be just fine in the majority of the cases. What you are asked here
    1818are a bunch of questions relating to the kind of network protocols that you
    1919have enabled in your kernel.</para>
  • chapter06/perl-inst.xml

    rf5cc1c17 r2c094d6  
    99
    1010<para>If you want more control over the way perl sets itself up to be
    11 build, you can run the interactive <userinput>Configure</userinput> script
     11built, you can run the interactive <userinput>Configure</userinput> script
    1212and modify the way perl is built. If you think you can live with the
    1313(sensible) defaults perl auto-detects, then just use the commands listed
  • chapter06/pwdgroup.xml

    rf5cc1c17 r2c094d6  
    3636<para>The created groups aren't part of any standard -- they are the groups
    3737that the MAKEDEV script in the next section uses.
    38 Besides the group "root", the LSB recommends only a group "bin" with a GID
    39 of 1 to be present. All other group names and GIDs can be chosen freely by
     38Besides the group "root", the LSB recommends only a group "bin", with a GID
     39of 1, be present. All other group names and GIDs can be chosen freely by
    4040the user, as well-written packages don't depend on GID numbers but use the
    4141group's name.</para>
  • chapter07/hostname.xml

    rf5cc1c17 r2c094d6  
    1212
    1313<para><quote>lfs</quote> needs to be replaced with the name the computer is
    14 to be called.  You should not enter the FQDN (Fully Qualified Domain
     14to be called. You should not enter the FQDN (Fully Qualified Domain
    1515Name) here. That information will be put in the
    1616<filename>/etc/hosts</filename> file later on.</para>
Note: See TracChangeset for help on using the changeset viewer.