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: Sat, 8 Oct 2022 11:08:52 +0200 [thread overview]
Message-ID: <CAJGKYO7YfWSx6APDV3_5i4MuGrvy9PH538sUdbbT+uBOCzjS-Q@mail.gmail.com> (raw)
In-Reply-To: <CAJGKYO4fGii7VYBZFHNbG6TSkV6FSkixtsOiLoVmeOXLejQ3JQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
Il giorno sab 8 ott 2022 alle ore 10:28 Roberto A. Foglietta
<roberto.foglietta@gmail.com> ha scritto:
>
> Il giorno mar 4 ott 2022 alle ore 08:02 Moessbauer, Felix
> <felix.moessbauer@siemens.com> ha scritto:
> >
>
> > " [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 😉
> >
>
> Hi Felix,
>
> this is what I found and fits with what was expecting to find:
>
> $ sudo find build -name \*.wic\*
> build/tmp/deploy/images/debx86/eval-image-debian-bullseye-debx86.wic
Is it possible to avoid creating a sstate-cache of the {image or rootfs}?
Mine is over 9GB and its cache is useless. Screenshot 12KB attached.
Thanks, R.
[-- Attachment #2: sstate-cache.png --]
[-- Type: image/png, Size: 11903 bytes --]
next prev parent reply other threads:[~2022-10-08 9:09 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
2022-10-08 8:28 ` Roberto A. Foglietta
2022-10-08 9:08 ` Roberto A. Foglietta [this message]
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=CAJGKYO7YfWSx6APDV3_5i4MuGrvy9PH538sUdbbT+uBOCzjS-Q@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