removed exit+enter chroot commands, replaced by an "exec /bin/bash",

moved it's explanation to glibc-exp.xml


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1030 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-08-25 16:56:29 +00:00
parent f3c04e6f69
commit 76a3d6d07c
2 changed files with 8 additions and 8 deletions

View File

@ -55,5 +55,12 @@ hasn't been installed yet.</para>
<para><userinput>mv -f config.make~ config.make:</userinput> Again, we are moving <para><userinput>mv -f config.make~ config.make:</userinput> Again, we are moving
the temporary file over the original.</para> the temporary file over the original.</para>
<para><userinput>exec /bin/bash:</userinput>This command will
start a new bash shell which will replace the current shell. This is
done to get rid of the "I have no name!" message in the command
prompt, which was caused by bash's inability to resolve a userid to
a username (which in turn was caused by the missing Glibc
installation).</para>
</sect2> </sect2>

View File

@ -31,8 +31,7 @@ would do.</para>
<userinput>make &amp;&amp;</userinput> <userinput>make &amp;&amp;</userinput>
<userinput>make install &amp;&amp;</userinput> <userinput>make install &amp;&amp;</userinput>
<userinput>make localedata/install-locales &amp;&amp;</userinput> <userinput>make localedata/install-locales &amp;&amp;</userinput>
<userinput>logout</userinput> <userinput>exec /bin/bash</userinput></screen></para>
&c6-chrootcmd;</screen></para>
<para>During the configure stage you will see the following warning:</para> <para>During the configure stage you will see the following warning:</para>
@ -45,11 +44,5 @@ would do.</para>
gettext package, but it can safely be ignored in our case. The glibc gettext package, but it can safely be ignored in our case. The glibc
installation will not be affected.</para> installation will not be affected.</para>
<para>The last two commands make you exit and re-enter the chroot'ed
environment. This is done to get rid of the "I have
no name!" message in the command prompt, which was caused by bash's
inability to resolve a userid to a username (which in turn was caused by
the missing Glibc installation).</para>
</sect2> </sect2>