From: Vadim Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 0/3] init: Add s6 as init system
Date: Wed, 16 Jan 2019 23:51:32 +0200 [thread overview]
Message-ID: <20190116215135.32142-1-vadim4j@gmail.com> (raw)
Add new system init support (BR2_INIT_S6) based on s6 suite. This is very-very
basic support which does not have any setup automation logic (but only getty)
but it allows to install custom s6-rc services in a bit easier way by the
board. All s6-rc services which were copied by rootfs-overlay or post-build
will be compiled as s6-rc db into /etc/s6-rc/compiled-initial, which also has
/etc/s6-rc/compiled link to easy replace it in runtime.
In case if such kind of change will be merged, then may be it would be good to
think about of some packages integration into s6-rc system.
Vadim Kochan (3):
package/s6-linux-init: Build also for the host
package/s6-linux-init: Allow to install as init system
package/s6-rc: Allow to integrate s6-rc services
package/s6-linux-init/s6-linux-init.mk | 69 +++++++++++++++++++++++++++++++++-
package/s6-rc/rc.init | 4 ++
package/s6-rc/rc.shutdown | 3 ++
package/s6-rc/s6-rc.mk | 32 ++++++++++++++++
system/Config.in | 9 ++++-
5 files changed, 114 insertions(+), 3 deletions(-)
create mode 100644 package/s6-rc/rc.init
create mode 100644 package/s6-rc/rc.shutdown
--
2.14.1
next reply other threads:[~2019-01-16 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 21:51 Vadim Kochan [this message]
2019-01-16 21:51 ` [Buildroot] [RFC 1/3] package/s6-linux-init: Build also for the host Vadim Kochan
2019-01-16 21:51 ` [Buildroot] [RFC 2/3] package/s6-linux-init: Allow to install as init system Vadim Kochan
2019-01-16 21:51 ` [Buildroot] [RFC 3/3] package/s6-rc: Allow to integrate s6-rc services Vadim Kochan
2019-01-20 15:31 ` [Buildroot] [RFC 0/3] init: Add s6 as init system Eric Le Bihan
2019-01-30 20:50 ` Thomas De Schampheleire
2019-02-08 12:20 ` Vadym Kochan
2019-02-11 21:40 ` Eric Le Bihan
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=20190116215135.32142-1-vadim4j@gmail.com \
--to=vadim4j@gmail.com \
--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