source: chapter05/introduction.xml@ 04f5529

10.0 10.0-rc1 10.1 10.1-rc1 11.0 11.0-rc1 11.0-rc2 11.0-rc3 11.1 11.1-rc1 11.2 11.2-rc1 11.3 11.3-rc1 12.0 12.0-rc1 12.1 12.1-rc1 6.0 6.1 6.1.1 6.3 6.4 6.5 6.6 6.7 6.8 7.0 7.1 7.2 7.3 7.4 7.5 7.5-systemd 7.6 7.6-systemd 7.7 7.7-systemd 7.8 7.8-systemd 7.9 7.9-systemd 8.0 8.1 8.2 8.3 8.4 9.0 9.1 arm bdubbs/gcc13 ml-11.0 multilib renodr/libudev-from-systemd s6-init trunk v3_1 v3_2 v3_3 v4_0 v4_1 v5_0 v5_1 v5_1_1 xry111/arm64 xry111/arm64-12.0 xry111/clfs-ng xry111/lfs-next xry111/loongarch xry111/loongarch-12.0 xry111/loongarch-12.1 xry111/mips64el xry111/pip3 xry111/rust-wip-20221008 xry111/update-glibc
Last change on this file since 04f5529 was 2a761d4, checked in by Mark Hymers <markh@…>, 23 years ago

fixed a couple of typos

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1188 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 2.0 KB
Line 
1<sect1 id="ch05-introduction">
2<title>Introduction</title>
3
4<para>In the following chapters we will install all the software that belongs
5to a basic Linux system. After you're done with this and the next chapter,
6you'll have a fully working Linux system. The remaining chapters deal
7with creating the boot scripts, making the LFS system bootable and
8setting up basic networking.</para>
9
10<para>The software in this chapter will be linked statically and will be
11reinstalled in the next chapter and linked dynamically. The
12reason for the static version first is that there is a chance that our
13normal Linux system and the LFS system aren't using the same C
14Library versions. If the programs in the first part are linked against
15an older C library version, those programs might not work well on the
16LFS system. Another reason is to resolve circular dependencies. An
17example of such a dependency is that you need a compiler to install a
18compiler, and you're going to need a shell to install a shell and that
19compiler.</para>
20
21<para>The key to learning what makes Linux tick is to know exactly what packages
22are used for and why a user or the system needs them. Descriptions
23of the package content are provided after the Installation subsection of each
24package and in Appendix A as well.</para>
25
26<para>During the installation of various packages, you will more than likely see
27all kinds of compiler warnings scrolling by on the screen. These are
28normal and can be safely ignored. They are just that, warnings (mostly
29about improper use of the C or C++ syntax, but not illegal use. It's just
30that, often, C standards changed and packages still use the old standard
31which is not a problem).</para>
32
33<para>Before we start, make sure the LFS environment variable is setup
34properly if you decided to make use of it. Run the following:</para>
35
36<para><screen><userinput>echo $LFS</userinput></screen></para>
37
38<para>Check to make sure the output contains the correct directory to the LFS
39partition's mount point (/mnt/lfs for example).</para>
40
41</sect1>
42
Note: See TracBrowser for help on using the repository browser.