Changeset b642d80 for BOOK/prologue/common/foreword.xml
- Timestamp:
- Jul 15, 2006, 3:21:48 AM (18 years ago)
- Branches:
- clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
- Children:
- 07bbf3a
- Parents:
- 32f1da4
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
BOOK/prologue/common/foreword.xml
r32f1da4 rb642d80 11 11 <title>Foreword</title> 12 12 13 <para>My adventures in Linux began in 1998 when I downloaded and 14 installed my first distribution. After working with it for a while, I 15 discovered issues I definitely would have liked to see improved upon. 16 For example, I didn't like the arrangement of the bootscripts or the way 17 programs were configured by default. I tried a number of alternative 18 distributions to address these issues, yet each had its pros and cons. 19 Finally, I realized that if I wanted full satisfaction from my Linux 20 system, I would have to build my own from scratch.</para> 13 <para>The Linux From Scratch Project has seen many changes in the 14 few years of its existance. I personally became involved with the 15 project in 1999, around the time of the 2.x releases. At that time, 16 the build process was to create static binaries with the host system, 17 then chroot and build the final binaries on top of the static ones.</para> 21 18 22 <para>What does this mean? I resolved not to use pre-compiled packages 23 of any kind, nor CD-ROMs or boot disks that would install basic 24 utilities. I would use my current Linux system to develop my own 25 customized system. This <quote>perfect</quote> Linux system would then 26 have the strengths of various systems without their associated 27 weaknesses. In the beginning, the idea was rather daunting, but I 28 remained committed to the idea that a system could be built that would 29 conform to my needs and desires rather than to a standard that just 30 did not fit what I was looking for.</para> 19 <para>Later came the use of the /static directory to hold the initial 20 static builds, keeping them separated from the final system, then 21 the PureLFS process developed by Ryan Oliver and Greg Schafer, 22 introducing a new toolchain build process that divorces even our initial 23 builds from the host. Finally, LFS 6 bought Linux Kernel 2.6, the 24 udev dynamic device structure, sanitized kernel headers, and other 25 improvements to the Linux From Scratch system.</para> 31 26 32 <para>After sorting through issues such as circular dependencies and 33 compile-time errors, I created a custom-built Linux system that was 34 fully operational and suitable to individual needs. This process also 35 allowed me to create compact and streamlined Linux systems which are 36 faster and take up less space than traditional operating systems. I 37 called this system a Linux From Scratch system, or an CLFS system for 38 short.</para> 27 <para>The one "flaw" in LFS is that it has always been based on a x86 28 class processor. With the advent of the Athlon 64 and Intel EM64T 29 processors, the x86-only LFS is no longer ideal. Throughout this time, 30 Ryan Oliver developed and documented a process by which you could 31 build Linux for any system and from any system; by use of 32 cross-compilation techniques. Thus, the Cross LFS project was born.</para> 39 33 40 <para>As I shared my goals and experiences with other members of the 41 Linux community, it became apparent that there was sustained interest 42 in the ideas set forth in my Linux adventures. Such custom-built CLFS 43 systems serve not only to meet user specifications and requirements, but 44 also serve as an ideal learning opportunity for programmers and system 45 administrators to enhance their Linux skills. Out of this broadened 46 interest, the Linux From Scratch Project was born.</para> 34 <para>CLFS follows the same guiding principles the LFS project has 35 always followed, e.g., knowing your system inside and out by virtue 36 of having built the system yourself. Additionally, during a CLFS 37 build, you will learn advanced techniques such as cross-build toolchains, 38 multilib support (32 & 64-bit libraries side-by-side), alternative 39 architectures such as Sparc, MIPS, and Alpha, and much more.</para> 47 40 48 <para>This <emphasis>Linux From Scratch</emphasis> book provides 49 readers with the background and instruction to design and build custom 50 Linux systems. This book highlights the Linux from Scratch project and 51 the benefits of using this system. Users can dictate all aspects of 52 their system, including directory layout, script setup, and security. 53 The resulting system will be compiled completely from the source code, 54 and the user will be able to specify where, why, and how programs are 55 installed. This book allows readers to fully customize Linux systems 56 to their own needs and allows users more control over their 57 system.</para> 58 59 <para>I hope you will have a great time working on your own CLFS 60 system, and enjoy the numerous benefits of having a system that is 61 truly <emphasis>your own</emphasis>.</para> 41 <para>We hope you enjoy building your own CLFS system, and the benefits 42 that come from a system tailored to your needs!</para> 62 43 63 44 <literallayout>-- 64 Gerard Beekmans 65 gerard@linuxfromscratch.org</literallayout> 45 Jeremy Utley, CLFS 1.x Release Manager (Page Author) 46 Jim Gifford, CLFS Project Co-leader 47 Ryan Oliver, CLFS Project Co-leader 48 Joe Ciccone, Justin Knierin, Chris Staub, Matt Darcy, Ken Moffat, 49 Manuel Canales Esparcia, and Nathan Coulson - CLFS Developers</literallayout> 66 50 67 51 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.