[Buildroot] [PATCH 1/1] dbus: fix system_bus_socket location

Adam Duskett aduskett at gmail.com
Fri Feb 9 12:54:29 UTC 2018


Hey Jan;

I am going to reject my own patch.  After more research, it seems like
I was using a very
old setup script that removed a bunch of symlinks from /var and setup
them as actual
folders due to selinux context concerns.

Newer versions of selinux handle these symlinks fine. So in the end,
my setup was broken.

Thanks!

Adam

On Fri, Feb 9, 2018 at 7:28 AM, Jan Kundrát <jan.kundrat at cesnet.cz> wrote:
>> That solution won't work on a rootfs with that is read/write.  My own
>> filing
>> system doesn't have a symlink from /var/run to ./run
>>
>> Perhaps it's just me?
>
>
> Hi Adam, according to both D-Bus and systemd upstreams, having separate /run
> from /var/run is broken. New enough systemd also warns against that.
>
> Just changing the D-Bus socket location won't work. My patch links a
> bugreport where people have mentioned that the /var/run/dbus essentially
> cannot change because it's hard-coded in other SW as well.
>
> Can you investigate which part creates /run and /var/run on your
> configuration of buildroot, but with a fresh-from-scratch build? Grepping
> for "/run" in build/packages-file-list.txt should answer that.
>
> Cheers,
> Jan


More information about the buildroot mailing list