From 15b6ed42732e28bdc509ecf0ab9ed9c14915d153 Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Wed, 21 Jan 2004 22:15:22 +0000 Subject: Adding a few cross references. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3180 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/chapter06.xml | 24 ++++++++++++------------ chapter06/gcc.xml | 4 ++-- chapter06/makedev.xml | 8 ++++---- chapter06/mountproc.xml | 8 ++++---- 4 files changed, 22 insertions(+), 22 deletions(-) (limited to 'chapter06') diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml index 26e33a9d3..2797dcffc 100644 --- a/chapter06/chapter06.xml +++ b/chapter06/chapter06.xml @@ -273,11 +273,11 @@ with a GID of 1, be present. All other group names and GIDs can be chosen freely by the user, as well-written packages don't depend on GID numbers but use the group's name. -Lastly, we re-login to the chroot environment. User name and group name -resolution will start working immediately after the -/etc/passwd and /etc/group files are -created, because we installed a full Glibc in Chapter 5. This will get rid of -the I have no name! prompt. +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 +created the /etc/passwd and +/etc/group files, user name and group name resolution +will now work. exec /tools/bin/bash --login +h @@ -329,13 +329,13 @@ adjusted linker by running the following from within the make -C ld INSTALL=/tools/bin/install install If you somehow missed the earlier warning to retain the Binutils -source and build directories from the second pass in Chapter 5 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 than -/usr. This is not ideal, however, our -testing has shown that the resulting Binutils program binaries should be +source and build directories from the second pass in +, 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 +than /usr. This is not ideal, however, +our testing has shown that the resulting Binutils program binaries should be identical. From now on every compiled program will link only diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml index db2d3ab1b..9609b8713 100644 --- a/chapter06/gcc.xml +++ b/chapter06/gcc.xml @@ -37,7 +37,7 @@ compilers. Instructions for building these can be found at . Be careful not to apply the GCC -Specs patch from Chapter 5 here. +Specs patch from here. First apply the No-Fixincludes patch that we also used in the previous chapter: @@ -95,7 +95,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 -Chapter 5. +. diff --git a/chapter06/makedev.xml b/chapter06/makedev.xml index d48d57cfd..4b273d54e 100644 --- a/chapter06/makedev.xml +++ b/chapter06/makedev.xml @@ -48,10 +48,10 @@ Alternatively, you may create devices via the mknod program. Please refer to its man and info pages if you need more information. -Additionally, if you were unable to mount the devpts filesystem earlier in -the "Mounting the proc and devpts file systems" section, now is the time to -try the alternatives. If your kernel supports the devfs file system, run the -following command to mount devfs: +Additionally, if you were unable to mount the devpts filesystem earlier +in , now is the time to try the alternatives. If +your kernel supports the devfs file system, run the following command to mount +devfs: mount -t devfs devfs /dev diff --git a/chapter06/mountproc.xml b/chapter06/mountproc.xml index c9ce922ea..d9190e8ac 100644 --- a/chapter06/mountproc.xml +++ b/chapter06/mountproc.xml @@ -47,11 +47,11 @@ your kernel supports by peeking into its internals with a command such as cat /proc/filesystems. If a file system type named devfs is listed there, then we'll be able to work around the problem by mounting the host's devfs file system on top of the new -/dev structure which we'll create later on in the -"Creating devices (Makedev)" section. If devfs was not listed, do not worry +/dev structure which we'll create later on in the section +on . If devfs was not listed, do not worry because there is yet a third way to get PTYs working inside the chroot -environment. We'll cover this shortly in the aforementioned Makedev -section. +environment. We'll cover this shortly in the aforementioned + section. Remember, if for any reason you stop working on your LFS, and start again later, it's important to check that these filesystems are still mounted inside -- cgit v1.2.3-54-g00ecf