git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@330 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Thomas Balu Walter 2001-03-16 18:06:46 +00:00
parent 1b256332de
commit aff91c471b
5 changed files with 63 additions and 57 deletions

View File

@ -2,8 +2,8 @@
<title>About $LFS</title> <title>About $LFS</title>
<para> <para>
Please read the following carefully: throughout this book you will Please read the following carefully: throughout this book
frequently see the variable name $LFS. $LFS must at all times be the variable name $LFS will frequently be used. $LFS must at all times be
replaced by the directory where the partition that contains the LFS system replaced by the directory where the partition that contains the LFS system
is mounted. How to create and where to mount the partition will be is mounted. How to create and where to mount the partition will be
explaind in full detail later on in chapter 4. In my case, the LFS explaind in full detail later on in chapter 4. In my case, the LFS
@ -14,13 +14,14 @@ cp inittab /mnt/lfs/etc.
</para> </para>
<para> <para>
It's important that you do this no matter where you read it; be it in It's important that this is done no matter where it is read; be it in
commands you enter on the prompt, or in a file you edit or create. commands entered on the prompt, or in a file edited or created.
</para> </para>
<para> <para>
If you want, you can set the environment variable LFS. This way you can Another possible solution is to set the environment variable LFS.
literally enter $LFS instead of replacing it by something like This way the $LFS can be entered literally instead of replacing it by
something like
/mnt/lfs. This is accomplished by running: export LFS=/mnt/lfs. /mnt/lfs. This is accomplished by running: export LFS=/mnt/lfs.
</para> </para>
@ -31,20 +32,21 @@ automatically.
</para> </para>
<para> <para>
Do not forget to set the $LFS variable at all times. If you haven't set Do not forget to set the $LFS variable at all times. If
the variable and you use it in a command, $LFS will be ignored and whatever the variable is not set and is used it in a command, $LFS will be ignored
and whatever
is left will be executed. The command cp inittab $LFS/etc without the $LFS is left will be executed. The command cp inittab $LFS/etc without the $LFS
variable set will result in copying the inittab file to the /etc variable set will result in copying the inittab file to the /etc
directory, which will overwrite your system's inittab. A file like inittab directory, which will overwrite the host-system's inittab. A file like inittab
isn't that big a problem as it can easily be restored, but if you would isn't that big a problem as it can easily be restored, but if
make this mistake during the installation of the C Library, you could this mistake is made during the installation of the C Library, things might
damage things. be damaged
</para> </para>
<para> <para>
One way to make sure that $LFS is set at all times is adding it to One way to make sure that $LFS is set at all times is adding it to
your /root/.bash_profile and/or /root/.bashrc file(s) so that every time you the /root/.bash_profile and/or /root/.bashrc file(s) so that every time a
'su' to install LFS, the $LFS variable is set for you. 'su' to root is done to install LFS, the $LFS variable is set for.
</para> </para>
</sect1> </sect1>

View File

@ -7,7 +7,7 @@ process, not to mention very error-prone.
</para> </para>
<para> <para>
To save you guys and girls some time, you can download the bootscripts To save some time, the bootscripts can be downloaded
from <ulink from <ulink
url="http://download.linuxfromscratch.org/bootscripts/"> url="http://download.linuxfromscratch.org/bootscripts/">
http://download.linuxfromscratch.org/bootscripts/</ulink> or <ulink http://download.linuxfromscratch.org/bootscripts/</ulink> or <ulink

View File

