From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>,
Jan Kiszka <jan.kiszka@siemens.com>, Natalia Tasci <nt@ilbers.de>,
Zhihang Wei <wzh@ilbers.de>
Subject: Re: [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification
Date: Tue, 9 Sep 2025 11:18:47 +0200 [thread overview]
Message-ID: <aL_w98-05IgkmXV5@abai.de> (raw)
In-Reply-To: <70095639-d103-4e7f-8c26-1f79b80efe9c@siemens.com>
On 2025-09-05 17:06, 'Jan Kiszka' via isar-users wrote:
> This was wrong, unfortunately: The original purpose of this whole recipe
> is to generate an initramfs that contains all tools needed to perform
> early filesystem checks. As this information is not available at the
> time we build the rootfs, only after wic ran, I once decided achieve the
> desired effect by recreating the initramfs on first boot.
>
> If anyone has a better idea how to model that more elegantly, I'm all
> ears. Otherwise, we need to revert this and address the boot time issue
> by reducing the number of targets where it is run.
We'll check.
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/aL_w98-05IgkmXV5%40abai.de.
next prev parent reply other threads:[~2025-09-09 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 7:42 [PATCH 0/1] Don't run update-initramfs with enable-fsck Uladzimir Bely
2022-01-21 7:42 ` [PATCH 1/1] enable-fsck: don't run update-initramfs after fstab modification Uladzimir Bely
2025-09-05 15:06 ` 'Jan Kiszka' via isar-users
2025-09-09 9:18 ` Baurzhan Ismagulov [this message]
2022-01-25 6:46 ` [PATCH 0/1] Don't run update-initramfs with enable-fsck Jan Kiszka
2022-02-14 10:18 ` 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=aL_w98-05IgkmXV5@abai.de \
--to=ibr@radix50.net \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=nt@ilbers.de \
--cc=quirin.gylstorff@siemens.com \
--cc=wzh@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