From: Adrian Bunk <bunk@stusta.de>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Conflict of systemd and sysvinit
Date: Tue, 27 Aug 2019 21:23:17 +0300 [thread overview]
Message-ID: <20190827182317.GB29638@localhost> (raw)
In-Reply-To: <3e6e1e23-ead9-7982-0bc1-49639638a216@windriver.com>
On Mon, Aug 19, 2019 at 12:22:30PM -0500, Mark Hatle wrote:
> On 8/19/19 11:49 AM, Otavio Salvador wrote:
> > On Mon, Aug 19, 2019 at 1:48 PM Mark Hatle <mark.hatle@windriver.com> wrote:
> >> On 8/19/19 11:27 AM, Ross Burton wrote:
> >>> On 19/08/2019 11:37, Otavio Salvador wrote:
> >>>> On Sun, Aug 18, 2019 at 11:00 PM Kang Kai <Kai.Kang@windriver.com> wrote:
> >>>>> On 2019/8/18 上午3:27, Otavio Salvador wrote:
> >>>>> Would you like to give more detailed steps how the error occurred? And
> >>>>> what's extra settings in you local.conf please?
> >>>>
> >>>> I had sysvinit and systemd enabled.
> >>>
> >>> The autobuilder should be exercising this, so when it's fixed we need to
> >>> ensure the AB covers the case Otavio is hitting.
> >>
> >> If they are both enabled what is the expected functionality of the system?
> >> (which is init, etc...)
> >
> > The image needs to pick the desired ones.
>
> Ok.. so build both packages.. and then come install time, one or the other must
> be in the PACKAGE_INSTALL (however the image chooses to do this), and the other
> should NOT be included.
>
> This could be problematic, as I've seen recipes build with systemd dependencies
> in them. (Both initscripts as well as system health monitoring and such.. That
> would conflict with a sysvinit [or systemd] if configured for the other.)
> Someone may need to review dependencies in the system looking for things that
> depend on systemd... or have a systemd/sysvinit 'conflict' of some kind. (I've
> not attempted such an audit before.)
>...
Dependencies on libsystemd are not a problem in sysvinit systems,
assuming there is proper runtime fallback code.
Shipping both an init script and a systemd unit file is also not a problem.
In Debian you can just switch the init system and reboot and it works,
with all the other binary packages unchanged.
> --Mark
cu
Adrian
BTW: There are problems like how to make GNOME happy without systemd,
and there is a lack of people in Debian working actively on the
sysvinit side. But on a high level the problems you were worried
about are "works in Debian".
prev parent reply other threads:[~2019-08-27 18:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-17 19:27 Conflict of systemd and sysvinit Otavio Salvador
2019-08-19 1:59 ` Kang Kai
2019-08-19 10:37 ` Otavio Salvador
2019-08-19 16:27 ` Ross Burton
2019-08-19 16:47 ` Mark Hatle
2019-08-19 16:49 ` Otavio Salvador
2019-08-19 17:22 ` Mark Hatle
2019-08-27 18:23 ` Adrian Bunk [this message]
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=20190827182317.GB29638@localhost \
--to=bunk@stusta.de \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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.