Systemd port on custom embedded linux

Cristian Axenie cristian.axenie at gmail.com
Fri Sep 10 01:14:13 PDT 2010


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[1]: systemd 8 running in system mode. (+PAM +LIBWRAP
-AUDIT -SELINUX +IPV6 -SYSVINIT)
[   19.440000] systemd[1]: /sbin/modprobe failed with error code 1.
[   19.450000] systemd[1]: No hostname configured.
[   19.460000] systemd[1]: Set hostname to <localhost>.
[   19.470000] systemd[1]: Netlink failure for request 2: Operation not
supported
[   19.490000] systemd[1]: Failed to configure loopback device: Operation
not supported
[   19.510000] systemd[1]: Failed to create private D-Bus server: Operating
system does not support abstract socket namespace
[   19.540000] systemd[1]: Failed to allocate manager object: Input/output
error
[   19.560000] systemd-cgroups-agent[672]: Failed to get D-Bus connection:
Operating system does not support abstract socket namespace

Any ideas ?

Best !

On Wed, Sep 8, 2010 at 6:19 PM, Cristian Axenie
<cristian.axenie at gmail.com>wrote:

> The patches aren't applying correctly ! For what version of systemd were
> extracted?
>
> Best !
>
>
> On Wed, Sep 8, 2010 at 5:59 PM, Gustavo Sverzut Barbieri <
> barbieri at profusion.mobi> wrote:
>
>> On Wed, Sep 8, 2010 at 11:44 AM, Cristian Axenie
>> <cristian.axenie at gmail.com> wrote:
>> > TIA for the patch. I would like to see this working. Where should the
>> patch
>> > be available?
>>
>> just sent them to mail list:
>>
>>
>> http://lists.freedesktop.org/archives/systemd-devel/2010-September/000272.html
>>
>> http://lists.freedesktop.org/archives/systemd-devel/2010-September/000273.html
>>
>> while they should not depend on each other, the way build.h is done
>> the patches do depend... or you just apply ipv6 patch and fix the
>> conflict, it is pretty simple.
>>
>>
>> > As for the systemd unit dir in dbus setup it is present and I am now
>> adding
>> > it to udev configuration.
>>
>> yeah, my system did not work properly until i did that.
>>
>>
>>
>> --
>> Gustavo Sverzut Barbieri
>> http://profusion.mobi embedded systems
>> --------------------------------------
>> MSN: barbieri at gmail.com
>> Skype: gsbarbieri
>> Mobile: +55 (19) 9225-2202
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20100910/1d741a3d/attachment.html>


More information about the systemd-devel mailing list