From 13a9dc2d62c5a1fa1c354cdfa54ce18c8f5ff67f Mon Sep 17 00:00:00 2001 From: Manuel Canales Esparcia Date: Wed, 11 Jan 2006 12:02:10 +0000 Subject: Indented chapter01 except changelog.xml. Renamed administrativa.xml to resources.xml. Standarized the ID values. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@7265 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter01/administrativa.xml | 83 ------------------- chapter01/askforhelp.xml | 188 +++++++++++++++++++++++-------------------- chapter01/chapter01.xml | 21 ++--- chapter01/how.xml | 147 ++++++++++++++++----------------- chapter01/livecd.xml | 146 +++++++++++++++++++++------------ chapter01/resources.xml | 91 +++++++++++++++++++++ chapter09/whatnow.xml | 2 +- 7 files changed, 372 insertions(+), 306 deletions(-) delete mode 100644 chapter01/administrativa.xml create mode 100644 chapter01/resources.xml diff --git a/chapter01/administrativa.xml b/chapter01/administrativa.xml deleted file mode 100644 index 52aea6168..000000000 --- a/chapter01/administrativa.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - %general-entities; -]> - -Resources - - - - -FAQ - -If during the building of the LFS system you encounter any -errors, have any questions, or think there is a typo in the book, -please start by consulting the Frequently Asked Questions (FAQ) -that is located at . - - - -Mailing Lists - -The linuxfromscratch.org server hosts a number of mailing lists -used for the development of the LFS project. These lists include the main -development and support lists, among others. If the FAQ does not solve the -problem you are having, the next step would be to search the mailing lists at -. - -For information on the different lists, how to subscribe, archive -locations, and additional information, visit -. - - - - - -IRC - -Several members of the LFS community offer assistance on our -community Internet Relay Chat (IRC) network. Before using this -support, please make sure that your question is not already answered in the LFS -FAQ or the mailing list archives. You can find the IRC network at -irc.linuxfromscratch.org. -The support channel is named #LFS-support. - - - -References - -For additional information on the packages, useful tips are -available in the LFS Package Reference page located at . - - - - -Mirror Sites - -The LFS project has a number of world-wide mirrors to make accessing the -website and downloading the required packages more convenient. Please visit the -LFS website at for a list of current -mirrors. - - -Contact Information - -Please direct all your questions and comments to one of the LFS mailing -lists (see above). - - - - diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml index fa6ddccaa..f5f550318 100644 --- a/chapter01/askforhelp.xml +++ b/chapter01/askforhelp.xml @@ -1,87 +1,101 @@ - %general-entities; ]> - -Help - - -If an issue or a question is encountered while working -through this book, check the FAQ page at . -Questions are often already answered there. If your question is -not answered on this page, try to find the source of the problem. The -following hint will give you some guidance for troubleshooting: . - -If you cannot find your problem listed in the FAQ, search the mailing -lists at . - -We also have a wonderful LFS community that is willing to offer assistance -through the mailing lists and IRC (see the section of this book). However, we get -several support questions everyday and many of them can be easily answered by -going to the FAQ and by searching the mailing lists first. So for us to offer -the best assistance possible, you need to do some research on your own first. -That allows us to focus on the more unusual support needs. If your searches do -not produce a solution, please include all relevant information (mentioned -below) in your request for help. - - -Things to Mention - -Apart from a brief explanation of the problem being experienced, -the essential things to include in any request for help are: - - -The version of the book being used (in this case -&version;) -The host distribution and version being used to -create LFS -The package or section the problem was encountered in -The exact error message or symptom being received -Note whether you have deviated from the book at all - - -Deviating from this book does not -mean that we will not help you. After all, LFS is about personal -preference. Being upfront about any changes to the established -procedure helps us evaluate and determine possible causes of your -problem. - - - -Configure Script Problems - -If something goes wrong while running the configure -script, review the config.log file. This file may -contain errors encountered during configure which were not -printed to the screen. Include the relevant lines if you -need to ask for help. - - - -Compilation Problems - -Both the screen output and the contents of various files are -useful in determining the cause of compilation problems. The screen output -from the configure script and the -make run can be helpful. It -is not necessary to include the entire output, but do include enough -of the relevant information. Below is an example of the type of -information to include from the screen output from make: + + + + + Help + + If an issue or a question is encountered while working through + this book, check the FAQ page at . + Questions are often already answered there. If your question is not + answered on this page, try to find the source of the problem. The + following hint will give you some guidance for troubleshooting: + . + + If you cannot find your problem listed in the FAQ, search the mailing + lists at . + + We also have a wonderful LFS community that is willing to offer + assistance through the mailing lists and IRC (see the section of this book). However, + we get several support questions everyday and many of them can be easily + answered by going to the FAQ and by searching the mailing lists first. + So for us to offer the best assistance possible, you need to do some + research on your own first. That allows us to focus on the more unusual + support needs. If your searches do not produce a solution, please include + all relevant information (mentioned below) in your request for help. + + + Things to Mention + + Apart from a brief explanation of the problem being experienced, + the essential things to include in any request for help are: + + + + The version of the book being used (in this case &version;) + + + The host distribution and version being used to create LFS + + + The package or section the problem was encountered in + + + The exact error message or symptom being received + + + Note whether you have deviated from the book at all + + + + + Deviating from this book does not mean that + we will not help you. After all, LFS is about personal preference. + Being upfront about any changes to the established procedure helps us + evaluate and determine possible causes of your problem. + + + + + + Configure Script Problems + + If something goes wrong while running the configure + script, review the config.log file. This file may + contain errors encountered during configure which were + not printed to the screen. Include the relevant lines + if you need to ask for help. + + + + + Compilation Problems + + Both the screen output and the contents of various files are useful + in determining the cause of compilation problems. The screen output from + the configure script and the make + run can be helpful. It is not necessary to include the entire output, but + do include enough of the relevant information. Below is an example of the + type of information to include from the screen output from + make: gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" --DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" +-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\" -DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I. -g -O2 -c getopt1.c -gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o -expand.o file.o function.o getopt.o implicit.o job.o main.o -misc.o read.o remake.o rule.o signame.o variable.o vpath.o +gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o +expand.o file.o function.o getopt.o implicit.o job.o main.o +misc.o read.o remake.o rule.o signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o -lutil job.o: In function `load_too_high': -/lfs/tmp/make-3.79.1/job.c:1565: undefined reference +/lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg' collect2: ld returned 1 exit status make[2]: *** [make] Error 1 @@ -90,23 +104,23 @@ make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/lfs/tmp/make-3.79.1' make: *** [all-recursive-am] Error 2 -In this case, many people would just include the bottom -section: + In this case, many people would just include the bottom + section: make [2]: *** [make] Error 1 -This is not enough information to properly diagnose the problem -because it only notes that something went wrong, not -what went wrong. The entire section, as in the -example above, is what should be saved because it includes the command -that was executed and the associated error message(s). + This is not enough information to properly diagnose the problem + because it only notes that something went wrong, not + what went wrong. The entire section, as in the + example above, is what should be saved because it includes the command + that was executed and the associated error message(s). -An excellent article about asking for help on the Internet is -available online at . Read and -follow the hints in this document to increase the likelihood of getting -the help you need. - + An excellent article about asking for help on the Internet is + available online at . Read and + follow the hints in this document to increase the likelihood of getting + the help you need. - + + diff --git a/chapter01/chapter01.xml b/chapter01/chapter01.xml index 15019e65d..3906cf0aa 100644 --- a/chapter01/chapter01.xml +++ b/chapter01/chapter01.xml @@ -1,17 +1,20 @@ - %general-entities; ]> + - -Introduction - + + + + Introduction - - - - - + + + + + diff --git a/chapter01/how.xml b/chapter01/how.xml index 55d1447d6..6c1c3b26f 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -1,88 +1,89 @@ - %general-entities; ]> - -How to Build an LFS System - -The LFS system will be built by using a previously installed -Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This -existing Linux system (the host) will be used as a starting point to -provide necessary programs, including a compiler, linker, and shell, -to build the new system. Select the development option -during the distribution installation to be able to access these -tools. + + -As an alternative to installing an entire separate distribution onto your -machine, you may wish to use the Linux From Scratch LiveCD. The CD works well as -a host system, providing all the tools you need to successfully follow the -instructions in this book. Additionally, it contains all the source packages, -patches and a copy of this book. So once you have the CD, no network connection -or additional downloads are necessary. For more information about the LFS LiveCD -or to download a copy, visit . + How to Build an LFS System - of this book describes how -to create a new Linux native partition and file system, the place -where the new LFS system will be compiled and installed. explains which packages and -patches need to be downloaded to build an LFS system and how to store -them on the new file system. -discusses the setup for an appropriate working environment. Please read - carefully as it explains several -important issues the developer should be aware of before beginning to -work through and -beyond. + The LFS system will be built by using a previously installed + Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This + existing Linux system (the host) will be used as a starting point to + provide necessary programs, including a compiler, linker, and shell, + to build the new system. Select the development option + during the distribution installation to be able to access these + tools. - explains the -installation of a number of packages that will form the basic -development suite (or toolchain) which is used to build the actual -system in . Some of these -packages are needed to resolve circular dependencies—for example, -to compile a compiler, you need a compiler. + As an alternative to installing an entire separate distribution + onto your machine, you may wish to use the Linux From Scratch LiveCD. + The CD works well as a host system, providing all the tools you need + to successfully follow the instructions in this book. Additionally, + it contains all the source packages, patches and a copy of this book. + So once you have the CD, no network connection or additional downloads + are necessary. For more information about the LFS LiveCD or to download + a copy, visit . - also shows the user how -to build a first pass of the toolchain, including Binutils and GCC -(first pass basically means these two core packages will be -re-installed a second time). The next step is to build Glibc, the C library. -Glibc will be compiled by the toolchain programs built in the first pass. Then, -a second pass of the toolchain will be built. This time, the toolchain will be -dynamically linked against the newly built Glibc. The remaining - packages are built using this second -pass toolchain. When this is done, the LFS installation process will no longer -depend on the host distribution, with the exception of the running kernel. - + of this book describes how + to create a new Linux native partition and file system, the place + where the new LFS system will be compiled and installed. explains which packages and + patches need to be downloaded to build an LFS system and how to store + them on the new file system. + discusses the setup for an appropriate working environment. Please read + carefully as it explains several + important issues the developer should be aware of before beginning to + work through and beyond. -This effort to isolate the new system from the host distribution may seem -excessive, but a full technical explanation is provided in -. + explains the + installation of a number of packages that will form the basic + development suite (or toolchain) which is used to build the actual + system in . Some of these + packages are needed to resolve circular dependencies—for example, + to compile a compiler, you need a compiler. -In , the full LFS system is -built. The chroot (change root) program is used to enter a virtual -environment and start a new shell whose root directory will be set to -the LFS partition. This is very similar to rebooting and instructing -the kernel to mount the LFS partition as the root partition. The -system does not actually reboot, but instead chroot's because creating a -bootable system requires additional work which is not necessary just -yet. The major advantage is that chrooting allows the -builder to continue using the host while LFS is being built. While -waiting for package compilation to complete, a user can switch to a -different virtual console (VC) or X desktop and continue using the -computer as normal. + also shows the user how to + build a first pass of the toolchain, including Binutils and GCC (first pass + basically means these two core packages will be re-installed a second time). + The next step is to build Glibc, the C library. Glibc will be compiled by + the toolchain programs built in the first pass. Then, a second pass of the + toolchain will be built. This time, the toolchain will be dynamically linked + against the newly built Glibc. The remaining packages are built using this second + pass toolchain. When this is done, the LFS installation process will no + longer depend on the host distribution, with the exception of the running + kernel. -To finish the installation, the LFS-Bootscripts are set up in , and the kernel and boot loader are set -up in . contains information on furthering the -LFS experience beyond this book. After the steps in this book have -been implemented, the computer will be ready to reboot into the new -LFS system. + This effort to isolate the new system from the host distribution may + seem excessive, but a full technical explanation is provided in + . -This is the process in a nutshell. Detailed information on each -step is discussed in the following chapters and package descriptions. -Items that may seem complicated will be clarified, and everything will -fall into place as the reader embarks on the LFS adventure. + In , the full LFS system is + built. The chroot (change root) program is used to enter + a virtual environment and start a new shell whose root directory will be + set to the LFS partition. This is very similar to rebooting and instructing + the kernel to mount the LFS partition as the root partition. The system + does not actually reboot, but instead chroot's because + creating a bootable system requires additional work which is not necessary + just yet. The major advantage is that chrooting allows the + builder to continue using the host while LFS is being built. While waiting + for package compilation to complete, a user can switch to a different + virtual console (VC) or X desktop and continue using the computer as + normal. - + To finish the installation, the LFS-Bootscripts are set up in + , and the kernel and boot loader are set + up in . + contains information on furthering the LFS experience beyond this book. + After the steps in this book have been implemented, the computer will be + ready to reboot into the new LFS system. + + This is the process in a nutshell. Detailed information on each + step is discussed in the following chapters and package descriptions. + Items that may seem complicated will be clarified, and everything will + fall into place as the reader embarks on the LFS adventure. + diff --git a/chapter01/livecd.xml b/chapter01/livecd.xml index d76e58506..68c408c55 100644 --- a/chapter01/livecd.xml +++ b/chapter01/livecd.xml @@ -1,66 +1,106 @@ - %general-entities; ]> - -About the Included CD - -For your convenience, we have included a CD with this book that -contains the source packages needed for creating a Linux From Scratch -system. The CD is bootable and provides a stable working environment -for building LFS. This book refers to this system as the -host system. The CD images are actively maintained and -updated versions can be found at - + + -In addition to the tools required to build LFS, the host system -on the CD has a number of other helpful tools installed: + About the Included CD - - An HTML version of this book - The X Window System Environment - - Web Tools - - Wget (command line file retriever) - Lynx (text web browser) - Irssi (console IRC client) - Firefox (graphical web browser) - Xchat (X-based IRC client) - - + For your convenience, we have included a CD with this book that + contains the source packages needed for creating a Linux From Scratch + system. The CD is bootable and provides a stable working environment + for building LFS. This book refers to this system as the + host system. The CD images are actively maintained and + updated versions can be found at + - - Text Editors - - Vim - Nano - - + In addition to the tools required to build LFS, the host system + on the CD has a number of other helpful tools installed: - - Network Tools - - SSH Server and Client - NFS Server and Client - Smbmount (mount.cifs) for Windows shares - Subversion - Dhcpcd (DHCP client) - - + - - Filesystem Programs - - Reiserfsprogs - Xfsprogs - - + + An HTML version of this book + - nALFS - A tool for automating LFS builds - + + The X Window System Environment + - + + Web Tools + + + Wget (command line file retriever) + + + Lynx (text web browser) + + + Irssi (console IRC client) + + + Firefox (graphical web browser) + + + Xchat (X-based IRC client) + + + + + + Text Editors + + + Vim + + + Nano + + + + + + Network Tools + + + SSH Server and Client + + + NFS Server and Client + + + Smbmount (mount.cifs) for Windows shares + + + Subversion + + + Dhcpcd (DHCP client) + + + + + + Filesystem Programs + + + Reiserfsprogs + + + Xfsprogs + + + + + nALFS - A tool for automating LFS builds + + + + + diff --git a/chapter01/resources.xml b/chapter01/resources.xml new file mode 100644 index 000000000..de67308ff --- /dev/null +++ b/chapter01/resources.xml @@ -0,0 +1,91 @@ + + + %general-entities; +]> + + + + + Resources + + + FAQ + + If during the building of the LFS system you encounter any + errors, have any questions, or think there is a typo in the book, + please start by consulting the Frequently Asked Questions (FAQ) + that is located at . + + + + + Mailing Lists + + The linuxfromscratch.org server hosts a number of mailing + lists used for the development of the LFS project. These lists include the + main development and support lists, among others. If the FAQ does not solve + the problem you are having, the next step would be to search the mailing + lists at . + + For information on the different lists, how to subscribe, archive + locations, and additional information, visit + . + + + + + + + IRC + + Several members of the LFS community offer assistance on our + community Internet Relay Chat (IRC) network. Before using this support, + please make sure that your question is not already answered in the LFS + FAQ or the mailing list archives. You can find the IRC network at + irc.linuxfromscratch.org. The support channel is named + #LFS-support. + + + + + References + + For additional information on the packages, useful tips are + available in the LFS Package Reference page located at . + + + + + Mirror Sites + + The LFS project has a number of world-wide mirrors to make accessing + the website and downloading the required packages more convenient. Please + visit the LFS website at for a list + of current mirrors. + + + + + Contact Information + + Please direct all your questions and comments to one of the LFS + mailing lists (see above). + + + + diff --git a/chapter09/whatnow.xml b/chapter09/whatnow.xml index 445564e1a..8e7fa33c7 100644 --- a/chapter09/whatnow.xml +++ b/chapter09/whatnow.xml @@ -81,7 +81,7 @@ There are several LFS mailing lists you may subscribe to if you are in need of help, want to stay current with the latest developments, want to contribute to the project, and more. See for more + linkend="ch-intro-maillists"/> for more information. -- cgit v1.2.3-54-g00ecf