Changeset 9c10139 for chapter01/how.xml
- Timestamp:
- 01/30/2005 10:21:16 AM (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:
- d7ea6f24
- Parents:
- a460953
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/how.xml
ra460953 r9c10139 10 10 <para>See testing</para> 11 11 12 <!--13 <para>You are going to build your LFS system by using a previously installed14 Linux distribution (such as Debian, Mandrake, Red Hat, or SuSE). This existing15 Linux system (the host) will be used as a starting point, because you will need16 programs like a compiler, linker and shell to build the new system. Normally17 all the required tools are available if you selected <quote>development</quote>18 as one of the options when you installed your distribution.</para>19 20 <para>In <xref linkend="chapter-partitioning"/> you will first create a new Linux native21 partition and file system, the place where your new LFS system will be compiled22 and installed. Then in <xref linkend="chapter-getting-materials"/> you download all the23 packages and patches needed to build an LFS system, and store them on the new24 file system. In <xref linkend="chapter-final-preps"/> you set up a good25 environment to work in.</para>26 27 <para><xref linkend="chapter-temporary-tools"/> then discusses the installation of a number28 of packages that will form the basic development suite (or <emphasis>toolchain</emphasis>) which is29 used to build the actual system in <xref linkend="chapter-building-system"/>. Some of these30 packages are needed to resolve circular dependencies - for example, to compile31 a compiler you need a compiler.</para>32 33 <para>The first thing to be done in <xref linkend="chapter-temporary-tools"/> is build a34 first pass of the toolchain, made up of Binutils and GCC. The programs from35 these packages will be linked statically in order for them to be usable36 independently of the host system. The second thing to do is build Glibc, the37 C library. Glibc will be compiled by the toolchain programs just built in38 the first pass. The third thing to do is build a second pass of the toolchain.39 This time the toolchain will be dynamically linked against the newly built40 Glibc. The remaining <xref linkend="chapter-temporary-tools"/> packages are all built using41 this second pass toolchain and dynamically linked against the new42 host-independent Glibc. When this is done, the LFS installation process will no43 longer depend on the host distribution, with the exception of the running44 kernel.</para>45 46 <para>You may be thinking that <quote>this seems like a lot of work, just to47 get away from my host distribution</quote>. Well, a full technical explanation48 is provided at the start of <xref linkend="chapter-temporary-tools"/>, including some notes49 on the differences between statically and dynamically linked programs.</para>50 51 <para>In <xref linkend="chapter-building-system"/> your real LFS system will be built. The52 <command>chroot</command> (change root) program is used to enter a virtual environment and start53 a new shell whose root directory will be set to the LFS partition. This is very54 similar to rebooting and instructing the kernel to mount the LFS partition as55 the root partition. The reason that you don't actually reboot, but instead56 chroot, is that creating a bootable system requires additional work which isn't57 necessary just yet. But the major advantage is that <quote>chrooting</quote> allows you to58 continue using the host while LFS is being built. While waiting for package59 compilation to complete, you can simply switch to a different VC (Virtual60 Console) or X desktop and continue using the computer as you normally61 would.</para>62 63 <para>To finish the installation, the bootscripts are set up in64 <xref linkend="chapter-bootscripts"/>, the kernel and bootloader are set up in65 <xref linkend="chapter-bootable"/>, and <xref linkend="chapter-finalizing"/> contains some66 pointers to help you after you finish the book. Then, finally, you're ready to67 reboot your computer into your new LFS system.</para>68 69 <para>This is the process in a nutshell. Detailed information on the steps you70 will take are discussed in the chapters and package descriptions as you71 progress through them. If something isn't completely clear now, don't worry,72 everything will fall into place soon.</para>73 74 <para>Please read <xref linkend="chapter-final-preps"/> carefully as it explains75 a few important things you should be aware of before you begin to work through76 <xref linkend="chapter-temporary-tools"/> and beyond.</para>77 -->78 79 12 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.