From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: 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:32:30 +0100 [thread overview]
Message-ID: <09b5fcd2-caf6-64fb-d310-33ab62eaa18a@ilbers.de> (raw)
In-Reply-To: <884bdd75-b3db-430e-b34f-f84f57e98d48@googlegroups.com>
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.
2) The build for armhf debian stretch is stable (both - native and cross)
Regards,
Maxim.
On 3/2/19 11:55 PM, hh h wrote:
> Hi,
>
> I am selecting build system and distro for my small Linux embedded
> device, it has small resources, about 128 MB Flash and 64 MB RAM. The
> device is a typical embedded system, no GUI, no Desktop environment, no
> multiple user interfaces, the C++ applications are simply for data
> transfer and communication using TCP/IP, the applications were
> previously running well on Debian 8 armhf, so isar Debian is my first
> choice, but the Debian image size could be a major problem, it could be
> too large to blow out the device resource constraints, OE or Yocto or
> OpenWrt image seems much smaller than the Debian armhf image. Is it
> possible to control / reduce Debian armhf image size by isar build, to
> reach the same resource level in OE Yocto or OpenWrt?
>
> Also how stable is the isar build for Debian stretch armhf?
>
> Thank you and appreciate it.
>
> Kind regards,
>
> - jh
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to isar-users+unsubscribe@googlegroups.com
> <mailto:isar-users+unsubscribe@googlegroups.com>.
> To post to this group, send email to isar-users@googlegroups.com
> <mailto:isar-users@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/884bdd75-b3db-430e-b34f-f84f57e98d48%40googlegroups.com
> <https://groups.google.com/d/msgid/isar-users/884bdd75-b3db-430e-b34f-f84f57e98d48%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
next prev parent reply other threads:[~2019-03-05 6:32 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 [this message]
2019-03-05 6:50 ` Jan Kiszka
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=09b5fcd2-caf6-64fb-d310-33ab62eaa18a@ilbers.de \
--to=mosipov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jupiter.hce@gmail.com \
/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