Updating repo with sys req xml

LXCR-7666 completing the last steps

Signed-off-by: Miruna Paun <Miruna.Paun@enea.com>

1 files changed, 162 insertions, 0 deletions

diff --git a/doc/system_requirements.xml b/doc/system_requirements.xml
new file mode 100644
index 0000000..fb55c8e
--- /dev/null
+++ b/doc/system_requirements.xml
@@ -0,0 +1,162 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="enea-linux-sysreq">
+  <title>System Requirements</title>
+
+  <para>The host requirements listed below are extensive to allow for the
+  building of Linux images via the Yocto system, and not just
+  applications.</para>
+
+  <para>Please also see the system requirements in the Yocto 2.1 documents:
+  Yocto Project Start <ulink
+  url="http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html#yp-resources">
+  http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html#yp-resources</ulink>
+  and the Yocto Project Reference Manual <ulink
+  url="http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#intro-requirements">
+  http://www.yoctoproject.org/docs/2.1/ref-manual/ref-manual.html#intro-requirements</ulink>.
+  If needed, replace the Yocto version in the links provided with a more
+  recent version.</para>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec align="left" colname="1" colwidth="1*" />
+
+      <colspec align="left" colname="2" colwidth="3*" />
+
+      <spanspec nameend="2" namest="1" spanname="onetwo" />
+
+      <tbody>
+        <row>
+          <entry spanname="onetwo"><emphasis role="bold"> Build host
+          requirements<indexterm>
+              <primary>system requirements</primary>
+            </indexterm></emphasis></entry>
+        </row>
+
+        <row>
+          <entry>Linux distribution</entry>
+
+          <entry>The downloaded code shall be built on a Linux host to
+          generate images for your target or for emulation in QEMU. For
+          information about the supported hosts and targets, see the <emphasis
+          role="bold">Enea Linux Release Information</emphasis> in your Enea
+          Linux distribution.</entry>
+        </row>
+
+        <row>
+          <entry>Internet access</entry>
+
+          <entry>Internet access must be available when building an image,
+          since bitbake downloads source files from various servers during the
+          build.</entry>
+        </row>
+
+        <row>
+          <entry>Packages</entry>
+
+          <entry>Depending on the Linux distribution and version on host, some
+          packages may be required, by bitbake for example. You will install
+          any required packages while following the installation
+          instructions.</entry>
+        </row>
+
+        <row>
+          <entry>Targets</entry>
+
+          <entry>Images can be built or downloaded for any of the targets
+          supported in this release, as specified in the <emphasis
+          role="bold">Enea Linux Release Information</emphasis>.</entry>
+        </row>
+
+        <row>
+          <entry>Disk space</entry>
+
+          <entry><para>Your system should have at least 50 GB of free disk
+          space when bitbaking the basic enea-image-name kernel image.</para>
+          <para>For larger images and to allow for future package extensions
+          and variations in the build process, a minimum of 100 GB free disk
+          space is recommended.</para></entry>
+        </row>
+
+        <row>
+          <entry>Recommended RAM</entry>
+
+          <entry><para>Your system must have at least 4 GB available
+          RAM.</para> <para>It is recommended to have 8 GB RAM available for
+          parallel build jobs.</para></entry>
+        </row>
+
+        <row>
+          <entry>Java</entry>
+
+          <entry>Java <indexterm>
+              <primary>java</primary>
+            </indexterm>is required to run Eclipse. Currenly, Eclipse
+          generally recommends at least Java 6 JRE/JDK. More information
+          regarding operating environments for Eclipse, is provided in the
+          <emphasis>Eclipse Project Release Notes</emphasis> for the version
+          used. This can usually be found via
+          http://www.eclipse.org/eclipse/development/readme_eclipse_version.
+          See the <emphasis role="bold">Enea Linux Release Information
+          </emphasis>for the Eclipse Version.</entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+
+  <para>The build time depends on the capacity of the processor and other
+  hardware, available resources, speed of internet connection, load situation,
+  etc. E.g: on a fast 16 core machine with 16 GB RAM and SSD disks, a complete
+  build from source could take about two hours.</para>
+
+  <informaltable>
+    <tgroup cols="2">
+      <colspec align="left" colname="1" colwidth="1*" />
+
+      <colspec align="left" colname="2" colwidth="3*" />
+
+      <spanspec nameend="2" namest="1" spanname="onetwo" />
+
+      <tbody>
+        <row>
+          <entry spanname="onetwo"><emphasis role="bold">Target
+          Requirements</emphasis></entry>
+        </row>
+
+        <row>
+          <entry>External memory</entry>
+
+          <entry>To boot a CGL<indexterm>
+              <primary>CGL</primary>
+            </indexterm> image, you need at least 16 GB on a hard-disk
+          drive<indexterm>
+              <primary>HDD</primary>
+            </indexterm> on eSATA, USB drive, or SD card.<remark>INFO: (packed
+          rootfs 4.5 GB + unpacked rootfs 1.5 GB + good
+          margins)</remark><remark>INFO: NFS does not support SELinux. In
+          order to have a security-enhanced Linux, one must take off from an
+          NFS-booted system and proceed with boot from external
+          memory.</remark></entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
+
+  <section id="ensure-bash">
+    <title>System Shell Configuration</title>
+
+    <para>Before installing Enea Linux, ensure that bash is the default
+    shell.</para>
+
+    <para>If your system runs Ubuntu, you can use ls -l to ensure
+    <filename>/usr/bin</filename> is a symbolic link to bash. In case the link
+    points to dash, which is default in some Ubuntu versions, change it to
+    bash by running <emphasis role="bold">sudo dpkg-reconfigure
+    dash</emphasis> and answer <emphasis role="bold">No</emphasis> to the
+    question "Use dash as the default system shell (/bin/sh)?":</para>
+
+    <programlisting># ls -l /bin/sh
+        lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; bash</programlisting>
+  </section>
+</section>
\ No newline at end of file