From: Ian Geiser <geiseri@geekcentral.pub>
To: "Christopher Larson" <clarson@kergoth.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Wic and "live" images
Date: Tue, 31 May 2016 11:24:52 -0400 [thread overview]
Message-ID: <155076adecd.fbd58d4e28737.2520989404842375814@geekcentral.pub> (raw)
In-Reply-To: <CABcZANnTRsoFWBdshg1mvV1AWvxjs_XqYb0horJwFSpqrswT6Q@mail.gmail.com>
---- On Tue, 24 May 2016 15:56:39 -0400 Christopher Larson <clarson@kergoth.com> wrote ----
>
> On Tue, May 24, 2016 at 12:51 PM, Ed Bartosh <ed.bartosh@linux.intel.com> wrote:
>
> The thing is, it's likely the machine/bsp setting the WKS_FILE, yet in OE/yocto we prefer machine/distro/image to be orthogonal. If you're injecting machine specific logic into an image, that image isn't going to be generally useful for all machines, and so violates our philosophy.
Isn't the physical disk image the place that machine/distro/image all intersect though? Maybe this is some philosophy I have always not gotten because it seems every time I make an image for a machine I am fighting the current. Really I think at the core what I want is a partition layout that I can put a payload in. wic seems exactly that, but I am not sure how to get from my rootfs, initramfs and kernel to there. Thanks!
next prev parent reply other threads:[~2016-05-31 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 9:52 Wic and "live" images Ian Geiser
2016-05-23 10:36 ` Ed Bartosh
2016-05-23 12:13 ` Ian Geiser
2016-05-23 13:00 ` Sergey 'Jin' Bostandzhyan
2016-05-23 13:09 ` Ian Geiser
2016-05-24 19:51 ` Ed Bartosh
2016-05-24 19:56 ` Christopher Larson
2016-05-24 20:16 ` Ed Bartosh
2016-05-24 20:30 ` Christopher Larson
2016-05-25 11:35 ` Ed Bartosh
2016-05-25 20:04 ` Christopher Larson
2016-05-31 15:31 ` Ian Geiser
2016-05-31 16:13 ` Christopher Larson
2016-05-31 15:24 ` Ian Geiser [this message]
2016-05-31 15:19 ` Ian Geiser
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=155076adecd.fbd58d4e28737.2520989404842375814@geekcentral.pub \
--to=geiseri@geekcentral.pub \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.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.