diff options
author | Gerard Beekmans <gerard@linuxfromscratch.org> | 2002-05-31 12:03:05 +0000 |
---|---|---|
committer | Gerard Beekmans <gerard@linuxfromscratch.org> | 2002-05-31 12:03:05 +0000 |
commit | c61dd1e8cd538930bbffedec17564b535e6e47d6 (patch) | |
tree | cd2a2c8f2218c41dd19fb7154770d2253e7fe004 /chapter01/how.xml | |
parent | 53c19e734b65febebc76cfb79d55067b8ebd21bf (diff) |
applied Scot's LFS-BOOK-CVS-20020530-XML.patch
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1954 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter01/how.xml')
-rw-r--r-- | chapter01/how.xml | 88 |
1 files changed, 53 insertions, 35 deletions
diff --git a/chapter01/how.xml b/chapter01/how.xml index 75e1702f3..b3cd9b439 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -2,47 +2,65 @@ <title>How things are going to be done</title> <?dbhtml filename="how.html" dir="chapter01"?> -<para>We are going to build the LFS system by using an already installed Linux -distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc. There -is no need to have any kind of bootdisk. We will use an existing Linux -system as the base (since we need a compiler, linker, text editor, and -other tools).</para> +<para>We are going to build the LFS system by using a previously installed +Linux distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc. +We will use the existing Linux system as the development platform, because +we need tools like a compiler, linker, text editor, and other necessary +development tools to build our system. Ordinarily, the required tools are +available by default if we selected "development" as one of our installation +options when we installed the distributed Linux.</para> <para>After you have downloaded the necessary packages that make up an LFS -system you will create a new Linux native partition onto which the LFS system -will be installed.</para> - -<para>The next step, chapter 5, will be the installation of a number of -packages that are statically linked and installed on the LFS partition. -These packages form a basic development suite which will be used to -install the actual system, and are also needed to resolve circular -dependencies. Examples of circular dependencies are: you need a compiler -to install a compiler. You need a shell in order to install a shell. And -so on.</para> - -<para>Chapter 6 installs the actual base system. We use the chroot program -to start a new shell whose root directory will be set to the LFS -partition. This, in essence, is the same as rebooting and having the -kernel mount the LFS partition as the root partition. The reason that -we don't actually reboot, but instead chroot, is that this way you can -still use your host system. While software is being installed you can -simply switch to a different VC (Virtual Console) or X desktop and -continue using your computer as you normally would.</para> - -<para>When all the software is installed, chapter 7 will set up the boot -scripts. Chapter 8 will set up the Linux boot loader and in chapter 9 -there are some pointers what you can do after you finish the book. Then -you can finally reboot your system into your new LFS system, and start -to really use it.</para> +system we will create a new Linux native partition and filesystem. Here +is where the LFS system will be compiled and installed.</para> + +<para>The next step, chapter 5, will discuss the installation of a number of +packages that will form a basic development suite that is used to +build the actual system, or needed to resolve circular dependencies. For +example, you need a compiler to build a new compiler, and you need a shell +in order to install a new shell. The packages in this chapter will be linked +statically. Static linking describes a method of compiling software so that +it does not require the presence of libraries when building is complete. +The resulting program is able to function on its own. The program is able to +do so because the pieces of the program that would normally remain in the +libraries are copied from the libraries and built right into the program. +Ordinarily software is built with dynamic linking. This conserves storage +space and increases the efficiency of many programs. We statically link +our software in chapter 5 because we will in theory be moving our +development system to a virtual environment where the already mentioned +libraries will be absent. If the software is built dynamically, our +development suite will not function. Since the libraries we are talking +about are provided by our distribution Linux, the goal of chapter 5 is to +build a development environment where those libraries are not required +and is therefore independent of the distribution.</para> + +<para>In chapter 6 we will build and install our final system. We will use +the chroot program to enter a virtual environment and start a new shell +whose root directory will be set to the partition where we built all the +chapter 5 software. This is very similar to rebooting and instructing the +kernel to mount our LFS partition as the root partition. The reason that +we don't actually reboot, but instead chroot, is that creating a static +system that we can boot into requires more work that simply isn't necessary. +As well, we can continue to use our platform system while we are building +LFS. While software is being compiled and installed you can simply switch +to a different VC (Virtual Console) or X desktop and continue using your +computer normally.</para> + +<para>When all the software from chapter 6 is installed, chapters 7,8 and 9 +will help us finalize our installation. We will set up our boot +scripts in chapter 7. In chapter 8 we will build our final linux kernel and +set up the Linux boot loader. Chapter 9 has some pointers to help you after +you finish the book. Then finally, you reboot your system and boot into your +new LFS system, and start to really use it.</para> <para>This is the process in a nutshell. Detailed information on the steps -you are taking are provided in the chapters as you go through them. If -something isn't completely clear yet, don't worry. It will become very -clear shortly.</para> +we will take are discussed in the chapters and package descriptions as you +progress through them. If something isn't completely clear now, don't worry. +It should become very clear shortly.</para> <para>Please read chapter 2 carefully as it explains a few important things -you need to be aware of before you work your way through chapters 5 and -above.</para> +you should be aware of before you begin to work through chapters 5 and +later.</para> </sect1> |