From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.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 08:17:52 +0200 [thread overview]
Message-ID: <CAJGKYO5YPbZiTin-rzbmO3edd4RZ9QO55o4G6VH7-8VmaZHENQ@mail.gmail.com> (raw)
In-Reply-To: <AM9PR10MB4869A23D2AC88A607F28B33A895A9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM>
Il giorno mar 4 ott 2022 alle ore 08:02 Moessbauer, Felix
<felix.moessbauer@siemens.com> ha scritto:
>
> > 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
>
> 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
Thanks Felix, you got the point. I will give it a try at that patch.
Best, R-
P.S.: finally I found how to send text only e-mail from my google account. :-)
next prev parent reply other threads:[~2022-10-04 6:18 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
2022-10-04 6:17 ` Roberto A. Foglietta [this message]
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=CAJGKYO5YPbZiTin-rzbmO3edd4RZ9QO55o4G6VH7-8VmaZHENQ@mail.gmail.com \
--to=roberto.foglietta@gmail.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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