Changeset cfc2a54 for postlfs/config/profile.xml

Timestamp:

08/22/2003 03:37:27 PM (21 years ago)

Author:

Larry Lawrence <larry@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

0108c1d

Parents:

71f73f0f

Message:

Added Bill's patch to postlfs

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@984 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• postlfs/config/profile.xml (modified) (5 diffs)

postlfs/config/profile.xml

@@ -6 +6 @@
 referred to as just "the shell") uses a collection of startup files to
 help create an environment to run in.  Each file has a specific use and
-may affect login and interactive environments differently.</para>
-
-<para>An interactive login shell is started after a successful login by
-<filename>/bin/login</filename> by reading the
+may affect login and interactive environments differently.  The files in
+the <filename>/etc</filename> directory generally provide global
+settings. If an equivalent file exists in your home directory it may
+override the global settings.
+</para>
+
+<para>An interactive login shell is started after a successful login, using
+<filename>/bin/login</filename>, by reading the
 <filename>/etc/passwd</filename> file.  An
 interactive non-login shell is started at the command line (e.g.
@@ -21 +25 @@
 Shells.</emphasis></para>
 
-<para>The following files are needed to make sure that the correct
-environment is read for each of the ways the shell can be invoked:
-<filename>/etc/profile</filename>, <filename>/etc/bashrc</filename>,
+<para>The following files are used to make sure that the correct
+environment is established for each of the ways the shell can be invoked:
+<filename>/etc/profile</filename> and its private equivalent
 <filename>~/.bash_profile</filename>, and
-<filename>~/.bashrc</filename>.  The file
-<filename>~/.bash_logout</filename> is not used for an invocation of the
-shell.  It is read by the shell when a user logouts of the system.  The
-files <filename>/etc/profile</filename> and
+<filename>/etc/bashrc</filename> (unofficial) and its private equivalent
+<filename>~/.bashrc</filename>.
+</para>
+
+<para>
+The file <filename>~/.bash_logout</filename> is not used for an
+invocation of the shell.  It is read by the shell when a user logs out
+of the system.</para>
+
+<para>The files <filename>/etc/profile</filename> and
 <filename>~/.bash_profile</filename> are read when the shell is invoked
-as a interactive login shell.  The file <filename>~/.bashrc</filename>
+as an interactive login shell.  The file <filename>~/.bashrc</filename>
 is read when the shell is invoked as an interactive non-login
-shell.</para> 
+shell and it reads <filename>/etc/bashrc</filename> if it exists</para> 
+
+<para>Also useful are the <filename>/etc/dircolors</filename> and
+<filename>~/.dircolors</filename> files called from
+<filename>/etc/profile</filename>. They control colorized output of
+things like <emphasis>ls --color</emphasis>.
+</para>
 
 <para>Here is a base <filename>/etc/profile</filename>.  Comments in the
@@ -141 +157 @@
 
 <para>Here is a base <filename>~/.bash_profile</filename>.  Comments in
-the file should explain everything you need.</para>
+the file should explain everything you need.  If you want each new user
+to have this file automatically provided, just change the output of the
+next command to <filename>/etc/skel/.bash_profile</filename> and check the
+permissions after the command is run. You can then copy
+<filename>/etc/skel/.bash_profile</filename> to the home directories of
+already existing users, including root, and set the owner and group
+appropriately. 
+</para>
 
 <screen><userinput><command>cat &gt; ~/.bash_profile &lt;&lt; "EOF"</command>
@@ -168 +191 @@
 
 <para>Here is a base <filename>~/.bashrc</filename>.  Comments in the
-file should explain everything you need.</para>
+file should explain everything you need.  The comments and
+instructions for using <filename>/etc/skel</filename> for
+<filename>.bash_profile</filename> above also apply here. Only the
+target file names are different.</para>
 
 <screen><userinput><command>cat &gt; ~/.bashrc &lt;&lt; "EOF"</command>
@@ -205 +231 @@
 <command>EOF</command></userinput></screen>
 
-<para>If you want to use the <filename>/etc/dircolors</filename> or
-<filename>~/.dircolors</filename> files called from
-<filename>/etc/profile</filename>, then run the following: 
-<userinput>/bin/dircolors -p > /etc/dircolors</userinput> or 
-<userinput>/bin/dircolors -p > ~/.dircolors</userinput> respectively.
-The file in the <filename>/etc</filename> directory should be used for
-global settings and if one exists in your home directory then it will
-overwrite the global settings.  It might be a good idea to create a base
-<filename>.dircolors</filename> file and place it in the
-<filename>/etc/skel</filename> directory for new users.</para>
+<para>
+If you want to use the <filename>dircolors</filename> capability
+then run the following command. The <filename>/etc/skel</filename> setup
+steps seen 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 copied.
+</para>
+
+<para>
+<userinput><command>/bin/dircolors -p > /etc/dircolors</command></userinput>
+</para>
 
 <para>Ian Macdonald has written an excellent collection of tips and