Ignore:
Timestamp:
08/08/2004 02:10:39 AM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
ef13657
Parents:
78349b7
Message:

Completed global edits for upcoming 6.0 release

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/testing/BOOK@3999 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter05/hostreqs.xml

    r78349b7 r6e41459  
    55]>
    66<sect1 id="ch-tools-hostreqs">
    7 <title>Host system requirements</title>
     7<title>Host System Requirements</title>
    88<?dbhtml filename="hostreqs.html"?>
    99
    10 <para>Due to the experimental nature of the current book, the host must be
    11 running at <emphasis>least</emphasis> a 2.6.2 kernel compiled with GCC-3.0 or
    12 higher. There are two main reasons for the high requirement.  Firstly, we make
    13 use of the Native Posix Threading Library (NPTL) whose testsuite will segfault
    14 if the host's kernel hasn't been compiled with GCC-3.0 or later.  Secondly, the
    15 2.6.2 or later version of the kernel is required for the use of Udev. Udev
    16 creates devices dynamically by reading from the
    17 <systemitem class="filesystem">sysfs</systemitem> file system. Only very
    18 recently has support for this file system been implemented in most of the kernel
    19 drivers, however. We must be sure that all the critical system devices get
    20 created properly.</para>
     10<para>The host must be running at least a 2.6.2 kernel compiled with
     11GCC-3.0 or higher. There are two main reasons for this high
     12requirement. First, the Native Posix Threading Library (NPTL)
     13testsuite will segfault if the host's kernel hasn't been compiled with
     14GCC-3.0 or a later version. Secondly, the 2.6.2 or later version of
     15the kernel is required for the use of Udev. Udev creates devices
     16dynamically by reading from the <systemitem
     17class="filesystem">sysfs</systemitem> file system. However, only
     18recently has support for this file system been implemented in most of
     19the kernel drivers. We must be sure that all critical system devices
     20get created properly.</para>
    2121
    22 <para>In order to check that your host kernel meets the requirements outlined
    23 above, you can run the following command:</para>
     22<para>In order to determine whether the host kernel meets the
     23requirements outlined above, run the following command:</para>
    2424
    2525<screen><userinput>cat /proc/version</userinput></screen>
    … …  
    2929<blockquote><screen><computeroutput>Linux version 2.6.2 (user@host) (gcc version 3.4.0) #1 Tue Apr 20 21:22:18 GMT 2004</computeroutput></screen></blockquote>
    3030
    31 <para>If the results of the above command state that your host kernel wasn't
    32 compiled using a GCC-3.0 (or later) compiler, you will need to compile one
    33 yourself, and reboot your host to use the newly compiled kernel. Instructions
    34 for compiling the kernel and configuring the bootloader (assuming your host uses
    35 GRUB) are given in <xref linkend="chapter-bootable"/>.</para>
     31<para>If the results of the above command state that the host kernel
     32was not compiled using a GCC-3.0 (or later) compiler, one will need to
     33be compiled.  The host system will then need to be rebooted to use the
     34newly compiled kernel. Instructions for compiling the kernel and
     35configuring the bootloader (assuming your host uses GRUB) are located
     36in <xref linkend="chapter-bootable"/>.</para>
    3637
    3738</sect1>
     39
Note: See TracChangeset for help on using the changeset viewer.