From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: do QEMU images really come with dropbear and an nfs server?
Date: Fri, 27 Jul 2012 10:38:12 -0700 [thread overview]
Message-ID: <5012D204.9010101@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207271016320.15452@oneiric>
On 07/27/2012 07:18 AM, Robert P. J. Day wrote:
>
> the yocto dev manual currently suggests that QEMU images come with
> both dropbear and an nfs server:
>
> http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#using-pre-built-binaries-and-qemu
>
> i don't have a QEMU image in front of me to test, but the definition
> of the basic QEMU images doesn't seem to suggest that that's true.
>
> i can see it's easy to add them, but the manual suggests they're
> there by default. or am i misreading something?
It looks like we may need a manual tweak here.
core-image-minimal does not come with any ssh server. core-image-lsb
should have openssh instead of dropbear. So unless something changed
very recently, core-image-sato is the only one that has dropbear in it
by default.
Also, the manual states "The QEMU images also contain an embedded
Network File System (NFS) server that exports the image's root
filesystem." This isn't strictly true - instead we offer a native tool
which runs a userspace NFS server and if some prep work is done by the
user (extracting a rootfs tarball with runqemu-extract-sdk), you can
then point the runqemu script to that directory instead of a rootfs
image file.
Someone please correct me if I'm wrong.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-07-27 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 14:18 do QEMU images really come with dropbear and an nfs server? Robert P. J. Day
2012-07-27 17:38 ` Scott Garman [this message]
2012-07-27 18:04 ` Robert P. J. Day
2012-07-27 18:41 ` Scott Garman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5012D204.9010101@intel.com \
--to=scott.a.garman@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.