From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
hh h <jupiter.hce@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Can isar Debian armhf image size be controlled?
Date: Tue, 5 Mar 2019 07:50:19 +0100 [thread overview]
Message-ID: <68538b5b-67dc-0836-5f72-3347399522ce@siemens.com> (raw)
In-Reply-To: <09b5fcd2-caf6-64fb-d310-33ab62eaa18a@ilbers.de>
On 05.03.19 07:32, Maxim Yu. Osipov wrote:
> Hi,
>
> 1) For reference ISAR armhf target - Terasic DE0-Nano-SoC - the current default
> isar-image-base rootfs gives
>
>
> isar/build/tmp/work/debian-stretch-armhf/isar-image-base/rootfs$ sudo du -sh .
> 163M .
>
> The rootfs is already trimmed from /var/cache/apt entries.
It may be further trimmed (by making it a "non-Debian" image, e.g. removing any
package management) to something like 120M or maybe even 100M. We are planning
to provide mechanisms that allow such manual tunings during image generation.
But then you usually start installing your actual application, and its
dependencies can blow up the image again. We do not know your scenario, so this
is hard to tell.
In general, you have to be in a very high volume market so that the additional
engineering and maintenance costs (when using a non-commodity distro) pay off
via saved hardware budget.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-03-05 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 22:55 hh h
2019-03-05 6:32 ` Maxim Yu. Osipov
2019-03-05 6:50 ` Jan Kiszka [this message]
2019-03-05 10:29 ` Henning Schild
2019-03-05 11:26 ` JH
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=68538b5b-67dc-0836-5f72-3347399522ce@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jupiter.hce@gmail.com \
--cc=mosipov@ilbers.de \
/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