Made the final updates needed to Rel Notes and UG

LXCR-7925

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

7 files changed, 296 insertions, 324 deletions

diff --git a/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml
index f6bd068..1db30fd 100644
--- a/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml
+++ b/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml
@@ -42,7 +42,7 @@ export PATH=~/bin:$PATH</programlisting></para>
     correct also compared to the "previous" REL VER in pardoc-distro.xml
     "prev_baseline".</bridgehead>
 
-    <para id="EneaLinux_REL_VER"><phrase>1.0</phrase></para>
+    <para id="EneaLinux_REL_VER"><phrase>1.1</phrase></para>
 
     <para id="Yocto_VER"><phrase>2.1</phrase></para>
 
diff --git a/doc/book-enea-nfv-access-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
index 4763281..8028d78 100644
--- a/doc/book-enea-nfv-access-guide/doc/getting_started.xml
+++ b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
@@ -4,6 +4,202 @@
 <chapter id="plat-release-content">
   <title>Getting Started with ENFV Access</title>
 
+  <para>Using Enea NFV Access requires access to a Linux machine, which is
+  used for preparing the bootable drive or for developing applications. System
+  requirements for the development host are detailed in the <xi:include
+  href="../../s_docbuild/olinkdb/pardoc-common.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(book_enea_nfv_access_release_info/1)" /> document included
+  with this release.</para>
+
+  <section id="sysshell_config">
+    <title>System Shell Configuration</title>
+
+    <para>Before installing Enea NFV Access, 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 <literal>Use dash as the default system shell
+    (/bin/sh)?</literal>:</para>
+
+    <programlisting># ls -l /bin/sh
+lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; bash</programlisting>
+  </section>
+
+  <section id="access_installer">
+    <title>Enea NFV Access Installer</title>
+
+    <para>The easiest way to get up and running with Enea NFV Access is to use
+    the installer provided in the install directory for each supported
+    architecture in this release. The purpose of this installer is to guide
+    you through creating a bootable Enea NFV Access installation on a physical
+    media (e.g. USB stick or HDD).</para>
+
+    <section id="installer_prereq">
+      <title>Installer Prerequisites</title>
+
+      <para>Using the installer on the development host requires the
+      following:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>a GRUB .efi binary</para>
+        </listitem>
+
+        <listitem>
+          <para>a physical drive of 16GB or larger</para>
+        </listitem>
+
+        <listitem>
+          <para>For USB booting you will need: a development based rootfs,
+          provided with the release (e.g.
+          <filename>enea-nfv-access-dev-inteld1521.tar.gz</filename>).</para>
+        </listitem>
+
+        <listitem>
+          <para>For booting from an SSD or HDD you will need: any rootfs that
+          needs to be installed on the board, provided with the release (e.g.
+          <filename>enea-nfv-access.tar.gz</filename>).</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+
+    <section id="installer_usage">
+      <title>Installer Usage</title>
+
+      <para>The <emphasis role="bold">Enea NFV Access installer</emphasis>
+      shall be executed on the development host machine with root permissions.
+      Once the <filename>nfv_installer</filename> prompt is displayed, press
+      <literal>ENTER</literal> to get the full list of built-in
+      commands:</para>
+
+      <programlisting>help              - a guide on how to use the installer
+list-params       - lists parameters
+list-steps        - lists the available steps and the parameters that they depend on
+set               - sets a parameter (e.g. "set drive=/dev/sda")
+clear             - clears a parameter (e.g. "clear drive")
+list-partitions   - lists current drives and partitions
+dry               - describes the steps to be executed and checks if the files exist
+run               - executes the steps
+q or quit         - exits the script</programlisting>
+
+      <para>Enea NFV Access creates a bootable media by performing these
+      steps:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Create two partitions on a designated drive (e.g.
+          /dev/sda):</para>
+
+          <itemizedlist>
+            <listitem>
+              <para>a 512MB partition for GRUB</para>
+            </listitem>
+
+            <listitem>
+              <para>the rest of the drive is reserved for the rootfs</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Configure GRUB on one partition (usually the first
+          one).</para>
+        </listitem>
+
+        <listitem>
+          <para>Copy a root filesystem on the other partition.</para>
+        </listitem>
+      </orderedlist>
+
+      <note>
+        <para>Running step 3 will implicitly copy the installer on that root
+        filesystem in
+        <filename>/usr/bin/install_nfvaccess.sh.</filename></para>
+      </note>
+
+      <para>Each step mentioned above is executed or not depending on whether
+      certain parameters are set. Run the
+      <command><literal>list-steps</literal></command> command in order to
+      understand the built-in steps that the installer can execute and what
+      parameters they depend on. The command will print the following:</para>
+
+      <orderedlist>
+        <listitem>
+          <para><command>Format drive</command> - Uses the drive set for the
+          <literal>drive</literal> parameter to create a 512MB partition for
+          GRUB and another partition for the rootfs. The rootfs partition will
+          be as large as the physical media minus 512MB. This step depends on
+          the following parameter(s): <programlisting>drive=</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">GRUB install</emphasis> - Installs the
+          binary pointed to by <literal>grub_binary</literal> on the drive set
+          in <literal>grub_destination</literal>. A
+          <filename>grub.cfg</filename> file will be created that will be
+          configured to boot off of <literal>rootfs_destination</literal>.
+          This step depends on the following parameters:<programlisting>grub_destination=
+grub_binary=
+rootfs_destination=</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Root filesystem install</emphasis> -
+          Copies the files found in <literal>rootfs_targz</literal> to the
+          drive set in <literal>rootfs_destination</literal>. This step
+          depends on the following parameters:<programlisting>rootfs_targz=
+rootfs_destination=</programlisting></para>
+        </listitem>
+      </orderedlist>
+
+      <para>Parameters can be set through the <command>set</command> command
+      or cleared using the <command>clear</command> command. Since some
+      parameters are common for multiple steps, as is
+      <literal>rootfs_destination</literal> for the GRUB and rootfs
+      installation steps, you can get a list of all the parameters, by running
+      <literal>list-params</literal>.</para>
+
+      <para>The following parameters can be configured:<programlisting>grub_destination=[drive]    - specifies the drive where GRUB will be installed
+grub_binary=[file]          - points to the GRUB executable to be installed
+                              where grub_destination is set
+rootfs_destination=[drive]  - specifies where the rootfs will be deployed
+rootfs_targz=[.tar.gz file] - what file to unpack to where rootfs_destination is set
+drive=[/dev/sdaX]           - what drive to partition</programlisting></para>
+
+      <para>Before performing the actual partitioning and copying, a dry run,
+      using the <command>dry</command> command, can be executed without
+      affecting the actual layout of the physical media. Once all the
+      parameters are set according to the intended scenario, simply execute
+      the <command>run</command> command to set up the bootable media. Below
+      are a few examples of how the Enea NFV Access installer may be
+      used.</para>
+
+      <para>Example of partitioning a drive:<programlisting>set drive=/dev/sda
+run</programlisting></para>
+
+      <para>Example of partitioning a drive, installing GRUB and a root
+      filesystem:<programlisting>set drive=/dev/sda
+set grub_destination=/dev/sda1
+set grub_binary=/home/user/grub-binary.efi
+set rootfs_destination=/dev/sda2
+set rootfs_targz=/home/user/rootfs.tar.gz
+run</programlisting></para>
+
+      <para>Example of deploying ONLY a root filesystem:<programlisting>set rootfs_destination=/dev/sda2
+set rootfs_targz=/home/user/rootfs.tar.gz
+runs</programlisting></para>
+
+      <para>After using the installer and setting up the bootable media,
+      connect it to the target machine and configure the target machine to use
+      it as a primary boot device.</para>
+    </section>
+  </section>
+
   <section id="release-content">
     <title>NFV Access Release content</title>
 
