Changes in chapter07/introduction.xml [7152faa:e49e2ea]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/introduction.xml
r7152faa re49e2ea 1 <?xml version="1.0" encoding=" UTF-8"?>1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" 3 3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ … … 11 11 <title>Introduction</title> 12 12 13 <warning> 14 <para>Please make sure the temporary system is already booted on the 15 target machine. All commands in this chapter and the following chapters 16 should be executed on the target machine instead of the host distro, 17 unless the book explicitly says a command is for the host. Running a 18 command for the temporary system on the host can completely destroy the 19 host distro.</para> 20 </warning> 21 13 22 <para>This chapter shows how to build the last missing bits of the temporary 14 23 system: the tools needed to build the 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> 24 that all circular dependencies have been resolved and the temporary system 25 is already bootable, we can boot it on the target machine and it would be 26 completely isolated from the host operating system. Then we can continue 27 to build on the target machine.</para> 18 28 19 <para>For proper operation of the isolated environment, some communication20 with the running kernel must be established. This is done viathe29 <para>For proper operation of the temporary system, some communication 30 with the running kernel must be established. This is done through the 21 31 so-called <emphasis>Virtual Kernel File Systems</emphasis>, which will be 22 mounted before entering the chroot environment. You may want to verify23 that they are mounted by issuing the <command>findmnt</command> command.</para>32 mounted as soon as possible after boot. You may want to check 33 that they are mounted by issuing <command>mount</command>.</para> 24 34 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 bad commands.</para> 35 <para>All commands in this and following chapters are run as &root; on the 36 target system, fortunately without access to the host system. 37 Be careful anyway, as if the storage devices of your target system already 38 contains some important data, it's possible to destroy them with bad 39 commands.</para> 31 40 32 41 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.