From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/openrc: new init package OpenRC (0.38.3)
Date: Wed, 6 Mar 2019 19:12:21 +0100 [thread overview]
Message-ID: <20190306181221.GS2721@scaer> (raw)
In-Reply-To: <20190306173639.GR2721@scaer>
Micha?, Arnout, All,
On 2019-03-06 18:36 +0100, Yann E. MORIN spake thusly:
> Maybe we're taking the problem in the wrong way, then?
And actually, I think we are. As per [0]:
Since 0.25 OpenRC includes openrc-init, which can replace /sbin/init
Also, the 0.25 release notes contain:
This version contains an OpenRC-specific implementation of init for
Linux which can be used in place of sysvinit or any other init process.
I checked, and it looks like this is still the case in OpenRC's master
branch.
So, I believe we should aim for this solution, because it drastically
simplifies things.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-03-06 18:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 19:44 [Buildroot] [PATCH] package/openrc: new init package OpenRC (0.38.3) Michał Łyszczek
2019-03-04 18:59 ` Arnout Vandecappelle
2019-03-05 21:38 ` Yann E. MORIN
2019-03-05 23:20 ` michal.lyszczek at bofc.pl
2019-03-06 9:58 ` Arnout Vandecappelle
2019-03-06 17:36 ` Yann E. MORIN
2019-03-06 18:12 ` Yann E. MORIN [this message]
2019-03-06 19:47 ` Yann E. MORIN
2019-03-07 8:53 ` michal.lyszczek at bofc.pl
2019-03-07 9:58 ` Arnout Vandecappelle
2019-03-07 8:36 ` michal.lyszczek at bofc.pl
2019-03-07 9:36 ` Arnout Vandecappelle
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=20190306181221.GS2721@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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