@@ -48,8 +244,7 @@
                 -- enea-glibc-x86_64-enea-image-virtualization-guest-sdk /
                    -core2-64-toolchain-7.0.sh
                    /* self-extracting archive installing cross-compilation
-                   toolchain for the guest (QEMU x86-64) */
-</programlisting>
+                   toolchain for the guest (QEMU x86-64) */</programlisting>
 
     <para>For each combination of image and target, the following set of
     artifacts is available:</para>
@@ -155,7 +350,7 @@ label el_ramfs
         <listitem>
           <para>grub (<literal>grub-efi-bootx64.efi</literal>) - availalble as
           a pre-built artifact under
-          <literal>inteld1521/images/</literal>enea-nfv-access.</para>
+          <literal>inteld1521/images/enea-nfv-access</literal>.</para>
         </listitem>
 
         <listitem>
diff --git a/doc/book-enea-nfv-access-guide/doc/overview.xml b/doc/book-enea-nfv-access-guide/doc/overview.xml
index 01e70a9..5b9a54e 100644
--- a/doc/book-enea-nfv-access-guide/doc/overview.xml
+++ b/doc/book-enea-nfv-access-guide/doc/overview.xml
@@ -4,7 +4,7 @@
 <chapter id="overview">
   <title>Overview</title>
 
-  <para>The NFV Access Guide available with this release of Enea NFV Access
+  <para>The NFV Access Guide available with this release of the Enea NFV Access
   Platform seeks to provide further information that will help all intended
   users make the most out of the virtualization features.</para>
 
