From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "Prusty, Badrikesh" <badrikesh.prusty@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "Heinisch, Alexander" <alexander.heinisch@siemens.com>,
"Cetin, Gokhan" <gokhan.cetin@siemens.com>
Subject: Re: [PATCH v3 0/1] image-postproc: ignore systemd preset failures
Date: Fri, 20 Feb 2026 08:20:59 +0000 [thread overview]
Message-ID: <cc816d1921dae6691dd414ea9f48a06c28148fd6.camel@siemens.com> (raw)
In-Reply-To: <64b54a7b-4a10-4621-a090-6f63a987f183@siemens.com>
On Thu, 2026-02-19 at 20:10 +0100, Jan Kiszka wrote:
> On 19.02.26 18:52, Jan Kiszka wrote:
> > On 19.02.26 05:44, 'Badrikesh Prusty' via isar-users wrote:
> > > changes in v3:
> > > * Do not disable pre-population of enabled systemd services during build,
> > > as this is the correct default behavior. Downstream layers can disable
> > > it if needed.
> > > * Ignore failures from systemd preset only.
> > >
> > > changes in v2:
> > > * Disable populate-systemd-preset at build time by default due to service
> > > failures observed on some systems.
> > >
> > > Badrikesh Prusty (1):
> > > image-postproc: ignore systemd preset failures
> > >
> > > meta/classes-recipe/rootfs.bbclass | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> >
> > Is this series aiming at these new warnings of Isar?
> >
> > DEBUG: Executing shell function image_postprocess_disable_systemd_firstboot
> > /proc/ is not mounted. This is not a supported mode of operation. Please fix
> > your invocation environment to mount /proc/ and /sys/ properly. Proceeding anyway.
> > Your mileage may vary.
> > Created symlink '/etc/systemd/system/systemd-firstboot.service' → '/dev/null'.
> > WARNING: Your image is not configured completely according to systemd-firstboot.
> > WARNING: It prompted: ""
> > DEBUG: Shell function image_postprocess_disable_systemd_firstboot finished
> >
>
> Hmm, no. This seems to be another to-do for Felix' rootless patches. I
> was running them, and this warning is gone when going back to vanilla Isar.
Good catch. We need /proc and /sys mounted, which we currently not do
in this task.
Felix
>
> Jan
>
> --
> Siemens AG, Foundational Technologies
> Linux Expert Center
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/cc816d1921dae6691dd414ea9f48a06c28148fd6.camel%40siemens.com.
prev parent reply other threads:[~2026-02-20 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 4:44 'Badrikesh Prusty' via isar-users
2026-02-19 4:44 ` [PATCH v3 1/1] " 'Badrikesh Prusty' via isar-users
2026-02-19 13:36 ` 'MOESSBAUER, Felix' via isar-users
2026-02-19 15:26 ` 'Prusty, Badrikesh' via isar-users
2026-02-19 17:52 ` [PATCH v3 0/1] " 'Jan Kiszka' via isar-users
2026-02-19 19:10 ` 'Jan Kiszka' via isar-users
2026-02-20 8:20 ` 'MOESSBAUER, Felix' 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=cc816d1921dae6691dd414ea9f48a06c28148fd6.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=alexander.heinisch@siemens.com \
--cc=badrikesh.prusty@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=gokhan.cetin@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