All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH] local.conf.sample: Add DISTRO_FEATURES_INITMAN
Date: Wed, 23 Jan 2013 10:12:28 +0200	[thread overview]
Message-ID: <50FF9B6C.4030301@intel.com> (raw)
In-Reply-To: <50FF1B49.5020205@linux.intel.com>


On 01/23/2013 01:05 AM, Darren Hart wrote:
>
> On 01/22/2013 09:01 AM, Richard Purdie wrote:
>> On Tue, 2013-01-22 at 17:29 +0200, Radu Moisan wrote:
>>> Default option is sysvinit
>>>
>>> Signed-off-by: Radu Moisan <radu.moisan@intel.com>
>>> ---
>>>   meta-yocto/conf/local.conf.sample |    3 +++
>>>   1 file changed, 3 insertions(+)
>>>
>>> diff --git a/meta-yocto/conf/local.conf.sample b/meta-yocto/conf/local.conf.sample
>>> index 200b4af..273e0eb 100644
>>> --- a/meta-yocto/conf/local.conf.sample
>>> +++ b/meta-yocto/conf/local.conf.sample
>>> @@ -243,3 +243,6 @@ BB_DISKMON_DIRS = "\
>>>   # track the version of this file when it was generated. This can safely be ignored if
>>>   # this doesn't mean anything to you.
>>>   CONF_VERSION = "1"
>>> +
>>> +# set default init manager: sysvinit or systemd
>>> +DISTRO_FEATURES_INITMAN ?= "sysvinit"
> Is tiny-init also an appropriate value here?

No it is not. We could consider it though.

>
> How does this differ from VIRTUAL_RUNTIME_init_manager?
>

It's just a naming style issue, I used VIRTUAL_RUNTIME_init_manager when 
I started and eventually Richard suggested the new variant.

Radu



  reply	other threads:[~2013-01-23  8:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22 15:29 [PATCH] local.conf.sample: Add DISTRO_FEATURES_INITMAN Radu Moisan
2013-01-22 17:01 ` Richard Purdie
2013-01-22 23:05   ` Darren Hart
2013-01-23  8:12     ` Radu Moisan [this message]
2013-01-23 16:22       ` Darren Hart
2013-01-23 17:01         ` Saul Wold

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=50FF9B6C.4030301@intel.com \
    --to=radu.moisan@intel.com \
    --cc=dvhart@linux.intel.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.