From: Robert Yang <liezhi.yang@windriver.com>
To: oe-core <openembedded-core@lists.openembedded.org>
Subject: krogoth's core-image-minimal is much bigger than jethro's
Date: Fri, 13 May 2016 14:48:26 +0800 [thread overview]
Message-ID: <573578BA.80207@windriver.com> (raw)
* For ext4:
11M -> 26M
The similar to vmdk, qcow2 and iso.
* For tar.bz2:
2.7M -> 4.5M
The main problem is eudev-hwdb which would be 12M after installed, jethro
doesn't use this, but udev by default, and it's gone in krogoth.
$ du -sh core-image-minimal/1.0-r0/rootfs/etc/udev/*
0 core-image-minimal/1.0-r0/rootfs/etc/udev/cache.data
6.4M core-image-minimal/1.0-r0/rootfs/etc/udev/hwdb.bin
5.2M core-image-minimal/1.0-r0/rootfs/etc/udev/hwdb.d
8.0K core-image-minimal/1.0-r0/rootfs/etc/udev/rules.d
4.0K core-image-minimal/1.0-r0/rootfs/etc/udev/udev.conf
Is there an easier way to fix this problem, please ? It's not a good
news for the user who uses core-imag-minimal/udev when they want to
upgrade to krogoth. And this would hurt the small device which uses
udev.
The conf is:
MACHINE = "qemux86-64"
DISTRO = "poky"
PACKAGE_CLASSES = "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES = "buildstats image-mklibs"
$ bitbake core-image-minimal
For jethro:
$ ls -lh core-image-minimal-qemux86-64-20160513061306.rootfs.ext4
11M core-image-minimal-qemux86-64-20160513061306.rootfs.ext4
$ du -sh core-image-minimal-qemux86-64-20160513061306.rootfs.ext4
7.9M core-image-minimal-qemux86-64-20160513061306.rootfs.ext4
For krogoth:
$ ls -lh core-image-minimal-qemux86-64-20160513061459.rootfs.ext4
26M core-image-minimal-qemux86-64-20160513061459.rootfs.ext4
$ du -sh core-image-minimal-qemux86-64-20160513061459.rootfs.ext4
core-image-minimal-qemux86-64-20160513061459.rootfs.ext4
--
Thanks
Robert
next reply other threads:[~2016-05-13 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 6:48 Robert Yang [this message]
2016-05-13 7:07 ` krogoth's core-image-minimal is much bigger than jethro's Andrea Adami
2016-05-13 7:23 ` Robert Yang
2016-05-13 7:46 ` Gary Thomas
2016-05-13 7:46 ` Gary Thomas
2016-05-13 14:05 ` Burton, Ross
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=573578BA.80207@windriver.com \
--to=liezhi.yang@windriver.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