Systemd port on custom embedded linux

Cristian Axenie cristian.axenie at gmail.com
Wed Sep 8 07:44:50 PDT 2010


TIA for the patch. I would like to see this working. Where should the patch
be available?
As for the systemd unit dir in dbus setup it is present and I am now adding
it to udev configuration.

Best !


On Wed, Sep 8, 2010 at 5:32 PM, Gustavo Sverzut Barbieri <
barbieri at profusion.mobi> wrote:

> On Wed, Sep 8, 2010 at 11:25 AM, Cristian Axenie
> <cristian.axenie at gmail.com> wrote:
> > I've managed to add the cgroupfs support and the systems doesn't complain
> > when mounting any filesystem. Due to the fact that I have disabled
> selinux
> > and auditing support I get the following messages :
> >
> > [   18.770000] Freeing init memory: 152K
> > [   19.430000] systemd[1]: systemd 8 running in system mode. (+PAM
> +LIBWRAP
> > -AUDIT -SELINUX)
> > [   19.470000] systemd[1]: /sbin/modprobe failed with error code 1.
>
> probably it's because of missing unix, autofs4 or ipv6 modules (or
> built-in support).
>
> while unix and autofs4 are required, ipv6 should be optional and I'll
> send a patch later today for it. Anyway, if its is ipv6 don't worry as
> it is just informative.
>
>
> > [   19.480000] systemd[1]: No hostname configured.
> > [   19.490000] systemd[1]: Set hostname to <localhost>.
> > [   19.500000] systemd[1]: Netlink failure for request 2: Operation not
> > supported
> > [   19.520000] systemd[1]: Failed to configure loopback device: Operation
> > not supported
>
> these are due ipv6, my patch will fix them as well.
>
>
> > [   19.550000] systemd[1]: Failed to create private D-Bus server:
> Operating
> > system does not support abstract socket namespace
> > [   19.570000] systemd[1]: Failed to allocate manager object:
> Input/output
> > error
> > [   19.590000] systemd-cgroups-agent[672]: Failed to get D-Bus
> connection:
> > Operating system does not support abstract socket namespace
>
> you need udev and dbus with --with-systemdsystemunitdir=/lib/systemd/system
>
>
> > It seems that I have stripped to much of the functionality required for
> > systemd to work when trying to make it lightweight.  Should I reconsider
> > some aspects ? Can you point the vital elements ?
>
> these should make it work. If you don't need sysv init compatibility,
> then check out the patch I've send... at least it will remove some
> stat/open and avoid some checks you don't need.
>
> --
> 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/20100908/8ecafba0/attachment-0001.htm>


More information about the systemd-devel mailing list