diff --git a/chapter01/how.xml b/chapter01/how.xml index 12c17db6e..c5fb2f96b 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -9,26 +9,26 @@ programs like a compiler, linker and shell to build the new system. Normally all the required tools are available if you selected development as one of the options when you installed your distribution. -In you will first create a new Linux native +In you will first create a new Linux native partition and file system, the place where your new LFS system will be compiled -and installed. Then in you download all the +and installed. Then in you download all the packages and patches required to build an LFS system, and store them on the new file system. - then discusses the installation of a number + then discusses 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 +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. -The first thing to be done in is build a +The first thing to be done in is build a first pass of the toolchain, made up of Binutils and GCC. The programs from these packages will be linked statically in order for them to be usable independently of the host system. The second thing to do is build Glibc, the C library. Glibc will be compiled by the toolchain programs we just built in the first pass. The third thing to do is build a second pass of the toolchain. This time the toolchain will be dynamically linked against the newly built -Glibc. The remaining packages are all built using +Glibc. The remaining packages are all built using this second pass toolchain and dynamically linked against the new host-independent Glibc. When this is done, the LFS installation process will no longer depend on the host distribution, with the exception of the running @@ -36,10 +36,10 @@ kernel. You may be thinking that this seems like a lot of work, just to get away from my host distribution. Well, a full technical explanation -is provided at the start of , including some notes +is provided at the start of , including some notes on the differences between statically and dynamically linked programs. -In your real LFS system will be built. The +In your real LFS system will be 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 @@ -52,8 +52,8 @@ Console) or X desktop and continue using the computer as you normally would. To finish the installation, the bootscripts are set up in -, the kernel and bootloader are set up in -, and contains some +, the kernel and bootloader are set up in +, and contains some pointers to help you after you finish the book. Then, finally, you're ready to reboot your computer into your new LFS system. @@ -62,9 +62,9 @@ will take are discussed in the chapters and package descriptions as you progress through them. If something isn't completely clear now, don't worry, everything will fall into place soon. -Please read carefully as it explains a few +Please read carefully as it explains a few important things you should be aware of before you begin to work through - and beyond. + and beyond. diff --git a/chapter02/aboutlfs.xml b/chapter02/aboutlfs.xml index ff1ecf0e0..7aac118ba 100644 --- a/chapter02/aboutlfs.xml +++ b/chapter02/aboutlfs.xml @@ -6,7 +6,7 @@ variable LFS will be used frequently. $LFS must at all times be replaced with the directory where the partition that contains the LFS system is mounted. How to create and where to mount the partition will be explained in full detail in -. For the moment let's assume that the LFS partition +. For the moment let's assume that the LFS partition is mounted on /mnt/lfs. When you are told to run a command like diff --git a/chapter02/aboutsbus.xml b/chapter02/aboutsbus.xml index d1a7485e5..cf2685e70 100644 --- a/chapter02/aboutsbus.xml +++ b/chapter02/aboutsbus.xml @@ -12,7 +12,7 @@ with the idea of using the Static Binutils Unit (abbreviated to SBU). It works like this: the first package you compile in this book is the -statically linked Binutils in , and the time it +statically linked Binutils in , and the time it takes to compile this package is what we call the "Static Binutils Unit" or "SBU". All other compile times will be expressed relative to this time. diff --git a/chapter02/abouttestsuites.xml b/chapter02/abouttestsuites.xml index 258f35352..e580a9a79 100644 --- a/chapter02/abouttestsuites.xml +++ b/chapter02/abouttestsuites.xml @@ -16,12 +16,12 @@ properly functioning system. But be warned, the test suites for GCC and Glibc can take a very long time to complete, especially on slower hardware. Experience has shown us that there is little to be gained from running -the test suites in . There can be no escaping the +the test suites in . There can be no escaping the fact that the host system always exerts influence on the tests in that chapter, often causing weird and inexplicable failures. Not only that, the tools built -in are temporary and eventually discarded. For the +in are temporary and eventually discarded. For the average reader of this book we recommend not to run the -test suites in . The instructions for running those +test suites in . The instructions for running those test suites are still provided for the benefit of testers and developers, but they are strictly optional for everyone else. @@ -35,7 +35,7 @@ is running out of pseudo terminals (PTYs for short). The symptom is an unusually high number of failing tests. This can happen for a number of reasons. Most likely is that the host system doesn't have the devpts file system set up correctly. We'll discuss this in -more detail later on in . +more detail later on in . diff --git a/chapter02/chapter02.xml b/chapter02/chapter02.xml index 3265cac98..9d6956300 100644 --- a/chapter02/chapter02.xml +++ b/chapter02/chapter02.xml @@ -1,4 +1,4 @@ - + Important information diff --git a/chapter03/chapter03.xml b/chapter03/chapter03.xml index 9f59c60e1..cdbe189d6 100644 --- a/chapter03/chapter03.xml +++ b/chapter03/chapter03.xml @@ -1,4 +1,4 @@ - + Preparing a new partition diff --git a/chapter04/chapter04.xml b/chapter04/chapter04.xml index f2770f786..79e770ccd 100644 --- a/chapter04/chapter04.xml +++ b/chapter04/chapter04.xml @@ -1,4 +1,4 @@ - + The materials: packages and patches diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml index a2734acc8..8e5699990 100644 --- a/chapter05/chapter05.xml +++ b/chapter05/chapter05.xml @@ -1,4 +1,4 @@ - + Constructing a temporary system @@ -71,10 +71,10 @@ details behind the overall build method. It's not essential that you understand everything here immediately. Most of it will make sense once you have performed an actual build. Feel free to refer back here at any time. -The overall goal of is to provide a sane, +The overall goal of is to provide a sane, temporary environment that we can chroot into, and from which we can produce a clean, trouble-free build of the target LFS system in -. Along the way, we attempt to divorce ourselves +. Along the way, we attempt to divorce ourselves from the host system as much as possible, and in so doing build a self-contained and self-hosted toolchain. It should be noted that the build process has been designed in such a way so as to minimize the risks for @@ -109,7 +109,7 @@ the shlib-versions file in the root of the Glibc source tree. -Some key technical points of how the build +Some key technical points of how the build method works: @@ -207,10 +207,10 @@ would defeat our goal of getting away from the host. --with-lib-path configure switch to control ld's library search path. From this point onwards, the core toolchain is self-contained and self-hosted. The remainder of the - packages all build against the new Glibc in + packages all build against the new Glibc in /tools and all is well. -Upon entering the chroot environment in , the +Upon entering the chroot environment in , the first major package we install is Glibc, due to its self-sufficient nature that we mentioned above. Once this Glibc is installed into /usr, we perform a quick changeover of diff --git a/chapter05/gcc-pass2.xml b/chapter05/gcc-pass2.xml index 462f92f0b..b8dcbaa60 100644 --- a/chapter05/gcc-pass2.xml +++ b/chapter05/gcc-pass2.xml @@ -50,7 +50,7 @@ process is warranted here. Under normal circumstances, the GCC fixincludes script scans your system for header files that need to be fixed. It might find that some Glibc header files on your host system need to be fixed, fix them and put them in the GCC private include directory. Then, later on in -, after we've installed the newer Glibc, this +, after we've installed the newer Glibc, this private include directory would be searched before the system include directory, resulting in GCC finding the fixed headers from the host system, which would most likely not match the Glibc version actually used for the LFS diff --git a/chapter05/glibc.xml b/chapter05/glibc.xml index 5b5f1d77e..1340cc9c0 100644 --- a/chapter05/glibc.xml +++ b/chapter05/glibc.xml @@ -90,7 +90,7 @@ so: system, in particular the kernel. Additionally, here in this chapter some tests can be adversely affected by existing tools or environmental issues on the host system. Of course, these won't be a problem when we run the Glibc test suite -inside the chroot environment of . In general, the +inside the chroot environment of . In general, the Glibc test suite is always expected to pass. However, as mentioned above, some failures are unavoidable in certain circumstances. Here is a list of the most common issues we are aware of: @@ -117,9 +117,9 @@ fail due to test timeouts being exceeded. In summary, don't worry too much if you see Glibc test suite failures -here in this chapter. The Glibc in is the one we'll +here in this chapter. The Glibc in is the one we'll ultimately end up using so that is the one we would really like to see pass. -But please keep in mind, even in some failures +But please keep in mind, even in some failures could still occur -- the math tests for example. When experiencing a failure, make a note of it, then continue by reissuing the make check. The test suite diff --git a/chapter05/tcl.xml b/chapter05/tcl.xml index 4788f3875..1668a895d 100644 --- a/chapter05/tcl.xml +++ b/chapter05/tcl.xml @@ -48,7 +48,7 @@ here are not surprising, but are not considered critical: Coordinated Universal Time (UTC) also known as Greenwich Mean Time (GMT), but only for the duration of the test suite run. This ensures the clock tests are exercised correctly. More information on the TZ environment variable will be -given later on in . +given later on in . Sometimes package test suites will give false failures. You can diff --git a/chapter06/aboutdebug.xml b/chapter06/aboutdebug.xml index ccf05b83e..6708deb54 100644 --- a/chapter06/aboutdebug.xml +++ b/chapter06/aboutdebug.xml @@ -41,7 +41,7 @@ or ELF binary), run strip --strip-debug filename. Wildcards can be used to treat multiple files (use something like strip --strip-debug $LFS/tools/bin/*). -For your convenience, includes one simple +For your convenience, includes one simple command to strip all debugging symbols from all programs and libraries on your system. Additional information on optimization can be found in the hint at . diff --git a/chapter06/bootscripts.xml b/chapter06/bootscripts.xml index bb2a511ab..159470d1f 100644 --- a/chapter06/bootscripts.xml +++ b/chapter06/bootscripts.xml @@ -23,7 +23,7 @@ like something more radical, search the LFS mailing lists for depinit. If you decide to use BSD style, or some other style scripts, you can skip the next chapter when you arrive at it and move on to -. +. Install the boot scripts: diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml index ef78e75e7..44ec75c9e 100644 --- a/chapter06/chapter06.xml +++ b/chapter06/chapter06.xml @@ -1,4 +1,4 @@ - + Installing basic system software @@ -269,7 +269,7 @@ freely by the user, as well-written packages don't depend on GID numbers but use the group's name. To get rid of the "I have no name!" prompt, we will start a new shell. -Since we installed a full Glibc in , and have just +Since we installed a full Glibc in , and have just created the /etc/passwd and /etc/group files, user name and group name resolution will now work. @@ -325,7 +325,7 @@ adjusted linker by running the following from within the If you somehow missed the earlier warning to retain the Binutils source and build directories from the second pass in -, or otherwise accidentally deleted them or just +, or otherwise accidentally deleted them or just don't have access to them, don't worry, all is not lost. Just ignore the above command. The result will be that the next package, Binutils, will link against the Glibc libraries in /tools rather diff --git a/chapter06/gcc-2953.xml b/chapter06/gcc-2953.xml index e79db7dbf..171c4d908 100644 --- a/chapter06/gcc-2953.xml +++ b/chapter06/gcc-2953.xml @@ -28,7 +28,7 @@ default optimizations, such as CFLAGS and CXXFLAGS, we recommend unsetting or modifying them when building GCC. This is an older release of GCC which we are going to install for the -purpose of compiling the Linux kernel in . This +purpose of compiling the Linux kernel in . This version is recommended by the kernel developers when you need absolute stability. Later versions of GCC have not received as much testing for Linux kernel compilation. Using a diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml index 824307bd6..7cf0f81a4 100644 --- a/chapter06/gcc.xml +++ b/chapter06/gcc.xml @@ -92,7 +92,7 @@ compiler. To satisfy those packages, create a symlink: we performed earlier in this chapter. Refer back to and repeat the check. If the results are wrong, then most likely you erroneously applied the GCC Specs patch from -. +. diff --git a/chapter07/chapter07.xml b/chapter07/chapter07.xml index c85b1d60c..7e07e8ecd 100644 --- a/chapter07/chapter07.xml +++ b/chapter07/chapter07.xml @@ -1,4 +1,4 @@ - + Setting up system boot scripts diff --git a/chapter07/loadkeys.xml b/chapter07/loadkeys.xml index 2a864c088..770c307d7 100644 --- a/chapter07/loadkeys.xml +++ b/chapter07/loadkeys.xml @@ -3,7 +3,7 @@ If you decided to compile your keymap file directly into the kernel back -at the end of , then you strictly speaking don't +at the end of , then you strictly speaking don't need to run this loadkeys script, since the kernel has already set up the keymap for you. You can still run it if you want, it isn't going to hurt you. It could even be beneficial to keep it in case you run a lot of different diff --git a/chapter08/chapter08.xml b/chapter08/chapter08.xml index 258d394f7..b83bf7691 100644 --- a/chapter08/chapter08.xml +++ b/chapter08/chapter08.xml @@ -1,4 +1,4 @@ - + Making the LFS system bootable diff --git a/chapter09/chapter09.xml b/chapter09/chapter09.xml index bb04f7f52..10af4f606 100644 --- a/chapter09/chapter09.xml +++ b/chapter09/chapter09.xml @@ -1,4 +1,4 @@ - + The End