diff --git a/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml b/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml
index 255f733..9e0d47c 100644
--- a/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml
+++ b/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml
@@ -4,7 +4,7 @@
 <chapter id="workflow">
   <title>Using NFV Access SDKs</title>
 
-  <para>Enea NFV Access comes with a standard SDKs which can be used to
+  <para>Enea NFV Access comes with a standard SDK which can be used to
   develop user-applications and kernel modules for both host and guest
   images.</para>
 
diff --git a/doc/book-enea-nfv-access-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
index 6ca8568..383f4f2 100644
--- a/doc/book-enea-nfv-access-release-info/doc/about_release.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/about_release.xml
@@ -27,76 +27,60 @@
 
     <programlisting>-- documentation/
    /* NFV Access documentation */
--- inteld1521/
-   /* artifacts for the host side */
-        -- deb/
-           /* deb packages */
-        -- images/
-            -- enea-image-virtualization-host
-               /* precompiled artifacts for the Host release image */
-                -- various artifacts
-            -- enea-image-virtualization-host-sdk
-               /* precompiled artifacts for the Host SDK image.
-               The SDK image contains userspace tools and kernel
-               configurations necessary for developing, debugging
-               and profiling applications and kernel modules */
-                -- various artifacts
-        -- sdk
-           /* NFV Access SDK for the host */
-                -- enea-glibc-x86_64-enea-image-virtualization-host-sdk /
-                   -corei7-64-toolchain-7.0.sh
-                   /* self-extracting archive installing
-                   cross-compilation toolchain for the host */
--- qemux86-64
-   /* artifacts for the guest side */
-        -- deb/
-           /* deb packages */
-        -- images/
-            -- enea-image-virtualization-guest
-               /* precompiled artifacts for the Guest image */
-                -- various artifacts
-        -- sdk
-           /* NFV Access SDK for the guest */
-                -- enea-glibc-x86_64-enea-image-virtualization-guest-sdk /
-                   -core2-64-toolchain-7.0.sh
-                   /* self-extracting archive installing cross-compilation
-                   toolchain for the guest (QEMU x86-64) */</programlisting>
+-- x86-64 /* architecture */
+        -- inteld1521/
+           /* artifacts for the host side */
+                -- deb/
+                   /* deb packages */
+                -- images/
+                    -- enea-nfv-access
+                       /* precompiled artifacts for the platform release image */
+                        -- various artifacts (rootfs, kernel, config etc.)
+                    -- enea-nfv-access-dev
+                       /* precompiled artifacts for development process. The image
+                          contains userspace tools and kernel configurations necessary
+                          for developing, debugging and profiling applications and
+                          kernel modules */
+                        -- various artifacts
+        -- qemux86-64
+                -- deb/
+                   /* deb packages */
+                -- images/
+                    -- enea-nfv-access-guest
+                       /* precompiled artifacts for QEMU/Docker release image  */
+                        -- various artifacts
+                    -- enea-nfv-access-guest-dev
+                       /* precompiled artifacts for development process. The image
+                          contains userspace tools and kernel configurations necessary
+                          for developing, debugging and profiling applications and
+                          kernel modules  */
+                        -- various artifacts
+        -- install
+                -- install-sdk.sh
+                       /* self-extracting archive installing cross-compilation
+                          toolchain for the platform */</programlisting>
 
     <para>For each combination of image and target, the following set of
     artifacts is available:</para>
 
     <programlisting>-- bzImage
    /* kernel image */
--- bzImage-target.bin
+-- bzImage-&lt;target&gt;.bin
    /* kernel image, same as above */
--- config-target.config
+-- config-&lt;target&gt;.config
    /* kernel configuration file */
--- core-image-minimal-initramfs-target.cpio.gz
-   /* cpio archive of the initramfs */
--- core-image-minimal-initramfs-target.qemuboot.conf
-   /* qemu config file for the initramfs image */
--- image-name-target.ext4
-   /* EXT4 image of the rootfs */
--- image-name-target.hddimg
-   /* msdos filesystem containing syslinux, kernel, initrd and rootfs image */
--- image-name-target.iso
-   /* CD .iso image */
--- image-name-target.qemuboot.conf
-   /* qemu config file for the image */
--- image-name-target.tar.gz
+-- &lt;image-name&gt;-&lt;target&gt;.ext4.gz
+   /* compressed EXT4 image of the rootfs */
+-- &lt;image-name&gt;-&lt;target&gt;.qcow2
+   /* QCOW image for QEMU - only for guest images */
+-- &lt;image-name&gt;-&lt;target&gt;.qemuboot.conf
+   /* qemu config file for the guest images */
+-- &lt;image-name&gt;-&lt;target&gt;.tar.gz
    /* tar archive of the image */
