Browse Source

Preface: Add note about the Essential Pre-Reading Hint. Closes Bug 585.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2935 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Greg Schafer 22 years ago
parent
commit
cd40510a8f

+ 3 - 0
chapter01/changelog.xml

@@ -95,6 +95,9 @@
 </itemizedlist>
 </itemizedlist>
 </para></listitem>
 </para></listitem>
 
 
+<listitem><para>October 7th, 2003 [greg]: Preface: Add note about the Essential
+Pre-Reading Hint. Closes Bug 585.</para></listitem>
+
 <listitem><para>October 6th, 2003 [greg]: Simplify seds in "Locking in Glibc"
 <listitem><para>October 6th, 2003 [greg]: Simplify seds in "Locking in Glibc"
 and "Re-adjusting the toolchain" sections. Rearrange "How things are going to be
 and "Re-adjusting the toolchain" sections. Rearrange "How things are going to be
 done" section.</para></listitem>
 done" section.</para></listitem>

+ 2 - 2
chapter05/lockingglibc.xml

@@ -35,8 +35,8 @@ occurrence of "/lib/ld-linux.so.2" with "/tools/lib/ld-linux.so.2".</para>
 <important><para>If you are working on a platform where the name of the dynamic
 <important><para>If you are working on a platform where the name of the dynamic
 linker is something other than <filename>ld-linux.so.2</filename>, you
 linker is something other than <filename>ld-linux.so.2</filename>, you
 <emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the
 <emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the
-name of your platform's dynamic linker in the above commands. Refer back to the
-"Toolchain technical notes" section if necessary.</para></important>
+name of your platform's dynamic linker in the above commands. Refer back to
+<xref linkend="ch05-toolchaintechnotes"/> if necessary.</para></important>
 
 
 <para>Lastly, there is a possibility that some include files from the host
 <para>Lastly, there is a possibility that some include files from the host
 system have found their way into GCC's private include dir. This can happen
 system have found their way into GCC's private include dir. This can happen

+ 2 - 2
chapter06/adjustingtoolchain.xml

@@ -53,8 +53,8 @@ changes were actually made.</para>
 <important><para>If you are working on a platform where the name of the dynamic
 <important><para>If you are working on a platform where the name of the dynamic
 linker is something other than <filename>ld-linux.so.2</filename>, you
 linker is something other than <filename>ld-linux.so.2</filename>, you
 <emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the
 <emphasis>must</emphasis> substitute <filename>ld-linux.so.2</filename> with the
-name of your platform's dynamic linker in the above commands. Refer back to the
-"Toolchain technical notes" section if necessary.</para></important>
+name of your platform's dynamic linker in the above commands. Refer back to
+<xref linkend="ch05-toolchaintechnotes"/> if necessary.</para></important>
 
 
 <caution><para>It is imperative at this point to stop and ensure that the
 <caution><para>It is imperative at this point to stop and ensure that the
 basic functions (compiling and linking) of the adjusted toolchain are working
 basic functions (compiling and linking) of the adjusted toolchain are working

+ 3 - 3
chapter06/binutils-inst.xml

@@ -14,9 +14,9 @@ everything is set up correctly by performing a simple test:</para>
 
 
 <para>Your chroot environment is not set up for proper PTY operation. In this
 <para>Your chroot environment is not set up for proper PTY operation. In this
 case there is no point in running the test suites for Binutils and GCC until you
 case there is no point in running the test suites for Binutils and GCC until you
-are able to resolve the issue. Please refer back to the "Mounting the proc and
-devpts file systems" and "Creating devices (Makedev)" sections and perform the
-recommended steps to fix the problem.</para>
+are able to resolve the issue. Please refer back to <xref linkend="ch06-proc"/>
+and <xref linkend="ch06-makedev"/> and perform the recommended steps to fix the
+problem.</para>
 
 
 <note><para>The test suite for Binutils in this section is considered
 <note><para>The test suite for Binutils in this section is considered
 <emphasis>critical</emphasis>. Our advice is to not skip it under any
 <emphasis>critical</emphasis>. Our advice is to not skip it under any

+ 2 - 1
chapter06/man-inst.xml

@@ -54,7 +54,8 @@ configuration file in the <filename>/etc</filename> directory.</para></listitem>
 edit the man.conf file and add the <userinput>-c</userinput> argument
 edit the man.conf file and add the <userinput>-c</userinput> argument
 to nroff.</para></note>
 to nroff.</para></note>
 
 
-<para>You may want to also take a look at the BLFS book which deals with 
+<para>You may want to also take a look at the BLFS page at
+<ulink url="&blfs-root;view/cvs/postlfs/compressdoc.html"/> which deals with
 formatting and compression issues for man pages.</para>
 formatting and compression issues for man pages.</para>
 
 
 </sect2>
 </sect2>

+ 9 - 0
preface/prerequisites.xml

@@ -19,6 +19,15 @@ UNIX software distributions under Linux. This HOWTO is available at
 available at
 available at
 <ulink url="http://espc22.murdoch.edu.au/~stewart/guide/guide.html"/>.</para></listitem>
 <ulink url="http://espc22.murdoch.edu.au/~stewart/guide/guide.html"/>.</para></listitem>
 
 
+<listitem><para>The Essential Pre-Reading Hint</para>
+
+<para>This is an LFS Hint written specifically for new users of Linux. It is
+mostly a list of links to excellent sources of information on a wide range of
+topics. Any person attempting to install LFS, should at least have an
+understanding of many of the topics in this hint. It is available at
+
+<ulink url="&hints-root;essential_prereading.txt"/></para></listitem>
+
 </itemizedlist>
 </itemizedlist>
 
 
 </sect1>
 </sect1>