@ -4,18 +4,20 @@
<para> <para>
LFS Commands is a tarball containing files which list the installation LFS Commands is a tarball containing files which list the installation
commands for the packages installed in this book. These files can be commands for the packages installed in this book. These files can be
used to dump to your shell and install the packages, though some files used to dump to a shell and install the packages, though some files
need to be modified (for example when you install the console-tools need to be modified (for example when the console-tools package is
package you need to select your keyboard layout file which can't be guessed). installed it is needed to select the keyboard layout file which can't be
guessed).
</para> </para>
<para> <para>
These files can be used to quickly find out which commands have been These files can be used to quickly find out which commands have been
changed between the different LFS versions as well. You can download the changed between the different LFS versions as well. A user just downloads the
lfs-commands tarball for this book version and the previous book version lfs-commands tarball for this book version and the previous book version
and run a diff on the files. That way you can see which package have and run a diff on the files. That way it is possible to see which packages
updated installation instructions so you can modify your own scripts, or have
reinstall a package if you deem necessary. updated installation instructions and he can modify his own scripts, or
reinstall a package if it seems necessary.
</para> </para>
<para> <para>

View File

@ -2,28 +2,29 @@
<title>How to download the software</title> <title>How to download the software</title>
<para> <para>
Throughout this document I will assume that you have stored all the Throughout this document I will assume that all the
packages you have downloaded somewhere in $LFS/usr/src. packages that were downloaded are placed somewhere in $LFS/usr/src.
</para> </para>
<para> <para>
I use the convention of having a $LFS/usr/src/sources directory. I use the convention of having a $LFS/usr/src/sources directory.
Under sources you'll find the directory 0-9 and the directories a Under sources I have the directory 0-9 and the directories a
through z. A package as sysvinit-2.78.tar.gz is stored under through z. A package as sysvinit-2.78.tar.gz is stored under
$LFS/usr/src/sources/s/ A package as bash-2.04.tar.gz is stored under $LFS/usr/src/sources/s/ A package as bash-2.04.tar.gz is stored under
$LFS/usr/src/sources/b/ and so forth. You don't have to follow this $LFS/usr/src/sources/b/ and so forth. This convention does not have to be
convention of course, I was just giving an example. It's better to keep followed of course, I was just giving an example. It's better to keep
the packages out of $LFS/usr/src and move them to a subdirectory, so the packages out of $LFS/usr/src and move them to a subdirectory, so
we'll have a clean $LFS/usr/src directory in which we will unpack the we'll have a clean $LFS/usr/src directory in which we will unpack the
packages and work with them. packages and work with them.
</para> </para>
<para> <para>
The next chapter contains the list of all the packages you need to download, The next chapter contains the list of all the packages that need to be
downloaded,
but the partition that is going to contain our LFS system isn't created yet. but the partition that is going to contain our LFS system isn't created yet.
Therefore, store the files temporarily somewhere where you want and remember Therefore, the files are temporarily stored somewhere else and later
to copy them to $LFS/usr/src/ when you have finished the chapter in which copied to $LFS/usr/src/ when the chapter in which
you prepare a new partition (chapter 4). the new partition is prepared got finished.
</para> </para>
</sect1> </sect1>

View File

@ -2,19 +2,19 @@
<title>How to install the software</title> <title>How to install the software</title>
<para> <para>
Before you can actually start doing something with a package, you need Before a user can actually start doing something with a package, he needs
to unpack it first. Often you will find the package files being tar'ed and to unpack it first. Often the package files are tar'ed and
gzip'ed. (You can determine this by looking at the extension of the file. gzip'ed. (that can determined by looking at the extension of the file.
tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
example.) I'm not going to write down every time how to ungzip and how example.) I'm not going to write down every time how to ungzip and how
to untar an archive. I will tell you how to do that once, in this section. to untar an archive. I will tell how to do that once, in this section.
There is also the possibility that you have the ability of downloading There is also the possibility that a .tar.bz2 file can be downloaded.
a .tar.bz2 file. Such a file is tar'ed and compressed with the bzip2 program. Such a file is tar'ed and compressed with the bzip2 program.
Bzip2 achieves a better compression than the commonly used gzip does. In Bzip2 achieves a better compression than the commonly used gzip does. In
order to use bz2 archives you need to have the bzip2 program installed. order to use bz2 archives the bzip2 program needs to be installed.
Most if not every distribution comes with this program so chances are Most if not every distribution comes with this program so chances are
high it is already installed on your system. If not, install it using high it is already installed on the host-system. If not, it's installed using
your distribution's installation tool. the distribution's installation tool.
</para> </para>
<para> <para>
@ -28,7 +28,7 @@ To start with, change to the $LFS/usr/src directory by running:
</literallayout></blockquote> </literallayout></blockquote>
<para> <para>
When you have a file that is tar'ed and gzip'ed, you unpack it by If a file is tar'ed and gzip'ed, it is unpacked by
running either one of the following two commands, depending on the running either one of the following two commands, depending on the
filename format: filename format:
</para> </para>
@ -42,7 +42,7 @@ filename format:
<para> <para>
When you have a file that is tar'ed and bzip2'ed, you unpack it by If a file is tar'ed and bzip2'ed, it is unpacked by
running: running:
</para> </para>
@ -60,7 +60,7 @@ to handle gzip archives.
</para> </para>
<para> <para>
When you have a file that is tar'ed, you unpack it by running: If a file is just tar'ed, it is unpacked by running:
</para> </para>
<blockquote><literallayout> <blockquote><literallayout>
@ -71,15 +71,15 @@ When you have a file that is tar'ed, you unpack it by running:
<para> <para>
When the archive is unpacked a new directory will be created under the When the archive is unpacked a new directory will be created under the
current directory (and this document assumes that you unpack the archives current directory (and this document assumes that the archives are unpacked
under the $LFS/usr/src directory). You have to enter that new directory under the $LFS/usr/src directory). A user has to enter that new directory
before you continue with the installation instructions. So every time the before continuing with the installation instructions. So every time the
book is going to install a program, it's up to you to unpack the source book is going to install a program, it's up to the user to unpack the source
archive. archive.
</para> </para>
<para> <para>
When you have a file that is gzip'ed, you unpack it by running: f a file is gzip'ed, it is unpacked by running:
</para> </para>
<blockquote><literallayout> <blockquote><literallayout>
@ -89,13 +89,14 @@ When you have a file that is gzip'ed, you unpack it by running:
</literallayout></blockquote> </literallayout></blockquote>
<para> <para>
After you have installed a package you can do two things with it. You can After a package is installed two things can be done with it.
either delete the directory that contains the sources or you can keep it. Either the directory that contains the sources can be deleted
If you decide to keep it, that's fine with me. But, if you need the same package or it can be kept.
again in a later chapter, you need to delete the directory first before using If it is kept, that's fine with me. But, if the same package is needed
it again. If you don't do this, you might end up in trouble because old again in a later chapter, the directory needs to be deleted first before using
settings will be used (settings that apply to your normal Linux system but it again. If this is not done, it might end up in trouble because old
which don't always apply to your LFS system). Doing a simple make clean settings will be used (settings that apply to the normal Linux system but
which don't always apply to the LFS system). Doing a simple make clean
or make distclean does not always guarantee a totally clean source tree. or make distclean does not always guarantee a totally clean source tree.
The configure script can also have files lying around in various The configure script can also have files lying around in various
subdirectories which aren't always removed by a make clean process. subdirectories which aren't always removed by a make clean process.
@ -104,8 +105,8 @@ subdirectories which aren't always removed by a make clean process.
<para> <para>
There is one exception to that rule: don't remove the linux kernel source There is one exception to that rule: don't remove the linux kernel source
tree. A lot of programs need the kernel headers, so that's the only tree. A lot of programs need the kernel headers, so that's the only
directory you don't want to remove, unless you are not going to directory that should not be removed, unless no software is to be compiled
compile any software anymore. anymore.
</para> </para>
</sect1> </sect1>