public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Florin Sarbu <florin.sarbu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: systemd services in the rootfs
Date: Thu, 14 Feb 2013 11:09:54 +0200	[thread overview]
Message-ID: <511CA9E2.70700@windriver.com> (raw)
In-Reply-To: <511CA4B2.1090307@intel.com>

The issue I was referring to was that the individual packages (that 
contain the systemd service files) generated from various recipes, do 
not end up in the rootfs solely by having them declared in the 
SYSTEMD_PACKAGES and having DISTRO_FEATURES_INITMAN ="systemd". You need 
now to explicitly add these ${PN}-systemd (or whatever name you choose 
for the packages that will hold the systemd services) in some 
packagegroups or image recipes to have them in the rootfs. It is not a 
question of where to have them in the rootfs, but rather to have them 
added in the do_rootfs stage.

Hope I cleared things up a little better now.

Thanks,
Florin

On 02/14/2013 10:47 AM, Radu Moisan wrote:
>
> On 02/13/2013 05:33 PM, Florin Sarbu wrote:
>> Hi all,
>> following the transition of the systemd.bbclass from 
>> meta-openembedded to oe-core, I stumbled upon on what seems to me a 
>> missing feature that has not been brought along in the new 
>> systemd.bbclass in oe-core. Seems that if one does not explicitly 
>> specify the inclusion of the packages containing the systemd services 
>> in a packagegroup or image recipe or use some other mechanism that 
>> will determine the addition of these packages in the final rootfs, 
>> then the root filesystem will not contain the systemd services. Even 
>> though DISTRO_FEATURES_INITMAN="systemd" is set. The 
>> meta-openembedded systemd.bbclass, needed no additional adding of the 
>> systemd related packages, just RRECOMMENDED and things worked as 
>> expected. Shouldn't the DISTRO_FEATURES_INITMAN do just that? Is it 
>> something that still needs to be done on the systemd.bbclass or would 
>> you suggest that from now on we will have to manually add the systemd 
>> packages in packagegroups, image recipes etc?
>>
>
> Each recipe should install it's service files in the appropriate 
> location, like ${D}${systemd-unitdir}/system (check out searchpaths in 
> systemd.bbclass)
>
> For reference you can check on my branch enabling patches
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rmoisan/systemd-ross&id=38dfb4ec00aa87ab20065de7b391572f19679ca8 
>
>
> Radu
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2013-02-14  9:26 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 [this message]
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
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=511CA9E2.70700@windriver.com \
    --to=florin.sarbu@windriver.com \
    --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