Changeset c093e6b for chapter07/introduction.xml
- Timestamp:
- 10/01/2022 10:30:12 PM (18 months ago)
- Branches:
- multilib
- Children:
- f3b2f16
- Parents:
- f29824e (diff), 4349661 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter07/introduction.xml
rf29824e rc093e6b 12 12 13 13 <para>This chapter shows how to build the last missing bits of the temporary 14 system: the tools needed by the build machinery ofvarious packages. Now14 system: the tools needed to build the various packages. Now 15 15 that all circular dependencies have been resolved, a <quote>chroot</quote> 16 16 environment, completely isolated from the host operating system (except for … … 18 18 19 19 <para>For proper operation of the isolated environment, some communication 20 with the running kernel must be established. This is done throughthe21 so-called <emphasis>Virtual Kernel File Systems</emphasis>, which mustbe22 mounted when entering the chroot environment. You may want to check23 that they are mounted by issuing <command>findmnt</command>.</para>20 with the running kernel must be established. This is done via the 21 so-called <emphasis>Virtual Kernel File Systems</emphasis>, which will be 22 mounted before entering the chroot environment. You may want to verify 23 that they are mounted by issuing the <command>findmnt</command> command.</para> 24 24 25 25 <para>Until <xref linkend="ch-tools-chroot"/>, the commands must be … … 28 28 are run as &root;, fortunately without access to the OS of the computer 29 29 you built LFS on. Be careful anyway, as it is easy to destroy the whole 30 LFS system with bad ly formedcommands.</para>30 LFS system with bad commands.</para> 31 31 32 32 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.