diff options
| -rw-r--r-- | chapter05/bash.xml | 2 | ||||
| -rw-r--r-- | chapter06/db.xml | 2 | ||||
| -rw-r--r-- | chapter06/findutils.xml | 4 | ||||
| -rw-r--r-- | chapter06/glibc.xml | 6 | ||||
| -rw-r--r-- | chapter06/kernfs.xml | 2 | ||||
| -rw-r--r-- | chapter07/network.xml | 2 | ||||
| -rw-r--r-- | chapter07/symlinks.xml | 4 |
7 files changed, 11 insertions, 11 deletions
diff --git a/chapter05/bash.xml b/chapter05/bash.xml index 4461fcb7e..87093c89b 100644 --- a/chapter05/bash.xml +++ b/chapter05/bash.xml @@ -41,7 +41,7 @@ release of Bash-&bash-version;. Apply those fixes:</para> <screen><userinput>patch -Np1 -i ../&bash-fixes-patch;</userinput></screen> - + <para>Prepare Bash for compilation:</para> <screen><userinput>./configure --prefix=/tools --without-bash-malloc</userinput></screen> diff --git a/chapter06/db.xml b/chapter06/db.xml index 7f16b8317..a2f85080a 100644 --- a/chapter06/db.xml +++ b/chapter06/db.xml @@ -56,7 +56,7 @@ <title>Installation of Berkeley DB</title> <para>Patch the package to eliminate potential trap events:</para> - + <screen><userinput>patch -Np0 -i ../&db-trap-patch;</userinput></screen> <para>Prepare Berkeley DB for compilation:</para> diff --git a/chapter06/findutils.xml b/chapter06/findutils.xml index baa82c191..1fe6d792a 100644 --- a/chapter06/findutils.xml +++ b/chapter06/findutils.xml @@ -71,11 +71,11 @@ <command>find</command>. As <filename class="directory">/usr</filename> may not be available during the early stages of booting, this program needs to be on the root partition. The <command>updatedb</command> - script also needs to be modified to correct an explicit path:</para> + script also needs to be modified to correct an explicit path:</para> <screen><userinput>mv -v /usr/bin/find /bin</userinput> sed -i -e 's/find:=${BINDIR}/find:=\/bin/' /usr/bin/updatedb</screen> - + </sect2> <sect2 id="contents-findutils" role="content"> diff --git a/chapter06/glibc.xml b/chapter06/glibc.xml index b055ddf01..eb6d8d080 100644 --- a/chapter06/glibc.xml +++ b/chapter06/glibc.xml @@ -135,8 +135,8 @@ grep Error glibc-check-log</userinput></screen> <itemizedlist> <listitem> - <para>The <emphasis>nptl/tst-clock2</emphasis> and - <emphasis>tst-attr3</emphasis> tests sometimes + <para>The <emphasis>nptl/tst-clock2</emphasis> and + <emphasis>tst-attr3</emphasis> tests sometimes fail. The reason is not completely understood, but indications are that a heavy system load can trigger these failures.</para> </listitem> @@ -266,7 +266,7 @@ EOF</userinput></screen> class='directory'>/usr/share/zoneinfo</filename> such as <emphasis>Canada/Eastern</emphasis> or <emphasis>EST5EDT</emphasis> that are not identified by the script but can be used.</para> - + <para>Then create the <filename>/etc/localtime</filename> file by running:</para> diff --git a/chapter06/kernfs.xml b/chapter06/kernfs.xml index 034d60422..1570de4be 100644 --- a/chapter06/kernfs.xml +++ b/chapter06/kernfs.xml @@ -62,7 +62,7 @@ mknod -m 666 $LFS/dev/null c 1 3</userinput></screen> <screen><userinput>mount --bind /dev $LFS/dev</userinput></screen> </sect2> - + <sect2 id="ch-system-kernfsmount"> <title>Mounting Virtual Kernel File Systems</title> diff --git a/chapter07/network.xml b/chapter07/network.xml index 91954bba8..3e8a4ad36 100644 --- a/chapter07/network.xml +++ b/chapter07/network.xml @@ -55,7 +55,7 @@ EOF</userinput></screen> <!-- Yes, I know that VLANs are beyond BLFS. This is not the reason to get them incorrect by default when every distro does this right. --> - + <para>If you are going to use the bus position as a key, create Udev rules similar to the following:</para> diff --git a/chapter07/symlinks.xml b/chapter07/symlinks.xml index c3e799867..f807f5bd2 100644 --- a/chapter07/symlinks.xml +++ b/chapter07/symlinks.xml @@ -49,10 +49,10 @@ EOF</userinput></screen> <para>The SUBSYSTEM=="block" key is needed in order to avoid matching SCSI generic devices. Without it, in the case with SCSI - CD-ROMs, the symlinks will sometimes point to the correct + CD-ROMs, the symlinks will sometimes point to the correct <filename>/dev/srX</filename> devices, and sometimes to <filename>/dev/sgX</filename>, which is wrong.</para> - + <para>The second approach yields:</para> <screen role="nodump"><userinput>cat >/etc/udev/rules.d/82-cdrom.rules <<"EOF" |