diff --git a/chapter02/stages.xml b/chapter02/stages.xml index 830ec0c1f..7c151975f 100644 --- a/chapter02/stages.xml +++ b/chapter02/stages.xml @@ -71,8 +71,7 @@ A few operations, from Changing Ownership to Entering the Chroot Environment must be done as the root user, with the LFS - environment variable set for the - rootuser. + environment variable set for the &root; user. diff --git a/chapter04/addinguser.xml b/chapter04/addinguser.xml index 535f20b02..b659b4841 100644 --- a/chapter04/addinguser.xml +++ b/chapter04/addinguser.xml @@ -86,8 +86,8 @@ case $(uname -m) in esac In some host systems, the following command does not complete - properly and suspends the login to the lfs user to the background. If the - prompt "lfs:~$" does not appear immediately, entering the + properly and suspends the login to the &lfs-user; user to the background. + If the prompt "lfs:~$" does not appear immediately, entering the fg command will fix the issue. Next, login as user lfs. diff --git a/chapter07/cleanup.xml b/chapter07/cleanup.xml index 651f2e8d6..6ed78fb93 100644 --- a/chapter07/cleanup.xml +++ b/chapter07/cleanup.xml @@ -156,9 +156,9 @@ tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz . restore when they don't need to. --> The following commands are extremely dangerous. If - you run rm -rf ./* as the root user and you + you run rm -rf ./* as the &root; user and you do not change to the $LFS directory or the LFS - environment variable is not set for the root user, it will destroy + environment variable is not set for the &root; user, it will destroy your entire host system. YOU ARE WARNED. cd $LFS diff --git a/chapter07/introduction.xml b/chapter07/introduction.xml index 2b0030d7b..6605ddea4 100644 --- a/chapter07/introduction.xml +++ b/chapter07/introduction.xml @@ -25,7 +25,7 @@ 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 + 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. diff --git a/chapter08/bash.xml b/chapter08/bash.xml index 787882b59..4ea981d5b 100644 --- a/chapter08/bash.xml +++ b/chapter08/bash.xml @@ -73,7 +73,7 @@ chown -Rv tester . - The testsuite of the package is designed to be run as a non-root + The testsuite of the package is designed to be run as a non-&root; user that owns the terminal connected to standard input. To satisfy the requirement, spawn a new pseudo terminal using Expect and run the tests as the echo "dummy:x:102:tester" >> /etc/group - Fix some of the permissions so that the non-root user can compile and - run the tests: + Fix some of the permissions so that the non-&root; user can + compile and run the tests: chown -Rv tester . diff --git a/chapter08/util-linux.xml b/chapter08/util-linux.xml index 7aba82c85..d90936b78 100644 --- a/chapter08/util-linux.xml +++ b/chapter08/util-linux.xml @@ -84,7 +84,7 @@ make - If desired, run the test suite as a non-root user: + If desired, run the test suite as a non-&root; user: Running the test suite as the root user can be harmful to diff --git a/chapter10/kernel.xml b/chapter10/kernel.xml index 713bab93b..f1469f0b4 100644 --- a/chapter10/kernel.xml +++ b/chapter10/kernel.xml @@ -248,8 +248,8 @@ File systems ---> If the host system has a separate /boot partition, the files copied below should go there. The easiest way to do that is to bind /boot on the - host (outside chroot) to /mnt/lfs/boot before proceeding. As the root - user in the host system: + host (outside chroot) to /mnt/lfs/boot before proceeding. As the + &root; user in the host system: mount --bind /boot /mnt/lfs/boot diff --git a/chapter11/reboot.xml b/chapter11/reboot.xml index 9166a8c49..3d7953897 100644 --- a/chapter11/reboot.xml +++ b/chapter11/reboot.xml @@ -46,8 +46,8 @@ Installing sudo may be useful for - building packages as a non-root user and easily installing the resulting - packages in your new system. + building packages as a non-&root; user and easily installing the + resulting packages in your new system. If you want to access your new system from a remote system within a comfortable GUI environment, install