Changeset 0c745d0a


Ignore:
Timestamp:
03/30/06 09:05:35 (7 years ago)
Author:
Jim Gifford <clfs@…>
Children:
48a4914005e2a14c4601c0e301a14fed2e7111b6
Parents:
aff2cacbeb739ec0f57d656b7786ec2423ce25fa
git-author:
Jim Gifford <clfs@jg555.com>2006-03-30 09:05:35+00:00
git-committer:
Jim Gifford <clfs@jg555.com>2006-03-30 09:05:35+00:00
Message:

r2752@server (orig r1333): darcym | 2006-03-30 00:48:05 -0800
Minor update to prerequististes wording and a few additions specific to CLFS


File:
1 edited

Legend:

Unmodified
Added
Removed
  • prologue/common/prerequisites.xml

    rbf8c11f r0c745d0a  
    1111  <title>Prerequisites</title> 
    1212 
    13   <para>Building an LFS system is not a simple task. It requires a certain 
     13  <para>Building an CLFS system is not a simple task. It requires a certain 
    1414  level of existing knowledge of Unix system administration in order to 
    1515  resolve problems, and correctly execute the commands listed. In particular, 
     
    1818  directory and file contents, and change the current directory. It is also 
    1919  expected that the reader has a reasonable knowledge of using and installing 
    20   Linux software.</para> 
     20  Linux software. A basic knowledge of the architectures being used in  
     21  the Cross LFS process and the host operating systems in use is also 
     22  required</para> 
    2123 
    22   <para>Because the LFS book assumes <emphasis>at least</emphasis> this basic 
     24  <para>Because the CLFS book assumes <emphasis>at least</emphasis> this basic 
    2325  level of skill, the various LFS support forums are unlikely to be able to 
    2426  provide you with much assistance; you will find that your questions regarding 
     
    2628  to the LFS essential pre-reading list.</para> 
    2729 
    28   <para>Before building an LFS system, we recommend reading the following 
     30  <para>Before building a CLFS system, we recommend reading the following 
    2931  HOWTOs:</para> 
    3032 
Note: See TracChangeset for help on using the changeset viewer.