public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: "Chen, Qi" <Qi.Chen@windriver.com>,
	 "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "mns@gomspace.com" <mns@gomspace.com>
Subject: Re: [OE-core][PATCH] systemd: add osc-context PACKAGECONFIG
Date: Wed, 22 Apr 2026 10:43:58 +0100	[thread overview]
Message-ID: <d8f2d6b47fe28deff165d852a9b5d732abfa283f.camel@pbarker.dev> (raw)
In-Reply-To: <PH0PR11MB5611699DC4504F7E5A489A71ED232@PH0PR11MB5611.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]

On Thu, 2026-04-16 at 03:41 +0000, Chen, Qi wrote:
> Hi Paul,
> 
> The purpose of this patch is to give vendors/distributions an easy way to disable installing the file.
> Distributions can put something like PACKAGECONFIG:remove:pn-systemd = "osc-context" in their distro conf file.
> 
> We have looked into this problem so we know what's going on and how to handle it. But how do we convey this information properly to users.
> Users get this messy output from console and they have negative impression about your product before they go to any doc.
> 
> I like systemd pioneering things, but for the current status, I guess most embedded systems will not benefit from this PS0 setting.
> The net effect will be relatively negative. Users get messy output from console in some case. They get it every time they type a command or just the "Enter" key. And they get annoyed.
> I got this feedback from two very experienced BSP developers, separately.
> 
> So could you please give this patch a second thought? I also think disabling this PACKAGECONFIG for oe-core is a more reasonable default. What do you think?

Hi Qi,

Thanks for the additional info.

I don't really like this approach, I'd prefer a "proper" fix in systemd
and/or inittab, but that isn't likely to happen quickly. So as a
compromise, yes, we should take this patch for now.

Best regards,

-- 
Paul Barker


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2026-04-22  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15  8:29 [OE-core][PATCH] systemd: add osc-context PACKAGECONFIG Qi.Chen
2026-04-15  9:35 ` Paul Barker
2026-04-16  3:41   ` Chen, Qi
2026-04-22  9:43     ` Paul Barker [this message]
2026-04-24  5:05       ` [PATCH] " Martin Siegumfeldt

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=d8f2d6b47fe28deff165d852a9b5d732abfa283f.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=Qi.Chen@windriver.com \
    --cc=mns@gomspace.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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