Re: [OE-core] How to implement systemd
On 02/14/2013 02:42 PM, Mike Looijmans wrote: On 02/14/2013 01:57 PM, Mike Looijmans wrote: On 02/14/2013 01:42 PM, Marcin Juszkiewicz wrote: W dniu 14.02.2013 13:35, Mike Looijmans pisze: So far i've been using good old initscripts for my systems. I want to try out systemd. Having zero experience with that, I just added systemd to the DISTRO_FEATURES and started a fresh build. The build ran fine, but it produced something that still seems to be using initscripts, albeit that a few things stopped working (the network did not start, for example). DISTRO_FEATURES_INITMAN = systemd is what you want. Sorry, I have to amend my original post. DISTRO_FEATURES_INITMAN = systemd is just what I did (added it to my distro .conf file), because from the source I gathered that that was the way to get it into DISTRO_FEATURES. How can I check whether it's using systemd? I don't see any obvious difference in the rootfs, and I never saw any systemd package being built either. Ah, to (probably) answer my own question, there was a hidden VIRTUAL-RUNTIME_init_manager = sysvinit in my config chain, which was probably the cause. Running another build, and I've seen a systemd task being run now... That indeed solved the issue. However, the image doesn't get to a point that I can actually log in or do something useful, so I guess the default is still sysvinit for good reasons :) Here's all the logging I get before it dies: systemd[1]: systemd 197 running in system mode. (-PAM -LIBWRAP -AUDIT -SELINUX +IMA +S YSVINIT -LIBCRYPTSETUP +GCRYPT +ACL +XZ) Welcome to Linux! š���͕��m�]: Cannot add dependency job for unit display-manager.service, ignoring: Uni t display-manager.service failed to load: No such file or directory. See system logs an Expecting device dev-ttyPS0.device.Wall Directory Watch.. [ OK ] Reached target Remote File Systems. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on Delayed Shutdown Socket.ility Named Pipe. [ OK ] Listening on udev Kernel Socket.ests to Console Directory Watch.. [ OK ] Listening on udev Control Socket.t. š���͕��m�]: Set up automount Arbitrary Executable File Formats File System Automount P [ OK ] Reached target Swap. [ OK ] Listening on Journal Socket. Mounting Temporary Directory. Starting Remount Root and Kernel File Systems. Starting Load Kernel Modules.. EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Mounting Debug File System.. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[OE-core] How to implement systemd
So far i've been using good old initscripts for my systems. I want to try out systemd. Having zero experience with that, I just added systemd to the DISTRO_FEATURES and started a fresh build. The build ran fine, but it produced something that still seems to be using initscripts, albeit that a few things stopped working (the network did not start, for example). Is there some openembedded guide on what one has to do to actually use systemd? I've tried google, but because i don't have a clue what keywords to look for, I got only irrelevant results on various Linux distributions while searching with oe-core initscripts to systemd and variations on that theme. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] How to implement systemd
W dniu 14.02.2013 13:35, Mike Looijmans pisze: So far i've been using good old initscripts for my systems. I want to try out systemd. Having zero experience with that, I just added systemd to the DISTRO_FEATURES and started a fresh build. The build ran fine, but it produced something that still seems to be using initscripts, albeit that a few things stopped working (the network did not start, for example). DISTRO_FEATURES_INITMAN = systemd is what you want. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] How to implement systemd
On 02/14/2013 01:42 PM, Marcin Juszkiewicz wrote: W dniu 14.02.2013 13:35, Mike Looijmans pisze: So far i've been using good old initscripts for my systems. I want to try out systemd. Having zero experience with that, I just added systemd to the DISTRO_FEATURES and started a fresh build. The build ran fine, but it produced something that still seems to be using initscripts, albeit that a few things stopped working (the network did not start, for example). DISTRO_FEATURES_INITMAN = systemd is what you want. Sorry, I have to amend my original post. DISTRO_FEATURES_INITMAN = systemd is just what I did (added it to my distro .conf file), because from the source I gathered that that was the way to get it into DISTRO_FEATURES. How can I check whether it's using systemd? I don't see any obvious difference in the rootfs, and I never saw any systemd package being built either. Mike. ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
Re: [OE-core] How to implement systemd
On 02/14/2013 01:57 PM, Mike Looijmans wrote: On 02/14/2013 01:42 PM, Marcin Juszkiewicz wrote: W dniu 14.02.2013 13:35, Mike Looijmans pisze: So far i've been using good old initscripts for my systems. I want to try out systemd. Having zero experience with that, I just added systemd to the DISTRO_FEATURES and started a fresh build. The build ran fine, but it produced something that still seems to be using initscripts, albeit that a few things stopped working (the network did not start, for example). DISTRO_FEATURES_INITMAN = systemd is what you want. Sorry, I have to amend my original post. DISTRO_FEATURES_INITMAN = systemd is just what I did (added it to my distro .conf file), because from the source I gathered that that was the way to get it into DISTRO_FEATURES. How can I check whether it's using systemd? I don't see any obvious difference in the rootfs, and I never saw any systemd package being built either. Ah, to (probably) answer my own question, there was a hidden VIRTUAL-RUNTIME_init_manager = sysvinit in my config chain, which was probably the cause. Running another build, and I've seen a systemd task being run now... ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
