Changeset 0636f6c for boot

Timestamp:

Feb 21, 2006, 1:57:38 AM (19 years ago)

Author:

Jim Gifford <clfs@…>

Children:

4d6fcf9

Parents:

db38a36

Message:

r981@server (orig r979): jim | 2005-12-30 10:11:32 -0800

r1226@server: cstaub | 2005-12-30 08:35:37 -0800
Updated package deps, removed explanation of cross-compiling from final-system binutils, and removed note about GRUB's testsuite failure

Location:

boot/common

Files:

• changingowner.xml (modified) (1 diff)
• settingenviron.xml (modified) (2 diffs)
• whatnext.xml (modified) (1 diff)

boot/common/changingowner.xml

@@ -24 +24 @@
 chown -R 0:0 $LFS/{bin,boot,dev,etc,home,lib,media,mnt,opt,proc,root,sbin,srv,sys,tmp,usr,var}</userinput></screen>
 
-  <para os="c">Optionally, you can do the same with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
+  <para os="c">The same issue also exists with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
   LFS system has been finished, they can be retained to build additional
   LFS systems. If the <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>

boot/common/settingenviron.xml

@@ -27 +27 @@
   Setting <envar>LC_ALL</envar> to <quote>POSIX</quote> or <quote>C</quote>
   (the two are equivalent) ensures that everything will work as expected
-  on your tempoary system.</para>
+  on your temporary system.</para>
 
   <para>By putting <filename class="directory">/tools/bin</filename> at
@@ -34 +34 @@
   if they have not yet been built on the target system. This configuration
   forces use of the final system binaries as they are built over the 
-  temp-system, minimising the chance final system programs being built
+  temp-system, minimising the chance of final system programs being built
   against the temp-system.</para>
 

boot/common/whatnext.xml

@@ -11 +11 @@
   <title>What to do next</title>
 
-  <para>Now your at the point to get your <filename
+  <para>Now you're at the point to get your <filename
   class="directory">${LFS}</filename> directory copied over to your target
-  machine. The easiest method would be to tar and copy the file up.</para>
+  machine. The easiest method would be to tar it up and copy the file.</para>
 
 <screen><userinput>tar -jcvf ${LFS}.tar.bz2 ${LFS}</userinput></screen>
 
-  <para>Some others have came up with other idea's on how to do this.
+  <para>Some others have came up with other ideas on how to do this.
   Below is a table with the method and link to where the information
   is stored.</para>