From: Saul Wold <sgw@linux.intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: self-hosted image vs. build appliance
Date: Wed, 20 Jun 2012 09:44:47 -0700 [thread overview]
Message-ID: <4FE1FDFF.5040401@linux.intel.com> (raw)
In-Reply-To: <CC07B7AA.119FA%belen.barros.pena@intel.com>
On 06/20/2012 09:23 AM, Barros Pena, Belen wrote:
> Does anybody know why are we calling it 'self-hosted-image' in Hob and
> 'build-appliance' in the Yocto Project website? Wouldn't it be easier if
> we used the same name everywhere? Which one should be used?
>
They are slightly different. The self-hosted-image is the recipe name
that generates the image. The build-appliance is the VMware OVF file
and bits needed to use VMPlayer or VMWorkstation. The self-hosted-image
is the underlying disk image used in the Build Appliance
Sau!
> Thanks!
>
> Belen
>
> ---------------------------------------------------------------------
> Intel Corporation (UK) Limited
> Registered No. 1134945 (England)
> Registered Office: Pipers Way, Swindon SN3 1RJ
> VAT No: 860 2173 47
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
next prev parent reply other threads:[~2012-06-20 16:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 16:23 self-hosted image vs. build appliance Barros Pena, Belen
2012-06-20 16:44 ` Saul Wold [this message]
2012-06-21 10:30 ` Barros Pena, Belen
2012-06-21 15:22 ` Saul Wold
2012-06-22 8:44 ` Barros Pena, Belen
2012-06-22 13:44 ` Rifenbark, Scott M
2012-06-25 9:38 ` Barros Pena, Belen
2012-06-25 9:47 ` Barros Pena, Belen
2012-06-20 22:16 ` Stewart, David C
2012-06-21 10:39 ` Barros Pena, Belen
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=4FE1FDFF.5040401@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=belen.barros.pena@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.