Changeset 81fd230 for chapter01/how.xml
- Timestamp:
- 02/19/2005 10:16:42 PM (19 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.1, 6.1.1, 6.3, 6.4, 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:
- 3d31fc4
- Parents:
- 2f9131f
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/how.xml
r2f9131f r81fd230 8 8 <?dbhtml filename="how.html"?> 9 9 10 <para>See testing</para> 10 <para>The LFS system will be built by using a previously installed 11 Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This 12 existing Linux system (the host) will be used as a starting point to 13 provide necessary programs, including a compiler, linker, and shell, 14 to build the new system. Select the <quote>development</quote> option 15 during the distribution installation to be able to access these 16 tools.</para> 17 18 <para><xref linkend="chapter-partitioning"/> of this book describes how 19 to create a new Linux native partition and file system, the place 20 where the new LFS system will be compiled and installed. <xref 21 linkend="chapter-getting-materials"/> explains which packages and 22 patches need to be downloaded to build an LFS system and how to store 23 them on the new file system. <xref linkend="chapter-final-preps"/> 24 discusses the setup for an appropriate work environment. Please read 25 <xref linkend="chapter-final-preps"/> carefully as it explains several 26 important issues the developer should be aware of before beginning to 27 work through <xref linkend="chapter-temporary-tools"/> and 28 beyond.</para> 29 30 <para><xref linkend="chapter-temporary-tools"/> explains the 31 installation of a number of packages that will form the basic 32 development suite (or toolchain) which is used to build the actual 33 system in <xref linkend="chapter-building-system"/>. Some of these 34 packages are needed to resolve circular dependencies—for example, 35 to compile a compiler, you need a compiler.</para> 36 37 <para><xref linkend="chapter-temporary-tools"/> also shows the user how 38 to build a first pass of the toolchain, including Binutils and GCC 39 (first pass basically means these two core packages will be 40 re-installed a second time). The programs from these packages will be 41 linked statically in order to be used independently of the host 42 system. The next step is to build Glibc, the C library. Glibc will be 43 compiled by the toolchain programs built in the first pass. Then, a 44 second pass of the toolchain will be built. This time, the toolchain 45 will be dynamically linked against the newly built Glibc. The 46 remaining <xref linkend="chapter-temporary-tools"/> packages are built 47 using this second pass toolchain. When this is done, the LFS 48 installation process will no longer depend on the host distribution, 49 with the exception of the running kernel.</para> 50 51 <para>While this may initially seem like a lot of work to get away 52 from a host distribution, a full technical explanation is provided at 53 the beginning of <xref linkend="chapter-temporary-tools"/>, 54 including notes on the differences between 55 statically and dynamically-linked programs.</para> 56 57 <para>In <xref linkend="chapter-building-system"/>, the full LFS system is 58 built. The chroot (change root) program is used to enter a virtual 59 environment and start a new shell whose root directory will be set to 60 the LFS partition. This is very similar to rebooting and instructing 61 the kernel to mount the LFS partition as the root partition. The 62 system does not actually reboot, but instead chroots because creating a 63 bootable system requires additional work which is not necessary just 64 yet. The major advantage is that <quote>chrooting</quote> allows the 65 builder to continue using the host while LFS is being built. While 66 waiting for package compilation to complete, a user can switch to a 67 different virtual console (VC) or X desktop and continue using the 68 computer as normal.</para> 69 70 <para>To finish the installation, the bootscripts are set up in <xref 71 linkend="chapter-bootscripts"/>, and the kernel and boot loader are set 72 up in <xref linkend="chapter-bootable"/>. <xref 73 linkend="chapter-finalizing"/> contains information on furthering the 74 LFS experience beyond this book. After the steps in this book have 75 been implemented, the computer will be ready to reboot into the new 76 LFS system.</para> 77 78 <para>This is the process in a nutshell. Detailed information on each 79 step is discussed in the following chapters and package descriptions. 80 Items that may seem complicated will be clarified, and everything will 81 fall into place as the developer embarks on the LFS adventure.</para> 11 82 12 83 </sect1> 84
Note:
See TracChangeset
for help on using the changeset viewer.