summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-03-17 10:56:02 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-18 18:00:08 +0000
commitc8bab9bca4635420164669eab574a939f57808ea (patch)
tree8451b2719bf97e334e4571faf53bf5f2d7be5af6 /documentation
parentb209beb54b1f84a21dcdc74bcc9d068139e3536b (diff)
downloadpoky-c8bab9bca4635420164669eab574a939f57808ea.tar.gz
documentation/poky-ref-manual/faq.xml: Spell Check
Performed a spell check and corrected several problems. (From OE-Core rev: e26e9f41eac1bb34a7d9276921d14e843444622d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/poky-ref-manual/faq.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml
index 03ae7144f7..96e32d5192 100644
--- a/documentation/poky-ref-manual/faq.xml
+++ b/documentation/poky-ref-manual/faq.xml
@@ -108,7 +108,7 @@
108 </listitem> 108 </listitem>
109 <listitem> 109 <listitem>
110 <para> 110 <para>
111 Send us bitbake recipes if you have them (see the Poky handbook to find out how to create recipes) 111 Send us BitBake recipes if you have them (see the Poky handbook to find out how to create recipes)
112 </para> 112 </para>
113 </listitem> 113 </listitem>
114 </itemizedlist> 114 </itemizedlist>
@@ -148,7 +148,7 @@
148 </question> 148 </question>
149 <answer> 149 <answer>
150 <para> 150 <para>
151 To add a package you need to create a bitbake recipe - see the Poky handbook to find out how to create a recipe. 151 To add a package you need to create a BitBake recipe - see the Poky handbook to find out how to create a recipe.
152 </para> 152 </para>
153 </answer> 153 </answer>
154 </qandaentry> 154 </qandaentry>
@@ -332,19 +332,19 @@
332 </question> 332 </question>
333 <answer> 333 <answer>
334 <para> 334 <para>
335 If the same build is failing in totally different and random ways the most likely explaination is that either the hardware you're running it on has some problem or if you are running it under virtualisation, the virtualisation probably has bugs. Poky processes a massive amount of data causing lots of network, disk and cpu activity and is senstive to even single bit failure in any of these areas. Totally random failures have always been traced back to hardware or virtualisation issues. 335 If the same build is failing in totally different and random ways the most likely explanation is that either the hardware you're running it on has some problem or if you are running it under virtualisation, the virtualisation probably has bugs. Poky processes a massive amount of data causing lots of network, disk and cpu activity and is sensitive to even single bit failure in any of these areas. Totally random failures have always been traced back to hardware or virtualisation issues.
336 </para> 336 </para>
337 </answer> 337 </answer>
338 </qandaentry> 338 </qandaentry>
339 <qandaentry> 339 <qandaentry>
340 <question> 340 <question>
341 <para> 341 <para>
342 What do we need to ship for licence complience? 342 What do we need to ship for license compliance?
343 </para> 343 </para>
344 </question> 344 </question>
345 <answer> 345 <answer>
346 <para> 346 <para>
347 This is a difficult question and you need to consult your lawyer for the answer for your specific case. Its worth bearing in mind that for GPL complience there needs to be enough information shipped to allow someone else to rebuild the same end result as you are shipping. This means sharing the source code, any patches applied to it but also any configuration information about how that package was configured and built. 347 This is a difficult question and you need to consult your lawyer for the answer for your specific case. Its worth bearing in mind that for GPL compliance there needs to be enough information shipped to allow someone else to rebuild the same end result as you are shipping. This means sharing the source code, any patches applied to it but also any configuration information about how that package was configured and built.
348 </para> 348 </para>
349 </answer> 349 </answer>
350 </qandaentry> 350 </qandaentry>