summaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-08-14 16:35:54 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-04 12:54:54 +0100
commit08b7044311674e4e414b2917fe6bfe161c2d83e5 (patch)
tree1a005b2c28b569dddcb387c6d1a70a30a4893ea8 /documentation/dev-manual
parent4972e8f49cd42c40b0f0c34ab05bdaa034dc1596 (diff)
downloadpoky-08b7044311674e4e414b2917fe6bfe161c2d83e5.tar.gz
documentation/dev-manual/dev-manual-start.xml: Updated NFS server/QEMU info
Changed the first sentence of the description of how to use QEMU images with NFS server. This is feedback from Scott Garman's review. (From yocto-docs rev: 6a33b1b58bd72756baf57228b7348ff662248012) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-start.xml10
1 files changed, 6 insertions, 4 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index 989437c6c0..065cf27d83 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -369,10 +369,12 @@
369 <filename>scp</filename> commands. 369 <filename>scp</filename> commands.
370 The <filename>core-image-minimal</filename> QEMU image, however, contains no ssh 370 The <filename>core-image-minimal</filename> QEMU image, however, contains no ssh
371 server.</para></listitem> 371 server.</para></listitem>
372 <listitem><para>The QEMU images also can be contain an embedded Network File 372 <listitem><para>You can use a provided, user-space NFS server to boot the QEMU session
373 System (NFS) server that exports the image's root filesystem. 373 using a local copy of the root filesystem on the host.
374 This allows you to make the filesystem available to the 374 In order to make this connection, you must extract a root filesystem tarball by using the
375 host.</para></listitem> 375 <filename>runqemu-extract-sdk</filename> command.
376 After running the command, you must then point the <filename>runqemu</filename>
377 script to the extracted directory instead of a root filesystem image file.</para></listitem>
376 </itemizedlist> 378 </itemizedlist>
377 </note> 379 </note>
378</section> 380</section>