sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

- documentation/poky-ref-manual/extendpoky.xml: Added text for choosing server 

[BUGID# 293] - I added text at the end of section 3.2.3 "Customizing Images
Using Custom IMAGE_FEATURES" to include explanation of the two servers
Poky uses for images by default.  Also how to change the variable
IMAGE_FEATURES to configure the server.  This change is part of the
fix for BUGID# 293 and was suggested by Scott Garman.

(From OE-Core rev: 13041874070ea2235f8c3abe156ae5e940b15f5f)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2011-03-17 07:41:33 -06:00 committed by Richard Purdie
parent 75c5760fe8
commit 5622f546c8
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
documentation/poky-ref-manual/extendpoky.xml
View File

@ -364,6 +364,16 @@ RRECOMMENDS_task-custom-tools = "\
Users can add extra features by extending the class or creating a custom class for use
with specialized image <filename>.bb</filename> files.
</para>
<para>
Poky ships with two SSH servers you can use in your images: Dropbear and OpenSSH.
Dropbear is a minimal SSH server appropriate for resource-constrained environments,
while OpenSSH is a well-known standard SSH server implementation.
By default, poky-image-sato is configured to use Dropbear.
The poky-image-basic and poky-image-lsb images both include OpenSSH.
To change these defaults, edit the <filename>IMAGE_FEATURES</filename> variable
so that it sets the image you are working with to include ssh-server-dropbear
or ssh-server-openssh.
</para>
</section>
<section id='usingpoky-extend-customimage-localconf'>