Current BE-LFS (but w/ GCC 3.3.3) merged -> 6.0 branch

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3445 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

1 files changed, 26 insertions, 0 deletions

diff --git a/chapter05/hostreqs.xml b/chapter05/hostreqs.xml
new file mode 100644
index 000000000..c2d2ef4fb
--- /dev/null
+++ b/chapter05/hostreqs.xml
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../general.ent">
+  %general-entities;
+]>
+<sect1 id="ch-tools-hostreqs">
+<title>Host system requirements</title>
+<?dbhtml filename="hostreqs.html"?>
+
+<para>Due to the experimental nature of BE-LFS, the host must be running at
+<emphasis>least</emphasis> a 2.6.2 kernel. The reasons for this high requirement
+is the use of NPTL, but more importantly the use of udev. Udev creates devices
+dynamically by reading from the sysfs file system. Only very recently has
+support for this file system been implemented in most of the kernel drivers,
+however. We must be sure that all the critical system devices get created
+properly.</para>
+
+<para>As for obtaining such a kernel, let's hope you distributor has provided
+a 2.6 kernel package for you. If so, install it. If not, you'll have to compile
+it yourself. If you're forced into a situation where you need to compile it
+yourself, it is highly recommended that you compile your kernel in a monolithic
+manner, as you probably don't want to go fiddling with your hosts module
+utilities. Supposing you don't want to listen, open up the module-init-tools
+tarball and check out the README on how to get module support for 2.6.</para>
+
+</sect1>