From: Mike Looijmans <mike.looijmans@topic.nl>
To: openembedded-core@lists.openembedded.org
Subject: Re: How to "implement" systemd
Date: Thu, 14 Feb 2013 14:42:17 +0100 [thread overview]
Message-ID: <511CE9B9.2010405@topic.nl> (raw)
In-Reply-To: <511CDF1D.2060805@topic.nl>
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...
next prev parent reply other threads:[~2013-02-14 13:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 15:33 systemd services in the rootfs Florin Sarbu
2013-02-14 8:47 ` Radu Moisan
2013-02-14 9:09 ` Florin Sarbu
2013-02-14 10:17 ` Burton, Ross
2013-02-14 12:32 ` Florin Sarbu
2013-02-14 15:30 ` Burton, Ross
2013-02-14 12:35 ` How to "implement" systemd Mike Looijmans
2013-02-14 12:42 ` Marcin Juszkiewicz
2013-02-14 12:57 ` Mike Looijmans
2013-02-14 13:42 ` Mike Looijmans [this message]
2013-02-15 8:38 ` Mike Looijmans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=511CE9B9.2010405@topic.nl \
--to=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox