Changeset 2ad6d43
- Timestamp:
- 04/21/2022 03:24:28 PM (2 years ago)
- Branches:
- arm
- Children:
- a3a9213
- Parents:
- f9dc44bc
- git-author:
- Xi Ruoyao <xry111@…> (04/21/2022 06:12:43 AM)
- git-committer:
- William Harrington <kb0iic@…> (04/21/2022 03:24:28 PM)
- Files:
-
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/stages.xml
rf9dc44bc r2ad6d43 72 72 <quote>Entering the Chroot Environment</quote> must be done as the 73 73 <systemitem class="username">root</systemitem> user, with the LFS 74 environment variable set for the 75 <systemitem class="username">root</systemitem>user.</para> 74 environment variable set for the &root; user.</para> 76 75 </listitem> 77 76 -
chapter04/addinguser.xml
rf9dc44bc r2ad6d43 87 87 88 88 <note><para>In some host systems, the following command does not complete 89 properly and suspends the login to the lfs user to the background. If the90 prompt "lfs:~$" does not appear immediately, entering the89 properly and suspends the login to the &lfs-user; user to the background. 90 If the prompt "lfs:~$" does not appear immediately, entering the 91 91 <command>fg</command> command will fix the issue.</para></note> 92 92 -
chapter07/cleanup.xml
rf9dc44bc r2ad6d43 157 157 158 158 <warning><para>The following commands are extremely dangerous. If 159 you run <command>rm -rf ./*</command> as the rootuser and you159 you run <command>rm -rf ./*</command> as the &root; user and you 160 160 do not change to the $LFS directory or the <envar>LFS</envar> 161 environment variable is not set for the rootuser, it will destroy161 environment variable is not set for the &root; user, it will destroy 162 162 your entire host system. YOU ARE WARNED.</para></warning> 163 163 -
chapter07/introduction.xml
rf9dc44bc r2ad6d43 26 26 run as <systemitem class="username">root</systemitem>, with the 27 27 <envar>LFS</envar> variable set. After entering chroot, all commands 28 are run as root, fortunately without access to the OS of the computer28 are run as &root;, fortunately without access to the OS of the computer 29 29 you built LFS on. Be careful anyway, as it is easy to destroy the whole 30 30 LFS system with badly formed commands.</para> -
chapter08/bash.xml
rf9dc44bc r2ad6d43 74 74 <screen><userinput remap="test">chown -Rv tester .</userinput></screen> 75 75 76 <para>The testsuite of the package is designed to be run as a non- root76 <para>The testsuite of the package is designed to be run as a non-&root; 77 77 user that owns the terminal connected to standard input. To satisfy the 78 78 requirement, spawn a new pseudo terminal using -
chapter08/coreutils.xml
rf9dc44bc r2ad6d43 125 125 <screen><userinput remap="test">echo "dummy:x:102:tester" >> /etc/group</userinput></screen> 126 126 127 <para>Fix some of the permissions so that the non- root user can compile and128 run the tests:</para>127 <para>Fix some of the permissions so that the non-&root; user can 128 compile and run the tests:</para> 129 129 130 130 <screen><userinput remap="test">chown -Rv tester . </userinput></screen> -
chapter08/util-linux.xml
rf9dc44bc r2ad6d43 85 85 <screen><userinput remap="make">make</userinput></screen> 86 86 87 <para>If desired, run the test suite as a non- rootuser:</para>87 <para>If desired, run the test suite as a non-&root; user:</para> 88 88 89 89 <warning><para>Running the test suite as the -
chapter10/kernel.xml
rf9dc44bc r2ad6d43 249 249 <para>If the host system has a separate /boot partition, the files copied 250 250 below should go there. The easiest way to do that is to bind /boot on the 251 host (outside chroot) to /mnt/lfs/boot before proceeding. As the root252 user in the <emphasis>host system</emphasis>:</para>251 host (outside chroot) to /mnt/lfs/boot before proceeding. As the 252 &root; user in the <emphasis>host system</emphasis>:</para> 253 253 254 254 <screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen> -
chapter11/reboot.xml
rf9dc44bc r2ad6d43 47 47 <listitem><para>Installing <ulink 48 48 url='&blfs-book;postlfs/sudo.html'>sudo</ulink> may be useful for 49 building packages as a non- root user and easily installing the resulting50 packages in your new system.</para></listitem>49 building packages as a non-&root; user and easily installing the 50 resulting packages in your new system.</para></listitem> 51 51 52 52 <listitem><para>If you want to access your new system from a remote system
Note:
See TracChangeset
for help on using the changeset viewer.