Changeset 576a66b
- Timestamp:
- May 16, 2006, 1:14:42 PM (19 years ago)
- Branches:
- clfs-1.2, clfs-2.1, clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
- Children:
- b0dbcb6
- Parents:
- 5c45d54
- Location:
- BOOK
- Files:
-
- 5 edited
-
general.ent (modified) (3 diffs)
-
introduction/common/how.xml (modified) (6 diffs)
-
introduction/common/resources.xml (modified) (1 diff)
-
prologue/common/errata.xml (modified) (1 diff)
-
prologue/common/organization.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
BOOK/general.ent
r5c45d54 r576a66b 1 1 <?xml version="1.0" encoding="ISO-8859-1"?> 2 2 3 <!ENTITY version " CLFS-SVN-20060516">3 <!ENTITY version "SVN-20060516"> 4 4 <!ENTITY version-x86 "&version;-x86"> 5 5 <!ENTITY version-x86_64 "&version;-x86_64-Multilib"> … … 21 21 22 22 <!ENTITY lfs-root "http://www.linuxfromscratch.org/"> 23 <!ENTITY clfs-root "http:/trac.cross-lfs.org/"> 23 24 <!ENTITY blfs-root "&lfs-root;blfs/"> 24 25 <!ENTITY faq-root "&lfs-root;faq/"> … … 26 27 <!ENTITY hints-index "&lfs-root;hints/list.html"> 27 28 <!ENTITY livecd-root "&lfs-root;livecd/"> 28 <!ENTITY test-results "& lfs-root;clfs/build-logs/&generic-version;/">29 <!ENTITY errata "& lfs-root;clfs/errata/&generic-version;/">29 <!ENTITY test-results "&clfs-root;clfs/build-logs/&generic-version;/"> 30 <!ENTITY errata "&clfs-root;clfs/errata/&generic-version;/"> 30 31 31 32 <!ENTITY gnu "http://ftp.gnu.org/gnu/"> -
BOOK/introduction/common/how.xml
r5c45d54 r576a66b 9 9 <?dbhtml filename="how.html"?> 10 10 11 <title>How to Build a nLFS System</title>11 <title>How to Build a CLFS System</title> 12 12 13 <para>The LFS system will be built by using a previously installed13 <para>The CLFS system will be built by using a previously installed 14 14 Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This 15 15 existing Linux system (the host) will be used as a starting point to … … 33 33 <para><xref linkend="chapter-partitioning"/> of this book describes how 34 34 to create a new Linux native partition and file system, the place 35 where the new LFS system will be compiled and installed. <xref35 where the new CLFS system will be compiled and installed. <xref 36 36 linkend="chapter-getting-materials"/> explains which packages and 37 patches need to be downloaded to build a nLFS system and how to store37 patches need to be downloaded to build a CLFS system and how to store 38 38 them on the new file system. <xref linkend="chapter-final-preps"/> 39 39 discusses the setup for an appropriate working environment. Please read … … 47 47 programs that run on the target machine. These cross-compile tools will 48 48 be used to create a temporary, minimal system that will be the basis for 49 building the final LFS system. Some of these packages are needed to resolve49 building the final CLFS system. Some of these packages are needed to resolve 50 50 circular dependencies—for example, to compile a compiler, you need a 51 51 compiler.</para> … … 71 71 beginning of <xref linkend="chapter-temp-system"/>.</para> 72 72 73 <para>In <xref linkend="chapter-building-system"/>, the full LFS system is73 <para>In <xref linkend="chapter-building-system"/>, the full CLFS system is 74 74 built. Depending on the system you are cross-compiling for, either you will 75 75 boot the minimal temp-system on the target machine, or chroot into it.</para> … … 77 77 <para>The <command>chroot</command> (change root) program is used to enter 78 78 a virtual environment and start a new shell whose root directory will be set 79 to the LFS partition. This is very similar to rebooting and instructing the80 kernel to mount the LFS partition as the root partition.79 to the CLFS partition. This is very similar to rebooting and instructing the 80 kernel to mount the CLFS partition as the root partition. 81 81 The major advantage is that <quote>chrooting</quote> allows the builder to 82 continue using the host while LFS is being built. While waiting for package82 continue using the host while CLFS is being built. While waiting for package 83 83 compilation to complete, a user can switch to a different virtual console 84 84 (VC) or X desktop and continue using the computer as normal.</para> 85 85 86 <para>Some systems cannot be built by chrooting so they must be booted instead. Generally, if you building for a different arch than the host system, you must reboot because the kernel will likely not support the target machine. Booting involves installing a few additional packages that are needed for bootup, installing bootscripts, and building a miminal kernel.</para> 86 <para>Some systems cannot be built by chrooting so they must be 87 booted instead. Generally, if you building for a different arch than 88 the host system, you must reboot because the kernel will likely not 89 support the target machine. Booting involves installing a few 90 additional packages that are needed for bootup, installing 91 bootscripts, and building a miminal kernel.</para> 87 92 88 <para>To finish the installation, the LFS-Bootscripts are set up in <xref93 <para>To finish the installation, the CLFS-Bootscripts are set up in <xref 89 94 linkend="chapter-bootscripts"/>, and the kernel and boot loader are set 90 95 up in <xref linkend="chapter-bootable"/>. <xref 91 96 linkend="chapter-finalizing"/> contains information on furthering the 92 LFS experience beyond this book. After the steps in this book have97 CLFS experience beyond this book. After the steps in this book have 93 98 been implemented, the computer will be ready to reboot into the new 94 LFS system.</para>99 CLFS system.</para> 95 100 <!-- --> 96 101 … … 98 103 step is discussed in the following chapters and package descriptions. 99 104 Items that may seem complicated will be clarified, and everything will 100 fall into place as the reader embarks on the LFS adventure.</para>105 fall into place as the reader embarks on the CLFS adventure.</para> 101 106 102 107 </sect1> -
BOOK/introduction/common/resources.xml
r5c45d54 r576a66b 32 32 <para>For information on the different lists, how to subscribe, archive 33 33 locations, and additional information, visit 34 <ulink url="&lfs-root;mail.html"/>.</para> 34 <ulink url="&lfs-root;mail.html"/>. For mailing lists specifically 35 for CLFS, visit <ulink url="&clfs-root;wiki/lists"/>.</para> 35 36 36 37 </sect2> -
BOOK/prologue/common/errata.xml
r5c45d54 r576a66b 11 11 <title>Errata</title> 12 12 13 <para>The software used to create a nLFS system is constantly being13 <para>The software used to create a CLFS system is constantly being 14 14 updated and enhanced. Security warnings and bug fixes may become 15 15 available after the LFS book has been released. To check whether the 16 package versions or instructions in this release of LFS need any16 package versions or instructions in this release of CLFS need any 17 17 modifications to accommodate security vulnerabilities or other bug fixes, 18 18 please visit <ulink url="&errata;"/> before proceeding with your build. -
BOOK/prologue/common/organization.xml
r5c45d54 r576a66b 49 49 50 50 <sect2> 51 <title>Part V - Building the LFS System</title>51 <title>Part V - Building the CLFS System</title> 52 52 53 <para>Part V guides the reader through the building of the LFS53 <para>Part V guides the reader through the building of the CLFS 54 54 system—compiling and installing all the packages one by one, 55 55 setting up the boot scripts, and installing the kernel. The resulting … … 67 67 anywhere else in the book. Appendix A contains definitions of acronyms and 68 68 terms used in the book, Appendix B has Acknowledgments of people who 69 have helped work on the LFS project and website, and Appendices C69 have helped work on the CLFS project and website, and Appendices C 70 70 and D have information about package dependencies and the the 71 71 build order.</para>
Note:
See TracChangeset
for help on using the changeset viewer.
