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

Miscellaneous fixes from the list. Thanks Bruce.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2921 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Greg Schafer 2003-10-05 08:56:39 +00:00
parent ec0ce9caba
commit 4e629074ec
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter03/creatingfs.xml
View File

@ -2,7 +2,7 @@
<title>Creating a file system on the new partition</title> <title>Creating a file system on the new partition</title>
<?dbhtml filename="creatingfs.html" dir="chapter03"?> <?dbhtml filename="creatingfs.html" dir="chapter03"?>
<para>Now the partition has been made, we can create a file system on it. <para>Now that we have a blank partition, we can create a file system on it.
Most widely used in the Linux world is the second extended file system (ext2), Most widely used in the Linux world is the second extended file system (ext2),
but with the high-capacity hard disks of today the so-called journaling file but with the high-capacity hard disks of today the so-called journaling file
systems are becoming increasingly popular. Here we will create an ext2 file systems are becoming increasingly popular. Here we will create an ext2 file

10
chapter05/introduction.xml
View File

@ -12,13 +12,13 @@ linker and libraries), and then use this to build all the other essential
tools.</para> tools.</para>
<para>The files compiled in this chapter will be installed under the <para>The files compiled in this chapter will be installed under the
<filename class="directory">$LFS/tools</filename> directory, <filename class="directory">$LFS/tools</filename> directory
to keep them separate from the files installed in the next chapter. to keep them separate from the files installed in the next chapter.
Since the packages compiled here are merely temporary, we don't want Since the packages compiled here are merely temporary, we don't want
them to pollute the soon-to-be LFS system.</para> them to pollute the soon-to-be LFS system.</para>
<para>The key to learning what makes a Linux system work is to know <para>The key to learning what makes a Linux system work is to know
what each package is used for, why the user or the system needs it. what each package is used for and why the user or the system needs it.
For this purpose a short summary of the content of each package is given For this purpose a short summary of the content of each package is given
before the actual installation instructions. For a short description of before the actual installation instructions. For a short description of
each program in a package, please refer to the corresponding section in each program in a package, please refer to the corresponding section in
@ -26,8 +26,8 @@ each program in a package, please refer to the corresponding section in
<para>Several of the packages are patched before compilation, but only when <para>Several of the packages are patched before compilation, but only when
the patch is needed to circumvent a problem. Often the patch is needed in the patch is needed to circumvent a problem. Often the patch is needed in
both this and the next chapter, but sometimes in only one of them. So, don't both this and the next chapter, but sometimes in only one of them. Therefore,
worry when instructions for a downloaded patch seem to be missing.</para> don't worry when instructions for a downloaded patch seem to be missing.</para>
<para>During the installation of most packages you will <para>During the installation of most packages you will
see all kinds of compiler warnings scroll by on your screen. These are see all kinds of compiler warnings scroll by on your screen. These are
@ -37,7 +37,7 @@ syntax. It's just that C standards have changed rather often and some
packages still use the older standard, which is not really a problem.</para> packages still use the older standard, which is not really a problem.</para>
<para>Before continuing, make sure the LFS environment variable is set up <para>Before continuing, make sure the LFS environment variable is set up
properly (if you decided to make use of it) by executing the following:</para> properly by executing the following:</para>
<para><screen><userinput>echo $LFS</userinput></screen></para> <para><screen><userinput>echo $LFS</userinput></screen></para>

4
chapter06/chroot.xml
View File

@ -8,8 +8,8 @@ the packages we need. Before you can chroot, however, you need to become
can execute the <userinput>chroot</userinput> command.</para> can execute the <userinput>chroot</userinput> command.</para>
<para>Just like earlier, ensure the LFS environment variable is set up properly <para>Just like earlier, ensure the LFS environment variable is set up properly
(if you decided to make use of it) by running <userinput>echo $LFS</userinput> by running <userinput>echo $LFS</userinput> and ensuring it shows the path to
and ensuring it shows the path to your LFS partition's mount point, which is your LFS partition's mount point, which is
<filename class="directory">/mnt/lfs</filename> if you followed our <filename class="directory">/mnt/lfs</filename> if you followed our
example.</para> example.</para>

2
chapter06/gzip-inst.xml
View File

@ -7,7 +7,7 @@
<para><screen><userinput>./configure --prefix=/usr</userinput></screen></para> <para><screen><userinput>./configure --prefix=/usr</userinput></screen></para>
<para>The gzexe program has the location of the gzip binary hardcoded into <para>The gzexe program has the location of the gzip binary hard-wired into
it. Because we later change the location of this binary, the following it. Because we later change the location of this binary, the following
command will place the new location into the gzexe binary.</para> command will place the new location into the gzexe binary.</para>