public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: Joshua Watt <JPEWhacker@gmail.com>,
	"koen.kooi@oss.qualcomm.com" <koen.kooi@oss.qualcomm.com>,
	"eichest@gmail.com" <eichest@gmail.com>,
	Stefan Eichenberger <stefan.eichenberger@toradex.com>
Subject: Re: [OE-core] [PATCH] systemd: Allow overriding PNI name policies
Date: Thu, 29 May 2025 20:03:49 +0000	[thread overview]
Message-ID: <930EFAE5-0AC3-4458-BA40-898F7759FB23@arm.com> (raw)
In-Reply-To: <A1955164-126F-4B34-B796-B2CD3E530AF7@oss.qualcomm.com>

On 15 Apr 2025, at 07:56, Koen Kooi via lists.openembedded.org <koen.kooi=oss.qualcomm.com@lists.openembedded.org> wrote:
> 
> > It's very difficult to configured systemd in a way that is acceptable
> > to everyone, and I'm not sure adding variable "knobs" for every
> > possible configuration option is feasible for systemd.

My 2c is that I agree with Josh.

I think that we need some helper classes to make it simple to configure systemd at a higher level in a separate recipe, by dropping in configuration fragments and links as needed. This separate recipe could be machine-specific, unlike the systemd recipe itself.  We could then remove the PNI logic from systemd itself (and any other half-attempts at configuration too).

> For me, the issue is that OE-core adds the MAC naming feature that upstream has disabled by default, which gives me unpredictable names for various on-SoC network interfaces[1]. Having a way, supported by OE-core, to disable the addition that results in predictable names not being predictable would be great. It would make PNI function as intended :)

Amusingly, the mac naming was added for some SoCs that don’t have anything else (oe-core 4a7b42fc and 37bd8e8d).  It’s almost like this is a machine-specific configuration that shouldn’t be part of the core systemd recipe at all…

I’m more than half tempted to revert the bulk of the PNI policy patches (leaving just the on/off toggle, without altering the behaviour otherwise), and if someone wants to override them on a per-machine basis then they can, using a per-machine recipe that writes a drop file to /usr/lib/systemd/network/99-default.link.d/pni.conf. 

Ross

      parent reply	other threads:[~2025-05-29 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09 10:15 [PATCH] systemd: Allow overriding PNI name policies Stefan Eichenberger
2025-04-10  7:34 ` [OE-core] " Koen Kooi
2025-04-14 17:03 ` Joshua Watt
2025-04-15  6:56   ` Koen Kooi
2025-04-15  7:21     ` Stefan Eichenberger
2025-05-29 20:03     ` Ross Burton [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=930EFAE5-0AC3-4458-BA40-898F7759FB23@arm.com \
    --to=ross.burton@arm.com \
    --cc=JPEWhacker@gmail.com \
    --cc=eichest@gmail.com \
    --cc=koen.kooi@oss.qualcomm.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stefan.eichenberger@toradex.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