From: "'Andreas Naumann' via isar-users" <isar-users@googlegroups.com>
To: Christoph Steiger <christoph.steiger@siemens.com>,
isar-users@googlegroups.com
Cc: felix.moessbauer@siemens.com, jan.kiszka@siemens.com
Subject: Re: [PATCH v3 1/1] rootfs: rework no-generate-initrd rootfs feature
Date: Thu, 6 Nov 2025 11:00:25 +0100 [thread overview]
Message-ID: <3977cb3e-769b-4557-ad44-858fcba466ac@emlix.com> (raw)
In-Reply-To: <79756434-1c74-434a-9079-883194ddf552@siemens.com>
Am 06.11.25 um 09:59 schrieb Christoph Steiger:
> Hi Andreas,
>
>> I stumbled over this a while ago and was suprised because I didnt see a
>> the change to "is now a default rootfs feature" announced anywhere.
>> Maybe it could be included in this Changelog entry.
> The default behavior remains completely unchanged (or at least that is
> the intention). The initrd was generated per default before, and the
> no-generate-intird feature was missing. Now the generate-initrd
> feature is enabled by default, and we generate the initrd as before.
I havn't looked into why, but since b0913306 (Delay creation of initrd
until end of rootfs install), we had to actively disable the initrd
creation for our images.
Actually now I have had a look: We reused the initramfs class in another
class, which diverted the initrd creation to another implementation.
Moving the do_generate_initramfs() to the rootfs class then had the
effect that we no longer overwrite it.
If this is not an API relevant thing, never mind.
regards,
Andreas
>
> Regards,
> Christoph
>
--
Andreas Naumann
emlix GmbH
Headquarters: Berliner Str. 12, 37073 Goettingen, Germany
Phone +49 (0)551 30664-0, e-mail info@emlix.com
District Court of Goettingen, Registry Number HR B 3160
Managing Directors: Heike Jordan, Dr. Uwe Kracke
VAT ID No. DE 205 198 055
Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
Office Bonn: Bachstr. 6, 53115 Bonn, Germany
http://www.emlix.com
--
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/3977cb3e-769b-4557-ad44-858fcba466ac%40emlix.com.
prev parent reply other threads:[~2025-11-06 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 7:26 'Christoph Steiger' via isar-users
2025-11-06 8:42 ` 'Andreas Naumann' via isar-users
2025-11-06 8:59 ` 'Christoph Steiger' via isar-users
2025-11-06 10:00 ` 'Andreas Naumann' via isar-users [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=3977cb3e-769b-4557-ad44-858fcba466ac@emlix.com \
--to=isar-users@googlegroups.com \
--cc=anaumann@emlix.com \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@siemens.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