Changeset ba0deaad


Ignore:
Timestamp:
07/22/2005 06:47:45 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
615b431
Parents:
e540c04
Message:

Minor textual updates to the 'Shell Startup files' and 'System Users and Groups' sections

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

Location:
postlfs/config
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • postlfs/config/profile.xml

    re540c04 rba0deaad  
    3131
    3232  <para>An interactive non-login shell is normally started at the command-line
    33   (e.g.,  <prompt>[prompt]$</prompt><command>/bin/bash</command>) or by the
     33  using a shell program (e.g.,
     34  <prompt>[prompt]$</prompt><command>/bin/bash</command>) or by the
    3435  <command>/bin/su</command> command.  An interactive non-login shell is also
    3536  started with a terminal program such as <command>xterm</command> or
    … …  
    5455  <para>For more information see <command>info bash</command> --
    5556  <emphasis role="strong">Nodes: Bash Startup Files and Interactive
    56   Shells.</emphasis></para>
     57  Shells</emphasis>.</para>
     58
     59  <note>
     60    <para>Most of the instructions below are used to create files located in
     61    the <filename class='directory'>/etc</filename> directory structure which
     62    requires you to execute the commands as the
     63    <systemitem class='username'>root</systemitem> user. If you elect to create
     64    the files in user's home directories instead, you should run the commands
     65    as an unprivileged user.</para>
     66  </note>
    5767
    5868  <sect2 id="etc-profile-profile">
    … …  
    6575    <para>Here is a base <filename>/etc/profile</filename>. This file starts by
    6676    setting up some helper functions and some basic parameters.  It specifies some
    67     <filename>bash</filename> history parameters and, for security purposes,
     77    <command>bash</command> history parameters and, for security purposes,
    6878    disables keeping a permanent history file for the <systemitem
    6979    class="username">root</systemitem> user.  It also sets a
    7080    default user prompt.  It then calls small, single purpose scripts in the
    7181    <filename class='directory'>/etc/profile.d</filename> directory to provide most
    72     initialization.  </para>
     82    of the initialization.</para>
    7383
    7484    <para>For more information on the escape sequences you can use for your prompt
    75     (e.g., the <envar>PS1</envar> environment variable) see <command>info
     85    (i.e., the <envar>PS1</envar> environment variable) see <command>info
    7686    bash</command> -- <emphasis role="strong">Node: Printing a
    77     Prompt.</emphasis></para>
     87    Prompt</emphasis>.</para>
    7888
    7989<screen role="root"><userinput>cat &gt; /etc/profile &lt;&lt; "EOF"
    … …  
    152162
    153163      <para>Now create the <filename class='directory'>/etc/profile.d</filename>
    154       directory, where the individual initialization scripts are placed.</para>
     164      directory, where the individual initialization scripts are placed:</para>
    155165
    156166<screen role="root"><userinput>install --directory --mode=0755 --owner=root --group=root /etc/profile.d</userinput></screen>
    … …  
    168178      <filename>/etc/dircolors</filename> files to control the colors of file names in a
    169179      directory listing. They control colorized output of things like <command>ls
    170       --color</command>.  The explaination of how to initialize these files is at the
     180      --color</command>.  The explanation of how to initialize these files is at the
    171181      end of this section.</para>
    172182
    … …  
    326336      <envar>PROMPT_COMMAND</envar> is executed as a command prior to issuing
    327337      each primary prompt.  The sequence \e is an ESC character.  \a is a
    328       BEL character.  For a reference on xterm escape sequences, see <ulink
    329       url="http://rtfm.etla.org/xterm/ctlseq.html"/></para>
     338      BEL character.  For a reference on <command>xterm</command> escape
     339      sequences, see <ulink
     340      url="http://rtfm.etla.org/xterm/ctlseq.html"/>.</para>
    330341
    331342<screen role="root"><userinput>cat &gt; /etc/profile.d/extra-prompt.sh &lt;&lt; "EOF"
    … …  
    591602    <para> If you want to use the <filename>dircolors</filename> capability, then
    592603    run the following command. The <filename class="directory">/etc/skel</filename>
    593     setup steps seen above also can be used here to provide a
     604    setup steps shown above also can be used here to provide a
    594605    <filename>~/.dircolors</filename> file when a new user is set up. As before,
    595606    just change the output file name on the following command and assure the
    … …  
    606617    <para>Finally, Ian Macdonald has written an excellent collection of tips and
    607618    tricks to enhance your shell environment.  You can read it online at
    608     <ulink url="http://www.caliban.org/bash/index.shtml">
    609     http://www.caliban.org/bash/index.shtml</ulink>.</para>
     619    <ulink url="http://www.caliban.org/bash/index.shtml"/>.</para>
    610620
    611621  </sect2>

  • postlfs/config/users.xml

    re540c04 rba0deaad  
    2828  </indexterm>
    2929
    30   <para>Throughout BLFS, there are many packages that install programs that
     30  <para>Throughout BLFS, many packages install programs that
    3131  run as daemons or in some way should have a user or group name
    3232  assigned.  Generally these names are used to map a user ID (uid) or group
    3333  ID (gid) for system use.  Generally the specific uid or gid numbers used
    34   by these applications are not significant.  The exception, of course is
    35   that root has a uid and gid of 0 (zero) that is indeed special.  The uid
    36   values are stored in <filename>/etc/passwd</filename> and the gid values
    37   are found in <filename>/etc/group</filename>.
    38   </para>
     34  by these applications are not significant.  The exception of course, is
     35  that <systemitem class='username'>root</systemitem> has a uid and gid of 0
     36  (zero) that is indeed special.  The uid values are stored in
     37  <filename>/etc/passwd</filename> and the gid values
     38  are found in <filename>/etc/group</filename>.</para>
    3939
    4040  <para>Customarily, Unix systems classify users and groups into two
    … …  
    4848  assigned will always be above these cutoff values.</para>
    4949
    50   <para>Additionally, the
    51   <ulink url='http://refspecs.freestandards.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/usernames.html'>
     50  <para>Additionally, the <ulink
     51  url='http://refspecs.freestandards.org/LSB_3.0.0/LSB-Core-generic/LSB-Core-generic/usernames.html'>
    5252  Linux Standards Base</ulink> recommends that system uid and gid values should be
    5353  below 100.</para>
Note: See TracChangeset for help on using the changeset viewer.