Systemd port on custom embedded linux
tomek at pipebreaker.pl
Fri Sep 10 01:39:47 PDT 2010
On Fri, Sep 10, 2010 at 11:14:13AM +0300, Cristian Axenie wrote:
> Hi, again !
> I've managed to apply the patches and fixed all conflicts, modified DBus and
> Udev and the problem persists regarding the abstract socket namespace.
> Mainly I think there is a DBus problem.
> Here's my boot output :
> [ 18.750000] Freeing init memory: 152K
> [ 19.400000] systemd: systemd 8 running in system mode. (+PAM +LIBWRAP
> -AUDIT -SELINUX +IPV6 -SYSVINIT)
> [ 19.440000] systemd: /sbin/modprobe failed with error code 1.
> [ 19.450000] systemd: No hostname configured.
> [ 19.460000] systemd: Set hostname to <localhost>.
> [ 19.470000] systemd: Netlink failure for request 2: Operation not
> [ 19.490000] systemd: Failed to configure loopback device: Operation
> not supported
> [ 19.510000] systemd: Failed to create private D-Bus server: Operating
> system does not support abstract socket namespace
> [ 19.540000] systemd: Failed to allocate manager object: Input/output
> [ 19.560000] systemd-cgroups-agent: Failed to get D-Bus connection:
> Operating system does not support abstract socket namespace
> Any ideas ?
Being this embedded system, I guess that you are cross-compiling all the
software? If so, have you noticed following messages in D-Bus configure:
WARNING: Cannot check for abstract sockets when cross-compiling, please use --enable-abstract-sockets
So I believe you need to recompile d-bus with --enable-abstract-sockets appended
to ./configure line.
Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking
xmpp: zdzichubg at chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML)
More information about the systemd-devel