From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v3 9/9] s6-linux-init: new package
Date: Thu, 16 Mar 2017 22:16:40 +0100 [thread overview]
Message-ID: <20170316211640.GA4981@itchy> (raw)
In-Reply-To: <87shmgyeha.fsf@dell.be.48ers.dk>
Hi!
On 17-03-13 23:54:41, Peter Korsgaard wrote:
> >>>>> "Eric" == Eric Le Bihan <eric.le.bihan.dev@free.fr> writes:
>
> > This new package provides s6-linux-init, a set of minimalistic tools to
> > create a s6-based init system, including a /sbin/init program, on a
> > machine running a Linux kernel.
>
> Hmm, should this then be added as one of the available init options in
> the system menu? Or if not, at least depend on BR2_INIT_NONE to ensure
> no other init system overwrites /sbin/init?
s6-linux-init [1] does not provide a replacement for /sbin/init, but
a tool to generate one FROM the target. So when this package is selected,
there is no risk of messing up target/sbin/init at build time. Hence no
need to make it depend on on BR2_INIT_NONE.
The s6* packages provide the tools to build an init system with service
supervision (as the author states it: "mechanism over policy"). It is up
to the user to glue everything via post-build scripts or a custom
skeleton. A basic example of such a skeleton [2] is available in a
personal Buildroot external customization [3].
Should some comments be added in s6-linux-init/Config.in to clarify
this?
[1] http://skarnet.org/software/s6-linux-init/
[2] https://github.com/elebihan/s6-br2-init-skeleton/
[3] https://github.com/elebihan/br2-ext-skarnet/blob/master/system/Config.in
--
ELB
prev parent reply other threads:[~2017-03-16 21:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 21:29 [Buildroot] [Patch v3 0/9] Introducing service supervision/management with s6 Eric Le Bihan
2016-12-19 21:29 ` [Buildroot] [Patch v3 1/9] skalibs: new package Eric Le Bihan
2017-02-07 10:21 ` Thomas De Schampheleire
2016-12-19 21:29 ` [Buildroot] [Patch v3 2/9] execline: " Eric Le Bihan
2017-03-01 22:54 ` Thomas Petazzoni
2016-12-19 21:29 ` [Buildroot] [Patch v3 3/9] s6: " Eric Le Bihan
2017-03-09 22:08 ` Thomas Petazzoni
2016-12-19 21:29 ` [Buildroot] [Patch v3 4/9] s6-dns: " Eric Le Bihan
2017-03-09 22:08 ` Thomas Petazzoni
2016-12-19 21:29 ` [Buildroot] [Patch v3 5/9] s6-networking: " Eric Le Bihan
2017-03-09 22:17 ` Thomas Petazzoni
2016-12-19 21:29 ` [Buildroot] [Patch v3 6/9] s6-rc: " Eric Le Bihan
2017-03-09 22:33 ` Thomas Petazzoni
2017-03-13 22:34 ` Peter Korsgaard
2017-03-14 12:40 ` Thomas Petazzoni
2016-12-19 21:29 ` [Buildroot] [Patch v3 7/9] s6-portable-utils: " Eric Le Bihan
2017-03-09 22:33 ` Thomas Petazzoni
2016-12-19 21:29 ` [Buildroot] [Patch v3 8/9] s6-linux-utils: " Eric Le Bihan
2017-03-10 21:53 ` Thomas Petazzoni
2016-12-19 21:29 ` [Buildroot] [Patch v3 9/9] s6-linux-init: " Eric Le Bihan
2017-03-10 21:55 ` Thomas Petazzoni
2017-03-13 22:54 ` Peter Korsgaard
2017-03-16 21:16 ` Eric Le Bihan [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=20170316211640.GA4981@itchy \
--to=eric.le.bihan.dev@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