Changeset 65ac2fd
- Timestamp:
- 04/22/2022 03:45:10 AM (2 years ago)
- Branches:
- multilib
- Children:
- 481b2e05
- Parents:
- 80d370b (diff), 93db1e61 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/stages.xml
r80d370b r65ac2fd 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
r80d370b r65ac2fd 90 90 91 91 <note><para>In some host systems, the following command does not complete 92 properly and suspends the login to the lfs user to the background. If the93 prompt "lfs:~$" does not appear immediately, entering the92 properly and suspends the login to the &lfs-user; user to the background. 93 If the prompt "lfs:~$" does not appear immediately, entering the 94 94 <command>fg</command> command will fix the issue.</para></note> 95 95 -
chapter07/cleanup.xml
r80d370b r65ac2fd 160 160 161 161 <warning><para>The following commands are extremely dangerous. If 162 you run <command>rm -rf ./*</command> as the rootuser and you162 you run <command>rm -rf ./*</command> as the &root; user and you 163 163 do not change to the $LFS directory or the <envar>LFS</envar> 164 environment variable is not set for the rootuser, it will destroy164 environment variable is not set for the &root; user, it will destroy 165 165 your entire host system. YOU ARE WARNED.</para></warning> 166 166 -
chapter07/introduction.xml
r80d370b r65ac2fd 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
r80d370b r65ac2fd 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
r80d370b r65ac2fd 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/python.xml
r80d370b r65ac2fd 110 110 </userinput></screen> 111 111 112 <important> 113 <para> 114 In LFS and BLFS we normally build and install Python modules with the 115 <command>pip3</command> command. Please take care that the 116 <command>pip3 install</command> commands in both the books should be 117 run as the &root; user unless it's for a Python virtual environment. 118 Running a <command>pip3 install</command> as a non-&root; user may seem 119 to work fine, but it will cause the installed module to be inaccessible 120 by other users. 121 </para> 122 123 <para> 124 <command>pip3 install</command> will not reinstall an already installed 125 module by default. For using the <command>pip3 install</command> 126 command to upgrade a module (for example, from meson-0.61.3 to 127 meson-0.62.0), insert the option <parameter>--upgrade</parameter> into 128 the command line. If it's really necessary to downgrade a module or 129 reinstall the same version for some reason, insert 130 <parameter>--force-reinstall</parameter> into the command line. 131 </para> 132 </important> 112 133 113 134 <para>If desired, install the preformatted documentation:</para> -
chapter08/util-linux.xml
r80d370b r65ac2fd 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
r80d370b r65ac2fd 281 281 <para>If the host system has a separate /boot partition, the files copied 282 282 below should go there. The easiest way to do that is to bind /boot on the 283 host (outside chroot) to /mnt/lfs/boot before proceeding. As the root284 user in the <emphasis>host system</emphasis>:</para>283 host (outside chroot) to /mnt/lfs/boot before proceeding. As the 284 &root; user in the <emphasis>host system</emphasis>:</para> 285 285 286 286 <screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen> -
chapter11/reboot.xml
r80d370b r65ac2fd 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 -
general.ent
r80d370b r65ac2fd 113 113 <!ENTITY github "https://github.com"> 114 114 115 <!ENTITY root "<systemitem class='username'>root</systemitem>"> 116 <!ENTITY lfs-user "<systemitem class='username'>lfs</systemitem>"> 117 115 118 <!ENTITY % packages-entities SYSTEM "packages.ent"> 116 119 %packages-entities;
Note:
See TracChangeset
for help on using the changeset viewer.