Updated ch. 8 Using Enea NFV Access SDKs.

Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

1 files changed, 19 insertions, 22 deletions

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 13ae3b7..9995594 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
@@ -116,7 +116,7 @@ int main(void) {
       <listitem>
         <para>Deploy the helloworld program to your target and run it:</para>
 
-        <programlisting>root@cn8304:~# ./helloworld
+        <programlisting># ./helloworld
 hello world</programlisting>
       </listitem>
     </orderedlist>
@@ -183,12 +183,9 @@ MODULE_LICENSE("GPL");</programlisting>
         <para>Deploy the kernel module <literal>hello.ko</literal> to your
         target and install/remove it:</para>
 
-        <programlisting>root@cn8304:~# insmod hello.ko
-root@cn8304:~# rmmod hello.ko
-root@cn8304:~# dmesg
-[...] Loading hello module...
-[...] Hello, world
-[...] Goodbye, world</programlisting>
+        <programlisting># insmod hello.ko
+# rmmod hello.ko
+</programlisting>
       </listitem>
     </orderedlist>
   </section>
@@ -227,7 +224,7 @@ root@cn8304:~# dmesg
           <para>On the host, run the <literal>qemu-ifup</literal> script
           located in <literal>/etc</literal> directory:</para>
 
-          <para><programlisting>root@cn8304:~# /etc/qemu-ifup –t tap0 –a 192.168.122.10 –p 1050 –g 22</programlisting></para>
+          <para><programlisting># /etc/qemu-ifup –t tap0 –a 192.168.122.10 –p 1050 –g 22</programlisting></para>
 
           <itemizedlist>
             <listitem>
@@ -268,9 +265,9 @@ root@cn8304:~# dmesg
           device and set the default gateway as the <literal>virbr0</literal>
           ip address:</para>
 
-          <para><programlisting>root@qemuarm64:~# ip addr add 192.168.122.10/24 dev enp0s2
-root@qemuarm64:~# ip link set enp0s2 up
-root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
+          <para><programlisting># ip addr add 192.168.122.10/24 dev enp0s2
+# ip link set enp0s2 up
+# ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
         </listitem>
 
         <listitem>
@@ -284,9 +281,9 @@ root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlist
           stopping the virtual machine, you can use the
           <literal>qemu-ifdown</literal> script to clean up the configuration
           on host. The following command will remove the tap interface and all
-          the iptables rules for the specific ip address: <programlisting>root@qemuarm64:~# /etc/qemu-ifdown –t tap0 –a 192.168.122.10</programlisting>If
+          the iptables rules for the specific ip address: <programlisting># /etc/qemu-ifdown –t tap0 –a 192.168.122.10</programlisting>If
           we need to remove only a particular port forwarding rule from
-          iptables, this should be run: <programlisting>root@qemuarm64:~# /etc/qemu-ifdown –t tap0 –a 192.168.122.10 –p 1050 –g 22</programlisting></para>
+          iptables, this should be run: <programlisting># /etc/qemu-ifdown –t tap0 –a 192.168.122.10 –p 1050 –g 22</programlisting></para>
         </listitem>
       </orderedlist>
     </section>
@@ -325,7 +322,7 @@ root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlist
       GDBServer and cross-gdb.</para>
 
       <para>On target, launch the GDBServer, specifying how to communicate
-      with GDB and the name of your program:<programlisting>root@cn8304:~# gdbserver :&lt;port_no&gt; /tmp/helloworld</programlisting>The
+      with GDB and the name of your program:<programlisting># gdbserver :&lt;port_no&gt; /tmp/helloworld</programlisting>The
       target will now be listening on the port given as a parameter to the
       gdbserver. On the development machine, from the
       <literal>&lt;sdkdir&gt;</literal>, start the cross-gdb:<programlisting>$ enea-linux-gdb &lt;path_to_the_program&gt;/helloworld</programlisting>Connect
@@ -350,7 +347,7 @@ root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlist
       <orderedlist>
         <listitem>
           <para>On the host, run the script <literal>qemu-ifup</literal>
-          located in <literal>/etc</literal> directory: <programlisting>root@cn8304:~# /etc/qemu-ifup –t tap0 –a 192.168.122.10 –p 1051 –g 1025</programlisting></para>
+          located in <literal>/etc</literal> directory: <programlisting># /etc/qemu-ifup –t tap0 –a 192.168.122.10 –p 1051 –g 1025</programlisting></para>
 
           <itemizedlist>
             <listitem>
@@ -387,16 +384,16 @@ root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlist
         <listitem>
           <para>On the guest, after logging, configure the virtual network
           device and set the default gateway to virbr0 ip
-          address:<programlisting>root@qemuarm64:~# ip addr add 192.168.122.10/24 dev enp0s2
-root@qemuarm64:~# ip link set enp0s2 up
-root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
+          address:<programlisting>ip addr add 192.168.122.10/24 dev enp0s2
+ip link set enp0s2 up
+ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
         </listitem>
 
         <listitem>
           <para>GDBserver is the program which runs on the guest VM and allows
           you to run GDB on your workstation. On the guest, launch GBDserver
           specifying how to communicate with GDB and the name of your program:
-          <programlisting>root@qemuarm64:~# gdbserver :1025 /tmp/helloworld</programlisting>The
+          <programlisting># gdbserver :1025 /tmp/helloworld</programlisting>The
           guest is now listening on port 1025, given as a parameter to the
           gdbserver.</para>
         </listitem>
@@ -416,7 +413,7 @@ root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlist
           <para>On the host, after finishing the cross-debugging session and
           stopping the virtual machine, you can use the
           <filename>qemu-ifdown</filename> script to clean up the
-          configuration on host:<programlisting>root@cn8304:~# /etc/qemu-ifdown -t tap0 -a 192.168.122.10</programlisting></para>
+          configuration on host:<programlisting># /etc/qemu-ifdown -t tap0 -a 192.168.122.10</programlisting></para>
         </listitem>
       </orderedlist>
     </section>
@@ -435,12 +432,12 @@ root@qemuarm64:~# ip route add default via 192.168.122.1 dev enp0s2</programlist
       <itemizedlist>
         <listitem>
           <para>On target, once serial communication is established, configure
-          <literal>kgdboc</literal> after the kernel boots:<programlisting>root@cn8304:~# echo ttyS0,115200 &gt; /sys/module/kgdboc/parameters/kgdboc</programlisting></para>
+          <literal>kgdboc</literal> after the kernel boots:<programlisting># echo ttyS0,115200 &gt; /sys/module/kgdboc/parameters/kgdboc</programlisting></para>
         </listitem>
 
         <listitem>
           <para>In order to connect to gdb via kgdboc, the kernel must first
-          be stopped:<programlisting>root@cn8304:~# echo g &gt; /proc/sysrq-trigger</programlisting></para>
+          be stopped:<programlisting># echo g &gt; /proc/sysrq-trigger</programlisting></para>
         </listitem>
 
         <listitem>