I've got an image for a AM3352 system based on Dylan and Arago and I'm trying to switch to systemd for init.
So far I haven't had much luck. First off I'm getting different results depending on where I turn it on. I'm turning it on via the following 2 lines: DISTRO_FEATURES_append = " systemd" VIRTUAL-RUNTIME_init_manager = "systemd" If I place these lines in my_image.bb file I seem to get a partial install of systemd, systemd_udev is there and seems to run but that's about it, there is no systemctrl journalctl and the sysvinit init scripts still seem to be called. If I place these lines in either local.conf or my_distrobution.conf all of the systemd utility seem to get installed and systemd startups up but it's clearly not configured correctly. For starters the systemd dbus isn't getting created and that seems to lead to a whole host of other problems, including journald constant spewing the following error messages: [ 55.926223] systemd-journald[715]: Failed to write entry, ignoring: Argument list too long [ 55.936931] systemd-journald[715]: Failed to rotate /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No such file or directory [ 55.950911] systemd-journald[715]: Failed to write entry, ignoring: Argument list too long [ 55.961580] systemd-journald[715]: Failed to rotate /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No such file or directory [ 55.975568] systemd-journald[715]: Failed to write entry, ignoring: Argument list too long [ 55.986329] systemd-journald[715]: Failed to rotate /run/log/journal/c37feca280b74ec583564afcc2a93f0a/system.journal: No such file or directory I don't know if it matters but this system has no display at all, it's a strictly embedded installation. Can anybody make any suggestions on what might be wrong? Thanks, Matt S. -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
