Changeset 2c094d6
- Timestamp:
- 09/28/2002 09:08:29 PM (22 years ago)
- 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
- Files:
-
- 75 edited
Legend:
- Unmodified
- Added
- Removed
-
appendixa/autoconf-desc.xml
rf5cc1c17 r2c094d6 12 12 <para>autoconf is a tool for producing shell scripts that automatically 13 13 configure software source code packages to adapt to many kinds of 14 Unix-like systems. 14 Unix-like systems. The configuration scripts produced by autoconf are 15 15 independent of autoconf when they are run, so their users do not need to 16 16 have autoconf.</para></sect4> … … 25 25 <sect4><title>autoreconf</title> 26 26 <para>If there are a lot of autoconf-generated configure scripts, the 27 autoreconf program can save some work. It runs autoconf (and28 autoheader ,where appropriate) repeatedly to remake the autoconf27 autoreconf program can save some work. It runs autoconf and 28 autoheader (where appropriate) repeatedly to remake the autoconf 29 29 configure scripts and configuration header templates in the directory 30 30 tree rooted at the current directory.</para></sect4> … … 32 32 <sect4><title>autoscan</title> 33 33 <para>The autoscan program can help to create a configure.in file for 34 a software package. autoscan examines source files in thedirectory35 tree rooted at a directory given as a command line argument, orthe36 current directory if none is given. It searches the source filesfor37 common portability problems and creates a file configure.scan which38 is apreliminary configure.in for that package.</para></sect4>34 a software package. autoscan examines the source files in a directory 35 tree. If a directory is not specified on the command line, then the 36 current working directory is used. The source files are searched for 37 common portability problems and a configure.scan file is created to 38 serve as the preliminary configure.in for that package.</para></sect4> 39 39 40 40 <sect4><title>autoupdate</title> … … 47 47 package. It prints the identifiers that the package already uses in C 48 48 preprocessor conditionals. If a package has already been set up to 49 have some portability, this program can help to figure out what its50 configure needs to check for. It may help fill in some gaps in a 51 configure.in generatedby autoscan.</para></sect4>49 have some portability, this program can help to determine what configure 50 needs to check. It may fill in some gaps in a configure.in file generated 51 by autoscan.</para></sect4> 52 52 53 53 </sect3> -
appendixa/automake-desc.xml
rf5cc1c17 r2c094d6 15 15 <sect4><title>aclocal, aclocal-1.6</title> 16 16 <para>automake includes a number of autoconf macros which can be used in 17 packages ; some of them are actually required by automake in certain18 situations. These macros must be defined in the aclocal.m4-file ;19 o therwisethey will not be seen by autoconf.</para>17 packages, some of which are needed by automake in certain 18 situations. These macros must be defined in the aclocal.m4-file 19 or they will not be seen by autoconf.</para> 20 20 21 21 <para>The aclocal program will automatically generate aclocal.m4 files 22 based on the contents of configure.in. 23 way to get automake-provided macros ,without having to search around.22 based on the contents of configure.in. This provides a convenient 23 way to get automake-provided macros without having to search around. 24 24 Also, the aclocal mechanism is extensible for use 25 25 by other packages.</para></sect4> … … 27 27 <sect4><title>automake, automake-1.6</title> 28 28 <para>To create all the Makefile.in's for a package, run the automake 29 program in the top level directory, with no arguments. 29 program in the top level directory, with no arguments. automake will 30 30 automatically find each appropriate Makefile.am (by scanning 31 31 configure.in) and generate the corresponding Makefile.in.</para></sect4> -
appendixa/bash-desc.xml
rf5cc1c17 r2c094d6 20 20 21 21 <sect4><title>sh</title> 22 <para>sh is a symlink to the bash program. 22 <para>sh is a symlink to the bash program. When invoked as sh, bash 23 23 tries to mimic the startup behavior of historical versions of sh as closely 24 24 as possible, while conforming to the POSIX standard as -
appendixa/bin86-desc.xml
rf5cc1c17 r2c094d6 19 19 20 20 <sect4><title>ld86</title> 21 <para>ld86 understands only the object files produced by the as86 assembler , it21 <para>ld86 understands only the object files produced by the as86 assembler. It 22 22 can link them into either an impure or a 23 23 separate I&D executable.</para></sect4> -
appendixa/binutils-desc.xml
rf5cc1c17 r2c094d6 12 12 <sect4><title>addr2line</title> 13 13 <para>addr2line translates program addresses into file names and line numbers. 14 Given an address and an executable, it uses the 14 Given an address and an executable, it uses the debugging information in 15 15 the executable to figure out which file name and line number are associated 16 16 with a given address.</para></sect4> … … 19 19 <para>The ar program creates, modifies, and extracts from archives. An archive 20 20 is a single file holding a collection of other files in a structure that makes 21 it 21 it possible to retrieve the original individual files (called members of 22 22 the archive).</para></sect4> 23 23 … … 33 33 34 34 <sect4><title>ld</title> 35 <para>ld combines a number of object and archive files, relocatestheir data35 <para>ld combines a number of object and archive files, relocates their data 36 36 and ties up symbol references. Often the last step in building a new compiled 37 37 program to run is a call to ld.</para></sect4> … … 54 54 <sect4><title>ranlib</title> 55 55 <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 archive56 the archive. The index lists each symbol defined by an archive member 57 57 that is a relocatable object file.</para></sect4> 58 58 … … 66 66 67 67 <sect4><title>strings</title> 68 <para>For each filegiven, strings prints the printable character sequences69 that are at least 4 characterslong (or the number specified with an68 <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 70 70 option to the program) and are followed by an unprintable character. By 71 71 default, it only prints the strings from the initialized and loaded … … 93 93 <sect4><title>libopcodes</title> 94 94 <para>libopcodes is a native library for dealing with opcodes and is 95 used in the course of building utilities such as objdump. 95 used in the course of building utilities such as objdump. Opcodes are 96 96 actually "readable text" versions of instructions for the 97 97 processor.</para></sect4> -
appendixa/bison-desc.xml
rf5cc1c17 r2c094d6 16 16 writing the actual program a user specifies how things should be connected 17 17 and with those rules a program is constructed that analyzes the 18 text file. 18 text file. There are a lot of examples where structure is needed and 19 19 one of them is the calculator.</para> 20 20 … … 40 40 the next thing that the computer sees is the result of 2*3 and the 41 41 number 1 which are joined by the add symbol. Adding 1 to the previous 42 result makes 7. In calculating the most complex calculations can be42 result makes 7. In calculating, the most complex calculations can be 43 43 broken down in this tree format and the computer just starts at the 44 44 bottom and works its way up to the top and comes with the correct -
appendixa/bzip2-desc.xml
rf5cc1c17 r2c094d6 27 27 <sect4><title>bzip2</title> 28 28 <para>bzip2 compresses files using the Burrows-Wheeler block sorting text 29 compression algorithm ,and Huffman coding. Compression is generally30 considerably 31 compressors ,and approaches the performance of the PPM family of statistical29 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 32 32 compressors.</para></sect4> 33 33 … … 37 37 <sect4><title>bzless</title> 38 38 <para>bzless is a filter which allows examination of compressed 39 or plain text files one screenful at a time on a soft-copy39 or plain text files, one screenful at a time on a soft-copy 40 40 terminal, like less.</para></sect4> 41 41 42 42 <sect4><title>bzmore</title> 43 43 <para>bzmore is a filter which allows examination of compressed 44 or plain text files one screenful at a time on a soft-copy44 or plain text files, one screenful at a time on a soft-copy 45 45 terminal, like more.</para></sect4> 46 46 … … 53 53 <sect4><title>libbz2</title> 54 54 <para>libbz2 is the library for implementing lossless, block-sorting data 55 compression using the Burrows-Wheeler algorithm.</para></sect4>55 compression, using the Burrows-Wheeler algorithm.</para></sect4> 56 56 57 57 </sect3> -
appendixa/e2fsprogs-desc.xml
rf5cc1c17 r2c094d6 21 21 22 22 <sect4><title>compile_et</title> 23 <para>compile_et is used to convert a table listing error-code names24 and associated messages into a C source file suitable for use with the25 com_err library.</para></sect4>23 <para>compile_et is used to convert a table, listing error-code names 24 and associated messages, into a C source file that is suitable for use 25 with the com_err library.</para></sect4> 26 26 27 27 <sect4><title>debugfs</title> 28 <para>The debugfs program is a file system debugger. It can be used 28 <para>The debugfs program is a file system debugger. It can be used to examine 29 29 and change the state of an ext2 file system.</para></sect4> 30 30 … … 34 34 35 35 <sect4><title>e2fsck and fsck.ext2</title> 36 <para>e2fsck is used to check and optionally repair Linux second37 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 37 second extended filesystems.</para></sect4> 38 38 39 39 <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 41 41 a file.</para></sect4> 42 42 … … 46 46 47 47 <sect4><title>fsck</title> 48 <para>fsck is used to check and optionally repair a Linux49 filesystem.</para></sect4>48 <para>fsck is used to check, and optionally repair, a Linux file 49 system.</para></sect4> 50 50 51 51 <sect4><title>fsck.ext3</title> 52 <para>fsck.ext3 is used to check and optionally repaira Linux ext352 <para>fsck.ext3 is used to check, and optionally repair, a Linux ext3 53 53 filesystems.</para></sect4> 54 54 … … 59 59 <sect4><title>mk_cmds</title> 60 60 <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 subsystem61 a C source file as output, which is intended to be used with the subsystem 62 62 library, libss.</para></sect4> 63 63 … … 85 85 <para>The uuidgen program creates a new universally unique identifier (UUID) 86 86 using 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 other88 systems in the past and in the future.</para></sect4>87 among all UUIDs created, on the local system and on other 88 systems, in the past and in the future.</para></sect4> 89 89 90 90 </sect3> -
appendixa/ed-desc.xml
rf5cc1c17 r2c094d6 9 9 10 10 <sect4><title>ed</title> 11 <para>ed is a line-oriented text editor. 11 <para>ed is a line-oriented text editor. It is used to create, display, 12 12 modify and otherwise manipulate text files.</para></sect4> 13 13 -
appendixa/file-desc.xml
rf5cc1c17 r2c094d6 10 10 <sect4><title>file</title> 11 11 <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 succeeds12 three sets of tests, performed in this order: filesystem tests, 13 magic number tests and language tests. The first test that succeeds 14 14 causes the file type to be printed.</para></sect4> 15 15 -
appendixa/fileutils-desc.xml
rf5cc1c17 r2c094d6 16 16 <sect4><title>chmod</title> 17 17 <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 octal18 can be either a symbolic representation of changes to make or an octal 19 19 number representing the bit pattern for the new permissions.</para></sect4> 20 20 … … 39 39 <para>dir and vdir are versions of ls with different default output formats. 40 40 These 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 they43 are listed one per line. For dir, files are by default listed in columns,44 sorted vertically. For vdir, files are by defaultlisted in41 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 45 45 long format.</para></sect4> 46 46 47 47 <sect4><title>dircolors</title> 48 <para>dircolors 48 <para>dircolors outputs commands to set the LS_COLOR environment variable. 49 49 The LS_COLOR variable is use to change the default color scheme used by 50 50 ls and related utilities.</para></sect4> 51 51 52 52 <sect4><title>du</title> 53 <para>du displays the amount of disk space used by each argument and for each54 subdirectory of directory arguments.</para></sect4>53 <para>du displays the amount of disk space used by each file or directory 54 listed on the command-line and by each of their subdirectories.</para></sect4> 55 55 56 56 <sect4><title>install</title> -
appendixa/flex-desc.xml
rf5cc1c17 r2c094d6 10 10 <sect4><title>flex</title> 11 11 <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> 12 patterns in text. Pattern recognition is very useful in many applications. 13 A user sets up rules about what to look for and flex will make a program 14 that looks for those patterns. The reason people use flex is that it is 15 much easier to set up rules for what to look for than to write the actual 16 program which finds the text.</para></sect4> 18 17 19 18 <sect4><title>flex++</title> -
appendixa/gcc-desc.xml
rf5cc1c17 r2c094d6 10 10 11 11 <sect4><title>cc, cc1, cc1plus, gcc</title> 12 <para>These are the C compiler. 12 <para>These are the C compiler. A compiler translates source code in 13 13 text format to a format that a computer understands. After a source code 14 14 file is compiled into an object file, a linker will create an executable … … 22 22 <para>The C++ language provides function overloading, which means that it is 23 23 possible to write many functions with the same name (providing each takes 24 parameters of different types). 24 parameters of different types). All C++ function names are encoded into 25 25 a low-level assembly label (this process is known as mangling). The c++filt 26 26 program does the inverse mapping: it decodes (demangles) low-level names … … 64 64 65 65 <sect4><title>libstdc++</title> 66 <para>libstdc++ is the C++ library. 66 <para>libstdc++ is the C++ library. It is used by C++ programs and contains 67 67 functions that are frequently used in C++ programs. This way the 68 68 programmer doesn't have to write certain functions (such as writing a -
appendixa/gettext-desc.xml
rf5cc1c17 r2c094d6 12 12 13 13 <sect4><title>config.charset</title> 14 <para>The config.charset script outputs a system 14 <para>The config.charset script outputs a system-dependent table of 15 15 character encoding aliases.</para></sect4> 16 16 17 17 <sect4><title>config.rpath</title> 18 <para>The config.rpath script outputs a system 18 <para>The config.rpath script outputs a system-dependent set of variables, 19 19 describing how to set the run time search path of shared libraries in an 20 20 executable.</para></sect4> … … 24 24 i18n) and for localization (also known as l10n). Programs can be 25 25 compiled with Native Language Support (NLS) which enable them to output 26 messages in the user s native language rather than in the default English26 messages in the user's native language rather than in the default English 27 27 language.</para></sect4> 28 28 … … 37 37 <sect4><title>msgattrib</title> 38 38 <para>The msgattrib program filters the messages of a translation catalog 39 according to their attributes ,and manipulates the attributes.</para></sect4>39 according to their attributes and manipulates the attributes.</para></sect4> 40 40 41 41 <sect4><title>msgcat</title> -
appendixa/glibc-desc.xml
rf5cc1c17 r2c094d6 73 73 <para>pt_chown sets the owner, group and access permission of the 74 74 slave pseudo terminal corresponding to the master pseudo terminal passed 75 on file descriptor `3'. 76 function. 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 77 77 line.</para></sect4> 78 78 … … 84 84 85 85 <sect4><title>sln</title> 86 <para>sln symbolically links dest to source. 87 needing no dynamic linking at all. 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 88 88 links to dynamic libraries if the dynamic linking system for some reason 89 89 is nonfunctional.</para></sect4> … … 140 140 141 141 <sect4><title>libc, libc_nonshared, libc_p</title> 142 <para>These files constitute the main C library. 142 <para>These files constitute the main C library. The C library is a 143 143 collection of commonly used functions in programs. 144 144 This way a programmer doesn't need to create his own functions for every … … 150 150 library, the code from the C library is copied into the executable file. 151 151 When a program uses a dynamic library, the executable will not 152 contain the code from the C library, but 152 contain the code from the C library, but instead a routine that loads 153 153 the functions from the library at the time the program is run. This 154 154 means a significant decrease in the file size of a program. The -
appendixa/groff-desc.xml
rf5cc1c17 r2c094d6 54 54 <sect4><title>grotty</title> 55 55 <para>grotty translates the output of GNU troff into a form suitable for 56 typewriter-like 56 typewriter-like devices.</para></sect4> 57 57 58 58 <sect4><title>gtbl</title> … … 60 60 61 61 <sect4><title>hpftodit</title> 62 <para>hpftodit creates a font file for use with groff -Tlj4 from an 62 <para>hpftodit creates a font file for use with groff -Tlj4 from an HP 63 63 tagged font metric file.</para></sect4> 64 64 … … 75 75 <para>lookbib prints a prompt on the standard error (unless the standard input 76 76 is 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 77 of keywords, searches the bibliographic databases in a specified file for 78 78 references containing those keywords, prints any references found on the 79 standard output ,and repeats this process until the end of input.</para></sect4>79 standard output and repeats this process until the end of input.</para></sect4> 80 80 81 81 <sect4><title>mmroff</title> … … 94 94 <sect4><title>pic</title> 95 95 <para>pic compiles descriptions of pictures embedded within troff or TeX input 96 files into commands that are understood by TeX or 96 files into commands that are understood by TeX or troff.</para></sect4> 97 97 98 98 <sect4><title>pre-grohtml and post-grohtml</title> … … 103 103 <para>refer copies the contents of a file to the standard output, except that 104 104 lines between .[ and .] are interpreted as citations, and lines between .R1 105 and .R2 areinterpreted as commands about how citations are to be105 and .R2 are interpreted as commands about how citations are to be 106 106 processed.</para></sect4> 107 107 108 108 <sect4><title>soelim</title> 109 109 <para>soelim reads files and replaces lines of the form 110 <emphasis>.so file</emphasis> by thecontents of110 <emphasis>.so file</emphasis> by the contents of 111 111 <emphasis>file</emphasis>.</para></sect4> 112 112 113 113 <sect4><title>tbl</title> 114 114 <para>tbl compiles descriptions of tables embedded within troff input files 115 into commands that are understood bytroff.</para></sect4>115 into commands that are understood by troff.</para></sect4> 116 116 117 117 <sect4><title>tfmtodit</title> -
appendixa/gzip-desc.xml
rf5cc1c17 r2c094d6 24 24 25 25 <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 27 on the command line or a file being read from standard input.</para></sect4> 29 28 30 29 <sect4><title>zcmp</title> … … 36 35 <sect4><title>zforce</title> 37 36 <para>zforce forces a .gz extension on all gzip files so that gzip will not 38 compress them twice. 37 compress them twice. This can be useful for files with names truncated 39 38 after a file transfer.</para></sect4> 40 39 … … 44 43 <sect4><title>zmore</title> 45 44 <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 the45 files, one screen at a time on a soft-copy terminal (similar to the 47 46 more program).</para></sect4> 48 47 -
appendixa/introduction.xml
rf5cc1c17 r2c094d6 29 29 packages than about others. If you think anything should be added to the 30 30 following descriptions, please don't hesitate to email the mailing 31 lists. 31 lists. We intend that the list should contain an in-depth description 32 32 of every package installed, but we can't do it without help.</para> 33 33 34 34 <para>Please note that currently only what a package does is described and not 35 why it needs to be installed. 35 why it needs to be installed. This may be added later.</para> 36 36 37 37 <para>Also listed are all of the installation dependencies for all the -
appendixa/kbd-desc.xml
rf5cc1c17 r2c094d6 69 69 <sect4><title>setleds</title> 70 70 <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 thatyou can71 enabled by default and, by using this program, you can 72 72 achieve this.</para></sect4> 73 73 … … 84 84 <sect4><title>showfont</title> 85 85 <para>showfont displays data about a font. The information shown includes font 86 information, font properties, character metrics ,and86 information, font properties, character metrics and 87 87 character bitmaps.</para></sect4> 88 88 -
appendixa/kernel-desc.xml
rf5cc1c17 r2c094d6 19 19 <sect4><title>linux kernel headers</title> 20 20 <para>These are the files we copy to 21 <filename>/usr/include/{linux,asm}</filename> in Chapter 5. 21 <filename>/usr/include/{linux,asm}</filename> in Chapter 5. They should 22 22 match those which glibc was compiled against and therefore should 23 23 <emphasis>not</emphasis> be replaced when upgrading the kernel. They are -
appendixa/less-desc.xml
rf5cc1c17 r2c094d6 10 10 <sect4><title>less</title> 11 11 <para>The less program is a file pager (or text viewer). It 12 displays the contents of a file withthe ability to scroll. Less is an12 displays the contents of a file and has the ability to scroll. Less is an 13 13 improvement on the common pager called <quote>more</quote>. Less has 14 14 the ability to scroll backwards through files as well and it doesn't need -
appendixa/libtool-desc.xml
rf5cc1c17 r2c094d6 25 25 26 26 <sect4><title>libltdl, libltdl.so.3, libltdl.so.3.1.0</title> 27 <para>A small library that aims at hiding from programmers27 <para>A small library that aims at hiding, from programmers, 28 28 the various difficulties of dlopening libraries.</para></sect4> 29 29 -
appendixa/m4-desc.xml
rf5cc1c17 r2c094d6 9 9 10 10 <sect4><title>m4</title> 11 <para>m4 is a macro processor. It copies input to output expanding macros as it11 <para>m4 is a macro processor. It copies input to output, expanding macros as it 12 12 goes. Macros are either built-in or user-defined and can take any number 13 13 of arguments. Besides just doing macro expansion, m4 has built-in functions -
appendixa/man-desc.xml
rf5cc1c17 r2c094d6 10 10 11 11 <sect4><title>apropos</title> 12 <para>apropos searches a set of database files containing short descriptions13 of system commands for keywords anddisplays the result on the standard12 <para>apropos searches for keywords in a set of database files, containing 13 short descriptions of system commands, and displays the result on the standard 14 14 output.</para></sect4> 15 15 … … 17 17 <para>makewhatis reads all the manual pages contained in given sections of 18 18 manpath or the pre-formatted pages contained in the given sections of 19 catpath. For each page, it writes a line in the whatis database; each20 line consists of the name of the page and a shortdescription,21 separated 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 22 22 the NAME section of the manual page.</para></sect4> 23 23 … … 32 32 33 33 <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> 35 whatis searches for keywords in a set of database files, containing short 36 descriptions of system commands, and displays the result on the standard 36 37 output. Only complete word matches are displayed.</para></sect4> 37 38 -
appendixa/modutils-desc.xml
rf5cc1c17 r2c094d6 15 15 16 16 <sect4><title>genksyms</title> 17 <para>genksyms reads (on standard input) the output from gcc 17 <para>genksyms reads (on standard input) the output from gcc -E source.c 18 18 and generates a file containing version information.</para></sect4> 19 19 … … 40 40 <sect4><title>modinfo</title> 41 41 <para>modinfo examines an object file associated with a kernel module and 42 displays any 42 displays any information that it can glean.</para></sect4> 43 43 44 44 <sect4><title>modprobe</title> -
appendixa/ncurses-desc.xml
rf5cc1c17 r2c094d6 14 14 15 15 <sect4><title>clear</title> 16 <para>clear clears the screen if this is possible. 16 <para>clear clears the screen if this is possible. It looks in 17 17 the environment for the terminal type and then in the terminfo database 18 18 to figure out how to clear the screen.</para></sect4> … … 21 21 <para>infocmp can be used to compare a binary terminfo entry with 22 22 other terminfo entries, rewrite a terminfo description to 23 take advantage of the use= terminfo field, or print out a24 terminfo descriptionfrom the binary file (term) in a variety of23 take advantage of the use= terminfo field, or print out a 24 terminfo description from the binary file (term) in a variety of 25 25 formats (the opposite of what tic does).</para></sect4> 26 26 … … 31 31 <sect4><title>reset</title> 32 32 <para>reset sets cooked and echo modes, turns off cbreak and raw modes, 33 turns on new-line translation 33 turns on new-line translation and resets any unset special characters to 34 34 their default values before doing terminal initialization the same way 35 35 as tset.</para></sect4> -
appendixa/nettools-desc.xml
rf5cc1c17 r2c094d6 37 37 <sect4><title>netstat</title> 38 38 <para>netstat is a multi-purpose tool used to print the network connections, 39 routing tables, interface statistics, masquerade connections ,and multicast39 routing tables, interface statistics, masquerade connections and multicast 40 40 memberships.</para></sect4> 41 41 -
appendixa/perl-desc.xml
rf5cc1c17 r2c094d6 29 29 30 30 <sect4><title>perl, perl5.6.1</title> 31 <para>perl is the Practical Extraction and Report Language. 32 some of the best features of C, sed, awk ,and sh into one powerful31 <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 33 33 language.</para></sect4> 34 34 … … 42 42 <sect4><title>perldoc</title> 43 43 <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 it44 embedded in the perl installation tree or in a perl script and displays it 45 45 via "pod2man | nroff -man | $PAGER".</para></sect4> 46 46 -
appendixa/shadowpwd-desc.xml
rf5cc1c17 r2c094d6 6 6 <para>chage, chfn, chpasswd, chsh, dpasswd, expiry, faillog, gpasswd, 7 7 groupadd, groupdel, groupmod, groups, grpck, grpconv, grpunconv, lastlog, 8 login, 8 login, logoutd, mkpasswd, newgrp, newusers, passwd, pwck, pwconv, pwunconv, 9 9 sg (link to newgrp), useradd, userdel, usermod, vigr (link to vipw) and 10 10 vipw</para></sect3> … … 27 27 28 28 <sect4><title>chsh</title> 29 <para>chsh 29 <para>chsh changes the user login shell.</para></sect4> 30 30 31 31 <sect4><title>dpasswd</title> … … 129 129 <para>vipw and vigr will edit the files /etc/passwd and /etc/group, 130 130 respectively. With the -s flag, they will edit the shadow versions of 131 those files, /etc/shadow and /etc/gshadow,respectively.</para></sect4>131 those files, /etc/shadow and /etc/gshadow, respectively.</para></sect4> 132 132 133 133 </sect3> -
appendixa/shellutils-desc.xml
rf5cc1c17 r2c094d6 43 43 44 44 <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> 46 46 47 47 <sect4><title>hostid</title> … … 61 61 <sect4><title>nohup</title> 62 62 <para>nohup runs a command immune to hangups, with output to a 63 non-tty.</para></sect4>63 log file.</para></sect4> 64 64 65 65 <sect4><title>pathchk</title> … … 74 74 75 75 <sect4><title>printf</title> 76 <para>printf formats and prints data (the same as the printf C76 <para>printf formats and prints data (the same as the C printf 77 77 function).</para></sect4> 78 78 -
appendixa/sysvinit-desc.xml
rf5cc1c17 r2c094d6 20 20 <sect4><title>init</title> 21 21 <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. This22 processes from a script stored in the file /etc/inittab. This 23 23 file usually has entries which cause init to spawn gettys on each line that 24 24 users can log in. It also controls autonomous processes required by any … … 32 32 <sect4><title>last</title> 33 33 <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 34 by the -f flag) and displays a list of all users logged in (and out) 35 35 since that file was created.</para></sect4> 36 36 … … 59 59 <para>runlevel reads the system utmp file (typically /var/run/utmp) to locate 60 60 the runlevel record, and then prints the previous and current system 61 runlevel on its standard 61 runlevel on its standard output, separated by a single space.</para></sect4> 62 62 63 63 <sect4><title>shutdown</title> -
appendixa/texinfo-desc.xml
rf5cc1c17 r2c094d6 12 12 <para>The info program reads Info documents, usually contained in the 13 13 /usr/share/info directory. Info documents are like man(ual) pages, but 14 they tend to be more in depththan just explaining the options to a14 they tend to go deeper than just explaining the options to a 15 15 program.</para></sect4> 16 16 … … 23 23 program is run, a list with available topics (ie: available info documents) 24 24 will 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 necessary26 t o delete the topic in the index file as well. This program is used for25 available topics. If info files are removed manually, you must also delete 26 the topic in the index file. This program is used for 27 27 that. It also works the other way around when info documents are 28 28 added.</para></sect4> … … 30 30 <sect4><title>makeinfo</title> 31 31 <para>The makeinfo program translates Texinfo source documents into various 32 formats. 32 formats. Available formats are: info files, plain text and HTML.</para></sect4> 33 33 34 34 <sect4><title>texi2dvi</title> -
appendixa/textutils-desc.xml
rf5cc1c17 r2c094d6 22 22 23 23 <sect4><title>csplit</title> 24 <para>csplit outputs pieces of a file separated 24 <para>csplit outputs pieces of a file separated by (a) pattern(s) to files 25 25 xx01, xx02, ..., and outputs byte counts of each piece to standard 26 26 output.</para></sect4> … … 31 31 32 32 <sect4><title>expand</title> 33 <para>expand converts 33 <para>expand converts tabs in files to spaces, writing to standard 34 34 output.</para></sect4> 35 35 … … 107 107 108 108 <sect4><title>wc</title> 109 <para>wc prints line, word , and byte counts for each specified file,and a110 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 110 total line, if more than one file is specified.</para></sect4> 111 111 112 112 </sect3> -
chapter01/blfssupport.xml
rf5cc1c17 r2c094d6 3 3 4 4 <para>The blfs-support list handles support requests for any software 5 that is not built or installed in the LFS book. 5 that is not built or installed in the LFS book. Any software beyond what is 6 6 installed as part of the base LFS system can be discussed here.</para> 7 7 -
chapter01/changelog.xml
rf5cc1c17 r2c094d6 60 60 </para></listitem> 61 61 62 <listitem><para>September 28th, 2002 [timothy]: Applied Bill Maltby's 63 grammatic-fixes patch. Changed "$LFS" to "LFS" when speaking of the LFS 64 environment variable.</para></listitem> 65 62 66 <listitem><para>September 23rd, 2002 [timothy]: Applied Bill Maltby's 63 67 grammatic-related patches.</para></listitem> -
chapter01/conventions.xml
rf5cc1c17 r2c094d6 4 4 5 5 <para>To make things easy to follow, there are a number of conventions used 6 throughout the book. 6 throughout the book. Following are some examples:</para> 7 7 8 8 <para><userinput>./configure --prefix=/usr</userinput></para> 9 9 10 10 <blockquote><para>This form of text is designed to be typed exactly 11 as seen unless otherwise noted in the surrounding text. 11 as seen unless otherwise noted in the surrounding text. It is also used 12 12 in the explanation sections to identify which of the commands is being 13 13 referenced.</para></blockquote> … … 41 41 42 42 <blockquote><para>This type of section is used mainly when creating 43 configuration files. 43 configuration files. The first command (in bold) tells the system to create 44 44 the file $LFS/etc/group from whatever is typed on the following lines until 45 45 the sequence EOF is encountered. Therefore, this whole section is generally -
chapter01/lfssupport.xml
rf5cc1c17 r2c094d6 3 3 4 4 <para>The lfs-support mailing list provides support to users building an 5 LFS system as far as the end of the main book. 5 LFS system as far as the end of the main book. Requests for help with 6 6 installing software beyond the base system should go to the blfs-support 7 7 list.</para> -
chapter01/unsubscribe.xml
rf5cc1c17 r2c094d6 19 19 unsubscribe alfs-discuss</literallayout></blockquote> 20 20 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 22 22 email requesting a confirmation of the unsubscription 23 23 request. After this confirmation email is sent back, Listar will -
chapter02/aboutlfs.xml
rf5cc1c17 r2c094d6 4 4 5 5 <para>Please read the following carefully: throughout this book 6 the variable $LFS will be used frequently. $LFS must at all times be6 the variable LFS will be used frequently. $LFS must at all times be 7 7 replaced with the directory where the partition that contains the LFS system 8 8 is mounted. How to create and where to mount the partition will be … … 29 29 command).</para> 30 30 31 <para>If you plan to use $LFS, do not forget to set the $LFS variable at all31 <para>If you plan to use $LFS, do not forget to set the LFS variable at all 32 32 times. If the variable is not set and is used in a command, $LFS will 33 33 be ignored and whatever is left will be executed. A command like 34 34 <userinput>echo "root:x:0:0:root:/root:/bin/bash" > 35 $LFS/etc/passwd</userinput> without the $LFS variable set will35 $LFS/etc/passwd</userinput> without the LFS variable set will 36 36 re-create your host system's /etc/passwd file. Simply put: it will 37 37 destroy your current password database file.</para> … … 40 40 the /root/.bash_profile and /root/.bashrc files so that every time 41 41 you login as user root, or you <userinput>su</userinput> to user root, 42 the $LFS variable is set.</para>42 the LFS variable is set.</para> 43 43 44 44 </sect1> -
chapter02/askforhelp.xml
rf5cc1c17 r2c094d6 25 25 26 26 <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 just27 that we won't help you. After all, LFS is about choice. It'll just 28 28 help us to see other possible causes of your problem.)</para> 29 29 … … 46 46 <para>To help us find the cause of the problem, both screen output and 47 47 the contents of various files are useful. The screen output from both 48 the ./configure script and the make run can be useful. 48 the ./configure script and the make run can be useful. Don't blindly 49 49 include the whole thing but on the other hand, don't include too little. 50 50 As an example, here is some screen output from make:</para> 51 51 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. 55 55 -g -O2 -c getopt1.c 56 gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o57 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 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 59 59 -lutil job.o: In function `load_too_high': 60 60 /lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg' … … 67 67 68 68 <para>In this case, many people just include the bottom section where it 69 says <screen>make [2]: *** [make] Error 1</screen> and onwards. 69 says <screen>make [2]: *** [make] Error 1</screen> and onwards. This 70 70 isn't enough for us to diagnose the problem because it only tells us 71 71 that <emphasis>something</emphasis> went wrong, not 72 <emphasis>what</emphasis> went wrong. 72 <emphasis>what</emphasis> went wrong. The whole section, as 73 73 in the example above, is what should be included to be helpful, because it 74 74 includes the command that was executed and the command's error … … 76 76 77 77 <para>An excellent article on asking for help on the Internet in general 78 has been written by Eric S. Raymond. 78 has been written by Eric S. Raymond. It is available online at <ulink 79 79 url="http://www.tuxedo.org/~esr/faqs/smart-questions.html"/>. 80 80 Read and follow the hints in that document and you are much more likely -
chapter02/install.xml
rf5cc1c17 r2c094d6 4 4 5 5 <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. 7 aren't, the commands may work, but we can't guarantee it. 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 8 8 simple life, use bash.</para> 9 9 … … 32 32 33 33 <para>Nowadays most tar programs, but not all, are 34 patched to be able to use bzip2 files directly. 34 patched to be able to use bzip2 files directly. They use either 35 35 the -I, the -y, or the -j parameter, which work the same as the -z 36 36 parameter for handling gzip files. The above construction, however, … … 77 77 <para>There is one exception; the kernel source tree. Keep it around as you 78 78 will 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. 79 will use the kernel tree, so the source tree won't be in your way. If, 80 80 however, you are short of disk space, you can remove the kernel tree and 81 81 re-untar it later when required.</para> -
chapter02/platform.xml
rf5cc1c17 r2c094d6 6 6 said that, the main LFS development work occurs on the x86 platform. We 7 7 attempt to include information where possible on differences for other 8 platforms such as PPC. 8 platforms such as PPC. If you come across a problem compiling which is 9 9 not related to the x86 platform, still feel free to ask for help on the 10 mailing lists. 10 mailing lists. Even better, if you come up with a solution to a 11 11 particular problem related to one of the other platforms, please let us 12 know at the lfs-dev mailing list. 12 know at the lfs-dev mailing list. We will then (subject to confirming 13 13 it works) include that in the book.</para> 14 14 -
chapter03/mounting.xml
rf5cc1c17 r2c094d6 20 20 <para>Replace <quote>xxx</quote> by the partition's designation (like hda11).</para> 21 21 22 <para>This directory (/mnt/lfs) is the $LFS variable you have read about23 back in Chapter 2. If you were planning to make use of the $LFS environment22 <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 24 24 variable, <userinput>export LFS=/mnt/lfs</userinput> has to be executed 25 25 now.</para> -
chapter05/binutils-inst.xml
rf5cc1c17 r2c094d6 4 4 <para>This package is known to behave badly when you have changed its default 5 5 optimization flags (including the -march and -mcpu options). Binutils is 6 best left alone. 6 best left alone. Therefore, if you have defined any environment variables 7 7 that override default optimizations, such as CFLAGS and CXXFLAGS, we 8 recommend unsetting or modifying them when building binutils. 8 recommend unsetting or modifying them when building binutils. You have been 9 9 warned.</para> 10 10 -
chapter05/gcc-exp.xml
rf5cc1c17 r2c094d6 7 7 <ulink url="http://www.zipworld.com.au/~gschafer/lfs-tweaks.html"/>.</para> 8 8 9 <para><userinput>--prefix=/static:</userinput> This is NOT a typo. 9 <para><userinput>--prefix=/static:</userinput> This is NOT a typo. GCC hard 10 10 codes some paths while compiling and so we need to pass /static as the 11 prefix during ./configure. 11 prefix during ./configure. We pass the real install prefix during the 12 12 make install command later.</para> 13 13 -
chapter05/gcc-inst.xml
rf5cc1c17 r2c094d6 8 8 <para>This package is known to behave badly when you have changed its 9 9 default optimization flags (including the -march and -mcpu options). GCC is 10 best left alone. 10 best left alone. Therefore, if you have defined any environment variables 11 11 that override default optimizations, such as CFLAGS and CXXFLAGS, we 12 recommend unsetting or modifying them when building GCC. 12 recommend unsetting or modifying them when building GCC. You have 13 13 been warned.</para> 14 14 -
chapter05/patch-exp.xml
rf5cc1c17 r2c094d6 4 4 <para><userinput>CPPFLAGS=-D_GNU_SOURCE: </userinput> 5 5 This flag fixes installation problems of this package on PPC and m68k 6 platforms (that we know of). 6 platforms (that we know of). It doesn't hurt compilation on other 7 7 platforms, such as x86, so we do it by default.</para> 8 8 -
chapter05/whystatic.xml
rf5cc1c17 r2c094d6 30 30 that we only need one copy of the library. If <filename>ls</filename> and 31 31 <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. 32 copies of the library, as they can both get the code from the same file. 33 33 Even when in memory, the two programs share the same code, rather than loading 34 34 duplicates into memory. So not only are we saving hard disk space, but also … … 36 36 37 37 <para>If dynamic linking saves so much room, then why are we making everything 38 statically linked? 38 statically linked? Well, that's because when you chroot into your brand new 39 39 (but very incomplete) LFS environment, these dynamic libraries won't be 40 40 available because they are somewhere else in your old directory tree … … 53 53 54 54 <para>And there you have it, that's why you need to use those weird 55 <userinput>-static</userinput> flags. 55 <userinput>-static</userinput> flags. If you try building everything 56 56 without them, you'll see very quickly what 57 57 happens when you chroot into your newly crippled LFS system.</para> -
chapter06/aboutdebug.xml
rf5cc1c17 r2c094d6 3 3 <?dbhtml filename="aboutdebug.html" dir="chapter06"?> 4 4 5 <para>Most programs and libraries are by defaultcompiled with debugging5 <para>Most programs and libraries are, by default, compiled with debugging 6 6 symbols included (with gcc option -g).</para> 7 7 … … 44 44 <para>For your convenience, Chapter 9 includes one simple command to strip 45 45 all debugging symbols from all programs and libraries on your system. 46 Additional information on optimization you can find in the hint at46 Additional information on optimization can be found in the hint at 47 47 <ulink url="&hints-root;optimization.txt"/>.</para> 48 48 -
chapter06/binutils-exp.xml
rf5cc1c17 r2c094d6 3 3 4 4 <para><userinput>tooldir=/usr:</userinput> Normally, the tooldir (the 5 directory where the executables from binutils end up in) is set to5 directory where the executables from binutils end up) is set to 6 6 $(exec_prefix)/$(target_alias) which expands into, for example, 7 7 /usr/i686-pc-linux-gnu. Since we only build for our own system, we don't -
chapter06/binutils-inst.xml
rf5cc1c17 r2c094d6 3 3 <para>This package is known to behave badly when you have changed its 4 4 default optimization flags (including the -march and -mcpu options). Binutils 5 is best left alone. 5 is best left alone. Therefore, if you have defined any environment variables 6 6 that override default optimizations, such as CFLAGS and CXXFLAGS, we 7 recommend unsetting or modifying them when building binutils. 7 recommend unsetting or modifying them when building binutils. You have 8 8 been warned.</para> 9 9 -
chapter06/bzip2-exp.xml
rf5cc1c17 r2c094d6 4 4 <para><userinput>make -f Makefile-libbz2_so:</userinput> This will cause bzip2 5 5 to be built using a different Makefile file, in this case the 6 Makefile-libbz2_so file which creates a dynamic libbz2.so library and6 Makefile-libbz2_so file, which creates a dynamic libbz2.so library and 7 7 links the bzip2 utilities against it.</para> 8 8 -
chapter06/bzip2-inst.xml
rf5cc1c17 r2c094d6 17 17 ln -s bzip2 /bin/bzcat</userinput></screen></para> 18 18 19 <para>Although it's not strictly a part of a basic LFS system it's worth19 <para>Although it's not strictly a part of a basic LFS system, it's worth 20 20 mentioning that a patch for Tar can be downloaded which enables the tar 21 21 program to compress and uncompress using bzip2/bunzip2 easily. With a -
chapter06/chroot.xml
rf5cc1c17 r2c094d6 1 1 <sect1 id="ch06-chroot"> 2 <title>Entering the chroot 'edenvironment</title>2 <title>Entering the chroot environment</title> 3 3 <?dbhtml filename="chroot.html" dir="chapter06"?> 4 4 5 <para>It is time to enter the chroot 'edenvironment in order to begin installing5 <para>It is time to enter the chroot environment in order to begin installing 6 6 the packages we need. Before you can chroot, however, you need to become 7 7 <emphasis>root</emphasis>, since only <emphasis>root</emphasis> … … 9 9 10 10 <para>Become <emphasis>root</emphasis> and run the following command 11 to enter the chroot 'edenvironment:</para>11 to enter the chroot environment:</para> 12 12 13 13 <para><screen><userinput>chroot $LFS /static/bin/env -i \ … … 18 18 19 19 <para>The <userinput>-i</userinput> option given to the 20 <userinput>env</userinput> command will clear all variables of the chroot 'ed20 <userinput>env</userinput> command will clear all variables of the chroot 21 21 environment. After that, only the HOME, TERM, PS1 and PATH variables are 22 22 set again. The TERM=$TERM construct will set the TERM variable inside chroot … … 25 25 such as CFLAGS or CXXFLAGS, this is a good place to set them again.</para> 26 26 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, 28 28 because everything you do will be restricted to the LFS file system -- since 29 29 what the shell thinks is <filename class="directory">/</filename> is actually … … 31 31 32 32 <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 'edenvironment.33 in the following chapters are run from within the chroot environment. 34 34 If you ever leave this environment for any reason (rebooting for example), 35 35 you must remember to again enter chroot and mount proc (discussed later) -
chapter06/creatingdirs.xml
rf5cc1c17 r2c094d6 3 3 <?dbhtml filename="creatingdirs.html" dir="chapter06"?> 4 4 5 <para>Let's now create some structure in our LFS file system , let's create5 <para>Let's now create some structure in our LFS file system. Let's create 6 6 a directory tree. Issuing the following commands will create a more or less 7 7 standard tree:</para> … … 23 23 ln -s ../var/tmp /usr</userinput></screen></para> 24 24 25 <para>Directories are by defaultcreated with permission mode 755, but this25 <para>Directories are, by default, created with permission mode 755, but this 26 26 isn't desirable for all directories. We will make two changes: one to the home 27 27 directory of root, and another to the directories for temporary files.</para> … … 32 32 <para>The first mode change ensures that not just everybody can enter the 33 33 <filename class="directory">/root</filename> directory -- the same 34 a normal user would do with his or her home directory.34 as a normal user would do with his or her home directory. 35 35 The second mode change makes sure that any user can write to the 36 36 <filename class="directory">/tmp</filename> and 37 37 <filename class="directory">/var/tmp</filename> directories, but 38 cannot remove other users' sfiles from them. The latter is prohibited38 cannot remove other users' files from them. The latter is prohibited 39 39 by the so-called "sticky bit" -- the highest bit in the 1777 bit mask.</para> 40 40 … … 54 54 much like these for a base system. However, feel free to make your system 55 55 FHS-compliant. As to the structure of the 56 <filename class="directory">/usr/local/share</filename> subdirectory the FHS56 <filename class="directory">/usr/local/share</filename> subdirectory, the FHS 57 57 isn't precise, so we created here the directories that we think are needed.</para> 58 58 -
chapter06/e2fsprogs-exp.xml
rf5cc1c17 r2c094d6 5 5 reason for supplying this option is because of the setup of the 6 6 e2fsprogs Makefile. Some programs are essential for system use when, 7 for example, /usr isn't mounted (like the e2fsck program). 8 programs and libraries thereforebelong in directories like /lib and7 for example, /usr isn't mounted (like the e2fsck program). These 8 programs and libraries, therefore, belong in directories like /lib and 9 9 /sbin. If this option isn't passed to E2fsprogs's configure, it places 10 these programs in /usr whichis not what we want.</para>10 these programs in /usr, which is not what we want.</para> 11 11 12 12 <para><userinput>--enable-elf-shlibs:</userinput> This creates shared -
chapter06/findutils-inst.xml
rf5cc1c17 r2c094d6 19 19 <para>By default, the location of the updatedb database is in /usr/var. 20 20 If you would rather be FHS compliant, you may wish to use another 21 location. 21 location. The following commands use the database file 22 22 <filename>/var/lib/misc/locatedb</filename> which is FHS compliant.</para> 23 23 -
chapter06/gcc-inst.xml
rf5cc1c17 r2c094d6 8 8 <para>This package is known to behave badly when you have changed its 9 9 default optimization flags (including the -march and -mcpu options). GCC is 10 best left alone. 10 best left alone. Therefore, if you have defined any environment variables 11 11 that override default optimizations, such as CFLAGS and CXXFLAGS, we 12 recommend unsetting or modifying them when building Gcc. 12 recommend unsetting or modifying them when building Gcc. You have 13 13 been warned.</para> 14 14 -
chapter06/glibc-exp.xml
rf5cc1c17 r2c094d6 31 31 32 32 <para><userinput>--enable-add-ons:</userinput> This enables the add-on that 33 we install with Glibc :linuxthreads</para>33 we install with Glibc, linuxthreads</para> 34 34 35 35 <para><userinput>--libexecdir=/usr/bin:</userinput> This will cause the -
chapter06/glibc-inst.xml
rf5cc1c17 r2c094d6 13 13 <para>This package is known to behave badly when you have changed its 14 14 default optimization flags (including the -march and -mcpu options). Glibc 15 is best left alone. 15 is best left alone. Therefore, if you have defined any environment variables 16 16 that override default optimizations, such as CFLAGS and CXXFLAGS, we 17 recommend unsetting or modifying them when building Glibc. 17 recommend unsetting or modifying them when building Glibc. You have 18 18 been warned.</para> 19 19 … … 41 41 <para>An alternative to running <userinput>make 42 42 localedata/install-locales</userinput> is to only install those locales 43 which you need or want. 44 command. 43 which you need or want. This can be achieved using the localedef 44 command. Information on this can be found in the INSTALL 45 45 file in the glibc-&glibc-version; tree. One thing to note is that the 46 46 <userinput>localedef</userinput> program assumes that the <filename … … 50 50 <para>The Linux Threads man pages are not going to be installed at this 51 51 point 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 page52 later on in this chapter, so we'll come back to the Linux Threads man page 53 53 installation after that.</para> 54 54 -
chapter06/groff-exp.xml
rf5cc1c17 r2c094d6 3 3 4 4 <para><userinput>make PROCESSEDEXAMPLEFILES="":</userinput> Groff has a few 5 extra dependencies that we don't install with LFS. This option disable the5 extra dependencies that we don't install with LFS. This option disables the 6 6 need for those tools.</para> 7 7 -
chapter06/introduction.xml
rf5cc1c17 r2c094d6 4 4 5 5 <para>In this chapter we enter the building site, and start 6 constructing our LFS system in earnest. 6 constructing our LFS system in earnest. That is, we chroot into 7 7 our temporary mini Linux system, create some auxiliary things, 8 8 and then start installing all the packages, one by one.</para> … … 22 22 may also cause compilation difficulties. If a package refuses 23 23 to compile when using optimization, try to compile it without 24 optimization and see if 24 optimization and see if the problem goes away.</para> 25 25 26 26 <para>The order in which packages are installed in this chapter has … … 28 28 to <filename class="directory">/static</filename> hard-wired into it. 29 29 For the same reason, <emphasis>do not </emphasis> compile packages 30 in parallel. 30 in parallel. Compiling in parallel may save you some time (especially on 31 31 dual-CPU machines), but it could result in a program containing a 32 32 hard-wired path to <filename class="directory">/static</filename>, -
chapter06/kbd-exp.xml
rf5cc1c17 r2c094d6 4 4 <para><userinput>patch -Np1 -i ../kbd-&kbd-patch-version;.patch</userinput>: 5 5 This 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,6 behaviour, which is broken in current kbd versions. It is necessary to fix this, 7 7 because 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>8 The second part of the patch changes a Makefile so some utilities that are 9 not installed by default (setlogcons, setvesablank and getunimap) are also 10 installed.</para> 11 11 12 12 </sect2> -
chapter06/kernel-exp-headers.xml
rf5cc1c17 r2c094d6 27 27 28 28 <para>The essential part is where Linus states that the header files should be 29 <emphasis>the ones which glibc was compiled against</emphasis>. 29 <emphasis>the ones which glibc was compiled against</emphasis>. These are 30 30 the headers that should be used when you later compile other packages, as they 31 31 are the ones that match the object-code library files. By copying the headers, -
chapter06/kernel-exp.xml
rf5cc1c17 r2c094d6 9 9 <para><userinput>make mrproper</userinput>: This ensures that the kernel 10 10 tree is absolutely clean. The kernel team recommends that this command be 11 issued prior to <emphasis>each</emphasis> kernel compilation ,and that you11 issued prior to <emphasis>each</emphasis> kernel compilation and that you 12 12 shouldn't rely on the source tree being clean after untarring.</para> 13 13 -
chapter06/lilo-inst.xml
rf5cc1c17 r2c094d6 22 22 23 23 <para>The standard LILO prompt, or menu, may be replaced by the 24 LFS logo ,or any logo you like. Martin Imobersteg has written a24 LFS logo or any logo you like. Martin Imobersteg has written a 25 25 hint about this, which is located at 26 26 <ulink url="&hints-root;bootlogo.txt"/>.</para> -
chapter06/makedev-exp.xml
rf5cc1c17 r2c094d6 5 5 bunch of devices. Normally, these are all the devices you will need. But it 6 6 is possible that some special devices needed for your hardware configuration 7 are missing. Create these with ./MAKEDEV -v <device>. 7 are missing. Create these with ./MAKEDEV -v <device>. 8 8 The <userinput>generic-nopty</userinput> option mostly creates the same 9 devices as <userinput>generic -nopty</userinput>, but skips those that aren't9 devices as <userinput>generic</userinput>, but skips those that aren't 10 10 needed if you are using devpts.</para> 11 11 -
chapter06/makedev-inst.xml
rf5cc1c17 r2c094d6 2 2 <title>Creating devices</title> 3 3 4 <para> (Note that unpacking the MAKEDEV-&makedev-version;.bz2 file doesn't create5 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 5 a directory for you to cd into, as the file only contains a script.</para> 6 6 7 7 <para>Prepare for the creation of the device files by running the -
chapter06/man-inst.xml
rf5cc1c17 r2c094d6 18 18 19 19 <para>You may want to take a look at the man hint 20 at <ulink url="&hints-root;man.txt"/> which deals with formatting20 at <ulink url="&hints-root;man.txt"/>, which deals with formatting 21 21 and compression issues for man pages.</para> 22 22 -
chapter06/mountproc.xml
rf5cc1c17 r2c094d6 4 4 5 5 <para>In order for certain programs to function properly, the proc file 6 system must be available within the chroot 'edenvironment.6 system must be available within the chroot environment. 7 7 As a file system can be mounted as many times and in as many places 8 8 as you like, it's not a problem that the proc file system is already … … 22 22 not enough memory</screen></blockquote> 23 23 24 <para>Ignore these, they're just causeddue to the fact that the system24 <para>Ignore these, they're just due to the fact that the system 25 25 isn't installed completely yet and some files are missing. The mount itself 26 26 will be successful and that's all we care about at this point.</para> -
chapter06/ncurses-exp.xml
rf5cc1c17 r2c094d6 10 10 11 11 <para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be 12 executable. Ncurses install routine doesn't set the permissions12 executable. Ncurses's install routine doesn't set the permissions 13 13 properly so we do it manually instead.</para> 14 14 15 15 <para><userinput>ln -sf libncurses.a libcurses.a:</userinput> Some 16 programs try to link using -lcurses instead of -lncurses. 16 programs try to link using -lcurses instead of -lncurses. This symlink 17 17 ensures that such programs will link without errors.</para> 18 18 -
chapter06/nettools-inst.xml
rf5cc1c17 r2c094d6 15 15 <para>If you don't know what to answer to all the questions asked during 16 16 the <userinput>make</userinput> phase, then just accept the defaults, which 17 will be just infine in the majority of the cases. What you are asked here17 will be just fine in the majority of the cases. What you are asked here 18 18 are a bunch of questions relating to the kind of network protocols that you 19 19 have enabled in your kernel.</para> -
chapter06/perl-inst.xml
rf5cc1c17 r2c094d6 9 9 10 10 <para>If you want more control over the way perl sets itself up to be 11 buil d, you can run the interactive <userinput>Configure</userinput> script11 built, you can run the interactive <userinput>Configure</userinput> script 12 12 and modify the way perl is built. If you think you can live with the 13 13 (sensible) defaults perl auto-detects, then just use the commands listed -
chapter06/pwdgroup.xml
rf5cc1c17 r2c094d6 36 36 <para>The created groups aren't part of any standard -- they are the groups 37 37 that the MAKEDEV script in the next section uses. 38 Besides the group "root", the LSB recommends only a group "bin" with a GID39 of 1 tobe present. All other group names and GIDs can be chosen freely by38 Besides the group "root", the LSB recommends only a group "bin", with a GID 39 of 1, be present. All other group names and GIDs can be chosen freely by 40 40 the user, as well-written packages don't depend on GID numbers but use the 41 41 group's name.</para> -
chapter07/hostname.xml
rf5cc1c17 r2c094d6 12 12 13 13 <para><quote>lfs</quote> needs to be replaced with the name the computer is 14 to be called. 14 to be called. You should not enter the FQDN (Fully Qualified Domain 15 15 Name) here. That information will be put in the 16 16 <filename>/etc/hosts</filename> file later on.</para>
Note:
See TracChangeset
for help on using the changeset viewer.