2. Linux From Scratch 12.2
3. chapter07_introduction
4. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	Linux From Scratch 12.2/chapter07_introduction — Spanish	This chapter shows how to build the last missing bits of the temporary system: the tools needed to build the various packages. Now that all circular dependencies have been resolved, a <quote>chroot</quote> environment, completely isolated from the host operating system (except for the running kernel), can be used for the build.
	Linux From Scratch 12.2/chapter07_introduction — Spanish	For proper operation of the isolated environment, some communication with the running kernel must be established. This is done via the so-called <emphasis>Virtual Kernel File Systems</emphasis>, which will be mounted before entering the chroot environment. You may want to verify that they are mounted by issuing the <command>findmnt</command> command.
	Linux From Scratch 12.2/chapter07_introduction — Spanish	Until <xref linkend="ch-tools-chroot"/>, the commands must be run as <systemitem class="username">root</systemitem>, with the <envar>LFS</envar> variable set. After entering chroot, all commands are run as &root;, fortunately without access to the OS of the computer you built LFS on. Be careful anyway, as it is easy to destroy the whole LFS system with bad commands.