Changeset 9ee226e
- Timestamp:
- 05/27/2009 02:49:21 AM (15 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.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, 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:
- 7ec7f68
- Parents:
- ca2f862e
- Location:
- prologue
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
prologue/audience.xml
rca2f862e r9ee226e 16 16 an existing one?</quote></para> 17 17 18 <para>One important reason for this project's existence is to help you learn how 19 a Linux system works from the inside out. Building an LFS system helps 20 demonstrate what makes Linux tick, and how things work together and depend 21 on each other. One of the best things that this learning experience can 22 provide you with is the ability to customize a Linux system to suit your 23 own unique needs.</para> 18 <para>One important reason for this project's existence is to help you learn 19 how a Linux system works from the inside out. Building an LFS system helps 20 demonstrate what makes Linux tick, and how things work together and depend on 21 each other. One of the best things that this learning experience can provide is 22 the ability to customize a Linux system to suit your own unique needs.</para> 24 23 25 <para>A key benefit of LFS is that it allows you to have more control over the 26 system without relying on someone else's Linux implementation. With LFS, 27 you are in the driver's seat and dictate every aspect of the system.</para> 24 <para>Another key benefit of LFS is that it allows you to have more control 25 over the system without relying on someone else's Linux implementation. With 26 LFS, you are in the driver's seat and dictate every aspect of the 27 system.</para> 28 28 29 29 <para>LFS allows you to create very compact Linux systems. When installing … … 33 33 resources are no longer a consideration. Sometimes, however, you are still 34 34 constrained by size considerations if nothing else. Think about bootable 35 CDs, USB sticks and embedded systems. Those are areas where LFS can be35 CDs, USB sticks, and embedded systems. Those are areas where LFS can be 36 36 beneficial.</para> 37 37 … … 49 49 book.</para> 50 50 51 <para>There are too many good reasons to build your own LFS system to list them52 all here. In the end, education is by far the most powerful of reasons. As 53 you continue in your LFS experience, you will discover the power that 54 information and knowledge truly bring.</para>51 <para>There are too many other good reasons to build your own LFS system to 52 list them all here. In the end, education is by far the most powerful of 53 reasons. As you continue in your LFS experience, you will discover the power 54 that information and knowledge truly bring.</para> 55 55 56 56 </sect1> -
prologue/foreword.xml
rca2f862e r9ee226e 17 17 18 18 <para>There are always many ways to accomplish a single task. The same can be 19 said about Linux distributions. A great many have existed over the years. 20 Some still exist, some have morphed into something else yet others have 21 been relegated to our memories.</para> 22 23 <para>They all do things differently to suit the needs of their target audience. 24 Because there existed so many different ways to accomplish the same end 25 goal, I began to realize I no longer had to be limited by any one 19 said about Linux distributions. A great many have existed over the years. Some 20 still exist, some have morphed into something else, yet others have been 21 relegated to our memories. They all do things differently to suit the needs of 22 their target audience. Because so many different ways to accomplish the same 23 end goal exist, I began to realize I no longer had to be limited by any one 26 24 implementation. Prior to discovering Linux, we simply put up with issues in 27 other Operating Systems as you had no choice. It was what it was, whether 28 you liked it or not. With Linux, the concept of choice began to emerge. If 29 you didn't like something, you were free, even encouraged, to change 30 it.</para> 25 other Operating Systems as you had no choice. It was what it was, whether you 26 liked it or not. With Linux, the concept of choice began to emerge. If you 27 didn't like something, you were free, even encouraged, to change it.</para> 31 28 32 29 <para>I tried a number of distributions and could not decide on any one. They … … 45 42 46 43 <para>After sorting through issues such as circular dependencies and compile-time 47 errors, a custom-built Linux system was finally built. It was fully44 errors, I finally built a custom-built Linux system. It was fully 48 45 operational and perfectly usable like any of the other Linux systems out 49 46 there at the time. But it was my own creation. It was very satisfying to … … 53 50 54 51 <para>As I shared my goals and experiences with other members of the Linux 55 community, it became apparent that there was a sustained interest in th ose56 ideas. It quickly became apparentthat such custom-built Linux systems52 community, it became apparent that there was a sustained interest in these 53 ideas. It quickly became plain that such custom-built Linux systems 57 54 serve not only to meet user specific requirements, but also serve as an 58 55 ideal learning opportunity for programmers and system administrators to … … 64 61 build your own system. While this book provides a template that will result 65 62 in a correctly working system, you are free to alter the instructions to 66 suit yourself, which is in part the whole point of this project after all. You63 suit yourself, which is, in part, an important part of this project. You 67 64 remain in control; we just lend a helping hand to get you started on your 68 65 own journey.</para> 69 66 70 67 <para>I sincerely hope you will have a great time working on your own Linux From 71 Scratch system ,and enjoy the numerous benefits of having a system that is68 Scratch system and enjoy the numerous benefits of having a system that is 72 69 truly your own.</para> 73 70 -
prologue/hostreqs.xml
rca2f862e r9ee226e 60 60 61 61 <listitem> 62 <!-- Gcc-2.95.3 breaks feature tests when using CC="gcc -B/usr/bin/"63 in the *-pass1 sections -->64 62 <para><emphasis role="strong">Gcc-3.0.1</emphasis> (Versions 65 63 greater than &gcc-version; are not recommended as they have not … … 82 80 83 81 <listitem> 84 <para><emphasis role="strong">Linux Kernel-2.6. x</emphasis>82 <para><emphasis role="strong">Linux Kernel-2.6.18</emphasis> 85 83 (having been compiled with GCC-3.0 or greater)</para> 86 84 87 <para>The reason for the kernel version requirement is that thread-local 85 <para>The reason for the kernel version requirement is that we specify 86 that version when building <application>glibc</application> in Chapter 6 87 at the recommendation of the developers. This can be overridden if 88 desired but at least a 2.6.0 kerenl is required because thread-local 88 89 storage support in Binutils will not be built and the Native POSIX 89 90 Threading Library (NPTL) test suite will segfault if the host's kernel … … 91 92 GCC.</para> 92 93 93 <para>If the host kernel is either earlier than 2.6. x, or it was not94 compiled using a GCC-3.0 (or later) compiler, you will haveto replace95 the kernel with one adhering to the specifications. There are two 96 ways you can go about this.First, see if your Linux vendor provides a 97 2.6 kernel package. If so, you may wish to install it. If your vendor98 doesn't offer a 2.6 kernel package, or you would prefer not to install it,99 you can compile a 2.6 kernel yourself. Instructions for compiling the100 kernel and configuring the boot loader (assuming the host uses GRUB) are101 located in <xref linkend="chapter-bootable"/>.</para>94 <para>If the host kernel is either earlier than 2.6.18, or it was not 95 compiled using a GCC-3.0 (or later) compiler, you will need to replace 96 the kernel with one adhering to the specifications. There are two ways 97 you can go about this. First, see if your Linux vendor provides a 2.6.18 98 or later kernel package. If so, you may wish to install it. If your 99 vendor doesn't offer an acceptable kernel package, or you would prefer not to 100 install it, you can compile a kernel yourself. Instructions for 101 compiling the kernel and configuring the boot loader (assuming the host 102 uses GRUB) are located in <xref linkend="chapter-bootable"/>.</para> 102 103 103 104 <note> -
prologue/prerequisites.xml
rca2f862e r9ee226e 13 13 <para>Building an LFS system is not a simple task. It requires a certain 14 14 level of existing knowledge of Unix system administration in order to resolve 15 problems ,and correctly execute the commands listed. In particular, as an15 problems and correctly execute the commands listed. In particular, as an 16 16 absolute minimum, you should already have the ability to use the 17 17 command line (shell) to copy or move files and directories, list directory … … 22 22 <para>Because the LFS book assumes <emphasis>at least</emphasis> this basic 23 23 level of skill, the various LFS support forums are unlikely to be able to 24 provide you with much assistance ; you will find that your questions regarding25 such basic knowledge will likely go unanswered, or you will simply be referred26 to the LFS essential pre-reading list.</para>24 provide you with much assistance in these areas. You will find that your 25 questions regarding such basic knowledge will likely go unanswered or you 26 will simply be referred to the LFS essential pre-reading list.</para> 27 27 28 28 <para>Before building an LFS system, we recommend reading the following … … 35 35 36 36 <para>This is a comprehensive guide to building and installing 37 <quote>generic</quote> Unix software packages under Linux.</para> 37 <quote>generic</quote> Unix software packages under Linux. Although it 38 was written some time ago, it still provides a good summary of the 39 basic techniques needed to build and install software.</para> 38 40 </listitem> 39 41 … … 42 44 <ulink url="http://www.linuxhq.com/guides/LUG/guide.html"/></para> 43 45 44 <para>This guide covers the usage of assorted Linux software.</para> 46 <para>This guide covers the usage of assorted Linux software. This 47 reference is also fairly old, but still valid.</para> 45 48 </listitem> 46 49 -
prologue/typography.xml
rca2f862e r9ee226e 34 34 <screen><computeroutput>install-info: unknown option '--dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen> 35 35 36 <para>This form of text (fixed-width text) shows screen output, probably as36 <para>This form of text (fixed-width text) shows screen output, usually as 37 37 the result of commands issued. This format is also used to show filenames, 38 38 such as <filename>/etc/ld.so.conf</filename>.</para>
Note:
See TracChangeset
for help on using the changeset viewer.