gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

spelling corrections

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1572 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Mark Hymers 2002-02-14 14:58:00 +00:00
parent b1623f661d
commit 8f9069b37b
5 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter01/acknowledgements.xml
View File

@ -83,8 +83,8 @@ linuxfromscratch.com domain names.</para></listitem>
<listitem><para><ulink url="mailto:bkenoah@oswd.org">Frank <listitem><para><ulink url="mailto:bkenoah@oswd.org">Frank
Skettino</ulink> &lt;bkenoah@oswd.org&gt; at <ulink Skettino</ulink> &lt;bkenoah@oswd.org&gt; at <ulink
url="http://www.oswd.org">OSWD</ulink> for coming up the initial design url="http://www.oswd.org">OSWD</ulink> for coming up with the
of the LFS website.</para></listitem> initial design of the LFS website.</para></listitem>
<listitem><para><ulink url="mailto:garrett@linux.com">Garrett <listitem><para><ulink url="mailto:garrett@linux.com">Garrett
LeSage</ulink> &lt;garrett@linux.com&gt; for creating the LFS LeSage</ulink> &lt;garrett@linux.com&gt; for creating the LFS

4
chapter01/changelog.xml
View File

@ -96,7 +96,7 @@ the --libexecdir flag from fileutils' configure options.</para></listitem>
symlink from vipw to vigr after installing shadow.</para></listitem> symlink from vipw to vigr after installing shadow.</para></listitem>
<listitem><para>January 30th, 2002 [markh]: Chapters 5+6: Changed <listitem><para>January 30th, 2002 [markh]: Chapters 5+6: Changed
binutils and e2fsprogs installation instructions to use seperate binutils and e2fsprogs installation instructions to use separate
directories ala gcc and glibc.</para></listitem> directories ala gcc and glibc.</para></listitem>
<listitem><para>January 30th, 2002 [gerard]: Chapter 6 - Bootscripts: Added <listitem><para>January 30th, 2002 [gerard]: Chapter 6 - Bootscripts: Added
@ -119,7 +119,7 @@ wtmp files.</para></listitem>
Acknowledgements to be displayed as the first page in chapter Acknowledgements to be displayed as the first page in chapter
1.</para></listitem> 1.</para></listitem>
<listitem><para>January 30th, 2002 [gerard]: Chapter 1: Created a seperate <listitem><para>January 30th, 2002 [gerard]: Chapter 1: Created a separate
page to list the HTTP and FTP mirrors.</para></listitem> page to list the HTTP and FTP mirrors.</para></listitem>
<listitem><para>January 30th, 2002 [gerard]: Chapter 4 - Creating <listitem><para>January 30th, 2002 [gerard]: Chapter 4 - Creating

2
chapter05/gzip-exp.xml
View File

@ -6,7 +6,7 @@ rm $LFS/usr/bin/gunzip $LFS/usr/bin/gzip:</userinput> The reason we don't
simply use <quote>mv</quote> to move the files to the new location is simply use <quote>mv</quote> to move the files to the new location is
because gunzip is a hardlink to gzip. On older distributions you can't because gunzip is a hardlink to gzip. On older distributions you can't
move a hardlink to another partition (and it's very possible that $LFS and move a hardlink to another partition (and it's very possible that $LFS and
$LFS/usr are seperate partitions). With more recent distributions this $LFS/usr are separate partitions). With more recent distributions this
isn't a problem. If you run mv to move hardlinks across partitions it'll isn't a problem. If you run mv to move hardlinks across partitions it'll
just do a regular <quote>cp</quote> and discard the hardlink. But, we just do a regular <quote>cp</quote> and discard the hardlink. But, we
can't assume that every host distribution has a new enough kernel and can't assume that every host distribution has a new enough kernel and

2
chapter06/config-shadowpwd.xml
View File

@ -6,7 +6,7 @@ what 'password shadowing' means. All about that can be read in the doc/HOWTO
file within the unpacked shadow password suite's source tree. There's one file within the unpacked shadow password suite's source tree. There's one
thing you should keep in mind, if you decide to use shadow support, that thing you should keep in mind, if you decide to use shadow support, that
programs that need to verify passwords (examples are xdm, ftp daemons, programs that need to verify passwords (examples are xdm, ftp daemons,
pop3 daemons, etc) need to be 'shadow-compliant', eg. they need to pop3 daemons, etc) need to be 'shadow-compliant', e.g. they need to
be able to work with shadow'ed passwords.</para> be able to work with shadow'ed passwords.</para>
<para>To enable shadow'ed passwords, run the following command:</para> <para>To enable shadow'ed passwords, run the following command:</para>

4
chapter06/glibc-exp.xml
View File

@ -21,7 +21,7 @@ configuration. This is done because Glibc can't autodetect perl since
it hasn't been installed yet.</para> it hasn't been installed yet.</para>
<para><userinput>sed 's/root/0' login/Makefile.backup &gt; <para><userinput>sed 's/root/0' login/Makefile.backup &gt;
login/Makefile:</userinput> This sed command replaces all occurences of login/Makefile:</userinput> This sed command replaces all occurrences of
<filename>root</filename> in <filename>login/Makefile.backup</filename> <filename>root</filename> in <filename>login/Makefile.backup</filename>
with 0. This is because we don't have glibc on the LFS system yet, so with 0. This is because we don't have glibc on the LFS system yet, so
usernames can't be resolved to their user id's. Therefore, we replace usernames can't be resolved to their user id's. Therefore, we replace
@ -38,7 +38,7 @@ We do this because we are only building for our own system. Cross-compiling
is used, for instance, to build a package for an Apple Power PC on an is used, for instance, to build a package for an Apple Power PC on an
Intel system. The reason Glibc thinks we're cross-compiling is that it Intel system. The reason Glibc thinks we're cross-compiling is that it
can't compile a test program to determine this, so it automatically defaults can't compile a test program to determine this, so it automatically defaults
to a cross-compiler. Compiling the test program failes because Glibc hasn't to a cross-compiler. Compiling the test program fails because Glibc hasn't
been installed yet.</para> been installed yet.</para>
<para><userinput>exec /bin/bash:</userinput>This command will <para><userinput>exec /bin/bash:</userinput>This command will