From: heroxbd@gmail.com
To: gentoo-soc@lists.gentoo.org
Cc: openrc@gentoo.org, rleigh@debian.org, rra@debian.org
Subject: [gentoo-soc] [report 6.18-6.24] Daemons in Gentoo Prefix with OpenRC (extended to improving to OpenRC)
Date: Wed, 27 Jun 2012 08:25:44 +0900 [thread overview]
Message-ID: <86y5n98xl3.fsf_-_@gmail.com> (raw)
In-Reply-To: <86395po8sc.fsf_-_@gentoo.org> (heroxbd@gmail.com's message of "Thu, 21 Jun 2012 08:36:35 +0900")
Hey guys and gals,
reports for the scheduled in the last week:
ON-GOING 1. kill bugs for openrc
https://bugs.gentoo.org/buglist.cgi?quicksearch=openrc&list_id=1113873
ON-GOING 1.1 bug 413267
reproduced on my box, investigating the built in "single"
runlevel.
TODO 1.2 bug 409829
ON-GOING 2. evaluate other rc systems (in order)
DONE 2.0 smf (Openindiana)
2.0.1 updated in
https://wiki.gentoo.org/wiki/OpenRC
later mgorny created a page for general comparison,
http://wiki.gentoo.org/wiki/Comparison_of_init_systems
Further evaluations will go to the new page. Old page needs
to be cleaned up.
TODO 2.1 launchd (Mac OS X)
ON-GOING 2.2 upstart (Ubuntu)
as well as trying Gentoo Prefix on top of it (there has
been a big block for Prefix on Ubuntu, cf. bug
400839). and chaining openrc from upstart.
EXTRA NOTE 3. found another thread for introducing OpenRC to
debian[1]
3.1 in the reply by rra@debian[2], there are really what we are
missing in openrc (ecosystem).
3.2 rleigh@debian seems to represent the thinking of debian
community towards init system[3]: they don't like systemd
way of integrating everything. But they really need some
event-driven mechanism, which is not well defined by OpenRC
(yet).
3.3 talked with rleigh via irc, conveying (as patrick did) we are
eager to take ideas from debian, and impove OpenRC to suite
debian's need provided it's of general interest. And I am
eager to put my effort to carry ideas into reality.
3.4 discussed with patrick in #openrc considering the thread, and
agreed upon that we can extend OpenRC with some simple
helper scripts (event-driven, crash restart/statistics,
dbus-like API for triggers from outside) and kernel specific
hooks on top of the present OpenRC core. Changing OpenRC
itself to make a fancy feature (or fanboy's paradigm) is not
good practice.
In the next step, to improve OpenRC with recent ideas of init system, I
am thinking of packaging OpenRC in debian and let it work out of box
(maybe the LSB thing is the major block instead) as a practical measure
of the usefulness of new features I would have introduced. (I myself is
an old debian user for 8 years, therefore motivated to do so).
rleigh and rra, could you please be my mentor for the packaging?
Schedules for 6.25-7.1
======================
1. evaluating launchd, and finish upstart
2. the openrc single/reboot built runlevel switching bug
3. try to have a piece of script to prove my concept for using
openrc as a "event-driven" init system. try to work with
rleigh@debian (rra@debian), as they know what are really
needed. and synchronize with openrc herd.
Cheers,
Benda
1. http://thread.gmane.org/gmane.linux.debian.devel.general/171695
2. http://article.gmane.org/gmane.linux.debian.devel.general/171786
3. http://article.gmane.org/gmane.linux.debian.devel.general/171897
next prev parent reply other threads:[~2012-06-27 0:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 4:05 [gentoo-soc] [report 6.3-6.10] Daemons in Gentoo Prefix with OpenRC heroxbd
2012-06-11 17:05 ` Luca Barbato
2012-06-20 23:36 ` [gentoo-soc] [report 6.11-6.17] " heroxbd
2012-06-21 4:55 ` Luca Barbato
2012-06-21 7:13 ` heroxbd
2012-06-21 7:50 ` Luca Barbato
2012-06-26 23:25 ` heroxbd [this message]
2012-07-04 15:31 ` [gentoo-soc] [report 6.25-7.4] Daemons in Gentoo Prefix with OpenRC (extended to improving to OpenRC) heroxbd
2012-07-04 16:34 ` Luca Barbato
2012-07-05 12:43 ` heroxbd
2012-07-05 13:21 ` Luca Barbato
2012-07-09 7:05 ` heroxbd
2012-07-09 18:35 ` Rich Freeman
2012-07-09 19:11 ` Luca Barbato
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=86y5n98xl3.fsf_-_@gmail.com \
--to=heroxbd@gmail.com \
--cc=gentoo-soc@lists.gentoo.org \
--cc=openrc@gentoo.org \
--cc=rleigh@debian.org \
--cc=rra@debian.org \
/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