On 3/16/16 21:37 , Gary Thomas wrote:
On 03/16/2016 08:40 PM, K Richard Pixley wrote:
What's the intended difference between hddimg and hdddirect?
I'm confused about the intent here. The data flow in previous releases,
even jethro, seems to be somewhat confused/broken so looking at the
source
What's the intended difference between hddimg and hdddirect?
I'm confused about the intent here. The data flow in previous releases,
even jethro, seems to be somewhat confused/broken so looking at the
source code isn't really helping here.
Is one intended to be a simple syslinux bootable image
On 3/14/16 15:58 , Rudolf Streif wrote:
Richard,
On Mon, Mar 14, 2016 at 1:55 PM, K Richard Pixley <r...@noir.com
<mailto:r...@noir.com>> wrote:
If I add that line, (
IMAGE_FSTYPES = "vmdk"
), to my local.conf, I get:
rich@burgess> time b
If I add that line, (
IMAGE_FSTYPES = "vmdk"
), to my local.conf, I get:
rich@burgess> time bitbake core-image-minimal
ERROR: OE-core's config sanity checker detected a potential
misconfiguration.
Either fix the cause of this error or at your own risk disable
the checker
On 3/14/16 10:16 , Khem Raj wrote:
On Mon, Mar 14, 2016 at 10:11 AM, K Richard Pixley <r...@noir.com> wrote:
While we're on it...
Can anyone explain what a "live" image is intended to be?
it can either boot from the disk or you can run the installer to
install it to anoth
While we're on it...
Can anyone explain what a "live" image is intended to be?
(I haven't gotten a live image to "work", but I'm not entirely sure I
know what "work" means for a live image.)
Or how hdddirect is intended to be different from hddimg?
--rich
--
On 3/13/16 22:16 , Gary Thomas wrote:
I'd like to to some testing that qemu just doesn't seem up to
so I attempted to build a live ISO per the documentation. I
added these lines to local.conf:
IMAGE_FSTYPES_genericx86 += "live"
NOISO_genericx86 = "0"
When I try to build core-image-base I
