From mboxrd@z Thu Jan  1 00:00:00 1970
X-GM-THRID: 6663931010253586432
Date: Sat, 2 Mar 2019 14:55:46 -0800 (PST)
From: hh h <jupiter.hce@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Message-Id: <884bdd75-b3db-430e-b34f-f84f57e98d48@googlegroups.com>
Subject: Can isar Debian armhf image size be controlled?
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_8_2084530401.1551567346460"
X-Google-Token: EPKT7OMF5LDCq-K9JXo0
X-Google-IP: 27.32.173.11
X-TUID: 6zk3qE+j8Xfg

------=_Part_8_2084530401.1551567346460
Content-Type: multipart/alternative; 
	boundary="----=_Part_9_261319985.1551567346460"

------=_Part_9_261319985.1551567346460
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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



------=_Part_9_261319985.1551567346460
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div><br></div><div>I am selecting build sys=
tem 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++ applic=
ations are simply for data transfer and communication using TCP/IP, the app=
lications 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 co=
uld be too large to blow out the device resource constraints, OE or Yocto o=
r OpenWrt image seems much smaller than the Debian armhf image. Is it possi=
ble to control / reduce Debian armhf image size by isar build, to reach the=
 same resource level in OE Yocto or OpenWrt?</div><div><br></div><div>Also =
how stable is the isar build for Debian stretch armhf?</div><div><br></div>=
<div>Thank you and appreciate it.</div><div><br></div><div>Kind regards,</d=
iv><div><br></div><div>- jh<br></div><div><br></div><div><br></div></div>
------=_Part_9_261319985.1551567346460--

------=_Part_8_2084530401.1551567346460--