From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: RE: Avoid to produce the bmap stuff that double the size
Date: Tue, 4 Oct 2022 06:02:49 +0000 [thread overview]
Message-ID: <AM9PR10MB4869A23D2AC88A607F28B33A895A9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAJGKYO5qFY7gcoP3GPvii+nfqFHhwe220vFFwVwRD80yuYmY3g@mail.gmail.com>
> From: isar-users@googlegroups.com <isar-users@googlegroups.com> On Behalf Of Roberto A. Foglietta
> Sent: Tuesday, October 4, 2022 1:46 PM
> To: isar-users@googlegroups.com
> Subject: Avoid to produce the bmap stuff that double the size
>
> 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:
Hi Roberto,
The bmap itself is just a tiny xml file containing the offsets+sizes in the .wic file that contain relevant data.
This is especially important when adding additional free space at the end of a partition.
The large files are the partitions itself (*.p<x>), and these - unfortunately - do not get compressed even if the IMAGE_FSTYPE is set to "wic.xz".
Last week I sent a patch series that also fixes this:
" [PATCH v7 0/6] use xz and gzip on host (outside chroot)"
Please give it a try and if it works, feel free to ack.
Testers are always welcome 😉
P.S. Please send your emails as plain-text, not as HTML.
Best regards,
Felix
>
> $ 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
>
> Thanks, R->
next prev parent reply other threads:[~2022-10-04 6:02 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
2022-10-05 5:46 ` Roberto A. Foglietta
2022-10-04 6:02 ` Moessbauer, Felix [this message]
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=AM9PR10MB4869A23D2AC88A607F28B33A895A9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
--to=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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