From: Alex Suykov <alex.suykov@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] SysV init script revamp (proposal)
Date: Sat, 7 Mar 2015 11:27:37 +0200 [thread overview]
Message-ID: <20150307092737.GA28097@vostro> (raw)
In-Reply-To: <54FA0173.60504@zacarias.com.ar>
Fri, Mar 06, 2015 at 04:35:15PM -0300, Gustavo Zacarias wrote:
> Before going all crazy sending patches and possibly wasting a lot of
> time i'll write up my thoughts on how we could enhance/fix/clean the
> current scenario regarding initscript:
A word of support, it's a mess at present.
And since I was doing something related I'll post it here too.
My goal was to merge initscripts, systemd, scriptless sysv and my own init,
with focus mostly on foreground daemons.
The result, however, seems to be pretty close to your proposal,
with uniform (generated, in fact) initscripts, and possibly also
uniform pid file handling.
https://github.com/arsv/br
long(ish) description of ideas behind this:
https://raw.githubusercontent.com/arsv/br/master/brinits
Sysv-style configuration is missing atm, the plan was
to pick any variables from .run files (see netsnmp/snmpd.run)
and write them to relevant /etc/config.d/*.conf files.
The limiting factor is that any non-trivial variable handling,
basically any conditions, are not going to work well with systemd
(example: package/tvheadend/S99tvheadend).
And I feel better about residing to simple ARGS=... vs dropping
systemd just because of this.
next prev parent reply other threads:[~2015-03-07 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 19:35 [Buildroot] SysV init script revamp (proposal) Gustavo Zacarias
2015-03-07 9:27 ` Alex Suykov [this message]
2015-03-09 15:19 ` Mike Williams
2015-03-09 23:17 ` 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=20150307092737.GA28097@vostro \
--to=alex.suykov@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