From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: does "wic" allow one to actually format physical devices?
Date: Fri, 29 Jul 2016 13:35:22 +0300 [thread overview]
Message-ID: <20160729103522.GA376@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1607290614570.22106@localhost.localdomain>
On Fri, Jul 29, 2016 at 06:19:13AM -0400, Robert P. J. Day wrote:
> On Fri, 29 Jul 2016, Ed Bartosh wrote:
>
> > On Thu, Jul 28, 2016 at 05:30:14PM -0400, Robert P. J. Day wrote:
> > >
> > > never used "wic" before, and i'm wondering if it has the ability
> > > to not create dd-able images so much as partition and format
> > > physical target devices. surely, the underlying logic would be the
> > > same, i just want to work with the target hard drive and bypass
> > > creating the image itself.
> >
> > The only purpose of wic is to create images. I'm afraid it doesn't
> > have the functionality you're looking for.
>
> i thought that was the case, just wanted to make sure. and perhaps
> i'm just missing it, but where is the canonical documentation for wic,
> it might still be useful for what i'm doing.
The documentation is here:
http://www.yoctoproject.org/docs/2.1/mega-manual/mega-manual.html#creating-partitioned-images
you can get also gert some info from wic help overview|plugins|kickstart output.
> rday
>
> p.s. i'm assuming you can use 'wic' only in the context of an OE
> build, yes? at least it appears that way.
Yes, wic is tightly coupled with OE.
--
Regards,
Ed
prev parent reply other threads:[~2016-07-29 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 21:30 does "wic" allow one to actually format physical devices? Robert P. J. Day
2016-07-29 8:25 ` Ed Bartosh
2016-07-29 10:19 ` Robert P. J. Day
2016-07-29 10:35 ` Ed Bartosh [this message]
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=20160729103522.GA376@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox