From 15166351465432394bc6a75af5fe2499366921c6 Mon Sep 17 00:00:00 2001 From: Sona Sarmadi Date: Thu, 2 Aug 2018 08:05:54 +0200 Subject: 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 --- .../doc/using_enea_linux.xml | 36 +++++++++++----------- 1 file 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 @@ -15,6 +15,11 @@ Build Enea Linux images using the following steps: + + Set the $MACHINE/<machine> variable to the target you + need, e.g. intel-corei7-64. + + Clone Enea Linux sources using Repo tool. Please refer to for more details. @@ -112,13 +117,10 @@ $ repo sync $ TEMPLATECONF=meta-el-standard/conf/template.<machine> \ . ./oe-init-build-env <build_dir> - - Sourcing the build environment is needed everytime a new - shell is used. However, sourcing using the - TEMPLATECONF is only needed the first time - around. Afterwards it is enough to source the build directory - created before. - + Sourcing the build environment is needed everytime a new shell + is used. However, sourcing using the TEMPLATECONF + is only needed the first time around. Afterwards it is enough to + source the build directory created before. The build directory may reside on an NFS mount, but the @@ -182,10 +184,9 @@ $ cd <build_dir>/tmp/deploy/sdk/ # Here is the SDK installer script - DHCP server: In addition to - general DHCPD configuration, the DHCPD configuration should contain an - entry for the target with the following information about the - target: + For the DHCP server, in addition to the general configuration, the + DHCPD configuration should contain an entry for the target with the + following information: @@ -203,7 +204,7 @@ $ cd <build_dir>/tmp/deploy/sdk/ # Here is the SDK installer script The TFTP server shall be defined as - "next-server" + next-server @@ -213,7 +214,7 @@ $ cd <build_dir>/tmp/deploy/sdk/ # Here is the SDK installer script The NFS server IP address and the path to the rootfs on the - NFS server, defined as "option root-path" + NFS server, defined as option root-path @@ -227,10 +228,9 @@ $ cd <build_dir>/tmp/deploy/sdk/ # Here is the SDK installer script - TFTP server: The TFTP path to the - target's pxelinux.0 is given in the DHCP - configuration. Example of files in the TFTP subdirectory indicated by - the DHCP configuration: + 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: pxelinux.0 vesamenu.c32 @@ -261,7 +261,7 @@ label device01 DHCP and in the TFTP configuration. After configuring the servers, copy files from the build directory - into the correct configured paths: + into the correctly configured paths: -- cgit v1.2.3-54-g00ecf