From: richard.purdie@linuxfoundation.org
To: kai.kang@windriver.com
Cc: poky@yoctoproject.org, peter.kjellerstedt@axis.com,
openembedded-core@lists.openembedded.org
Subject: Re: [meta-poky][PATCH v4 1/3] poky.conf: make systemd as default init manager
Date: Thu, 30 May 2019 12:44:25 +0100 [thread overview]
Message-ID: <39d1e5c522b70d7c6dad4cb37641c0c1ae7cbd41.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190530092232.169453-2-kai.kang@windriver.com>
On Thu, 2019-05-30 at 05:22 -0400, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> Move configurations from local.conf.sample.extended to poky.conf to
> make
> systemd as default init manager for poky. Introduce a new variable
> 'POKY_INIT_MANAGER' whose value should be either 'systemd' or
> 'sysvinit'
> to configure the init manager setting.
>
> For users who still want to use sysvinit, set in local.conf or any
> other
> configure file with:
>
> POKY_INIT_MANAGER = "sysvinit"
>
> [YOCTO #13031]
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta-poky/conf/distro/poky.conf | 10 ++++++++++
> meta-poky/conf/local.conf.sample.extended | 9 ---------
> 2 files changed, 10 insertions(+), 9 deletions(-)
Thanks for working on this patchset, I think its nearly there. I'm
wondering if we should set
POKY_INIT_MANAGER_libc-musl = "sysvinit"
since I am worried about what I read about musl and systemd from a
security perspective.
I'm also wondering what we need to do with the autobuilder init system
tests, I think those may need rewriting to add some sysvinit tests.
Does POKY_INIT_MANAGER = "sysvinit systemd" work for the mode where we
allow old sysvinit scripts for compatibility?
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: richard.purdie@linuxfoundation.org
To: kai.kang@windriver.com
Cc: poky@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [meta-poky][PATCH v4 1/3] poky.conf: make systemd as default init manager
Date: Thu, 30 May 2019 12:44:25 +0100 [thread overview]
Message-ID: <39d1e5c522b70d7c6dad4cb37641c0c1ae7cbd41.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190530092232.169453-2-kai.kang@windriver.com>
On Thu, 2019-05-30 at 05:22 -0400, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> Move configurations from local.conf.sample.extended to poky.conf to
> make
> systemd as default init manager for poky. Introduce a new variable
> 'POKY_INIT_MANAGER' whose value should be either 'systemd' or
> 'sysvinit'
> to configure the init manager setting.
>
> For users who still want to use sysvinit, set in local.conf or any
> other
> configure file with:
>
> POKY_INIT_MANAGER = "sysvinit"
>
> [YOCTO #13031]
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta-poky/conf/distro/poky.conf | 10 ++++++++++
> meta-poky/conf/local.conf.sample.extended | 9 ---------
> 2 files changed, 10 insertions(+), 9 deletions(-)
Thanks for working on this patchset, I think its nearly there. I'm
wondering if we should set
POKY_INIT_MANAGER_libc-musl = "sysvinit"
since I am worried about what I read about musl and systemd from a
security perspective.
I'm also wondering what we need to do with the autobuilder init system
tests, I think those may need rewriting to add some sysvinit tests.
Does POKY_INIT_MANAGER = "sysvinit systemd" work for the mode where we
allow old sysvinit scripts for compatibility?
Cheers,
Richard
next prev parent reply other threads:[~2019-05-30 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 9:22 [meta-poky][PATCH v4 0/3] Make systemd as default init manager and configure wired network kai.kang
2019-05-30 9:22 ` kai.kang
2019-05-30 9:22 ` [meta-poky][PATCH v4 1/3] poky.conf: make systemd as default init manager kai.kang
2019-05-30 9:22 ` kai.kang
2019-05-30 11:44 ` richard.purdie [this message]
2019-05-30 11:44 ` richard.purdie
2019-05-31 2:07 ` Kang Kai
2019-05-31 2:07 ` Kang Kai
2019-05-31 9:00 ` richard.purdie
2019-05-31 9:00 ` richard.purdie
2019-05-31 9:07 ` Kang Kai
2019-05-31 9:07 ` Kang Kai
2019-05-30 9:22 ` [meta-poky][PATCH v4 2/3] poky-tiny.conf: not backfill distro feature systemd kai.kang
2019-05-30 9:22 ` kai.kang
2019-05-30 9:22 ` [meta-poky][PATCH v4 3/3] systemd-conf: configure wired network with dhcp kai.kang
2019-05-30 9:22 ` kai.kang
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=39d1e5c522b70d7c6dad4cb37641c0c1ae7cbd41.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=poky@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.