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

applied alex's ch5-intro-rewrite and chapter6-intro.patch patches

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1950 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2002-05-30 23:43:04 +00:00
parent f64f4b557a
commit 5756284c7e
2 changed files with 34 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
chapter05/introduction.xml
View File

@ -2,42 +2,36 @@
<title>Introduction</title> <title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter05"?> <?dbhtml filename="introduction.html" dir="chapter05"?>
<para>In the following chapters we will install all the software that belongs <para>In this chapter we will compile and install a minimal
to a basic Linux system. After you're done with this and the next chapter, Linux system. This system will contain just enough tools to be able
you'll have a fully working Linux system. The remaining chapters deal to start constructing the final LFS system in the next chapter.</para>
with creating the boot scripts, making the LFS system bootable and
setting up basic networking.</para>
<para>The software in this chapter will be linked statically and will be <para>The software in this chapter will be linked statically, because
reinstalled in the next chapter and linked dynamically. The there is a possibility that your host Linux system uses a different
reason for the static version first is that there is a chance that our version of the C library than the version you downloaded for
normal Linux system and the LFS system aren't using the same C use in your LFS system. If we were to link the programs in this
Library versions. If the programs in the first part are linked against chapter against that older C library, these programs might work
an older C library version, those programs might not work well on the incorrectly, or not at all, when we change to the LFS system.</para>
LFS system. Another reason is to resolve circular dependencies. An
example of such a dependency is that you need a compiler to install a
compiler, and you're going to need a shell to install a shell and that
compiler.</para>
<para>All the files from this chapter will be installed under the <filename <para>The files compiled in this chapter will be installed under the
class="directory">$LFS/static</filename> directory. By doing it this way, <filename class="directory">$LFS/static</filename> directory,
we keep the installation from this chapter separate from the final to keep them separate from the files installed in the next chapter.
installation in the next chapter. Everything done here is only temporarily As everything done here is only temporarily, we don't want
so we don't want it to pollute the to-be LFS system.</para> these files to pollute the to-be LFS system.</para>
<para>The key to learning what makes Linux tick is to know exactly what packages <para>The key to learning what makes a Linux system work is to know
are used for and why a user or the system needs them. Descriptions exactly what each package is used for, and why the user or the system
of the package content are provided after the Installation subsection of each needs it. For this purpose a short description of the content of each
package and in Appendix A as well.</para> package is given right after the installation instructions.</para>
<para>During the installation of various packages, you will more than likely see <para>During the installation of several packages you will probably
all kinds of compiler warnings scrolling by on the screen. These are see all kinds of compiler warnings scroll by on your screen. These are
normal and can be safely ignored. They are just that, warnings (mostly normal and can be safely ignored. They are just what they say they are:
about improper use of the C or C++ syntax, but not illegal use. It's just warnings -- mostly about improper, but not illegal, use of the C or C++
that, often, C standards changed and packages still use the old standard syntax. It's just that C standards have changed rather often and some
which is not a problem).</para> packages still use the older standard, which is not really a problem.</para>
<para>Before we start, make sure the LFS environment variable is set up <para>Before you start, make sure the LFS environment variable is set up
properly if you decided to make use of it. Run the following:</para> properly if you decided to make use of it. Run the following:</para>
<para><screen><userinput>echo $LFS</userinput></screen></para> <para><screen><userinput>echo $LFS</userinput></screen></para>

13
chapter06/introduction.xml
View File

@ -2,6 +2,11 @@
<title>Introduction</title> <title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter06"?> <?dbhtml filename="introduction.html" dir="chapter06"?>
<para>In this chapter we enter the building site, and start
constructing our LFS system in earnest. That is, we chroot into
our temporary mini Linux system, create some auxiliary things,
and then start installing all the packages, one by one.</para>
<para>The installation of all the software is pretty straightforward, and <para>The installation of all the software is pretty straightforward, and
you will probably think it would be so much easier and shorter to give you will probably think it would be so much easier and shorter to give
the generic installation instructions for a package here and only explain the generic installation instructions for a package here and only explain
@ -10,10 +15,10 @@ method. Although we agree with that, we choose to give the
full instructions for each and every package, simply to avoid any full instructions for each and every package, simply to avoid any
possible confusion and errors.</para> possible confusion and errors.</para>
<para>Now would be a good time to take a look at the optimization hint <para>If you plan to use compiler optimization for the packages
at <ulink url="&hints-root;optimization.txt"/> if you plan to use installed in this chapter, take a look at the optimization hint
compiler optimization for the packages at <ulink url="&hints-root;optimization.txt"/>.
installed in this chapter. Compiler optimization can make a program run Compiler optimization can make a program run
faster, but may also cause compilation problems. If you run into problems faster, but may also cause compilation problems. If you run into problems
when using optimization, always try it without optimization to see if when using optimization, always try it without optimization to see if
the problem persists.</para> the problem persists.</para>