From 02974d8f1b3545815123a71af984aa9dc45d19ae Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Sun, 14 Mar 2004 21:53:12 +0000 Subject: [PATCH] Re-adding HOME to the chroot command, and a few textual shuffles. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3291 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter01/askforhelp.xml | 18 ++++--- chapter01/changelog.xml | 4 +- chapter02/askforhelp.xml | 104 --------------------------------------- chapter05/patch.xml | 2 +- chapter06/chapter06.xml | 29 ++++++----- chapter06/patch.xml | 2 +- chapter09/whatnow.xml | 31 +++++++----- index.xml | 4 +- 8 files changed, 52 insertions(+), 142 deletions(-) delete mode 100644 chapter02/askforhelp.xml diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml index c4f3fa47f..b04a8161b 100644 --- a/chapter01/askforhelp.xml +++ b/chapter01/askforhelp.xml @@ -1,13 +1,17 @@ How to ask for help - + -If you encounter a problem while using this book, and your problem -is not listed in the FAQ (), you will find that -most of the people on Internet Relay Chat (IRC) and on the mailing lists -are willing to help you (see . -To assist us in diagnosing and solving your problem, include as much relevant -information as possible in your request for help. +If you run into a problem while working through this book, you should +first check the FAQ at -- most likely your question +is already answered there. If it is not, you should try to find the source of +the problem. The following hint might give you some ideas for your +troubleshooting: . + +If all that fails, you will find that most people on IRC and the mailing +lists (see ) are willing to help +you. But to assist them in diagnosing and solving your problem, please include +all relevant information in your request for help. Things to mention diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index a704656bb..3793604b2 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -36,8 +36,8 @@ first a summary, then a detailed log. -March 9th, 2004 [alex]: Chapter 6 - Removed HOME and --login -from the chroot commands. +March 9th, 2004 [alex]: Chapter 6 - Removed --login from the +chroot commands. March 6th, 2004 [alex]: Rotated the contents of chapters 2, 3 and 4. diff --git a/chapter02/askforhelp.xml b/chapter02/askforhelp.xml deleted file mode 100644 index 54c65f943..000000000 --- a/chapter02/askforhelp.xml +++ /dev/null @@ -1,104 +0,0 @@ - -How to ask for help - - -If you encounter a problem while using this book, and your problem -is not listed in the FAQ (), you will find that -most of the people on Internet Relay Chat (IRC) and on the mailing lists -are willing to help you. An overview of the LFS mailing lists can be -found via . To assist us in -diagnosing and solving your problem, include as much relevant -information as possible in your request for help. - - -Things to mention - -Apart from a brief explanation of the problem you're having, the -essential things to include in your request are: - - -the version of the book you are using (being &version;), -the host distribution and version you are using to create -LFS from, -the package or section giving you problems, -the exact error message or symptom you are receiving, -whether you have deviated from the book at all. - - -(Note that saying that you've deviated from the book doesn't mean -that we won't help you. After all, LFS is about choice. It'll just -help us to see other possible causes of your problem.) - - - - -Configure problems - -When something goes wrong during the stage where the configure script -is run, look through the config.log file. This file -may contain errors encountered during configure which weren't printed to -the screen. Include those relevant lines if you decide to ask for -help. - - - - -Compile problems - -To help us find the cause of the problem, both screen output and -the contents of various files are useful. The screen output from both -the ./configure script and the make run can be useful. Don't blindly -include the whole thing but on the other hand, don't include too little. -As an example, here is some screen output from make: - -gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" --DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\" --DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I. --g -O2 -c getopt1.c -gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o -function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o -signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o --lutil job.o: In function `load_too_high': -/lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg' -collect2: ld returned 1 exit status -make[2]: *** [make] Error 1 -make[2]: Leaving directory `/lfs/tmp/make-3.79.1' -make[1]: *** [all-recursive] Error 1 -make[1]: Leaving directory `/lfs/tmp/make-3.79.1' -make: *** [all-recursive-am] Error 2 - -In this case, many people just include the bottom section where it -says: - -make [2]: *** [make] Error 1 - -and onwards. This isn't enough for us to diagnose the problem because it -only tells us that something went wrong, not -what went wrong. The whole section, as in the example -above, is what should be included to be helpful, because it includes the -command that was executed and the command's error message(s). - -An excellent article on asking for help on the Internet in general -has been written by Eric S. Raymond. It is available online at . -Read and follow the hints in that document and you are much more likely -to get a response to start with and also to get the help you actually -need. - - - - -Test suite problems - -Many packages provide a test suite which, depending on the importance -of the package, we may encourage you to run. Sometimes packages will -generate false or expected failures. If you encounter these, you can check -the LFS Wiki page at to see whether we have -already noted and investigated them. If we already know -about them, then usually there is no need to be concerned. - - - - - - diff --git a/chapter05/patch.xml b/chapter05/patch.xml index d927b0327..67ce2da5c 100644 --- a/chapter05/patch.xml +++ b/chapter05/patch.xml @@ -13,7 +13,7 @@ Installation of Patch -Prepare Patch for compilation (the preprocessor flag +Prepare Patch for compilation (setting the preprocessor flags to -D_GNU_SOURCE is only needed on the PowerPC platform, on other architectures you can leave it out): diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml index da1ae8126..953fb3233 100644 --- a/chapter06/chapter06.xml +++ b/chapter06/chapter06.xml @@ -129,18 +129,21 @@ the following command to enter the small world that is, at the moment, populated with only the temporary tools: chroot $LFS /tools/bin/env -i \ -    TERM=$TERM PS1='\u:\w\$ ' \ +    HOME=/root TERM=$TERM PS1='\u:\w\$ ' \     PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \     /tools/bin/bash +h -The -i option given to the -env command will clear all variables of the chroot -environment. After that, only the TERM, PS1 and PATH variables are -set again. The TERM=$TERM construct will set the TERM variable inside chroot -to the same value as outside chroot; this variable is needed for programs -like less and vim to operate -properly. If you need other variables present, such as CFLAGS, CXXFLAGS or -HOME, this is a good place to set them. +The -i option passed to the env +command will clear all variables of the chroot environment. After that, only +the HOME, TERM, PS1 and PATH variables are set again. The HOME variable is set +mainly to prevent several small warnings during the configure runs of +Diffutils, Grep and Grub. The TERM variable is set to make programs such as +less and vim, that make use of the +Ncurses package, operate properly -- the TERM=$TERM construct sets the TERM +variable inside chroot to the same value as outside chroot. The main prompt +(PS1) is set to "username:working-dir# " (since the "\$" becomes "#" for root). +If you need other variables present, such as CFLAGS, CXXFLAGS or LDFLAGS, this +is a good place to set them. From this point on there's no need to use the LFS variable anymore, because everything you do will be restricted to the LFS file system -- since @@ -402,7 +405,9 @@ Some host distributions contain a ginstall symbolic link which takes precedence in the Makefile and thus can cause a problem here. The above command takes care of this also. -You can now remove the Binutils source and build directories. +You must now remove the Binutils source and build directories. (This is +important, as you should start the next section with a fresh untarring of the +package.) The next thing to do is to amend our GCC specs file so that it points to the new dynamic linker. Just like earlier on, we use a sed to accomplish @@ -580,7 +585,7 @@ If you're not sure whether you entered chroot with the command given in Then reenter it with: chroot $LFS /tools/bin/env -i \ -    TERM=$TERM PS1='\u:\w\$ ' \ +    HOME=/root TERM=$TERM PS1='\u:\w\$ ' \     PATH=/bin:/usr/bin:/sbin:/usr/sbin \     /tools/bin/bash @@ -610,7 +615,7 @@ destroyed. it, you should use the following modified chroot command: chroot $LFS /usr/bin/env -i \ -    TERM=$TERM PS1='\u:\w\$ ' \ +    HOME=/root TERM=$TERM PS1='\u:\w\$ ' \     PATH=/bin:/usr/bin:/sbin:/usr/sbin \     /bin/bash diff --git a/chapter06/patch.xml b/chapter06/patch.xml index 8a8be965a..8ff7e4c69 100644 --- a/chapter06/patch.xml +++ b/chapter06/patch.xml @@ -15,7 +15,7 @@ Installation of Patch -Prepare Patch for compilation (the preprocessor flag +Prepare Patch for compilation (setting the preprocessor flags to -D_GNU_SOURCE is only needed on PowerPCs, on other machines you can leave it out): diff --git a/chapter09/whatnow.xml b/chapter09/whatnow.xml index e39a814e6..4fdae39cc 100644 --- a/chapter09/whatnow.xml +++ b/chapter09/whatnow.xml @@ -2,37 +2,42 @@ What now? -We thank you for reading the LFS Book and hope that you've found this -book useful and worth your time. +Thank you for reading the LFS Book. We hope that you've found this book +useful and worth your time. Now that you have finished installing your LFS system, you may be -wondering "What now?". In order to answer that question, we have composed a -list of resources for you. +wondering what to do next. As an answer to that question we have composed a +short list of resources: Beyond Linux From Scratch -The Beyond Linux From Scratch book covers installation procedures -for a wide range of software beyond the scope of the LFS Book. The BLFS -project can be found at . +If you want extra utilities for your LFS system, there is the Beyond +Linux From Scratch book for you. It covers the installation procedures of many +different packages beyond the scope of the LFS book. Among them are +general libraries, programming languages, graphical desktops, multimedia, +networking and printing. The BLFS project can be found at +. LFS Hints -The LFS Hints are a collection of small, educational documents -submitted by volunteers in the LFS community. The Hints are available at -. +The LFS Hints are a collection of educational documents, often small, +submitted by volunteers in the LFS community. They cover subjects ranging from +dependencies to UTF-8 locales, from optimization to uGlibc, and from cloning to +TZ. The Hints are available at . Mailing lists -There are several LFS mailing lists you may subscribe to if you are -in need of help. See for more +There are several LFS mailing lists you may subscribe to if you want to +help develop the book further, assist others to build their systems, or are in +need of help yourself. See for more information. The Linux Documentation Project The goal of the Linux Documentation Project is to collaborate in all of the issues of Linux documentation. The LDP features a large collection -of HOWTOs, Guides and man pages; it may be found at +of HOWTOs, Guides and man pages, and can be found at . diff --git a/index.xml b/index.xml index aa0df7cc6..00b477a1c 100644 --- a/index.xml +++ b/index.xml @@ -2,8 +2,8 @@ - + +