From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6663931010253586432 X-Received: by 2002:a17:906:584c:: with SMTP id h12mr2806216ejs.2.1551781788691; Tue, 05 Mar 2019 02:29:48 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a17:906:9257:: with SMTP id c23ls4113745ejx.2.gmail; Tue, 05 Mar 2019 02:29:48 -0800 (PST) X-Google-Smtp-Source: APXvYqwX9UG39k2zfAtOx5g4zQGODxO+u6/XJFPocLY9nsno6bVmUD+gW9YTyso8/AUJdFbF0ffq X-Received: by 2002:a17:906:350e:: with SMTP id r14mr2812576eja.10.1551781788245; Tue, 05 Mar 2019 02:29:48 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551781788; cv=none; d=google.com; s=arc-20160816; b=cx4rDPdZVOMiFyemF+VNCsYTS+/TrqRaKNO7nLB+Ohk587/fm3LCdqIcQp9KoAMeLS 4fQAzv6oyVKWCjEFZRXAkSiAdBSD/8jjAGvGGQt8ZqNx4VbnZtQILXLcoioeL7Pv1is+ 529KAVJoxhHD94V3bQRRdB1VpQmfoA5LDc4BC7tMnNsC0gyOKhFQU4jJ79DjDyi4KXla 9ZaEvP2Q97Yuqsks7xDDO8CXp+NdVO+Izb/K7z5esF1ApXJFsuKCmYpYVU1HpnVaWxmy 1C11E06CDrP7ZusWS0usbLfhoEZgU1riWCiIieV1uGqmhB22joSjP3deQ2FsfrfLDo6l baeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=7LHvY3bVUWFYgjobB0x6HeEqGoah7pxpCOQSt5YEcNQ=; b=xPpQQgoXXpyA0Zx+VxumqLnupEyGKiLDFwpk2ltls6mrtGOa+rb4dcJhnhmfmoK0Au YN/p7lNhO7Y1ow++uOB85IBx5BJSs3fl1SNeRkCZezglMKujKlHQTH5yrD31i9xWZfH2 BylPP2cen3/5Lfay6aTC4fuP9ZwetW0wGi+OKxC09Vsn9Rpp/A1RsJzomRXhzBCQRzPg Uupu28SipPf90lWiAcGcc+oBagL9AqFSDD6d9AkS8BZf9y94zepOJfqikrXG/CQIslJ/ OyiTqqK59/+o4KlB8qu5E6PsGr+bhRrhuhqCCaXErVygh4gU2kPj+UOS//M5PUYenaWF u48A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id h12si361511edh.4.2019.03.05.02.29.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Mar 2019 02:29:48 -0800 (PST) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x25ATlqB021932 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 5 Mar 2019 11:29:47 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.69.211]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x25ATkUZ007889; Tue, 5 Mar 2019 11:29:46 +0100 Date: Tue, 5 Mar 2019 11:29:46 +0100 From: Henning Schild To: "[ext] Jan Kiszka" Cc: "Maxim Yu. Osipov" , hh h , isar-users Subject: Re: Can isar Debian armhf image size be controlled? Message-ID: <20190305112946.39a939af@md1za8fc.ad001.siemens.net> In-Reply-To: <68538b5b-67dc-0836-5f72-3347399522ce@siemens.com> References: <884bdd75-b3db-430e-b34f-f84f57e98d48@googlegroups.com> <09b5fcd2-caf6-64fb-d310-33ab62eaa18a@ilbers.de> <68538b5b-67dc-0836-5f72-3347399522ce@siemens.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-TUID: od5N+h8s2sDD Am Tue, 5 Mar 2019 07:50:19 +0100 schrieb "[ext] Jan Kiszka" : > On 05.03.19 07:32, Maxim Yu. Osipov wrote: > > Hi, > >=20 > > 1) For reference ISAR armhf target - Terasic DE0-Nano-SoC -=C2=A0 the > > current default isar-image-base rootfs gives > >=20 > >=20 > > isar/build/tmp/work/debian-stretch-armhf/isar-image-base/rootfs$ > > sudo du -sh . 163M=C2=A0=C2=A0=C2=A0 . If you have a closer look with i.e "ncdu" you will find that kernel and modules might require a lot. One way to safe space is using a custom kernel and not use too many modules, also not use an initrd. Other consumers are locales/zoneinfo/docs. These things can be cleaned up i.e. with a postrm script in a transient package. Or a few "rm"s in a do_rootfs_append or a custom task. I just manually removed some files and got down to 65MB (kernel and modules not included). > > The rootfs is already trimmed from /var/cache/apt entries. =20 >=20 > 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. Yes you can even remove apt and other "essential" packages, that would probably be a last resort and give you another 5-7MB. Note that manual removal of files and removing the package manager might significantly decrease the value of the rootfs. Depends on whether you care about updates and how you plan to ship/install them. > 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. True! But in this case we are probably talking about an old device that should receive new firmware. Henning > Jan >=20