gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

decorate the references to root and lfs user

Browse Source 
The references already correctly decorated are not changed because "if
it's not broken don't fix it".
This commit is contained in:
Xi Ruoyao 2022-04-21 14:12:43 +08:00
parent 421e0cfcda
commit e286d8db14
No known key found for this signature in database
GPG Key ID: D95E4716CCBB34DC
9 changed files with 14 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
chapter02/stages.xml
View File

@ -71,8 +71,7 @@
<para>A few operations, from <quote>Changing Ownership</quote> to <para>A few operations, from <quote>Changing Ownership</quote> to
<quote>Entering the Chroot Environment</quote> must be done as the <quote>Entering the Chroot Environment</quote> must be done as the
<systemitem class="username">root</systemitem> user, with the LFS <systemitem class="username">root</systemitem> user, with the LFS
environment variable set for the environment variable set for the &root; user.</para>
<systemitem class="username">root</systemitem>user.</para>
</listitem> </listitem>
<listitem> <listitem>

4
chapter04/addinguser.xml
View File

@ -86,8 +86,8 @@ case $(uname -m) in
esac</userinput></screen> esac</userinput></screen>
<note><para>In some host systems, the following command does not complete <note><para>In some host systems, the following command does not complete
properly and suspends the login to the lfs user to the background. If the properly and suspends the login to the &lfs-user; user to the background.
prompt "lfs:~$" does not appear immediately, entering the If the prompt "lfs:~$" does not appear immediately, entering the
<command>fg</command> command will fix the issue.</para></note> <command>fg</command> command will fix the issue.</para></note>
<para>Next, login as user <systemitem class="username">lfs</systemitem>. <para>Next, login as user <systemitem class="username">lfs</systemitem>.

4
chapter07/cleanup.xml
View File

@ -156,9 +156,9 @@ tar -cJpf $HOME/lfs-temp-tools-&version;.tar.xz .</userinput></screen>
restore when they don't need to. --> restore when they don't need to. -->
<warning><para>The following commands are extremely dangerous. If <warning><para>The following commands are extremely dangerous. If
you run <command>rm -rf ./*</command> as the root user and you you run <command>rm -rf ./*</command> as the &root; user and you
do not change to the $LFS directory or the <envar>LFS</envar> do not change to the $LFS directory or the <envar>LFS</envar>
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.</para></warning> your entire host system. YOU ARE WARNED.</para></warning>
<screen role="nodump"><computeroutput>cd $LFS <screen role="nodump"><computeroutput>cd $LFS

2
chapter07/introduction.xml
View File

@ -25,7 +25,7 @@
<para>Until <xref linkend="ch-tools-chroot"/>, the commands must be <para>Until <xref linkend="ch-tools-chroot"/>, the commands must be
run as <systemitem class="username">root</systemitem>, with the run as <systemitem class="username">root</systemitem>, with the
<envar>LFS</envar> variable set. After entering chroot, all commands <envar>LFS</envar> 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 you built LFS on. Be careful anyway, as it is easy to destroy the whole
LFS system with badly formed commands.</para> LFS system with badly formed commands.</para>

2
chapter08/bash.xml
View File

@ -73,7 +73,7 @@
<screen><userinput remap="test">chown -Rv tester .</userinput></screen> <screen><userinput remap="test">chown -Rv tester .</userinput></screen>
<para>The testsuite of the package is designed to be run as a non-root <para>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 user that owns the terminal connected to standard input. To satisfy the
requirement, spawn a new pseudo terminal using requirement, spawn a new pseudo terminal using
<application>Expect</application> and run the tests as the <systemitem <application>Expect</application> and run the tests as the <systemitem

4
chapter08/coreutils.xml
View File

@ -124,8 +124,8 @@ FORCE_UNSAFE_CONFIGURE=1 ./configure \
<screen><userinput remap="test">echo "dummy:x:102:tester" &gt;&gt; /etc/group</userinput></screen> <screen><userinput remap="test">echo "dummy:x:102:tester" &gt;&gt; /etc/group</userinput></screen>
<para>Fix some of the permissions so that the non-root user can compile and <para>Fix some of the permissions so that the non-&root; user can
run the tests:</para> compile and run the tests:</para>
<screen><userinput remap="test">chown -Rv tester . </userinput></screen> <screen><userinput remap="test">chown -Rv tester . </userinput></screen>

2
chapter08/util-linux.xml
View File

@ -84,7 +84,7 @@
<screen><userinput remap="make">make</userinput></screen> <screen><userinput remap="make">make</userinput></screen>
<para>If desired, run the test suite as a non-root user:</para> <para>If desired, run the test suite as a non-&root; user:</para>
<warning><para>Running the test suite as the <warning><para>Running the test suite as the
<systemitem class="username">root</systemitem> user can be harmful to <systemitem class="username">root</systemitem> user can be harmful to

4
chapter10/kernel.xml
View File

@ -248,8 +248,8 @@ File systems ---&gt;
<caution> <caution>
<para>If the host system has a separate /boot partition, the files copied <para>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 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 host (outside chroot) to /mnt/lfs/boot before proceeding. As the
user in the <emphasis>host system</emphasis>:</para> &root; user in the <emphasis>host system</emphasis>:</para>
<screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen> <screen role="nodump"><userinput>mount --bind /boot /mnt/lfs/boot</userinput></screen>
</caution> </caution>

4
chapter11/reboot.xml
View File

@ -46,8 +46,8 @@
<listitem><para>Installing <ulink <listitem><para>Installing <ulink
url='&blfs-book;postlfs/sudo.html'>sudo</ulink> may be useful for url='&blfs-book;postlfs/sudo.html'>sudo</ulink> may be useful for
building packages as a non-root user and easily installing the resulting building packages as a non-&root; user and easily installing the
packages in your new system.</para></listitem> resulting packages in your new system.</para></listitem>
<listitem><para>If you want to access your new system from a remote system <listitem><para>If you want to access your new system from a remote system
within a comfortable GUI environment, install <ulink within a comfortable GUI environment, install <ulink