From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: rs@ti.com, ross.burton@arm.com, mathieu.dubois-briand@bootlin.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] systemd: fix unmerged-bin tainted message
Date: Wed, 08 Apr 2026 22:58:04 +0100 [thread overview]
Message-ID: <ed0e1e8c378031b3ef0155e0afb3f75feacac243.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260408195024.1874335-2-rs@ti.com>
On Wed, 2026-04-08 at 14:50 -0500, Randolph Sapp via lists.openembedded.org wrote:
> From: Randolph Sapp <rs@ti.com>
>
> Systemd prefers both /bin and /sbin to link to /usr/bin. If this is not
> the case it reports that the system is tainted in systemctl status.
>
> Add a link from /usr/sbin to /usr/bin to prevent anything from being
> excluded from the merged bin directory. This mimics the current merged
> bin directory structure of Arch Linux [1].
>
> Update the systemd recipe to prevent creating a duplicate link when
> sbinmerge is enabled.
>
> This check was added to systemd back in 2024 [2].
>
> [1] https://gitlab.archlinux.org/archlinux/packaging/packages/filesystem/-/blob/main/PKGBUILD
> [2] https://github.com/systemd/systemd/commit/844863c61e7b501097da84a1e4d1e4a6aa6d9f0d
>
> Signed-off-by: Randolph Sapp <rs@ti.com>
> ---
>
> I feel like this is overloading the "usrmerge" distro feature somewhat. On the
> other hand, this parameter was added for systemd support, and systemd considers
> all of this to result in an unmerged-bin warning. I figure it's kind of fine.
>
> Open to opinions here, as we could also just add a "sbinmerge" distro feature.
> Then again, what would be the expected behavior when usrmerge is disabled? Would
> /usr/sbin just point to /usr/bin and /sbin to /bin then?
These are good questions. It feels like systemd is basically dictating
how the system should be laid out at this point and we may as well put
all this on the systemd distro feature as it is getting to the point
you can't use it without doing that :/.
It feels a bit like we should drop usrmerge too and just use systemd
there too since it doesn't have any seperate policy, it is just "do
what systemd says".
Cheers,
Richard
next prev parent reply other threads:[~2026-04-08 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 19:50 [oe-core][PATCH] systemd: fix unmerged-bin tainted message rs
2026-04-08 21:58 ` Richard Purdie [this message]
2026-04-09 4:30 ` Jörg Sommer
2026-04-09 7:49 ` Peter Kjellerstedt
2026-04-09 18:18 ` Randolph Sapp
[not found] ` <18A4C3228BFBCFA6.777565@lists.openembedded.org>
2026-04-09 18:43 ` Randolph Sapp
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=ed0e1e8c378031b3ef0155e0afb3f75feacac243.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=rs@ti.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