Changeset 490dc153

Timestamp:

02/05/2022 12:48:27 PM (22 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, arm, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/parallelism, xry111/pip3, xry111/rust-wip-20221008

Children:

d79ba5b

Parents:

69c4524

git-author:

Xi Ruoyao <xry111@…> (02/05/2022 03:36:39 AM)

git-committer:

Xi Ruoyao <xry111@…> (02/05/2022 12:48:27 PM)

Message:

remove "+h" in bash commands in chroot (#4998)

In the new cross-compilation approach, the $PATH in chroot does not
contain '/tools/bin'. So "+h" is useless in chroot as the newly
installed tools always replace the temporary counterpart at the same
location.

"+h" in chapter4/settingenviron.xml is kept deliberately. Currently
$LFS/tools/bin only contains programs prefixed with
"x86_64-lfs-linux-gnu-", and it's highly unlikely that any distro will
ever ship a program named with such prefix. So it may seems that we can
remove this "+h" as well. However, the situation may change in future
and we can take this oppertunity to teach the advantage and disvantage
of bash hash feature.

Files:

• chapter01/changelog.xml (modified) (1 diff)
• chapter04/settingenviron.xml (modified) (1 diff)
• chapter07/chroot.xml (modified) (2 diffs)
• chapter07/createfiles.xml (modified) (1 diff)
• chapter08/bash.xml (modified) (1 diff)
• chapter08/revisedchroot.xml (modified) (1 diff)

chapter01/changelog.xml

@@ -44 +44 @@
       <itemizedlist>
         <listitem>
+          <para>[xry111] - Rename <command>bash</command>
+          <literal>+h</literal> directives in chroot.  Fixes
+          <ulink url="&lfs-ticket-root;4998">#4998</ulink>.</para>
+        </listitem>
+        <listitem>
           <para>[xry111] - Update to man-db-2.10.0.  Fixes
           <ulink url="&lfs-ticket-root;5002">#5002</ulink>.</para>

chapter04/settingenviron.xml

@@ -65 +65 @@
   the shell will always search the <envar>PATH</envar> when a program is to
   be run. As such, the shell will find the newly compiled tools in
-  <filename class="directory">$LFS/tools</filename> as soon as they are
-  available without remembering a previous version of the same program in a
-  different location.</para>
+  <filename class="directory">$LFS/tools/bin</filename> as soon as they are
+  available without remembering a previous version of the same program
+  provided by the host distro, in
+  <filename class='directory'>/usr/bin</filename> or
+  <filename class='directory'>/bin</filename>.</para>
       </listitem>
     </varlistentry>

chapter07/chroot.xml

@@ -24 +24 @@
     PS1='(lfs chroot) \u:\w\$ ' \
     PATH=/usr/bin:/usr/sbin     \
-    /bin/bash --login +h</userinput></screen>
+    /bin/bash --login</userinput></screen>
 
   <para>The <parameter>-i</parameter> option given to the <command>env</command>
@@ -45 +45 @@
   <para>Notice that <filename class="directory">/tools/bin</filename> is not
   in the <envar>PATH</envar>. This means that the cross toolchain will no longer be
-  used in the chroot environment. This occurs when the shell does not
-  <quote>remember</quote> the locations of executed binaries&mdash;for this
-  reason, hashing is switched off by passing the <parameter>+h</parameter> option
-  to <command>bash</command>.</para>
+  used in the chroot environment.</para>
 
   <para>Note that the <command>bash</command> prompt will say

chapter07/createfiles.xml

@@ -185 +185 @@
   work:</para>
 
-<screen role="nodump"><userinput>exec /usr/bin/bash --login +h</userinput></screen>
-
-  <para>Note the use of the <parameter>+h</parameter> directive. This tells
-  <command>bash</command> not to use its internal path hashing. Without this
-  directive, <command>bash</command> would remember the paths to binaries it has
-  executed. To ensure the use of the newly compiled binaries as soon as they are
-  installed, the <parameter>+h</parameter> directive will be used for the duration
-  of this and the next chapter.</para>
+<screen role="nodump"><userinput>exec /usr/bin/bash --login</userinput></screen>
 
   <para>The <command>login</command>, <command>agetty</command>, and

chapter08/bash.xml

@@ -95 +95 @@
     currently being executed):</para>
 
- <screen role="nodump"><userinput>exec /usr/bin/bash --login +h</userinput></screen>
-
-    <note>
-      <para>The parameters used make the <command>bash</command>
-      process an interactive login shell and continues to disable hashing so
-      that new programs are found as they become available.</para>
-    </note>
+ <screen role="nodump"><userinput>exec /usr/bin/bash --login</userinput></screen>
 
   </sect2>

chapter08/revisedchroot.xml

@@ -14 +14 @@
 
 <screen><userinput>rm -rf /tmp/*</userinput></screen>
-
-  <para>Now log out and reenter the chroot environment with an updated
-  chroot command.  From now on, use this updated chroot command any time
-  you need to reenter the chroot environment after exiting:</para>
-
-<screen role="nodump"><userinput>logout
-
-chroot "$LFS" /usr/bin/env -i          \
-    HOME=/root TERM="$TERM"            \
-    PS1='(lfs chroot) \u:\w\$ '        \
-    PATH=/usr/bin:/usr/sbin            \
-    /usr/bin/bash --login</userinput></screen>
-
-  <para>Here the <parameter>+h</parameter> option is not used anymore, since
-  all the previous programs have been replaced: hashing is therefore
-  possible.</para>
-
-  <para>If the virtual kernel file systems have been unmounted, either manually
-  or through a reboot, ensure that the virtual kernel file systems are mounted
-  when reentering the chroot. This process was explained in <xref
-  linkend="ch-tools-bindmount"/> and <xref
-  linkend="ch-tools-kernfsmount"/>.</para>
 
   <para>There are also several files installed in the /usr/lib and /usr/libexec