From: Saul Wold <sgw@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/10] Initial systemd integration
Date: Mon, 21 Jan 2013 08:57:32 -0800 [thread overview]
Message-ID: <50FD737C.9030003@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LarPUYHTJBWqi3ze3=aN5+HvizyVvw3V-V+YmxtS4786g@mail.gmail.com>
On 01/21/2013 04:12 AM, Burton, Ross wrote:
> On 21 January 2013 03:30, Ciprian Ciubotariu <cheepeero@gmx.net> wrote:
>> However, with oe-core/meta providing a default embedded policy, higher
>> layers need to remove sysvinit or systemd stuff from base recipes, which is
>> against bitbake's additive language design (only append/prepend functions,
>> no -= operator) and against separating concerns.
>
> If you don't do a systemd build, you won't get any of the systemd
> files. Ditto, sysvinit (well, that's the goal - as it was an
> assumption until now that needs work still).
>
> An oe-core without *any* init system will be very cumbersome - every
> service will need a bbappend to actually work, with the subsequent
> maintenance costs.
>
Ouch, I thought that this was one of the goals of the select your init
system, ie don't use either sysvinit or systemd. Poky-Tiny has a single
file rc.local script to do the initialization of the system.
Sau!
> Ross
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2013-01-21 17:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 22:47 [PATCH 00/10] Initial systemd integration Ross Burton
2013-01-19 22:47 ` [PATCH 01/10] default-distrovars: Add DISTRO_FEATURES_INITMAN to DISTRO_FEATURES Ross Burton
2013-01-23 11:38 ` [PATCH] bitbake.conf: unbreak all builds with custom DISTRO_FEATURES Marcin Juszkiewicz
2013-01-23 11:43 ` Burton, Ross
2013-01-23 11:47 ` Marcin Juszkiewicz
2013-01-19 22:47 ` [PATCH 02/10] default-providers: Automatically set PREFERRED_PROVIDER_udev Ross Burton
2013-01-20 23:12 ` Martin Jansa
2013-01-20 23:15 ` Martin Jansa
2013-01-19 22:47 ` [PATCH 03/10] dbus: respect systemd distro feature Ross Burton
2013-01-19 22:47 ` [PATCH 04/10] systemd: add systemd recipes Ross Burton
2013-01-20 23:11 ` Martin Jansa
2013-01-21 12:07 ` Burton, Ross
2013-01-19 22:47 ` [PATCH 05/10] default-providers: Add systemd option to PREFERRED_PROVIDER_udev Ross Burton
2013-01-19 22:47 ` [PATCH 06/10] packagegroup-core-boot: install systemd-compat-units on systemd images Ross Burton
2013-01-19 22:47 ` [PATCH 07/10] update-rc.d: disable update-rc.d.bbclass when systemd enabled Ross Burton
2013-01-19 22:47 ` [PATCH 08/10] base-files: add fstab for systemd based systems Ross Burton
2013-01-19 22:47 ` [PATCH 09/10] packagegroup-core-boot: only install initscripts if we're using sysvinit Ross Burton
2013-01-19 22:47 ` [PATCH 10/10] libpam: register PAM session with logind Ross Burton
2013-01-20 18:34 ` [PATCH 00/10] Initial systemd integration Saul Wold
2013-01-20 20:21 ` Burton, Ross
2013-01-21 8:59 ` Martin Jansa
2013-01-21 9:21 ` Burton, Ross
2013-01-21 3:57 ` Saul Wold
2013-01-21 8:08 ` Burton, Ross
2013-01-21 8:19 ` Eric Bénard
2013-01-21 8:47 ` Radu Moisan
2013-01-21 10:14 ` Richard Purdie
2013-01-21 12:09 ` Burton, Ross
2013-01-21 12:10 ` Burton, Ross
2013-01-21 3:30 ` Ciprian Ciubotariu
2013-01-21 12:12 ` Burton, Ross
2013-01-21 16:57 ` Saul Wold [this message]
2013-01-21 17:00 ` Burton, Ross
2013-01-22 22:04 ` Ciprian Ciubotariu
2013-01-22 22:29 ` Richard Purdie
2013-01-22 9:30 ` ChenQi
2013-01-22 10:48 ` Radu Moisan
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=50FD737C.9030003@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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