From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [RFC 0/2] IMAGE_ROOTFS_SIZE Cleanup
Date: Mon, 23 May 2011 23:38:02 -0700 [thread overview]
Message-ID: <cover.1306218459.git.sgw@linux.intel.com> (raw)
This RFC is still in the works, I would like to have folks look at it.
Previously, IMAGE_ROOTFS_SIZE was being set with _ext2 or _ext3 in
various places, this caused problem, because it was not easily overriden.
By removing all the overrides, it allows the default mechanism to work
correctly.
Currently that default mechanism takes a du of the rootfs image and then
adds in an overhead factor (IMAGE_OVERHEAD_FACTOR) or 1.3x of the du size,
in most cases this should be sufficent. I am still testing this, and I
heard that there might be a post-install issue with RPM DB being larger.
This additional addresses a couple of other issues, by clearing all the bad
overrides, it allows Image or Layer overrides to work correctly either by
setting IMAGE_ROOTFS_SIZE to some arbitray number or by allowing some extra
space be added above the existing overhead via the IMAGE_ROOTFS_EXTRA_SPACE
option.
The base default is now 64M (maybe I need to only set the one in
bitbake.conf, comments abou tthat?) with the minimal images base as 8M
(currently qemux86 sizes up to 9.9M used on an 11M rootfs).
There will be a corresponding patch for meta-yocto to remove the
IMAGE_ROOTFS_SIZE defaults in atom-pc.conf and routerstationpro.conf
I welcome comments.
Thanks
Sau!
The following changes since commit ad72ffadca975166cd8a416e4bf7b7fe33616d39:
Merge branch 'master', remote-tracking branch 'origin/master' (2011-05-23 23:00:20 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib.git sgw/rootfs_size
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/rootfs_size
Saul Wold (2):
IMAGE_ROOTFS_SIZE Cleanup
image_types: add IMAGE_ROOTFS_EXTRA_SPACE
meta/classes/image_types.bbclass | 9 ++++++---
meta/conf/bitbake.conf | 4 ++++
meta/conf/distro/include/default-distrovars.inc | 2 --
meta/conf/machine/include/qemu.inc | 2 --
.../images/core-image-minimal-initramfs.bb | 2 ++
meta/recipes-core/images/core-image-minimal.bb | 2 ++
6 files changed, 14 insertions(+), 7 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-05-24 6:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 6:38 Saul Wold [this message]
2011-05-24 6:38 ` [RFC 1/2] IMAGE_ROOTFS_SIZE Cleanup Saul Wold
2011-05-26 18:04 ` Joshua Lock
2011-05-26 18:28 ` Saul Wold
2011-05-26 19:54 ` Joshua Lock
2011-05-26 20:55 ` Darren Hart
2011-05-26 21:01 ` Joshua Lock
2011-05-26 21:03 ` Darren Hart
2011-05-26 21:13 ` Joshua Lock
2011-05-26 21:15 ` Saul Wold
2011-05-26 21:31 ` Joshua Lock
2011-05-26 21:14 ` Paul Eggleton
2011-05-27 4:07 ` Darren Hart
2011-05-27 4:29 ` Saul Wold
2011-05-27 5:22 ` Darren Hart
2011-06-02 1:46 ` Tom Rini
2011-05-24 6:38 ` [RFC 2/2] image_types: add IMAGE_ROOTFS_EXTRA_SPACE Saul Wold
2011-05-26 18:04 ` Joshua Lock
2011-05-26 18:22 ` Saul Wold
2011-05-26 20:58 ` Darren Hart
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=cover.1306218459.git.sgw@linux.intel.com \
--to=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox