From: Stefan Eichenberger <eichest@gmail.com>
To: Koen Kooi <koen.kooi@oss.qualcomm.com>
Cc: JPEWhacker@gmail.com, openembedded-core@lists.openembedded.org,
Stefan Eichenberger <stefan.eichenberger@toradex.com>
Subject: Re: [OE-core] [PATCH] systemd: Allow overriding PNI name policies
Date: Tue, 15 Apr 2025 09:21:20 +0200 [thread overview]
Message-ID: <Z_4I8K3RT-3aNpyT@eichest-laptop> (raw)
In-Reply-To: <A1955164-126F-4B34-B796-B2CD3E530AF7@oss.qualcomm.com>
Hi Joshua and Koen,
On Tue, Apr 15, 2025 at 08:56:26AM +0200, Koen Kooi wrote:
>
>
> > Op 14 apr 2025, om 19:03 heeft Joshua Watt via lists.openembedded.org <JPEWhacker=gmail.com@lists.openembedded.org> het volgende geschreven:
> >
> > On Wed, Apr 9, 2025 at 4:15 AM Stefan Eichenberger via
> > lists.openembedded.org <eichest=gmail.com@lists.openembedded.org>
> > wrote:
> >>
> >> From: Stefan Eichenberger <stefan.eichenberger@toradex.com>
> >>
> >> Add two new variables, PNI_NAME_POLICY and PNI_ALTNAMES_POLICY, to allow
> >> overriding the default Predictable Network Interface (PNI) name and
> >> alternative name policies respectively.
> >>
> >> This allows setting different name policies via a .bbappend file if the
> >> defaults are not suitable for a specific use case.
> >
> > 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.
>
> 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 :)
This is the exact same issue we have.
> > You could do the exact same thing by putting your sed command in a
> > do_install:append() function (since you want to set them from a
> > bbappend anyway), and in that case it's irrelevant if pni-names is set
> > in PACKAGECONFIG or not.
>
> I know and I hate it:
>
> https://github.com/qualcomm-linux/meta-qcom-distro/commit/1820fefb6c67506726277f7f789fd5a4538ea33f
>
> It's fragile and noone on the oe-core side will realize that changing do_install() might break DISTROs that use such bbappend. A proper variable like Stefan proposes would be more obvious and less fragile.
>
> Or we could just drop the bit that adds 'mac' and have DISTROs that want that write a bbappend!
I also don't like the sed approach because exactly of what Koen says. I
agree that one of the base problem is that we already modify the policy
and not just use systemds default. If we just remove the "mac" part that
would be good for us as well.
Regards,
Stefan
next prev parent reply other threads:[~2025-04-15 7:21 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 [this message]
2025-05-29 20:03 ` Ross Burton
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=Z_4I8K3RT-3aNpyT@eichest-laptop \
--to=eichest@gmail.com \
--cc=JPEWhacker@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