From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v2 0/2] Significantly speedup image generation
Date: Wed, 14 May 2025 15:47:18 +0200 [thread overview]
Message-ID: <aCSe5qynrpBlH0Yp@abai.de> (raw)
In-Reply-To: <20250423124359.1081781-1-felix.moessbauer@siemens.com>
On 2025-04-23 14:43, 'Felix Moessbauer' via isar-users wrote:
> Especially on non native machines, the image generation can take a long time.
> This is due to the fact that the initrd is generated during the rootfs
> installation. By that, also the initrd is generated multiple times, despite
> only one final version is needed. In case of a out-of-rootfs initrd, it is built
> 5 times (2x in rootfs, 2x in initramfs +1x manually in initramfs).
>
> We optimize this by manually controlling when the initrd is built instead of
> relying on the triggers from the initramfs-tools. As initramfs-tools does
> not provide a conf.d style mechanism to completely disable the generation,
> we now install this package during bootstrap and then stub the update-initramfs
> calls during rootfs installation. In rootfs_postprocess, we restore the
> original update-initramfs calls and build the initrd manually.
Applied to next, thanks.
Capitalized the titles while at it.
With kind regards,
Baurzhan
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/aCSe5qynrpBlH0Yp%40abai.de.
prev parent reply other threads:[~2025-05-14 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 12:43 'Felix Moessbauer' via isar-users
2025-04-23 12:43 ` [PATCH v2 1/2] delay creation of initrd until end of rootfs install 'Felix Moessbauer' via isar-users
2025-04-23 12:43 ` [PATCH v2 2/2] report approximate progress during initrd generation 'Felix Moessbauer' via isar-users
2025-05-14 13:47 ` Baurzhan Ismagulov [this message]
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=aCSe5qynrpBlH0Yp@abai.de \
--to=ibr@radix50.net \
--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