From: Darren Hart <dvhart@linux.intel.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Wold, Saul" <saul.wold@intel.com>
Subject: Re: per-image ROOTFS sizes
Date: Wed, 12 Dec 2012 12:19:42 -0800 [thread overview]
Message-ID: <50C8E6DE.4020308@linux.intel.com> (raw)
In-Reply-To: <CAHUNapSTKMXS607--qaODp=Jg8e=rSKbPOhegCOA9vZ+YS3hrw@mail.gmail.com>
On 12/12/2012 12:14 PM, Trevor Woerner wrote:
> Hi Darren,
>
> On Wed, Dec 12, 2012 at 2:59 PM, Darren Hart <dvhart@linux.intel.com> wrote:
>> On 12/11/2012 01:05 PM, Trevor Woerner wrote:
>>> Are per-image ROOTFS sizes (i.e. IMAGE_ROOTFS_SIZE_<image>) still
>>> supported?
>> Interesting, I haven't tried myself. Have you tried and run into an issue?
>
>
> Yes. I had been trying to figure out why my:
>
> IMAGE_ROOTFS_SIZE_vmdk = "500000"
>
> line in my config file wasn't working when I found the link I provided
> earlier. Right now all I can say is that it doesn't work for _vmdk
> specifically.
That was:
http://patches.openembedded.org/patch/4671/
What is the reason you would like to do this just for vmdk? Is it to
avoid increasing the size of all the images when it is only vmdk you
care about? That would makes sense. Perhaps, for now, you could limit
the image types you build to just vmdk and increate the size without the
override?
Saul on CC for comment as that was his RFC Patch.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next prev parent reply other threads:[~2012-12-12 20:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 21:05 per-image ROOTFS sizes Trevor Woerner
2012-12-12 19:59 ` Darren Hart
2012-12-12 20:14 ` Trevor Woerner
2012-12-12 20:19 ` Darren Hart [this message]
2012-12-12 21:28 ` Trevor Woerner
2012-12-12 20:46 ` Robert P. J. Day
2012-12-12 21:56 ` Trevor Woerner
2012-12-12 22:03 ` Robert P. J. Day
2012-12-12 22:55 ` Trevor Woerner
2012-12-12 23:18 ` Robert P. J. Day
2012-12-12 23:16 ` Robert P. J. Day
2012-12-13 7:55 ` Saul Wold
2012-12-13 13:03 ` Robert P. J. Day
2012-12-13 17:42 ` Saul Wold
2012-12-13 19:14 ` Robert P. J. Day
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=50C8E6DE.4020308@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=saul.wold@intel.com \
--cc=twoerner@gmail.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.