gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Moved the exit and re-enter of the chroot commands right after the

Browse Source 
install. instructions


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@868 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2001-07-31 20:03:28 +00:00
parent af7bcdb0e7
commit 463e88840d
1 changed files with 8 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
chapter06/glibc-inst.xml
View File

@ -25,7 +25,9 @@ would do.</para>
<userinput>mv config.make~ config.make &amp;&amp;</userinput> <userinput>mv config.make~ config.make &amp;&amp;</userinput>
<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</userinput></screen></para> <userinput>make localedata/install-locales &amp;&amp;</userinput>
<userinput>logout &amp;&amp;</userinput>
&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>
@ -39,16 +41,11 @@ package. But there is nothing to worry about: Glib will still be
installed the same way as when msgfmt is present. It can safely be installed the same way as when msgfmt is present. It can safely be
ignored in our case.</para> ignored in our case.</para>
<para>By exiting the chroot'ed environment and re-entering it, you will be <para>The last two commands make you exit and re-enter the chroot'ed
able to get rid of the "I have no name!" message in the command prompt, environment and re-entering it. This is done to get rid of the "I have
which is caused by bash's inability to resolve a userid to a username. no name!" message in the command prompt, which was caused by bash's
You don't have to exit and re-enter chroot, but it's highly recommended inability to resolve a userid to a username (which in turn was caused by
to ensure a properly working bash.</para> the missing Glibc installation).</para>
<para>Run the following commands to accomplish this:</para>
<para><screen><userinput>logout</userinput>
&c6-chrootcmd;</screen></para>
</sect2> </sect2>