Changeset 34fe7e0
- Timestamp:
- 12/26/2020 03:51:54 PM (2 years ago)
- Branches:
- 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, s6-init, trunk, xry111/arm64, xry111/clfs-ng, xry111/git-transition, xry111/glibc-2.34, xry111/glibc-2.37, xry111/kcfg-revise, xry111/lfs-next, xry111/pip3, xry111/queue-11.3, xry111/rust-wip-20221008, xry111/tester-nohack, xry111/usr-move
- Children:
- fb87fac
- Parents:
- ce9b68d
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter02/aboutlfs.xml
rce9b68d r34fe7e0 58 58 user's <filename>.bash_profile</filename> is not normally used when 59 59 a virtual terminal is started. In this case, add the export command to 60 the <filename>.bashrc</filename> file for the user and root. In addition, 60 the <filename>.bashrc</filename> file for the user and 61 <systemitem class="username">root</systemitem>. In addition, 61 62 some distributions have instructions to not run the <filename>.bashrc</filename> 62 63 instructions in a non-interactive bash invocation. Be sure to add the -
chapter02/stages.xml
rce9b68d r34fe7e0 26 26 <itemizedlist> 27 27 <listitem> 28 <para>Procedures done as the root user after Section 2.4 need to 29 have the LFS environment variable set <emphasis>FOR THE ROOT 30 USER</emphasis>.</para> 28 <para>Procedures done as the 29 <systemitem class="username">root</systemitem> user after Section 30 2.4 need to have the LFS environment variable set 31 <emphasis>FOR THE ROOT USER</emphasis>.</para> 31 32 </listitem> 32 33 </itemizedlist> … … 42 43 43 44 <listitem> 44 <para>Threse two chapters must be done as user <emphasis>lfs</emphasis>. 45 <para>These two chapters <emphasis>must</emphasis> be done as user 46 <systemitem class="username">lfs</systemitem>. 45 47 A <command>su - lfs</command> needs to be done before any task in these 46 48 chapters. Failing to do that, you are at risk of installing packages to the … … 69 71 <para>A few operations, from <quote>Changing Ownership</quote> to 70 72 <quote>Entering the Chroot Environment</quote> must be done as the 71 root user, with the LFS environment variable set for the root user.</para> 73 <systemitem class="username">root</systemitem> user, with the LFS 74 environment variable set for the 75 <systemitem class="username">root</systemitem>user.</para> 72 76 </listitem> 73 77 74 78 <listitem> 75 79 <para> When entering chroot, the LFS environment variable must be set 76 for root. The LFS variable is not used afterwards.</para> 80 for <systemitem class="username">root</systemitem>. The LFS 81 variable is not used afterwards.</para> 77 82 </listitem> 78 83 … … 80 85 <para> The virtual file systems must be mounted. This can be done 81 86 before or after entering chroot by changing to a host virtual terminal 82 and, as root, running the commands in 87 and, as <systemitem class="username">root</systemitem>, running the 88 commands in 83 89 <xref linkend='ch-tools-bindmount'/> and 84 90 <xref linkend='ch-tools-kernfsmount'/>.</para> -
chapter05/glibc.xml
rce9b68d r34fe7e0 148 148 149 149 <warning><para>If <envar>LFS</envar> is not properly set, and despite the 150 recommendations, you are building as root, the next command will install 151 the newly built glibc to your host system, which most likely will render it 152 unusable. So double check that the environment is correctly set for user 153 <systemitem class="username">lfs</systemitem>.</para></warning> 150 recommendations, you are building as 151 <systemitem class="username">root</systemitem>, the next command will 152 install the newly built glibc to your host system, which most likely 153 will render it unusable. So double check that the environment is 154 correctly set, before running the following command.</para></warning> 154 155 155 156 <screen><userinput remap="install">make DESTDIR=$LFS install</userinput></screen> -
chapter06/introduction.xml
rce9b68d r34fe7e0 23 23 24 24 <para>Once again, let us recall that improper setting of <envar>LFS</envar> 25 together with building as root, may render your computer unusable. 25 together with building as <systemitem class="username">root</systemitem>, 26 may render your computer unusable. 26 27 This whole chapter must be done as user <systemitem 27 28 class="username">lfs</systemitem>, with the environment as described in -
chapter08/coreutils.xml
rce9b68d r34fe7e0 88 88 <listitem> 89 89 <para>This environment variable allows the package to be 90 built as the rootuser.90 built as the <systemitem class="username">root</systemitem> user. 91 91 </para> 92 92 </listitem> -
chapter08/tar.xml
rce9b68d r34fe7e0 57 57 <listitem> 58 58 <para>This forces the test for <function>mknod</function> to be run 59 as root. It is generally considered dangerous to run this test as 60 the root user, but as it is being run on a system that has only been 59 as <systemitem class="username">root</systemitem>. 60 It is generally considered dangerous to run this test as 61 the <systemitem class="username">root</systemitem> user, but as it 62 is being run on a system that has only been 61 63 partially built, overriding it is OK.</para> 62 64 </listitem> -
chapter08/util-linux.xml
rce9b68d r34fe7e0 89 89 <para>If desired, run the test suite as a non-root user:</para> 90 90 91 <warning><para>Running the test suite as the root user can be harmful to 91 <warning><para>Running the test suite as the 92 <systemitem class="username">root</systemitem> user can be harmful to 92 93 your system. To run it, the CONFIG_SCSI_DEBUG option for the kernel must 93 94 be available in the currently running system and must be built as a -
chapter09/systemd-custom.xml
rce9b68d r34fe7e0 42 42 43 43 <para>The boot messages can always be reviewed by using the 44 <userinput>journalctl -b</userinput> command as the root user.</para> 44 <userinput>journalctl -b</userinput> command as the 45 <systemitem class="username">root</systemitem> user.</para> 45 46 46 47 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.