source: chapter07/introduction.xml@ d11d449

11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 bdubbs/gcc13 multilib renodr/libudev-from-systemd trunk xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng 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 d11d449 was e286d8db, checked in by Xi Ruoyao <xry111@…>, 2 years ago

decorate the references to root and lfs user

The references already correctly decorated are not changed because "if
it's not broken don't fix it".

  • 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: the tools needed by the build machinery of various packages. Now
15 that all circular dependencies have been resolved, a <quote>chroot</quote>
16 environment, completely isolated from the host operating system (except for
17 the running kernel), can be used for the build.</para>
18
19 <para>For proper operation of the isolated environment, some communication
20 with the running kernel must be established. This is done through the
21 so-called <emphasis>Virtual Kernel File Systems</emphasis>, which must be
22 mounted when entering the chroot environment. You may want to check
23 that they are mounted by issuing <command>findmnt</command>.</para>
24
25 <para>Until <xref linkend="ch-tools-chroot"/>, the commands must be
26 run as <systemitem class="username">root</systemitem>, with the
27 <envar>LFS</envar> variable set. After entering chroot, all commands
28 are run as &root;, fortunately without access to the OS of the computer
29 you built LFS on. Be careful anyway, as it is easy to destroy the whole
30 LFS system with badly formed commands.</para>
31
32</sect1>
Note: See TracBrowser for help on using the repository browser.