diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml index b0b4cd210..ea37d74cc 100644 --- a/chapter01/changelog.xml +++ b/chapter01/changelog.xml @@ -6,6 +6,10 @@ +February 5th, 2004 [alex]: Chapter 6 - Simplified the final +install of the kernel headers to just copying them from the temporary tools +directory. + February 4th, 2004 [alex]: Chapters 5 + 6 - Moved the Mounting of proc and devpts to before Chrooting, dropped Util-linux from the tools, and added a little arch script for Perl. diff --git a/chapter01/chapter01.xml b/chapter01/chapter01.xml index 17bf587f8..7eb9aec66 100644 --- a/chapter01/chapter01.xml +++ b/chapter01/chapter01.xml @@ -4,7 +4,6 @@ &c1-how; &c1-conventions; -&c1-version; &c1-changelog; &c1-resources; &c1-acknowledgements; diff --git a/chapter04/chapter04.xml b/chapter04/chapter04.xml index 79e770ccd..b5ed2a808 100644 --- a/chapter04/chapter04.xml +++ b/chapter04/chapter04.xml @@ -100,7 +100,7 @@ Ed (&ed-version;) - &ed-size;: Expect (&expect-version;) - &expect-size;: -File (&file-version;) - &file-size;: -- (see Note 1 below) +File (&file-version;) - &file-size;: -- (see Note 1 below) Findutils (&findutils-version;) - &findutils-size;: @@ -127,7 +127,7 @@ GCC-testsuite (&gcc-version;) - &gcc-testsuite-size;: Gettext (&gettext-version;) - &gettext-size;: -Glibc (&glibc-version;) - &glibc-size;: -- (see Note 2 below) +Glibc (&glibc-version;) - &glibc-size;: -- (see Note 2 below) Grep (&grep-version;) - &grep-size;: @@ -253,7 +253,7 @@ tar jcvf &glibc-package; &glibc-dir; Alternatively, we've made our own tarball available which you can download courtesy of the generous LFS mirror sites. Please refer to the - section for the download links. + section for the download links. diff --git a/chapter05/kernelheaders.xml b/chapter05/kernelheaders.xml index adc7a668d..67636e622 100644 --- a/chapter05/kernelheaders.xml +++ b/chapter05/kernelheaders.xml @@ -42,13 +42,6 @@ cp -R include/asm-generic /tools/include cp -R include/linux /tools/include -There are a few kernel header files which make use of the -autoconf.h header file. Since we do not yet configure the -kernel, we need to create this file ourselves in order to avoid compilation -failures. Create an empty autoconf.h file: - -touch /tools/include/linux/autoconf.h - diff --git a/chapter05/perl.xml b/chapter05/perl.xml index 7251700c1..d6633ce75 100644 --- a/chapter05/perl.xml +++ b/chapter05/perl.xml @@ -18,7 +18,7 @@ patch -Np1 -i ../&perl-libc-patch; Perl insists on using the arch program to find out -the machine type. Create a little script to mimick this command: +the machine type. Create a little script to mimic this command: echo "uname -m" > /tools/bin/arch chmod 755 /tools/bin/arch diff --git a/chapter06/mountproc.xml b/chapter06/mountproc.xml index 381786f57..876dbd5c5 100644 --- a/chapter06/mountproc.xml +++ b/chapter06/mountproc.xml @@ -4,34 +4,34 @@ In order for certain programs to function properly, the proc and devpts file systems must be -available within the chroot environment. Since kernel version 2.4 a file system -can be mounted as many times and in as many places as you like, thus it's not a -problem that these file systems are already mounted on your host system, -especially so because they are virtual file systems. +available within the chroot environment. The proc file system is the process +information pseudo file system through which the kernel provides information +about the status of the system. And the devpts file system is nowadays the most +common way pseudo terminals (PTYs) are implemented. Since kernel version 2.4, a +file system can be mounted as many times and in as many places as you like, +thus it's not a problem that these file systems are already mounted on your +host system, especially so because they are virtual file systems. -First make the mount points for these filesystems: +First become root, as only root +can mount file systems in unusual places. Then check again that the LFS +environment variable is set correctly by running echo +$LFS and making sure it shows the path to your LFS partition's +mount point, which is /mnt/lfs if you +followed our example. + +Now make the mount points for these filesystems: mkdir -p $LFS/{proc,dev/pts} -Now become root, since only -root can mount file systems in unusual places. Then -check again that the LFS environment variable is set correctly by running -echo $LFS and making sure it shows the path to your LFS -partition's mount point, which is /mnt/lfs if you followed our example. - -The proc file system is the process information -pseudo file system through which the kernel provides information about the -status of the system. Mount it with: +Mount the proc file system with: mount proc $LFS/proc -t proc -The devpts file system is now the most common way -for pseudo terminals (PTYs) to be implemented. Mount it with: +And mount the devpts file system with: mount devpts $LFS/dev/pts -t devpts -This last command might fail with an error to the effect of: +This last command might fail with an error like:
filesystem devpts not supported by kernel
@@ -47,9 +47,9 @@ because there is yet a third way to get PTYs working inside the chroot 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 file systems are mounted again before -entering the chroot environment, otherwise some problems could occur. +Remember that if for any reason you stop working on your LFS, and start +again later, it's important to check that these file systems are mounted again +before entering the chroot environment, otherwise problems could occur. diff --git a/entities/book-structure.xml b/entities/book-structure.xml index e42cb7160..6147befbc 100644 --- a/entities/book-structure.xml +++ b/entities/book-structure.xml @@ -7,7 +7,6 @@ - @@ -55,6 +54,5 @@ -