From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [RFC PATCH 0/1] Image minimization
Date: Wed, 29 May 2019 12:56:56 +0200 [thread overview]
Message-ID: <af5d1212-7050-f4db-1445-abf4cf39075d@siemens.com> (raw)
In-Reply-To: <20190529104506.10508-1-claudius.heine.ext@siemens.com>
On 29.05.19 12:45, [ext] claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> Hi,
>
> here is a RFC patch that adds a minimization extensions to images.
>
> The basic idea behind this is that it allows to remove specific packages and
> files from the root file system in a post-processing step. This is useful in
> case there are tight storage space restrictions. It breaks the package
> management in multiple different ways and degrees, but the main idea is to
> reduce the root file system to a minimal set of files that are necessary for the
> device to still perform its function.
>
> I envision the `IMAGE_MINIMIZATION_FEATURES`, `IMAGE_MINIMIZATION_PACKAGES` and
> `IMAGE_MINIMIZATION_FILES` to be the user facing interface for this.
>
> While removing packages, I use the dpkg from the buildchroot in order to be
> independent from the tools on the image. This also allows to remove dpkg while
> still being able to use it.
>
> I would like to hear some input about the general design, before I start
> cleaning that up and testing it more intensively.
Looks reasonable from the interface POV. So, users would normally only juggle
with our predefined minimizations features and, thus,
IMAGE_MINIMIZATION_FEATURES. Only very few cases would then require stepping one
level down and fiddle directly with package lists or even individual files.
Would likely make this reasonably convenient.
I would suggest adding a tiny demo image as well, something that only gives you
a shell prompt or so.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2019-05-29 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 10:45 claudius.heine.ext
2019-05-29 10:45 ` [RFC PATCH 1/1] add minimization image extension claudius.heine.ext
2019-05-29 11:22 ` Henning Schild
2019-05-29 11:28 ` Henning Schild
2019-05-29 11:29 ` Jan Kiszka
2019-05-29 10:56 ` Jan Kiszka [this message]
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=af5d1212-7050-f4db-1445-abf4cf39075d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.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