From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>,
"[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>
Cc: isar-users@googlegroups.com, Claudius Heine <ch@denx.de>
Subject: Re: [RFC PATCH 1/1] add minimization image extension
Date: Wed, 29 May 2019 13:29:11 +0200 [thread overview]
Message-ID: <b63513fe-de89-cdeb-20c7-d3dc62bc67a2@siemens.com> (raw)
In-Reply-To: <20190529132215.09f61932@md1za8fc.ad001.siemens.net>
On 29.05.19 13:22, [ext] Henning Schild wrote:
> Hey,
>
> looks good! I once had something similar but much less flexible in a
> transient packages somehwere, uninstalling apt and removing a ton of
> files.
>
> I did use "ncdu" to identify files to look at. And there is
> https://wiki.debian.org/ReduceDebian with some more ideas.
>
> I guess one additional harsh but effective step could be deleting kernel
> modules and rebuilding depmod. And if an initrd is used, rebuild that
> as well.
Well, kernel modules is a topic for custom kernels - if you customize, you don't
need to delete. But deleting initrds is indeed a nice reusable pattern. Most
systems with custom kernels have no need for them anyway.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-05-29 11:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 10:45 [RFC PATCH 0/1] Image minimization 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 [this message]
2019-05-29 10:56 ` [RFC PATCH 0/1] Image minimization Jan Kiszka
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=b63513fe-de89-cdeb-20c7-d3dc62bc67a2@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=henning.schild@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