r4761 - trunk/BOOK/postlfs/config

randy at linuxfromscratch.org randy at linuxfromscratch.org
Fri Jul 22 11:47:46 PDT 2005


Author: randy
Date: 2005-07-22 12:47:45 -0600 (Fri, 22 Jul 2005)
New Revision: 4761

Modified:
   trunk/BOOK/postlfs/config/profile.xml
   trunk/BOOK/postlfs/config/users.xml
Log:
Minor textual updates to the 'Shell Startup files' and 'System Users and Groups' sections

Modified: trunk/BOOK/postlfs/config/profile.xml
===================================================================
--- trunk/BOOK/postlfs/config/profile.xml	2005-07-22 18:00:22 UTC (rev 4760)
+++ trunk/BOOK/postlfs/config/profile.xml	2005-07-22 18:47:45 UTC (rev 4761)
@@ -30,7 +30,8 @@
   startup.</para>
 
   <para>An interactive non-login shell is normally started at the command-line
-  (e.g.,  <prompt>[prompt]$</prompt><command>/bin/bash</command>) or by the
+  using a shell program (e.g.,
+  <prompt>[prompt]$</prompt><command>/bin/bash</command>) or by the
   <command>/bin/su</command> command.  An interactive non-login shell is also
   started with a terminal program such as <command>xterm</command> or
   <command>konsole</command> from within a graphical environment. This type of
@@ -53,8 +54,17 @@
 
   <para>For more information see <command>info bash</command> --
   <emphasis role="strong">Nodes: Bash Startup Files and Interactive
-  Shells.</emphasis></para>
+  Shells</emphasis>.</para>
 
+  <note>
+    <para>Most of the instructions below are used to create files located in
+    the <filename class='directory'>/etc</filename> directory structure which
+    requires you to execute the commands as the
+    <systemitem class='username'>root</systemitem> user. If you elect to create
+    the files in user's home directories instead, you should run the commands
+    as an unprivileged user.</para>
+  </note>
+
   <sect2 id="etc-profile-profile">
     <title>/etc/profile</title>
 
@@ -64,17 +74,17 @@
 
     <para>Here is a base <filename>/etc/profile</filename>. This file starts by
     setting up some helper functions and some basic parameters.  It specifies some
-    <filename>bash</filename> history parameters and, for security purposes,
+    <command>bash</command> history parameters and, for security purposes,
     disables keeping a permanent history file for the <systemitem
     class="username">root</systemitem> user.  It also sets a
     default user prompt.  It then calls small, single purpose scripts in the
     <filename class='directory'>/etc/profile.d</filename> directory to provide most
-    initialization.  </para>
+    of the initialization.</para>
 
     <para>For more information on the escape sequences you can use for your prompt
-    (e.g.,  the <envar>PS1</envar> environment variable) see <command>info
+    (i.e., the <envar>PS1</envar> environment variable) see <command>info
     bash</command> -- <emphasis role="strong">Node: Printing a
-    Prompt.</emphasis></para>
+    Prompt</emphasis>.</para>
 
 <screen role="root"><userinput>cat > /etc/profile << "EOF"
 <literal># Begin /etc/profile
@@ -151,7 +161,7 @@
       </indexterm>
 
       <para>Now create the <filename class='directory'>/etc/profile.d</filename>
-      directory, where the individual initialization scripts are placed.</para>
+      directory, where the individual initialization scripts are placed:</para>
 
 <screen role="root"><userinput>install --directory --mode=0755 --owner=root --group=root /etc/profile.d</userinput></screen>
 
@@ -167,7 +177,7 @@
       <para>This script uses the <filename>~/.dircolors</filename> and
       <filename>/etc/dircolors</filename> files to control the colors of file names in a
       directory listing. They control colorized output of things like <command>ls
-      --color</command>.  The explaination of how to initialize these files is at the
+      --color</command>.  The explanation of how to initialize these files is at the
       end of this section.</para>
 
 <screen role="root"><userinput>cat > /etc/profile.d/dircolors.sh << "EOF"
@@ -325,8 +335,9 @@
       <envar>PROMPT_COMMAND</envar>. If set, the value of
       <envar>PROMPT_COMMAND</envar> is executed as a command prior to issuing
       each primary prompt.  The sequence \e is an ESC character.  \a is a
-      BEL character.  For a reference on xterm escape sequences, see <ulink
-      url="http://rtfm.etla.org/xterm/ctlseq.html"/></para>
+      BEL character.  For a reference on <command>xterm</command> escape
+      sequences, see <ulink
+      url="http://rtfm.etla.org/xterm/ctlseq.html"/>.</para>
 
 <screen role="root"><userinput>cat > /etc/profile.d/extra-prompt.sh << "EOF"
 <literal>PROMPT_COMMAND="echo -ne '\e[1m${USER}@${HOSTNAME} : ${PWD}\e[0m\a'"
@@ -590,7 +601,7 @@
 
     <para> If you want to use the <filename>dircolors</filename> capability, then
     run the following command. The <filename class="directory">/etc/skel</filename>
-    setup steps seen above also can be used here to provide a
+    setup steps shown above also can be used here to provide a
     <filename>~/.dircolors</filename> file when a new user is set up. As before,
     just change the output file name on the following command and assure the
     permissions, owner, and group are correct on the files created and/or
@@ -605,8 +616,7 @@
 
     <para>Finally, Ian Macdonald has written an excellent collection of tips and
     tricks to enhance your shell environment.  You can read it online at
-    <ulink url="http://www.caliban.org/bash/index.shtml">
-    http://www.caliban.org/bash/index.shtml</ulink>.</para>
+    <ulink url="http://www.caliban.org/bash/index.shtml"/>.</para>
 
   </sect2>
 

Modified: trunk/BOOK/postlfs/config/users.xml
===================================================================
--- trunk/BOOK/postlfs/config/users.xml	2005-07-22 18:00:22 UTC (rev 4760)
+++ trunk/BOOK/postlfs/config/users.xml	2005-07-22 18:47:45 UTC (rev 4761)
@@ -27,15 +27,15 @@
     <primary sortas="e-etc-login.defs">/etc/login.defs</primary>
   </indexterm>
 
-  <para>Throughout BLFS, there are many packages that install programs that
+  <para>Throughout BLFS, many packages install programs that
   run as daemons or in some way should have a user or group name
   assigned.  Generally these names are used to map a user ID (uid) or group 
   ID (gid) for system use.  Generally the specific uid or gid numbers used
-  by these applications are not significant.  The exception, of course is
-  that root has a uid and gid of 0 (zero) that is indeed special.  The uid
-  values are stored in <filename>/etc/passwd</filename> and the gid values
-  are found in <filename>/etc/group</filename>.
-  </para>
+  by these applications are not significant.  The exception of course, is
+  that <systemitem class='username'>root</systemitem> has a uid and gid of 0
+  (zero) that is indeed special.  The uid values are stored in
+  <filename>/etc/passwd</filename> and the gid values
+  are found in <filename>/etc/group</filename>.</para>
 
   <para>Customarily, Unix systems classify users and groups into two
   categories: system users and regular users.  The system users and groups are
@@ -47,8 +47,8 @@
   <command>useradd</command> or a group with <command>groupadd</command> the values
   assigned will always be above these cutoff values.</para>
 
-  <para>Additionally, the 
-  <ulink url='http://refspecs.freestandards.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/usernames.html'>
+  <para>Additionally, the <ulink
+  url='http://refspecs.freestandards.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/usernames.html'>
   Linux Standards Base</ulink> recommends that system uid and gid values should be
   below 100.</para>
 




More information about the blfs-book mailing list