From: Patrick Ohly <patrick.ohly@intel.com>
To: colin.helliwell@ln-systems.com
Cc: 'Yocto discussion list' <yocto@yoctoproject.org>
Subject: Re: Changing over to systemd (no dhcp)
Date: Mon, 23 Jan 2017 10:19:03 +0100 [thread overview]
Message-ID: <1485163143.20333.17.camel@intel.com> (raw)
In-Reply-To: <0aa701d2754c$f26ba1b0$d742e510$@ln-systems.com>
On Mon, 2017-01-23 at 07:47 +0000, colin.helliwell@ln-systems.com wrote:
> Looking at one which does seem to switch over cleanly - dropbear - I'm
> puzzled how the recipe [dropbear.inc, in poky/meta/recipes-core]
> appears to install both init.d script and .service in its do_install,
> yet only one or the other ultimately shows up in the rootfs..?
> (Relates to my other question about how to determine the init type in
> do_install)
systemd.bbclass has a rm_sysvinit_initddir postfunc for do_install which
removes sysvinit config files if the DISTRO_FEATURES enable systemd and
do not enable sysvinit.
rm_systemd_unitdir does the opposite when systemd is disabled and only
sysvinit is enabled.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-01-23 9:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 15:10 Changing over to systemd (no dhcp) colin.helliwell
2017-01-18 17:51 ` Rick Altherr
2017-01-18 21:35 ` Andre McCurdy
2017-01-19 0:21 ` Rick Altherr
2017-01-19 7:21 ` colin.helliwell
2017-01-19 8:31 ` ChenQi
2017-01-19 10:06 ` colin.helliwell
2017-01-20 2:11 ` ChenQi
2017-01-20 13:59 ` colin.helliwell
2017-01-21 13:08 ` Leon Woestenberg
2017-01-23 7:47 ` colin.helliwell
2017-01-23 7:57 ` Mike Looijmans
2017-01-23 9:19 ` Patrick Ohly [this message]
2017-01-23 11:02 ` Mike Looijmans
2017-01-23 11:19 ` Maciej Borzęcki
2017-01-19 7:20 ` Kristian Amlie
2017-01-19 9:18 ` Mike Looijmans
2017-01-20 6:15 ` Michael Gloff
2017-01-20 14:27 ` Mike Looijmans
2017-01-21 12:41 ` Leon Woestenberg
2017-01-23 7:15 ` Mike Looijmans
2017-01-20 6:33 ` Khem Raj
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=1485163143.20333.17.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=colin.helliwell@ln-systems.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.