aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/yocto-project-qs')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml21
1 files changed, 5 insertions, 16 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 6db76f40b2..b1746aec8f 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -402,28 +402,17 @@
<para>
Use the following commands to build your image.
- The OpenEmbedded build process creates an entire Linux distribution, including the toolchain,
- from source.
- </para>
-
- <note><para>
- The build process using Sato currently consumes about 50 Gbytes
- of disk space.
- To allow for variations in the build process and for future
- package expansion, we recommend having at least 50 Gbytes
- of free disk space.
- </para></note>
-
- <note>
- <para>
+ The OpenEmbedded build process creates an entire Linux
+ distribution, including the toolchain, from source.
+ <note>
By default, the build process searches for source code using
a pre-determined order through a set of locations.
If you encounter problems with the build process finding and
downloading source code, see the
"<ulink url='&YOCTO_DOCS_REF_URL;#how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>How does the OpenEmbedded build system obtain source code and will it work behind my firewall or proxy server?</ulink>"
entry in the Yocto Project Reference Manual FAQ.
- </para>
- </note>
+ </note>
+ </para>
<para>
<literallayout class='monospaced'>