source: chapter07/introduction.xml@ 37e35d2

multilib-10.1
Last change on this file since 37e35d2 was 37e35d2, checked in by Thomas Trepl <thomas@…>, 4 years ago

Update to new lfs structure

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

  • Property mode set to 100644
File size: 1.5 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 temporary
14 system: first, the tools needed by the build machinery of various packages,
15 then three packages needed to run tests. Now that all circular dependencies
16 have been resolved, we can use a <quote>chroot</quote> environment,
17 completely isolated the host operating system used for the build, except
18 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>findmnt</command>.</para>
25
26 <para>Until <xref linkend="ch-tools-chroot"/>, the commands must be
27 run as <systemitem class="username">root</systemitem>, with the
28 <envar>LFS</envar> variable set. After entering chroot, all commands
29 are run as root, fortunately without access to the OS of the computer
30 you built LFS on. Be careful anyway, as it is easy to destroy the whole
31 LFS system with badly formed commands.</para>
32
33</sect1>
Note: See TracBrowser for help on using the repository browser.