Context Navigation

r90bc173	rbccbdaea
42	42	edit the file, you should leave the characters (normally '^[[H^[[2J') on the
43	43	first line alone.</para>
44
	44
45	45	<note><para>Terminal escape sequences are special codes recognized by the
46	46	terminal. The ^[ represents an ASCII ESC character. The sequence ESC [ H

postlfs/config/users.xml

r90bc173	rbccbdaea
30	30	<para>Throughout BLFS, many packages install programs that
31	31	run as daemons or in some way should have a user or group name
32		assigned. Generally these names are used to map a user ID (uid) or group
	32	assigned. Generally these names are used to map a user ID (uid) or group
33	33	ID (gid) for system use. Generally the specific uid or gid numbers used
34	34	by these applications are not significant. The exception of course, is

r90bc173	rbccbdaea
99	99
100	100	<bridgehead renderas="sect3">CrackLib Dependencies</bridgehead>
101
	101
102	102	<bridgehead renderas="sect4">Optional</bridgehead>
103	103	<para><xref linkend="python"/></para>

r90bc173	rbccbdaea
84	84	using <xref linkend='heimdal'/> to implement the functionality of this
85	85	package.</para></note> -->
86
	86
87	87
88	88	<para><application>MIT krb5</application> is distributed in a

-              r90bc173
+              rbccbdaea
         <title>Configuring Default Environment</title>
           <para>During previous configuration, several items were removed from
+          <para>During previous configuration, several items were removed from
           <filename>/etc/login.defs</filename>.  Some of these items are now
           controlled by the <filename class='libraryfile'>pam_env.so</filename>
           module and the <filename>/etc/security/pam_env.conf</filename>
           configuration file.  In particular, the default path has been
           changed.  To recover your default path, execute the following
+          controlled by the <filename class='libraryfile'>pam_env.so</filename>
+          module and the <filename>/etc/security/pam_env.conf</filename>
+          configuration file.  In particular, the default path has been
+          changed.  To recover your default path, execute the following
           commands:</para>
 …
           <note>
             <para>ENV_SUPATH is no longer supported.  You must create
             a valid <filename>/root/.bashrc</filename> file to provide a
+            <para>ENV_SUPATH is no longer supported.  You must create
+            a valid <filename>/root/.bashrc</filename> file to provide a
             modified path for the super-user.</para>
           </note>

-              r90bc173
+              rbccbdaea
     <bridgehead renderas="sect4">Optional</bridgehead>
 -->
   </sect2>
 …
       any program without typing a password each time root privileges are
       needed.  This can be configured as:</para>
       <screen># User alias specification
 User_Alias  ADMIN = YourLoginId

-              r90bc173
+              rbccbdaea
     (<command>csh</command>)</quote>. This is useful as an alternative shell
     for those who prefer C syntax to that of the <command>bash</command> shell,
     and also because some programs require the C shell in order to perform
+    and also because some programs require the C shell in order to perform
     installation tasks.</para>
 …
     <para><parameter>--bindir=/bin</parameter>: This installs the
     <command>tcsh</command> program in
+    <command>tcsh</command> program in
     <filename class='directory'>/bin</filename> instead of
     <filename class='directory'>/usr/bin</filename>.</para>
 …
     <para><command>ln -v -sf tcsh /bin/csh</command>: The FHS states that if
     there is a <application>C</application> shell installed, there should be a
     symlink from <filename>/bin/csh</filename> to it. This creates that
+    symlink from <filename>/bin/csh</filename> to it. This creates that
     symlink.</para>
 …
       <para>Update <filename>/etc/shells</filename> to include the C shell
       program names (as the <systemitem class="username">root</systemitem>
+      program names (as the <systemitem class="username">root</systemitem>
       user):</para>

Note: See TracChangeset for help on using the changeset viewer.