gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-05 22:04:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

o Removed "Where to store the downloaded software" section.

Browse Source 
o  Removed "How to install the software" section.


git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2201 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Timothy Bauscher 2002-10-24 00:42:55 +00:00
parent 65e858e78d
commit b100429a55
4 changed files with 4 additions and 110 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter01/changelog.xml
View File

@ -41,6 +41,10 @@
</itemizedlist>
</para></listitem>
<listitem><para>October 23rd, 2002 [timothy]: Chapter 02: Removed "Where
to store the downloaded software" and "How to install the software"
sections.</para></listitem>
<listitem><para>October 23rd, 2002 [timothy]: Upgraded to bison-1.75,
sed-4.0. Moved m4 before bison to meet its dependency.</para></listitem>

2
chapter02/chapter02.xml
View File

@ -4,8 +4,6 @@
&c2-aboutlfs;
&c2-aboutsbus;
&c2-download;
&c2-install;
&c2-platform;
&c2-askforhelp;

24
chapter02/download.xml
View File

@ -1,24 +0,0 @@
<sect1 id="ch02-download">
<title>Where to store the downloaded software</title>
<?dbhtml filename="download.html" dir="chapter02"?>
<para>Throughout this document, we will assume that all the
packages that were downloaded are placed somewhere in $LFS/usr/src.</para>
<para>While it doesn't matter at all where you save the downloaded
packages, we recommend storing it at least on the LFS partition. This
just makes sense because you need to have access to those those files
when you chroot to $LFS and when you boot into the LFS system, although
access when booted to $LFS could be handled other ways. $LFS/usr/src is
just a logical place to store source code, but by no means a requirement.
You may even want to create a subdirectory under $LFS/usr/src for tarball
storage. That way you can separate tarballs from temporary build
directories, but again that's up to you.</para>
<para>The next chapter contains a list of all the packages that need to be
downloaded. The LFS partition isn't created yet, so you can't store it
there yet. Just save it elsewhere for now, and when the LFS partition is
created, move them over.</para>
</sect1>

84
chapter02/install.xml
View File

@ -1,84 +0,0 @@
<sect1 id="ch02-install" xreflabel="Chapter 2 - How to install the software">
<title>How to install the software</title>
<?dbhtml filename="install.html" dir="chapter02"?>
<para>Before you start using the LFS book, we should point out that all
of the commands here assume that you are using the bash shell. If you
aren't, the commands may work, but we can't guarantee it. If you want a
simple life, use bash.</para>
<para>Before you can actually start doing something with a package, you need
to unpack it first. Often the package files are tar'ed and
gzip'ed or bzip2'ed. We're not going to write down every time how to
unpack an archive. We'll explain how to do that once, in this
section.</para>
<para>To start with, change to the $LFS/usr/src directory by running:</para>
<para><screen><userinput>cd $LFS/usr/src</userinput></screen></para>
<para>If a file is tar'ed and gzip'ed, it is unpacked by
running either one of the following two commands, depending on the
filename:</para>
<para><screen><userinput>tar -xvzf filename.tar.gz</userinput>
<userinput>tar -xvzf filename.tgz</userinput></screen></para>
<para>If a file is tar'ed and bzip2'ed, it is unpacked by
running:</para>
<para><screen><userinput>bzcat filename.tar.bz2 | tar -xv</userinput></screen></para>
<para>Nowadays most tar programs, but not all, are
patched to be able to use bzip2 files directly. They use either
the -I, the -y, or the -j parameter, which work the same as the -z
parameter for handling gzip files. The above construction, however,
works no matter how your host system decided to patch tar.</para>
<para>If a file is just tar'ed, it is unpacked by running:</para>
<para><screen><userinput>tar -xvf filename.tar</userinput></screen></para>
<para>When an archive is unpacked, a new directory will be created under the
current directory (and this book assumes that the archives are unpacked
under the $LFS/usr/src directory). Please enter that new directory
before continuing with the installation instructions. Again, every time
this book is going to install a package, it's up to you to unpack the source
archive and cd into the newly created directory.</para>
<para>From time to time you will be dealing with single files such as patch
files. These files are generally gzip'ed or bzip2'ed. Before such files
can be used they need to be uncompressed.</para>
<para>If a file is gzip'ed, it is unpacked by running:</para>
<para><screen><userinput>gunzip filename.gz</userinput></screen></para>
<para>If a file is bzip2'ed, it is unpacked by running:</para>
<para><screen><userinput>bunzip2 filename.bz2</userinput></screen></para>
<para>After a package has been installed, two things can be done with
it: either the directory that contains the sources can be deleted, or it
can be kept. We highly recommend deleting it. If you don't do this and
try to re-use the same source later on in the book (for example re-using
the source trees from Chapter 5 in Chapter 6), it may not work
as you expect it to. Source trees from Chapter 5 will have your host
distribution's settings, which don't always apply to the LFS system
after you enter the chroot environment. Even running something like
<emphasis>make clean</emphasis> doesn't always guarantee a clean source
tree.</para>
<para>So, save yourself a lot of hassle and just remove the source directory
immediately after you have installed it, but keep the downloaded tarball
available for when you need it again.</para>
<para>There is one exception; the kernel source tree. Keep it around as you
will need it later in this book when building a kernel. Nothing before then
will use the kernel tree, so the source tree won't be in your way. If,
however, you are short of disk space, you can remove the kernel tree and
re-untar it later when required.</para>
</sect1>