From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH 2/3] targz-img: Handle sparse files efficiently
Date: Mon, 7 Mar 2022 10:43:13 +0100 [thread overview]
Message-ID: <c096bbcc-7ebc-42d7-80ad-8ff1ed0f04b0@siemens.com> (raw)
In-Reply-To: <20220307100202.77e9d11d@md1za8fc.ad001.siemens.net>
On 07.03.22 10:02, Henning Schild wrote:
> Am Sat, 5 Mar 2022 17:34:49 +0100
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
>
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Saves space in case the image contains any sparse files.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> meta/classes/targz-img.bbclass | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/targz-img.bbclass
>> b/meta/classes/targz-img.bbclass index bf94af02..638e7767 100644
>> --- a/meta/classes/targz-img.bbclass
>> +++ b/meta/classes/targz-img.bbclass
>> @@ -7,7 +7,7 @@ TARGZ_IMAGE_FILE =
>> "${DEPLOY_DIR_IMAGE}/${IMAGE_FULLNAME}.tar.gz"
>> do_targz_image() {
>> rm -f ${TARGZ_IMAGE_FILE}
>> - sudo tar -cvzf ${TARGZ_IMAGE_FILE} --one-file-system -C
>> ${IMAGE_ROOTFS} .
>> + sudo tar -cvzSf ${TARGZ_IMAGE_FILE} --one-file-system -C
>> ${IMAGE_ROOTFS} . sudo chown $(id -u):$(id -g) ${TARGZ_IMAGE_FILE}
>
> I assume that can be unpacked with or without -S now, so no interface
> change. right?
>
Yes, see also "man tar".
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-03-07 9:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 16:34 [PATCH 0/3] Sparse tar generation Jan Kiszka
2022-03-05 16:34 ` [PATCH 1/3] sstate: Generate image packages using sparse Jan Kiszka
2022-05-24 19:03 ` Jan Kiszka
2022-03-05 16:34 ` [PATCH 2/3] targz-img: Handle sparse files efficiently Jan Kiszka
2022-03-07 9:02 ` Henning Schild
2022-03-07 9:43 ` Jan Kiszka [this message]
2022-03-05 16:34 ` [PATCH 3/3] vm-img: " Jan Kiszka
2022-03-07 9:04 ` Henning Schild
2022-03-07 9:46 ` Jan Kiszka
2022-03-07 14:09 ` Henning Schild
2022-03-07 14:41 ` Jan Kiszka
2022-03-07 14:53 ` Henning Schild
2022-04-21 16:05 ` [PATCH 0/3] Sparse tar generation Jan Kiszka
2022-04-25 6:04 ` Anton Mikanovich
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=c096bbcc-7ebc-42d7-80ad-8ff1ed0f04b0@siemens.com \
--to=jan.kiszka@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