summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSona Sarmadi <sona.sarmadi@enea.com>2018-08-02 08:05:54 +0200
committerSona Sarmadi <sona.sarmadi@enea.com>2018-08-02 13:29:41 +0200
commit15166351465432394bc6a75af5fe2499366921c6 (patch)
treeeebb4041a9208d2c5035908a40b9442402106265
parentddccea54b0fc621d293098e83a44202c90cf8a26 (diff)
downloadel_releases-standard-15166351465432394bc6a75af5fe2499366921c6.tar.gz
Fixed Miruna's review comments
1. Do we explain what the $MACHINE variable is anywhere or how to set it even if we only have one machine in this release? 2. in 5.1.2 after step 2 (Source the build environment) there are two notes, would you please make the first note into a para instead. 3. in 5.2.1 Boot via PXE using DHCP, TFTP, and NFS servers: In the first itemizedlist, you have quotation marks around a server name and a path marked by the literal tags, remove them please. doc/book-enea-linux-user-guide/doc/using_enea_linux.xml Line 186: Rephrase to: "For the DHCP server, in addition to the general configuration, the DHCPD configuration should contain an entry for the target with the following information:" Line 232: Rephrase to: "For the TFTP server, the TFTP path to the target's pxelinux.0 file is given in the DHCP Configuration. Examples of files included in the TFTP subdirectory indicated by the DHCP configuration are:" Line 264: "correctly" Change-Id: I8ae5383e121d51aa508f1a76da9d0578a58a2431 Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>
-rw-r--r--doc/book-enea-linux-user-guide/doc/using_enea_linux.xml36
1 files changed, 18 insertions, 18 deletions
diff --git a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
index ea801b2..4cee415 100644
--- a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
+++ b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
@@ -16,6 +16,11 @@
16 16
17 <procedure> 17 <procedure>
18 <step> 18 <step>
19 <para>Set the $MACHINE/&lt;machine&gt; variable to the target you
20 need, e.g. <literal>intel-corei7-64</literal>.</para>
21 </step>
22
23 <step>
19 <para>Clone Enea Linux sources using Repo tool. Please refer to 24 <para>Clone Enea Linux sources using Repo tool. Please refer to
20 <xref linkend="getting_sources" /> for more details.</para> 25 <xref linkend="getting_sources" /> for more details.</para>
21 26
@@ -112,13 +117,10 @@ $ repo sync</programlisting>
112$ TEMPLATECONF=meta-el-standard/conf/template.&lt;machine&gt; \ 117$ TEMPLATECONF=meta-el-standard/conf/template.&lt;machine&gt; \
113. ./oe-init-build-env &lt;build_dir&gt;</programlisting> 118. ./oe-init-build-env &lt;build_dir&gt;</programlisting>
114 119
115 <note> 120 <para>Sourcing the build environment is needed everytime a new shell
116 <para>Sourcing the build environment is needed everytime a new 121 is used. However, sourcing using the <literal>TEMPLATECONF</literal>
117 shell is used. However, sourcing using the 122 is only needed the first time around. Afterwards it is enough to
118 <literal>TEMPLATECONF</literal> is only needed the first time 123 source the build directory created before.</para>
119 around. Afterwards it is enough to source the build directory
120 created before.</para>
121 </note>
122 124
123 <note> 125 <note>
124 <para>The build directory may reside on an NFS mount, but the 126 <para>The build directory may reside on an NFS mount, but the
@@ -182,10 +184,9 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/ # Here is the SDK installer script</prog
182 target MAC address, and refers to the TFTP server for the boot image and 184 target MAC address, and refers to the TFTP server for the boot image and
183 to the NFS server for the root file system.</para> 185 to the NFS server for the root file system.</para>
184 186
185 <para><emphasis role="bold">DHCP server</emphasis>: In addition to 187 <para>For the DHCP server, in addition to the general configuration, the
186 general DHCPD configuration, the DHCPD configuration should contain an 188 DHCPD configuration should contain an entry for the target with the
187 entry for the target with the following information about the 189 following information:</para>
188 target:</para>
189 190
190 <itemizedlist spacing="compact"> 191 <itemizedlist spacing="compact">
191 <listitem> 192 <listitem>
@@ -203,7 +204,7 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/ # Here is the SDK installer script</prog
203 204
204 <listitem> 205 <listitem>
205 <para>The TFTP server shall be defined as 206 <para>The TFTP server shall be defined as
206 "<literal>next-server</literal>"</para> 207 <literal>next-server</literal></para>
207 </listitem> 208 </listitem>
208 209
209 <listitem> 210 <listitem>
@@ -213,7 +214,7 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/ # Here is the SDK installer script</prog
213 214
214 <listitem> 215 <listitem>
215 <para>The NFS server IP address and the path to the rootfs on the 216 <para>The NFS server IP address and the path to the rootfs on the
216 NFS server, defined as "<literal>option root-path</literal>"</para> 217 NFS server, defined as <literal>option root-path</literal></para>
217 </listitem> 218 </listitem>
218 </itemizedlist> 219 </itemizedlist>
219 220
@@ -227,10 +228,9 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/ # Here is the SDK installer script</prog
227 option root-path "192.168.2.20:/export/intel-corei7-64_rootfs"; 228 option root-path "192.168.2.20:/export/intel-corei7-64_rootfs";
228}</programlisting> 229}</programlisting>
229 230
230 <para><emphasis role="bold">TFTP server</emphasis>: The TFTP path to the 231 <para>For the TFTP server, the TFTP path to the target's pxelinux.0 file
231 target's <literal>pxelinux.0</literal> is given in the DHCP 232 is given in the DHCP Configuration. Examples of files included in the
232 configuration. Example of files in the TFTP subdirectory indicated by 233 TFTP subdirectory indicated by the DHCP configuration are:</para>
233 the DHCP configuration:</para>
234 234
235 <programlisting>pxelinux.0 235 <programlisting>pxelinux.0
236vesamenu.c32 236vesamenu.c32
@@ -261,7 +261,7 @@ label device01
261 DHCP and in the TFTP configuration.</para> 261 DHCP and in the TFTP configuration.</para>
262 262
263 <para>After configuring the servers, copy files from the build directory 263 <para>After configuring the servers, copy files from the build directory
264 into the correct configured paths:</para> 264 into the correctly configured paths:</para>
265 265
266 <orderedlist spacing="compact"> 266 <orderedlist spacing="compact">
267 <listitem> 267 <listitem>