From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Uladzimir Bely <ubely@ilbers.de>,
isar-users@googlegroups.com
Subject: Re: [PATCH v4 3/6] isar-bootstrap: Use tar output instead of directory
Date: Tue, 17 Oct 2023 17:05:42 +0300 [thread overview]
Message-ID: <c8431722-27d2-4f27-a8c8-db347593a920@ilbers.de> (raw)
In-Reply-To: <82855302-bd5a-46b8-94ef-77ffbf6b8438@siemens.com>
27/09/2023 13:07, 'Jan Kiszka' via isar-users wrote:
> On 27.09.23 06:33, Uladzimir Bely wrote:
>> From: Anton Mikanovich <amikan@ilbers.de>
>>
>> Do not unpack tar with rootfs content inside bootstrap recipe.
> Motivating this change here would be nice.
>
>> This also requires moving chroot prepare step to the later unpack step.
>>
>> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
>> ---
>> meta/classes/rootfs.bbclass | 11 +++++----
>> .../isar-bootstrap/isar-bootstrap.inc | 23 ++++---------------
>> 2 files changed, 12 insertions(+), 22 deletions(-)
>>
>> diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
>> index 7dec7b36..09d40563 100644
>> --- a/meta/classes/rootfs.bbclass
>> +++ b/meta/classes/rootfs.bbclass
>> @@ -73,12 +73,15 @@ rootfs_do_qemu() {
>> fi
>> }
>>
>> -BOOTSTRAP_SRC = "${DEPLOY_DIR_BOOTSTRAP}/${ROOTFS_DISTRO}-host_${DISTRO}-${DISTRO_ARCH}"
>> -BOOTSTRAP_SRC:${ROOTFS_ARCH} = "${DEPLOY_DIR_BOOTSTRAP}/${ROOTFS_DISTRO}-${ROOTFS_ARCH}"
>> +BOOTSTRAP_SRC = "${DEPLOY_DIR_BOOTSTRAP}/${ROOTFS_DISTRO}-host_${DISTRO}-${DISTRO_ARCH}.tar.zst"
>> +BOOTSTRAP_SRC:${ROOTFS_ARCH} = "${DEPLOY_DIR_BOOTSTRAP}/${ROOTFS_DISTRO}-${ROOTFS_ARCH}.tar.zst"
> zst is really slow on packing but fast on unpacking IIRC. Do we actually
> benefit from that (significantly more unpack than pack)?
>
> Or was it like that before already?
Zstd was chosen because it was already used for sstate.
Packing counts will always be <= unpacks, so it should be ok.
Other feedback will be addressed in v5.
>> rootfs_prepare[weight] = "25"
>> rootfs_prepare(){
>> - sudo cp -Trpfx --reflink=auto '${BOOTSTRAP_SRC}/' '${ROOTFSDIR}'
>> + sudo tar -xf "${BOOTSTRAP_SRC}" -C "${ROOTFSDIR}" --exclude="./dev/console"
>> +
>> + # setup chroot
>> + sudo "${ROOTFSDIR}/chroot-setup.sh" "setup" "${ROOTFSDIR}"
>> }
>>
>> ROOTFS_CONFIGURE_COMMAND += "rootfs_configure_isar_apt"
>> @@ -222,7 +225,7 @@ cache_deb_src() {
>> # Note: ISAR updates the apt state information(apt-get update) only once during bootstrap and
>> # relies on that through out the build. Copy that state information instead of apt-get update
>> # which generates a new state from upstream.
>> - sudo cp -Trpn --reflink=auto "${BOOTSTRAP_SRC}/var/lib/apt/lists/" "${ROOTFSDIR}/var/lib/apt/lists/"
>> + sudo tar -xf "${BOOTSTRAP_SRC}" ./var/lib/apt/lists --one-top-level="${ROOTFSDIR}"
>>
>> deb_dl_dir_import ${ROOTFSDIR} ${ROOTFS_BASE_DISTRO}-${BASE_DISTRO_CODENAME}
>> debsrc_download ${ROOTFSDIR} ${ROOTFS_BASE_DISTRO}-${BASE_DISTRO_CODENAME}
>> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
>> index d8ac9d00..cb1fc91a 100644
>> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
>> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.inc
>> @@ -16,7 +16,6 @@ PV = "1.0"
>> BOOTSTRAP_FOR_HOST ?= "0"
>>
>> DEBOOTSTRAP = "mmdebstrap"
>> -ROOTFSDIR = "${WORKDIR}/rootfs"
>> APTPREFS = "${WORKDIR}/apt-preferences"
>> APTSRCS = "${WORKDIR}/apt-sources"
>> APTSRCS_INIT = "${WORKDIR}/apt-sources-init"
>> @@ -287,9 +286,6 @@ do_bootstrap() {
>> fi
>> E="${@ isar_export_proxies(d)}"
>>
>> - sudo rm -rf --one-file-system "${ROOTFSDIR}"
>> - mkdir -p "${ROOTFSDIR}"
>> -
>> if [ "${ISAR_USE_CACHED_BASE_REPO}" = "1" ]; then
>> base_apt_tmp="$(mktemp -d /tmp/isar-base-aptXXXXXXXXXX)"
>> bootstrap_list="${WORKDIR}/sources.list.d/base-apt.list"
>> @@ -394,18 +390,9 @@ do_bootstrap() {
>> "${WORKDIR}/rootfs.tar.zst" \
>> "$bootstrap_list"
>>
>> - sudo -E -s <<'EOSUDO'
>> - set -e
>> -
>> - tar -xf "${WORKDIR}/rootfs.tar.zst" -C "${ROOTFSDIR}" --exclude="./dev/console"
>> -
>> - # setup chroot
>> - install -v -m755 "${WORKDIR}/chroot-setup.sh" "${ROOTFSDIR}/chroot-setup.sh"
>> - "${ROOTFSDIR}/chroot-setup.sh" "setup" "${ROOTFSDIR}"
>> + # Finalize debootstrap by setting the link in deploy
>> + sudo ln -Tfsr "${WORKDIR}/rootfs.tar.zst" "${DEPLOY_ISAR_BOOTSTRAP}.tar.zst"
>>
>> - # Finalize debootstrap by setting the link in deploy
>> - ln -Tfsr "${ROOTFSDIR}" "${DEPLOY_ISAR_BOOTSTRAP}"
>> -EOSUDO
>> if [ "${ISAR_USE_CACHED_BASE_REPO}" != "1" ]; then
>> deb_dl_dir_export "${WORKDIR}/dl_dir" "${BOOTSTRAP_BASE_DISTRO}-${BASE_DISTRO_CODENAME}"
>> sudo rm -rf --one-file-system "${WORKDIR}/dl_dir"
>> @@ -420,15 +407,15 @@ SSTATEPOSTINSTFUNCS += "bootstrap_sstate_finalize"
>>
>> bootstrap_sstate_prepare() {
>> # this runs in SSTATE_BUILDDIR, which will be deleted automatically
>> - sudo cp -a "$(dirname "${ROOTFSDIR}")/rootfs.tar.zst" ./bootstrap.tar.zst
>> + sudo cp -a "${WORKDIR}/rootfs.tar.zst" ./bootstrap.tar.zst
>> sudo chown $(id -u):$(id -g) bootstrap.tar.zst
>> }
>>
>> bootstrap_sstate_finalize() {
>> # this runs in SSTATE_INSTDIR
>> if [ -f bootstrap.tar.zst ]; then
>> - mv bootstrap.tar.zst "$(dirname "${ROOTFSDIR}")/rootfs.tar.zst"
>> - sudo ln -Tfsr "$(dirname "${ROOTFSDIR}")/rootfs.tar.zst" \
>> + mv bootstrap.tar.zst "${WORKDIR}/rootfs.tar.zst"
>> + sudo ln -Tfsr "${WORKDIR}/rootfs.tar.zst" \
>> "${DEPLOY_ISAR_BOOTSTRAP}.tar.zst"
>> fi
>> }
> Jan
>
next prev parent reply other threads:[~2023-10-17 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 4:33 [PATCH v4 0/6] Migrate to mmdebstrap Uladzimir Bely
2023-09-27 4:33 ` [PATCH v4 1/6] meta: Switch " Uladzimir Bely
2023-09-27 10:02 ` Jan Kiszka
2023-09-27 4:33 ` [PATCH v4 2/6] isar-bootstrap: Move preparations to hooks Uladzimir Bely
2023-09-27 10:05 ` Jan Kiszka
2023-09-27 4:33 ` [PATCH v4 3/6] isar-bootstrap: Use tar output instead of directory Uladzimir Bely
2023-09-27 10:07 ` Jan Kiszka
2023-10-17 14:05 ` Anton Mikanovich [this message]
2023-09-27 4:33 ` [PATCH v4 4/6] user_manual.md: Replace debootstrap with mmdebstrap Uladzimir Bely
2023-09-27 4:33 ` [PATCH v4 5/6] user_manual.md: Update minimal host requirements Uladzimir Bely
2023-09-27 4:33 ` [PATCH v4 6/6] isar-bootstrap: Remove unused code Uladzimir Bely
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=c8431722-27d2-4f27-a8c8-db347593a920@ilbers.de \
--to=amikan@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=ubely@ilbers.de \
/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