source: chapter05/hostreqs.xml@ 8250be1

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 8250be1 was ef57e3b, checked in by Manuel Canales Esparcia <manuel@…>, 20 years ago

Amplied the Index entries for Hotplug and Linux-Libc-Headers.
Tags corrections.

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

  • Property mode set to 100644
File size: 1.6 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
3 <!ENTITY % general-entities SYSTEM "../general.ent">
4 %general-entities;
5]>
6<sect1 id="ch-tools-hostreqs">
7<title>Host system requirements</title>
8<?dbhtml filename="hostreqs.html"?>
9
10<para>Due to the experimental nature of the current book, the host must be
11running at <emphasis>least</emphasis> a 2.6.2 kernel compiled with GCC-3.0 or
12higher. There are two main reasons for the high requirement. Firstly, we make
13use of the Native Posix Threading Library (NPTL) whose testsuite will segfault
14if the host's kernel hasn't been compiled with GCC-3.0 or later. Secondly, the
152.6.2 or later version of the kernel is required for the use of Udev. Udev
16creates devices dynamically by reading from the
17<systemitem class="filesystem">sysfs</systemitem> file system. Only very
18recently has support for this file system been implemented in most of the kernel
19drivers, however. We must be sure that all the critical system devices get
20created properly.</para>
21
22<para>As for obtaining such a kernel, let's hope you distributor has provided
23a 2.6 kernel package for you. If so, install it. If not, you'll have to compile
24it yourself. If you're forced into a situation where you need to compile it
25yourself, it is highly recommended that you compile your kernel in a monolithic
26manner, as you probably don't want to go fiddling with your hosts module
27utilities. Supposing you don't want to listen, open up the module-init-tools
28tarball and check out the README on how to get module support for 2.6.</para>
29
30</sect1>
Note: See TracBrowser for help on using the repository browser.