Changes in chapter04/addinguser.xml [4d8854a:aa9ade1]

File:

• chapter04/addinguser.xml (modified) (5 diffs)

chapter04/addinguser.xml

@@ -15 +15 @@
   the packages in the next two chapters are built as an unprivileged user.
   You could use your own user name, but to make it easier to set up a clean
-  working environment, create a new user called <systemitem
+  working environment, we will create a new user called <systemitem
   class="username">lfs</systemitem> as a member of a new group (also named
-  <systemitem class="groupname">lfs</systemitem>) and use this user during
+  <systemitem class="groupname">lfs</systemitem>) and run commands as &lfs-user; during
   the installation process. As <systemitem class="username">root</systemitem>,
   issue the following commands to add the new user:</para>
@@ -25 +25 @@
 
   <variablelist>
-    <title>The meaning of the command line options:</title>
+    <title>This is what the command line options mean:</title>
 
     <varlistentry>
@@ -55 +55 @@
       <listitem>
         <para>This parameter prevents possible copying of files from a skeleton
-        directory (default is <filename class="directory">/etc/skel</filename>)
+        directory (the default is <filename class="directory">/etc/skel</filename>)
         by changing the input location to the special null device.</para>
       </listitem>
@@ -69 +69 @@
   </variablelist>
 
-  <para>To log in as <systemitem class="username">lfs</systemitem> (as opposed
-  to switching to user <systemitem class="username">lfs</systemitem> when logged
-  in as <systemitem class="username">root</systemitem>, which does not require
-  the <systemitem class="username">lfs</systemitem> user to have a password),
-  give <systemitem class="username">lfs</systemitem> a password:</para>
+  <para>If you want to log in as &lfs-user; or switch to &lfs-user; from a
+  non-&root; user (as opposed to switching to user &lfs-user;
+  when logged in as &root;, which does not require the &lfs-user; user to
+  have a password), you need to set a password of &lfs-user;.  Issue the
+  following command as the &root; user to set the password:</para>
 
 <screen role="nodump"><userinput>passwd lfs</userinput></screen>
 
   <para>Grant <systemitem class="username">lfs</systemitem> full access to
-  all directories under <filename class="directory">$LFS</filename> by making
-  <systemitem class="username">lfs</systemitem> the directory owner:</para>
+  all the directories under <filename class="directory">$LFS</filename> by making
+  <systemitem class="username">lfs</systemitem> the owner:</para>
 
-<screen><userinput>chown -v lfs $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}</userinput></screen>
+<screen><userinput>chown -v lfs $LFS/{usr{,/*},lib,var,etc,bin,sbin,tools}
+case $(uname -m) in
+  x86_64) chown -v lfs $LFS/lib64 ;;
+esac</userinput></screen>
 
-  <note><para>In some host systems, the following command does not complete
-  properly and suspends the login to the &lfs-user; user to the background.
+<note><para>In some host systems, the following <command>su</command> command does not complete
+  properly and suspends the login for the &lfs-user; user to the background.
   If the prompt "lfs:~$" does not appear immediately, entering the
   <command>fg</command> command will fix the issue.</para></note>
 
-  <para>Next, login as user <systemitem class="username">lfs</systemitem>.
-  This can be done via a virtual console, through a display manager, or with
-  the following substitute/switch user command:</para>
+  <para>Next, start a shell running as user &lfs-user;. This can be done by
+  logging in as &lfs-user; on a virtual console, or with the following
+  substitute/switch user command:</para>
 
 <screen role="nodump"><userinput>su - lfs</userinput></screen>
@@ -96 +99 @@
   <para>The <quote><parameter>-</parameter></quote> instructs
   <command>su</command> to start a login shell as opposed to a non-login shell.
-  The difference between these two types of shells can be found in detail in
+  The difference between these two types of shells is described in detail in
   <filename>bash(1)</filename> and <command>info bash</command>.</para>