From 52ddd6c0334cefce551cc70e32d0c8c5163ef566 Mon Sep 17 00:00:00 2001 From: David Bryant Date: Fri, 30 Sep 2022 11:22:10 -0500 Subject: Clarify some things in Intro to chroot; simplify some verbiage. --- chapter07/introduction.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'chapter07/introduction.xml') diff --git a/chapter07/introduction.xml b/chapter07/introduction.xml index 6605ddea4..62a428416 100644 --- a/chapter07/introduction.xml +++ b/chapter07/introduction.xml @@ -11,22 +11,22 @@ Introduction This chapter shows how to build the last missing bits of the temporary - system: the tools needed by the build machinery of various packages. Now + system: the tools needed to build the various packages. Now that all circular dependencies have been resolved, a chroot environment, completely isolated from the host operating system (except for the running kernel), can be used for the build. For proper operation of the isolated environment, some communication - with the running kernel must be established. This is done through the + with the running kernel must be established. This is done via the so-called Virtual Kernel File Systems, which must be - mounted when entering the chroot environment. You may want to check - that they are mounted by issuing findmnt. + mounted before entering the chroot environment. You may want to verify + that they are mounted by issuing the findmnt command. Until , the commands must be run as root, with the LFS variable set. After entering chroot, all commands are run as &root;, fortunately without access to the OS of the computer you built LFS on. Be careful anyway, as it is easy to destroy the whole - LFS system with badly formed commands. + LFS system with bad commands. -- cgit v1.2.3-54-g00ecf