Fixed some minor typos

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1844 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Marc Heerdink 2002-04-21 13:01:52 +00:00
parent cdfd845cb8
commit 921ef9fb97
9 changed files with 10 additions and 10 deletions

View File

@ -42,7 +42,7 @@ available.</para></sect4>
textual message whose grammatical form depends on a number.</para></sect4>
<sect4><title>xgettext</title>
<para>The xgettext program extracts the message lines from the programers c
<para>The xgettext program extracts the message lines from the programmers' C
files. It's used to make the first translation template.</para></sect4>
</sect3>

View File

@ -21,7 +21,7 @@ mirror.</para></listitem>
<listitem><para><ulink url="mailto:hrx@hrxnet.de">Hagen Herrschaft</ulink>
&lt;hrx@hrxnet.de&gt; for running the de.linuxfromscratch.org
mirrors, and for his donation of a P4-2.2Ghz system to the LFS
mirrors, and for his donation of a P4-2.2GHz system to the LFS
project.</para></listitem>
<listitem><para><ulink url="mailto:tech-staff@mirror.ac.uk">UK Mirror

View File

@ -113,7 +113,7 @@ installation.</para></listitem>
<listitem><para>April 3rd, 2002 [gerard]: Chapter 06 - Bzip2: Reversed the
<userinput>make</userinput> and <userinput>make -f
Makefile-libbz2_so</userinput>. This is needed so all object files are
compiled with the PIC option (Position Independant Code).</para></listitem>
compiled with the PIC option (Position Independent Code).</para></listitem>
<listitem><para>April 3rd, 2002 [gerard]: Chapter 05 - Linux: Shortened the
installation instructions by cutting out the <userinput>make
@ -196,7 +196,7 @@ systems.</para></listitem>
<listitem><para>March 11th, 2002 [gerard]: Chapter 06 - Bzip2: Before
installing, remove <filename>/usr/bin/bz*</filename>. The bzip2
installation doens't deal with existing files properly when making hard
installation doesn't deal with existing files properly when making hard
links, so we remove the files first.</para></listitem>
<listitem><para>March 10th, 2002 [gerard]: Chapter 06 - Configure keyboard:

View File

@ -22,7 +22,7 @@ This command copies the cross-platform kernel header files to
<filename>$LFS/usr/include</filename></para>
<para><userinput>touch $LFS/usr/include/linux/autoconf.h</userinput>: Some
kernel header files include this <filename>autconf.h</filename> file, but
kernel header files include this <filename>autoconf.h</filename> file, but
outside the Linux source tree, that file has no meaning so we just create
an empty one so we don't get compile errors whenever it happens to be a
dependency of another kernel header file.</para>

View File

@ -24,7 +24,7 @@ separate file, which is loaded only when the program needs it. This is what
we call dynamically linked, as the library is loaded and unloaded dynamically,
as the program needs it.</para>
<para>So now we have a 1kb file and a 2.5MB file, but we still haven't saved any
<para>So now we have a 1KB file and a 2.5MB file, but we still haven't saved any
space (except maybe RAM until the library is needed). The REAL advantage to
dynamically linked libraries is that we only need one copy of the library.
If <filename>ls</filename> and <filename>rm</filename> both use the same

View File

@ -8,7 +8,7 @@ scripts at <ulink
url="&hints-root;bsd-init.txt">&hints-root;bsd-init.txt</ulink>.</para>
<para>If you decide to use BSD style, or some other style scripts, you can
skip chapter 7 when you arive at it and move on to chapter 8.</para>
skip chapter 7 when you arrive at it and move on to chapter 8.</para>
<para>Install LFS-Bootscripts by running the following command:</para>

View File

@ -21,7 +21,7 @@ programs try to link using -lcurses instead of -lncurses. This symlink
ensures that such programs will link without errors.</para>
<para><userinput>ln -sf ../../lib/libncurses.so etc:</userinput> These
symlinks are created to tidy up the installation. It's good practise to
symlinks are created to tidy up the installation. It's good practice to
have the *.so files in /usr/lib as well as in /lib, to ensure that the
linker is always able to find the files whether it's looking in /lib or
/usr/lib.</para>

View File

@ -6,7 +6,7 @@ the system) the init program is going to send the TERM and KILL signals
to all the processes that init started. But init prints a message to the
screen saying "sending all processes the TERM signal" and the same for the
KILL signal. This seems to imply that init sends this signal to all the
currently running processes, bu this isn't the case. To avoid this
currently running processes, but this isn't the case. To avoid this
confusion, you can change the init.c file so that the sentence reads
"sending all processes started by init the TERM signal" by running the
following commands. If you don't want to change it, skip it.</para>

View File

@ -5,7 +5,7 @@
<para>This chapter will setup the bootscripts that you installed in chapter
6. Most of these scripts will work without needing to modify them, but a
few do require additional configuration files setup as they deal with
hardware dependant information.</para>
hardware dependent information.</para>
</sect1>