From: Tom Zanussi <tom.zanussi@intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Making live images bigger
Date: Tue, 22 Mar 2011 02:39:14 -0500 [thread overview]
Message-ID: <1300779554.3049.196.camel@elmorro> (raw)
In-Reply-To: <4D87A03B.2000403@mlbassoc.com>
On Mon, 2011-03-21 at 12:00 -0700, Gary Thomas wrote:
> I'm running a live (USB) image on my Atom-PC and would like to
> install more programs. Now that I've figured out the magic to
> use zypper and rpm (thanks, Mark), I have a new problem. The
> image on the USB device is too small - basically no free space :-(
>
> So, I tried to adjust this by setting:
> /tmp/poky-amltd/meta-yocto/conf/machine/atom-pc.conf:IMAGE_ROOTFS_SIZE_ext3 ?= "1000000"
> which I think should give me a 1GB USB setup. Sadly, the result was exactly the
> same size as when I ran it with the default size.
>
> Any ideas what I'm doing wrong? I edited the config as above, then simply ran
> % bitbake poky-image-sato-live
> I can see that it rebuilt the images, but they're just too small still.
>
According to this in image.bbclass, the size should end up with 20% free
space (IMAGE_OVERHEAD_FACTOR = 1.2) regardless.
ROOTFS_SIZE=`du -ks ${IMAGE_ROOTFS}|awk '{size = $1 * ${IMAGE_OVERHEAD_FACTOR}; print (size > ${IMAGE_ROOTFS_SIZE} ? size : ${IMAGE_ROOTFS_SIZE}) }'`
But in any case, IMAGE_ROOTFS_SIZE_ext3 seems to be getting ignored -
the only way I was able to get a 1G image was to use the straight
IMAGE_ROOTFS_SIZE e.g. using
IMAGE_ROOTFS_SIZE ?= "1000000"
instead of
IMAGE_ROOTFS_SIZE_ext3 = "2000000"
in emenlow.conf. The image sizes before and after:
-rw-r--r-- 1 trz trz 582105088 2011-03-22 01:58 poky-image-sato-live-emenlow-20110322065226.hddimg
-rw-r--r-- 1 trz trz 581939200 2011-03-22 01:58 poky-image-sato-live-emenlow-20110322065226.iso
-rw-r--r-- 1 trz trz 1032947712 2011-03-22 02:21 poky-image-sato-live-emenlow-20110322071321.hddimg
-rw-r--r-- 1 trz trz 1032779776 2011-03-22 02:21 poky-image-sato-live-emenlow-20110322071321.iso
But 1000000 is half of what the default is supposed to in the first
place - if it was working correctly, it should have gotten 2Gb by
default apparently...
Tom
> Thanks
>
prev parent reply other threads:[~2011-03-22 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 19:00 Making live images bigger Gary Thomas
2011-03-22 7:39 ` Tom Zanussi [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=1300779554.3049.196.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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.