Changeset c61dd1e
- Timestamp:
- 05/31/2002 12:03:05 PM (22 years ago)
- Branches:
- 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, 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
- Children:
- 1f9327f
- Parents:
- 53c19e7
- Files:
-
- 11 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/alfsdiscuss.xml
r53c19e7 rc61dd1e 2 2 <title>alfs-discuss</title> 3 3 4 <para>The alfs-discuss list discusses the development of ALFS, which stands for 5 Automated Linux From Scratch. The goal of this project is to develop an 6 installation tool that can install an LFS system automatically. 7 Its main goal is to speed up compilation by taking away the need to 8 manually enter the commands to configure, compile, and install packages.</para> 4 <para>The alfs-discuss list discusses the development of ALFS, which is short 5 for Automated Linux From Scratch. The goal of this project is to develop an 6 installation tool that installs an LFS system automatically, thus speeding 7 up compilation by taking away the need to manually enter the commands.</para> 9 8 10 9 </sect2> -
chapter01/blfsbook.xml
r53c19e7 rc61dd1e 2 2 <title>blfs-book</title> 3 3 4 <para>The blfs-book list is used by the BLFS-BOOK editors 5 t o co-ordinate blfs-book's maintenance, like XML issues and the like.6 Actual discussion on what should be added and removed should take place4 <para>The blfs-book list is used by the BLFS-BOOK editors to co-ordinate 5 the maintenance of the BLFS book, such as XML source code issues and the 6 like. Actual discussion on what should be added and removed should take place 7 7 on blfs-dev.</para> 8 8 -
chapter01/blfsdev.xml
r53c19e7 rc61dd1e 2 2 <title>blfs-dev</title> 3 3 4 <para>The blfs-dev mailing list discusses matters related to the 5 BLFS-BOOK (Beyond LFS). If problems with the book come up, a bug 6 or two need to be 7 reported, or suggestions to improve the book (such as suggestions as to 8 installation instructions to add) are to be made, this mailing list 9 is the right one.</para> 4 <para>The blfs-dev mailing list discusses development of the 5 BLFS-BOOK (Beyond LFS). This is the maillist to submit bug reports, 6 and make suggestions to improve the BLFS book.</para> 10 7 11 <para>Requests for help with programs beyond the base LFS setup (not12 just those in BLFS) should go toblfs-support.</para>8 <para>Requests for help with programs beyond the base LFS build and setup 9 (not just those in the BLFS book) should be made in blfs-support.</para> 13 10 14 11 </sect2> -
chapter01/blfssupport.xml
r53c19e7 rc61dd1e 2 2 <title>blfs-support</title> 3 3 4 <para>The blfs-support list deals with support requests for any software 5 not installed in the LFS book. The list is not just for help with 6 software explicitly mentioned in the BLFS book, any software beyond that 4 <para>The blfs-support list handles support requests for any software 5 that is not built or installed in the LFS book. Any software beyond what is 7 6 installed as part of the base LFS system can be discussed here.</para> 8 7 -
chapter01/faq.xml
r53c19e7 rc61dd1e 3 3 <?dbhtml filename="faq.html" dir="chapter01"?> 4 4 5 <para>If you encounter any problems building an LFS system, you should5 <para>If you encounter any problems while building an LFS system, you should 6 6 check out <ulink url="http://www.linuxfromscratch.org/faq/"/> to see if 7 7 your question is already answered in the FAQ.</para> -
chapter01/how.xml
r53c19e7 rc61dd1e 3 3 <?dbhtml filename="how.html" dir="chapter01"?> 4 4 5 <para>We are going to build the LFS system by using an already installed Linux 6 distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc. There 7 is no need to have any kind of bootdisk. We will use an existing Linux 8 system as the base (since we need a compiler, linker, text editor, and 9 other tools).</para> 5 <para>We are going to build the LFS system by using a previously installed 6 Linux distribution such as Debian, SuSe, Slackware, Mandrake, RedHat, etc. 7 We will use the existing Linux system as the development platform, because 8 we need tools like a compiler, linker, text editor, and other necessary 9 development tools to build our system. Ordinarily, the required tools are 10 available by default if we selected "development" as one of our installation 11 options when we installed the distributed Linux.</para> 10 12 11 13 <para>After you have downloaded the necessary packages that make up an LFS 12 system you will create a new Linux native partition onto which the LFS system13 will beinstalled.</para>14 system we will create a new Linux native partition and filesystem. Here 15 is where the LFS system will be compiled and installed.</para> 14 16 15 <para>The next step, chapter 5, will be the installation of a number of 16 packages that are statically linked and installed on the LFS partition. 17 These packages form a basic development suite which will be used to 18 install the actual system, and are also needed to resolve circular 19 dependencies. Examples of circular dependencies are: you need a compiler 20 to install a compiler. You need a shell in order to install a shell. And 21 so on.</para> 17 <para>The next step, chapter 5, will discuss the installation of a number of 18 packages that will form a basic development suite that is used to 19 build the actual system, or needed to resolve circular dependencies. For 20 example, you need a compiler to build a new compiler, and you need a shell 21 in order to install a new shell. The packages in this chapter will be linked 22 statically. Static linking describes a method of compiling software so that 23 it does not require the presence of libraries when building is complete. 24 The resulting program is able to function on its own. The program is able to 25 do so because the pieces of the program that would normally remain in the 26 libraries are copied from the libraries and built right into the program. 27 Ordinarily software is built with dynamic linking. This conserves storage 28 space and increases the efficiency of many programs. We statically link 29 our software in chapter 5 because we will in theory be moving our 30 development system to a virtual environment where the already mentioned 31 libraries will be absent. If the software is built dynamically, our 32 development suite will not function. Since the libraries we are talking 33 about are provided by our distribution Linux, the goal of chapter 5 is to 34 build a development environment where those libraries are not required 35 and is therefore independent of the distribution.</para> 22 36 23 <para>Chapter 6 installs the actual base system. We use the chroot program 24 to start a new shell whose root directory will be set to the LFS 25 partition. This, in essence, is the same as rebooting and having the 26 kernel mount the LFS partition as the root partition. The reason that 27 we don't actually reboot, but instead chroot, is that this way you can 28 still use your host system. While software is being installed you can 29 simply switch to a different VC (Virtual Console) or X desktop and 30 continue using your computer as you normally would.</para> 37 <para>In chapter 6 we will build and install our final system. We will use 38 the chroot program to enter a virtual environment and start a new shell 39 whose root directory will be set to the partition where we built all the 40 chapter 5 software. This is very similar to rebooting and instructing the 41 kernel to mount our LFS partition as the root partition. The reason that 42 we don't actually reboot, but instead chroot, is that creating a static 43 system that we can boot into requires more work that simply isn't necessary. 44 As well, we can continue to use our platform system while we are building 45 LFS. While software is being compiled and installed you can simply switch 46 to a different VC (Virtual Console) or X desktop and continue using your 47 computer normally.</para> 31 48 32 <para>When all the software is installed, chapter 7 will set up the boot 33 scripts. Chapter 8 will set up the Linux boot loader and in chapter 9 34 there are some pointers what you can do after you finish the book. Then 35 you can finally reboot your system into your new LFS system, and start 36 to really use it.</para> 49 <para>When all the software from chapter 6 is installed, chapters 7,8 and 9 50 will help us finalize our installation. We will set up our boot 51 scripts in chapter 7. In chapter 8 we will build our final linux kernel and 52 set up the Linux boot loader. Chapter 9 has some pointers to help you after 53 you finish the book. Then finally, you reboot your system and boot into your 54 new LFS system, and start to really use it.</para> 37 55 38 56 <para>This is the process in a nutshell. Detailed information on the steps 39 you are taking are provided in the chapters as you go through them. If 40 something isn't completely clear yet, don't worry. It will become very 41 clear shortly.</para>57 we will take are discussed in the chapters and package descriptions as you 58 progress through them. If something isn't completely clear now, don't worry. 59 It should become very clear shortly.</para> 42 60 43 61 <para>Please read chapter 2 carefully as it explains a few important things 44 you need to be aware of before you work your waythrough chapters 5 and45 above.</para>62 you should be aware of before you begin to work through chapters 5 and 63 later.</para> 46 64 47 65 </sect1> -
preface/foreword.xml
r53c19e7 rc61dd1e 3 3 <?dbhtml filename="foreword.html" dir="preface"?> 4 4 5 <para>Having used a number of different Linux distributions, I was never fully6 satisfied with any of them. I didn't like the way the arrangement of the 7 bootscripts. I didn't like the way certain programs were configured by8 default. Much more of that sort of thing bothered me. Finally I realized that9 if I wanted full satisfisfaction from my Linux system I would have to build 10 my own system from scratch, using only the source code. I resolved not to use 11 pre-compiled packages of any kind, nor CD-ROM or 12 bootdisk that would install some basic utilities. I would use my current 13 Linux system todevelop my own.</para>5 <para>Having used a number of different Linux distributions, I was never 6 fully satisfied with any of them. I didn't like the way the arrangement of 7 the bootscripts. I didn't like the way certain programs were configured by 8 default. Much more of that sort of thing bothered me. Finally I realized 9 that if I wanted full satisfisfaction from my Linux system I would have to 10 build my own system from scratch, using only the source code. I resolved 11 not to use pre-compiled packages of any kind, nor CD-ROM or bootdisk that 12 would install some basic utilities. I would use my current Linux system to 13 develop my own.</para> 14 14 15 15 <para>This wild idea seemed very difficult at the time and often seemed -
preface/organpart1.xml
r53c19e7 rc61dd1e 2 2 <title>Part I - Introduction</title> 3 3 4 <para>Part One gives general information about this book (versions, where 5 to get it, changelog, mailing lists, and how to get in touch with us). 6 It also explains a few important aspects you really want and need to 7 read before starting to build an LFS system.</para> 4 <para>Part I gives general information about the contents of book 5 (revisions, where to get it, changelog, mailing lists, and other contact 6 information). It also contains suggested reading that discusses a few 7 important considerations to think about before beginning your LFS 8 system.</para> 8 9 9 10 </sect2> -
preface/organpart2.xml
r53c19e7 rc61dd1e 1 1 <sect2 id="pre-organ2"> 2 <title>Part II - Installation of the LFS system</title>2 <title>Part II - Installation of the base LFS system</title> 3 3 4 <para>Part Two guides you through the installation of the LFS system which will 5 be the foundation for the rest of the system. Whatever you choose to do 6 with your brand new LFS system, it will be built on the foundation 7 that's installed in this part.</para> 4 <para>Part II guides you through the building and installation of an LFS 5 system. The finished LFS system will be the core foundation that the rest 6 of your Linux system will be built on. What you choose to do with your brand 7 new LFS system will be built and supported by this foundation that we build 8 in Part II.</para> 8 9 9 10 </sect2> -
preface/organpart3.xml
r53c19e7 rc61dd1e 2 2 <title>Part III - Appendixes</title> 3 3 4 <para>Part Threecontains various Appendices.</para>4 <para>Part III contains various Appendices.</para> 5 5 6 6 </sect2> -
preface/whoread.xml
r53c19e7 rc61dd1e 4 4 5 5 <para>There are many reasons why somebody would want to read this book. The 6 principle reason being to install a LFS system. A question many people raise6 principle reason being to install an LFS system. A question many people raise 7 7 is "Why go through all the hassle of manually building a Linux system 8 from scratch when you can just download and install an 8 from scratch when you can just download and install an existing one?". That 9 9 is a good question.</para> 10 10 11 11 <para>One important reason for LFS's existence is helping people 12 learn how a Linux system works from the inside out. Building a LFS system12 learn how a Linux system works from the inside out. Building an LFS system 13 13 helps demonstrate what makes Linux tick, and how things work together and 14 14 depend on each other. And perhaps most importantly, how to customize it to … … 33 33 <para>We could compare distributed Linux to a hamburger you buy at a 34 34 fast-food restaurant. You have no idea what you are easting. LFS on the 35 other hand, doesn't give you a hamburger, but the recipe to make a hamburger. 36 This allows you to inspectit, omit unwanted ingredients, and allows you to37 add your own ingredients that enhance the flavo ur of your burger. When you35 other hand, doesn't give you a hamburger, but the recipe to make a hamburger. 36 This allows you to review it, omit unwanted ingredients, and allows you to 37 add your own ingredients that enhance the flavor of your burger. When you 38 38 are satisfied with the recipe, you go on to preparing it. You make it just 39 39 the way you like it: broil it, bake it, deep-fry it, barbeque it, or eat it 40 raw.</para>40 tar-tar (raw).</para> 41 41 42 42 <para>Another analogy that we can use is that of comparing LFS with a 43 finished house. LFS will give you the skeleton of a house, but it's up 44 to you to install plumbing, electrical outlets, kitchen, bathtub, 45 wallpaper, etc.</para> 43 finished house. LFS will give you the skeletal plan of a house, but it's up 44 to you to build it, giving you the freedom to adjust your plans as you go.</para> 46 45 47 <para>Another advantage of a custom built Linux system is security. 46 <para>Another advantage of a custom built Linux system is security. 48 47 By compiling the entire system from source code, you are empowered to audit 49 48 everything and apply all the security patches you feel are needed. You don't 50 49 have to wait for somebody else to compile binary packages that fix a security 51 hole. Examine the new patch and build it yourself. 50 hole. Examine the new patch and build it yourself. You have no guarantee 52 51 that the new package was built correctly and actually fixes the problem 53 52 (adequately). You never truly know whether a security hole is fixed or
Note:
See TracChangeset
for help on using the changeset viewer.