From: Florin Sarbu <florin.sarbu@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: systemd services in the rootfs
Date: Wed, 13 Feb 2013 17:33:57 +0200 [thread overview]
Message-ID: <511BB265.8030505@windriver.com> (raw)
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?
Thank you,
Florin
next reply other threads:[~2013-02-13 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 15:33 Florin Sarbu [this message]
2013-02-14 8:47 ` systemd services in the rootfs 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
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=511BB265.8030505@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