From: "Ashish Mishra" <emailaddress.ashish@gmail.com>
To: "MOHAMMED HASSAN" <hassanchattarki@gmail.com>,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] Size of production os image
Date: Mon, 12 May 2025 20:42:43 -0700 [thread overview]
Message-ID: <1013.1747107763159555423@lists.yoctoproject.org> (raw)
In-Reply-To: <CAPJWBngDN4qT+9mXVdiDLQfZn+-fQ7YkWfdDp28g+DBLRpD85w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1383 bytes --]
Hi ,
1) How much should be the size of RFS is not standard answer but depends on packages you want to add on RFS
2) Consider RFS as bucket. The size of bucket will be based on whats inside the bucket .
Hence two team can have very different size as their use case will be different
3) Just to give you an context , i just completed an project for Montavista where
i was able to bring the RFS size from 800MB to 250+MB i.e around 70% size reduction
4) How you do is depending upon what package you are adding , whats the alternate to existing package
then you go in deep of specific module to reduce their size
5) The good starting point will be to enable "buildhistory" in your custom build
6) An quick vies of the file you shared below are few starting points to help
You can evaluate them :
a) IMAGE_FEATURES:remove = " dbg-pkgs dev-pkgs "
b) Seems you are adding bash & zip both , you can shave only one on target
c) Remove VIM it can give you good saving
d) You can remove alsa from Machine & Distro feature if you don't want audio
e) Do you really require cpp ,cpio , cmake on target
f) mariadb could be heavy
g) Looks like many file system tools are being added in RFS , you can look at them
It would be helpful to others if you share your image & installed-package files as that gives clear idea as to what is going in RFS
Thanks ,
Ashish
[-- Attachment #2: Type: text/html, Size: 1872 bytes --]
next prev parent reply other threads:[~2025-05-13 3:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 8:05 Size of production os image MOHAMMED HASSAN
2025-05-12 8:57 ` [yocto] " Alexander Kanavin
2025-05-12 9:23 ` MOHAMMED HASSAN
2025-05-12 9:34 ` Alexander Kanavin
2025-05-12 9:36 ` MOHAMMED HASSAN
2025-05-12 9:47 ` Alexander Kanavin
2025-05-12 20:03 ` Khem Raj
2025-05-13 0:12 ` MOHAMMED HASSAN
2025-05-13 3:42 ` Ashish Mishra [this message]
2025-05-12 14:24 ` Philip Balister
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=1013.1747107763159555423@lists.yoctoproject.org \
--to=emailaddress.ashish@gmail.com \
--cc=hassanchattarki@gmail.com \
--cc=yocto@lists.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.