Changeset ce335792 for chapter07/introduction.xml
- Timestamp:
- 06/09/2020 01:35:39 PM (4 years ago)
- Branches:
- 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, 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
- Children:
- 3369724
- Parents:
- a89ab79
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/introduction.xml
ra89ab79 rce335792 6 6 ]> 7 7 8 <sect1 id="ch-tools-introduction ">8 <sect1 id="ch-tools-introduction-chroot"> 9 9 <?dbhtml filename="introduction.html"?> 10 10 11 11 <title>Introduction</title> 12 12 13 <para>This chapter shows how to build a minimal Linux system. 14 This system will contain just enough tools to start constructing the final 15 LFS system in <xref linkend="chapter-building-system"/> and allow a working 16 environment with more user convenience than a minimum environment would.</para> 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> 17 19 18 <para>There are two steps in building this minimal system. The first step 19 is to build a new and host-independent toolchain (compiler, assembler, 20 linker, libraries, and a few useful utilities). The second step uses this 21 toolchain to build the other essential tools.</para> 22 <!-- 23 <para>The files compiled in this chapter will be installed under the 24 <filename class="directory">$LFS</filename> directory to keep them 25 separate from the files installed in the next chapter and the host 26 production directories. Since the packages compiled here are temporary, 27 we do not want them to pollute the soon-to-be LFS system.</para> 28 --> 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 29 37 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.