Changeset 828c2db for prologue/common/audience.xml
- Timestamp:
- Jul 3, 2006, 5:57:20 PM (18 years ago)
- Children:
- a3c2af5
- Parents:
- bb355f0
- File:
-
- 1 edited
-
prologue/common/audience.xml (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
prologue/common/audience.xml
rbb355f0 r828c2db 18 18 question and is the impetus for this section of the book.</para> 19 19 20 <para>One important reason for LFS's existence is to help people learn21 how a Linux system works from the inside out. Building an LFS system20 <para>One important reason for CLFS's existence is to help people learn 21 how a Linux system works from the inside out. Building an CLFS system 22 22 helps demonstrate what makes Linux tick, and how things work together 23 23 and depend on each other. One of the best things that this learning … … 25 25 tastes and needs.</para> 26 26 27 <para>A key benefit of LFS is that it allows users to have more control27 <para>A key benefit of CLFS is that it allows users to have more control 28 28 over the system without relying on someone else's Linux implementation. 29 With LFS, <emphasis>you</emphasis> are in the driver's seat and dictate29 With CLFS, <emphasis>you</emphasis> are in the driver's seat and dictate 30 30 every aspect of the system, such as the directory layout and bootscript 31 31 setup. You also dictate where, why, and how programs are installed.</para> 32 32 33 <para>Another benefit of LFS is the ability to create a very compact33 <para>Another benefit of CLFS is the ability to create a very compact 34 34 Linux system. When installing a regular distribution, one is often 35 35 forced to include several programs which are probably never used. These 36 36 programs waste disk space, or worse, CPU cycles. It is not 37 difficult to build an LFS system of less than 100 megabytes (MB), which37 difficult to build an CLFS system of less than 100 megabytes (MB), which 38 38 is substantially smaller than the majority of existing 39 39 installations. Does this still sound like a lot of space? A few of us 40 have been working on creating a very small embedded LFS system. We40 have been working on creating a very small embedded CLFS system. We 41 41 successfully built a system that was specialized to run the Apache web 42 42 server with approximately 8MB of disk space used. Further stripping … … 47 47 <para>We could compare Linux distributions to a hamburger purchased at 48 48 a fast-food restaurant—you have no idea what might be in what you 49 are eating. LFS, on the other hand, does not give you a hamburger.50 Rather, LFS provides the recipe to make the exact hamburger desired.49 are eating. CLFS, on the other hand, does not give you a hamburger. 50 Rather, CLFS provides the recipe to make the exact hamburger desired. 51 51 This allows users to review the recipe, omit unwanted ingredients, and 52 52 add your own ingredients to enhance the flavor of the burger. When you … … 55 55 barbecue it.</para> 56 56 57 <para>Another analogy that we can use is that of comparing LFS with a58 finished house. LFS provides the skeletal plan of a house, but it is up59 to you to build it. LFS maintains the freedom to adjust plans throughout57 <para>Another analogy that we can use is that of comparing CLFS with a 58 finished house. CLFS provides the skeletal plan of a house, but it is up 59 to you to build it. CLFS maintains the freedom to adjust plans throughout 60 60 the process, customizing it to the user's needs and preferences.</para> 61 61 … … 81 81 learning along the way, then this book is your best choice.</para> 82 82 83 <para>There are too many good reasons to build your own LFS system to83 <para>There are too many good reasons to build your own CLFS system to 84 84 list them all here. This section is only the tip of the iceberg. As 85 you continue in your LFS experience, you will find the power that85 you continue in your CLFS experience, you will find the power that 86 86 information and knowledge truly bring.</para> 87 87
Note:
See TracChangeset
for help on using the changeset viewer.