--- image-name-target.wic
-   /* Wic image */
 -- microcode.cpio
-   /* kernel microcode data */
--- modules-target.tgz
+   /* kernel microcode data - Intel arch specific*/
+-- modules-&lt;target&gt;.tgz
    /* external kernel modules */
--- ovmf.*.qcow2
-   /* ovmf firmware for uefi support in qemu */
--- rmc.db
-   /* Central RMC Database */
--- systemd-bootx64.efi
-   /* systemd-boot EFI file */
 -- grub-efi-bootx64.efi
    /* GRUB EFI file */</programlisting>
   </section>
diff --git a/doc/book-enea-nfv-access-release-info/doc/system_requirements.xml b/doc/book-enea-nfv-access-release-info/doc/system_requirements.xml
deleted file mode 100644
index 7bab63d..0000000
--- a/doc/book-enea-nfv-access-release-info/doc/system_requirements.xml
+++ /dev/null
@@ -1,162 +0,0 @@
-<?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-nfv-access-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 link(s) 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
diff --git a/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml b/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
index 3217339..fb3f57f 100644
--- a/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/system_requirements_prerequisites.xml
@@ -5,101 +5,56 @@
   <title>System Requirements and Prerequisites</title>
 
   <para>Using Enea NFV Access or compiling applications requires certain
-  packages to be installed on your NFV Access development host.</para>
-
-  <section id="enea-nfv-access-sysreq">
-    <title>System Requirements</title>
-
-    <para>The host requirements listed below are extensive to allow getting
-    Enea NFV Access to be booted on target machines and for building
-    applications.</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 product can installed on the target machine
-            using a Linux host. For information about the supported hosts and
-            targets, see <xref
-            linkend="relinfo-supported-host-environment" />.</entry>
-          </row>
-
-          <row>
-            <entry>Packages</entry>
-
-            <entry>Depending on the Linux distribution and version of the
-            host, some packages may be required. See details on what packages
-            are needed and how to install, in the following sections.</entry>
-          </row>
-
-          <row>
-            <entry>Disk space</entry>
-
-            <entry>Your system should have at least 50 GB of free disk space
-            for installing the SDK or cross-compiling applications.</entry>
-          </row>
-
-          <row>
-            <entry>Recommended RAM</entry>
-
-            <entry>Your system must have at least 4 GB available RAM.</entry>
-          </row>
-        </tbody>
-      </tgroup>
-    </informaltable>
-  </section>
-
-  <section id="ensure-bash">
-    <title>System Shell Configuration</title>
-
-    <para>Before installing Enea NFV Access, 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 id="preq-packages">
-    <title>Prerequisite Packages</title>
-
-    <para>First ensure the system is up-to-date, then for the supported
-    distribution(s), you need the following packages:<remark>INFO: The
-    programlisting below is a parameters in eltf_params_updated.xml with ID:
-    "eltf-prereq-apt-get-command-host". If multiple hosts are supported, store
-    the commands for each host in the same programlisting with empty lines
-    between each - the comment with the FULL HOST name and version is
-    essential.</remark></para>
-
-    <xi:include href="eltf_params_updated.xml"
-                xmlns:xi="http://www.w3.org/2001/XInclude"
-                xpointer="element(eltf-prereq-apt-get-commands-host/1)" />
-  </section>
-
-  <section id="dns-server">
-    <title>Installing and Configuring the DNS server</title>
-
-    <para>CONTENT NEEDED</para>
-  </section>
+  packages to be installed on your NFV Access development host. The host
+  requirements listed below are extensive to allow getting Enea NFV Access to
+  be booted on target machines and for building applications.</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 product can installed on the target machine
+          using a Linux host. For information about the supported hosts and
+          targets, see <xref
+          linkend="relinfo-supported-host-environment" />.</entry>
+        </row>
+
+        <row>
+          <entry>Packages</entry>
+
+          <entry>Depending on the Linux distribution and version of the host,
+          some packages may be required. See details on what packages are
+          needed and how to install, in the following sections.</entry>
+        </row>
+
+        <row>
+          <entry>Disk space</entry>
+
+          <entry>Your system should have at least 50 GB of free disk space for
+          installing the SDK or cross-compiling applications.</entry>
+        </row>
+
+        <row>
+          <entry>Recommended RAM</entry>
+
+          <entry>Your system must have at least 4 GB available RAM.</entry>
+        </row>
+      </tbody>
+    </tgroup>
+  </informaltable>
 </chapter>
\ No newline at end of file