1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ |
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent"> |
---|
5 | %general-entities; |
---|
6 | ]> |
---|
7 | |
---|
8 | <sect1 id="pre-foreword"> |
---|
9 | <?dbhtml filename="foreword.html"?> |
---|
10 | |
---|
11 | <title>Foreword</title> |
---|
12 | |
---|
13 | <para>The Linux From Scratch Project has seen many changes in the |
---|
14 | few years of its existence. 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> |
---|
18 | |
---|
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> |
---|
26 | |
---|
27 | <para>The one "flaw" in LFS is that it has always been based on an 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-Compiled LFS (CLFS) was |
---|
33 | born.</para> |
---|
34 | |
---|
35 | <para>CLFS follows the same guiding principles the LFS project has |
---|
36 | always followed, e.g., knowing your system inside and out by virtue |
---|
37 | of having built the system yourself. Additionally, during a CLFS |
---|
38 | build, you will learn advanced techniques such as cross-build toolchains, |
---|
39 | multilib support (32 & 64-bit libraries side-by-side), alternative |
---|
40 | architectures such as Sparc, MIPS, and Alpha, and much more.</para> |
---|
41 | |
---|
42 | <para>We hope you enjoy building your own CLFS system, and the benefits |
---|
43 | that come from a system tailored to your needs.</para> |
---|
44 | |
---|
45 | <literallayout>-- |
---|
46 | Jeremy Utley, CLFS 1.x Release Manager (Page Author) |
---|
47 | Jim Gifford, CLFS Project Co-leader |
---|
48 | Ryan Oliver, CLFS Project Co-leader |
---|
49 | Joe Ciccone, Justin Knierim, Chris Staub, Matt Darcy, Ken Moffat, |
---|
50 | Manuel Canales Esparcia, and Nathan Coulson - CLFS Developers</literallayout> |
---|
51 | |
---|
52 | </sect1> |
---|