| [6370fa6] | 1 | <sect1 id="ch05-introduction">
|
|---|
| 2 | <title>Introduction</title>
|
|---|
| [75043c22] | 3 | <?dbhtml filename="introduction.html" dir="chapter05"?>
|
|---|
| [6370fa6] | 4 |
|
|---|
| [b822811] | 5 | <para>In the following chapters we will install all the software that belongs
|
|---|
| 6 | to a basic Linux system. After you're done with this and the next chapter,
|
|---|
| [607c7370] | 7 | you'll have a fully working Linux system. The remaining chapters deal
|
|---|
| 8 | with creating the boot scripts, making the LFS system bootable and
|
|---|
| [b822811] | 9 | setting up basic networking.</para>
|
|---|
| [6370fa6] | 10 |
|
|---|
| [2f5db45b] | 11 | <para>The software in this chapter will be linked statically and will be
|
|---|
| 12 | reinstalled in the next chapter and linked dynamically. The
|
|---|
| [6370fa6] | 13 | reason for the static version first is that there is a chance that our
|
|---|
| [72033583] | 14 | normal Linux system and the LFS system aren't using the same C
|
|---|
| [6370fa6] | 15 | Library versions. If the programs in the first part are linked against
|
|---|
| 16 | an older C library version, those programs might not work well on the
|
|---|
| [2f5db45b] | 17 | LFS system. Another reason is to resolve circular dependencies. An
|
|---|
| 18 | example of such a dependency is that you need a compiler to install a
|
|---|
| 19 | compiler, and you're going to need a shell to install a shell and that
|
|---|
| [d8897c2] | 20 | compiler.</para>
|
|---|
| [6370fa6] | 21 |
|
|---|
| [5e2cb65] | 22 | <para>All the files from this chapter will be installed under the <filename
|
|---|
| 23 | class="directory">$LFS/static</filename> directory. By doing it this way,
|
|---|
| [32cee45c] | 24 | we keep the installation from this chapter separate from the final
|
|---|
| [5e2cb65] | 25 | installation in the next chapter. Everything done here is only temporarily
|
|---|
| 26 | so we don't want it to pollute the to-be LFS system.</para>
|
|---|
| 27 |
|
|---|
| [2a761d4] | 28 | <para>The key to learning what makes Linux tick is to know exactly what packages
|
|---|
| [72033583] | 29 | are used for and why a user or the system needs them. Descriptions
|
|---|
| [6370fa6] | 30 | of the package content are provided after the Installation subsection of each
|
|---|
| [b822811] | 31 | package and in Appendix A as well.</para>
|
|---|
| [6370fa6] | 32 |
|
|---|
| [b822811] | 33 | <para>During the installation of various packages, you will more than likely see
|
|---|
| [607c7370] | 34 | all kinds of compiler warnings scrolling by on the screen. These are
|
|---|
| 35 | normal and can be safely ignored. They are just that, warnings (mostly
|
|---|
| 36 | about improper use of the C or C++ syntax, but not illegal use. It's just
|
|---|
| 37 | that, often, C standards changed and packages still use the old standard
|
|---|
| [b822811] | 38 | which is not a problem).</para>
|
|---|
| 39 |
|
|---|
| [34a2f0c] | 40 | <para>Before we start, make sure the LFS environment variable is set up
|
|---|
| [b822811] | 41 | properly if you decided to make use of it. Run the following:</para>
|
|---|
| 42 |
|
|---|
| 43 | <para><screen><userinput>echo $LFS</userinput></screen></para>
|
|---|
| 44 |
|
|---|
| 45 | <para>Check to make sure the output contains the correct directory to the LFS
|
|---|
| 46 | partition's mount point (/mnt/lfs for example).</para>
|
|---|
| [607c7370] | 47 |
|
|---|
| [6370fa6] | 48 | </sect1>
|
|---|
| 49 |
|
|---|
