From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>,
<isar-users@googlegroups.com>
Subject: Re: Avoid to produce the bmap stuff that double the size
Date: Tue, 4 Oct 2022 08:00:02 +0200 [thread overview]
Message-ID: <cb2c386d-959a-3860-173a-f24c8531819d@siemens.com> (raw)
In-Reply-To: <CAJGKYO5qFY7gcoP3GPvii+nfqFHhwe220vFFwVwRD80yuYmY3g@mail.gmail.com>
On 04.10.22 07:46, Roberto A. Foglietta wrote:
> Hi all,
>
> for small footprint embedded system having a bmap is a must and do not
> overload the drive but when ISAR is used to build 9.3 GB images, then
> the bmap stuff is useless, redundant and takes precious saving space. I
> can remove but I wish not produce it in first place:
>
> $ find build/tmp/deploy/ -name \*wic\*
> build/tmp/deploy/images/debx86/eval-image-debian-bullseye-debx86.wic
> build/tmp/deploy/images/debx86/eval-image-debian-bullseye-debx86.wic.p2
> build/tmp/deploy/images/debx86/eval-image-debian-bullseye-debx86.wic.bmap
> build/tmp/deploy/images/debx86/eval-image-debian-bullseye-debx86.wic.p1
>
I don't think you understood how bmap works and what relates to it. Only
the .bmap file comes from it. And if that is helpful or not depends on
how sparse the image is, not how large. But even with a fully populated
image, bmaptool trumps dd for other reasons.
The listed partition files relate to the discussion in
https://groups.google.com/g/isar-users/c/LtjoygRabns/m/YZsK6S6vCwAJ.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-10-04 6:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 5:46 Roberto A. Foglietta
2022-10-04 6:00 ` Jan Kiszka [this message]
2022-10-05 5:46 ` Roberto A. Foglietta
2022-10-04 6:02 ` Moessbauer, Felix
2022-10-04 6:17 ` Roberto A. Foglietta
2022-10-08 8:28 ` Roberto A. Foglietta
2022-10-08 9:08 ` Roberto A. Foglietta
2022-10-08 9:42 ` Moessbauer, Felix
2022-10-08 9:55 ` Roberto A. Foglietta
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=cb2c386d-959a-3860-173a-f24c8531819d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@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