source: chapter07/introduction.xml@ ce335792

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 ml-11.0 multilib trunk xry111/git-transition xry111/glibc-2.34 xry111/tester-nohack xry111/usr-move
Last change on this file since ce335792 was ce335792, checked in by Pierre Labastie <pieere@…>, 18 months ago

Add an introduction to chapter 6 and 7

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross2@11910 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 1.7 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-tools-introduction-chroot">
9 <?dbhtml filename="introduction.html"?>
10
11 <title>Introduction</title>
12
13 <para>This chapter shows how to build the last missing bits of the
14 temporary system: first, the tools needed by the build machinery of
15 various packages, then three packages needed to run tests.
16 Now that all circular dependencies have been resolved,
17 we can use a <quote>chroot</quote> environment, completely isolated
18 from the computer used for the build, except for the running kernel.</para>
19
20 <para>For proper operation of the isolated environment, some communication
21 with the running kernel must be established. This is done through the
22 so-called <emphasis>Virtual Kernel File Systems</emphasis>, which must be
23 mounted when entering the chroot environment. You may want to check
24 that they are mounted by issuing <command>ls $LFS/dev</command>,
25 <command>ls $LFS/proc</command>, or <command>ls $LFS/sys</command>.
26 Note that mounting the virtual kernel file systems must be done
27 <emphasis>each time you want to enter the chroot
28 environment</emphasis>.</para>
29
30 <para>Until <xref linkend="ch-tools-chroot"/>, the commands must be
31 run as <systemitem class="username">root</systemitem>, with the
32 <envar>LFS</envar> variable set. After entering chroot, all commands
33 are run as root, fortunately without access to the OS of the computer
34 you build LFS on. Be careful anyway, as it is easy to destroy the whole
35 LFS system with badly formed commands.</para>
36
37</sect1>
Note: See TracBrowser for help on using the repository browser.