From: "'Heinisch, Alexander' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Subject: Re: [PATCH v3 0/2] Enable systemd units based on systemd presets
Date: Tue, 21 Oct 2025 11:21:10 +0000 [thread overview]
Message-ID: <d79451250668d72535e7869e175878aff890eb14.camel@siemens.com> (raw)
In-Reply-To: <20250917103506.295010-1-alexander.heinisch@siemens.com>
Any updates on this patchset? Seems it got lost.
BR Alexander
On Wed, 2025-09-17 at 12:35 +0200, alexander.heinisch@siemens.com
wrote:
> From: Alexander Heinisch <alexander.heinisch@siemens.com>
>
> By default population of the presets is automatically done by systemd
> on first-boot.
>
> There were several issues with that:
>
> 1. The rootfs we get as a build artifact does not reflect the actual
> system running in the field.
>
> 2. For setups without writeable /etc this fails. With that addition
> it happens already at build time.
>
> Note: Additional services are enabled only. Services already enabled
> during the package installation won't be changed.
>
> Opt-out: `ROOTFS_FEATURES:remove = "populate-systemd-preset"`
>
> Changes since v2:
> - Enable postprocessing to populate systemd presets via
> ROOTFS_FEATURES
>
> Alexander Heinisch (2):
> Minor cleanup: Refactor ROOTFS_FEATURES assignment for image to
> make
> upcoming changes more easily trackable.
> classes/image-postproc: Enable systemd units based on systemd
> presets
>
> RECIPE-API-CHANGELOG.md | 18 ++++++++++++++++++
> meta/classes/image.bbclass | 10 +++++++++-
> meta/classes/rootfs.bbclass | 6 ++++++
> 3 files changed, 33 insertions(+), 1 deletion(-)
>
> --
> 2.39.5
>
--
Alexander Heinisch
Siemens AG
www.siemens.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/d79451250668d72535e7869e175878aff890eb14.camel%40siemens.com.
next prev parent reply other threads:[~2025-10-21 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 10:35 alexander.heinisch via isar-users
2025-09-17 10:35 ` [PATCH v3 1/2] Minor cleanup: Refactor ROOTFS_FEATURES assignment for image to make upcoming changes more easily trackable alexander.heinisch via isar-users
2025-09-17 10:35 ` [PATCH v3 2/2] classes/image-postproc: Enable systemd units based on systemd presets alexander.heinisch via isar-users
2025-10-21 11:21 ` 'Heinisch, Alexander' via isar-users [this message]
2025-10-21 16:07 ` [PATCH v3 0/2] " 'cedric.hombourger@siemens.com' via isar-users
2025-10-30 11:33 ` 'Heinisch, Alexander' via isar-users
2025-10-23 9:29 ` Zhihang Wei
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=d79451250668d72535e7869e175878aff890eb14.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@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