mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-03-06 06:14:47 +00:00
[Bug 229] explain why we cd before chroot to
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1373 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
18b6058533
commit
0bafc62c7c
@ -6,6 +6,9 @@
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem><para>December 11th, 2001 [markh]: Chapter 6: Add the "why we
|
||||
cd $LFS before chroot" explanation.</para></listitem>
|
||||
|
||||
<listitem><para>December 10th, 2001 [markh]: Chapter 6: Add kbd patch
|
||||
for loadkeys -d behaviour (patch by Matthias Benkmann; originally posted
|
||||
to the lfs-dev list).</para></listitem>
|
||||
|
@ -19,6 +19,13 @@ chroot to the same value as outside chroot which is needed for programs
|
||||
like vim and less to operate properly. If you need other variables
|
||||
present, such as CFLAGS or CXXFLAGS, you need to set them again.</para>
|
||||
|
||||
<para>The reason we do <userinput>cd $LFS</userinput> before running the
|
||||
<userinput>chroot</userinput> command is that older sh-utils packages
|
||||
have a chroot program which doesn't do the cd by itself, therefore
|
||||
meaning that we have to perform it manually. While this isn't an issue
|
||||
with most modern distributions, it does no harm anyways and ensures that
|
||||
the command works for everyone.</para>
|
||||
|
||||
<para>Now that we are inside a chroot'ed environment, we can continue to
|
||||
install all the basic system software. You have to make sure all the
|
||||
following commands in this and following chapters are run from within the
|
||||
|
@ -4,8 +4,8 @@
|
||||
|
||||
<!ENTITY book SYSTEM "book/book.xml">
|
||||
|
||||
<!ENTITY version "20011210">
|
||||
<!ENTITY releasedate "December 10th, 2001">
|
||||
<!ENTITY version "20011211">
|
||||
<!ENTITY releasedate "December 11th, 2001">
|
||||
|
||||
<!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
|
||||
<!ENTITY http-root "http://ftp.linuxfromscratch.org">
|
||||
|
Loading…
Reference in New Issue
Block a user