From: heroxbd@gmail.com
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] (draft) final report for OpenRC soc project 2012
Date: Thu, 16 Aug 2012 17:38:21 +0900 [thread overview]
Message-ID: <86628jdyf6.fsf@gmail.com> (raw)
In-Reply-To: <502C1903.1090805@gentoo.org> (Luca Barbato's message of "Wed, 15 Aug 2012 23:47:47 +0200")
Dear Luca,
Luca Barbato <lu_zero@gentoo.org> writes:
> On 8/15/12 5:14 PM, heroxbd@gmail.com wrote:
>> 1. Prefix support of OpenRC
>
> And it looks quite nice
Thanks :)
>> 2. A evaluation of existing init systems
>>
>> This includes solaris SMF, Mac OSX launchd, Fedora systemd, OpenSUSE
>> systemd/LSB combo, Ubuntu upstart and Debian LSB/insserv combo.
>
> Were is it? I'd like to read it =)
http://wiki.gentoo.org/wiki/Comparison_of_init_systems
And the "counter systemd" talk page,
http://wiki.gentoo.org/wiki/Talk:Comparison_of_init_systems
>> 3. service supervisor
>>
>> achieved via runit, doc at
>> http://www.awa.tohoku.ac.jp/~benda/projects/runit.html
>>
>> will move to wiki after runit feature is pulled in my WilliamH.
>>
>> git repo:
>> http://git.heroxbd.z.tuna.tsinghua.edu.cn/openrc.git?p=openrc.git;a=shortlog;h=refs/heads/runit
>>
>> This is a cool feature, while it have changes to default behavior of
>> OpenRC initscripts. Therefore documenting it comprehensively is
>> necessary. A GLEP will be composed to serve as an RFC for the Gentoo
>> community, official explanation and general guideline to simplify
>> present (already simplified compared to LSB conterparts) init scripts
>> shipped in ebuilds.
>>
>> btw, s6 (http://www.skarnet.org/software/s6/why.html) is a better
>> alternative to runit.
>
> Seems interesting indeed, would you consider working on it later?
Yes, the plan is,
a. finish the GLEP, raise to gentoo-dev ml, get it accepted.
with the reference implementation
b. refine the runit branch according to the accepted GLEP, push into
OpenRC master and make an OpenRC release. The build system should
make this feature optional and tunable with USE flags in openrc ebuild.
c. bug ebuild maintainers for possible polishing of their init
scripts, referring the GLEP.
>> 4. OOM killer/periodical command
>>
>> Not implemented here, tested with monit (http://mmonit.com/monit/)
>> and fcron (http://fcron.free.fr/). No integration or modification is
>> need in OpenRC, unlike runit. At most, we can introduce a
>> IN_PERIODICAL envvar, as how IN_HOTPLUG works.
>
> I'd like to have more information here.
Got it, preparing...
>> 5. event driven actions
>>
>> Same as hotplug feature already in OpenRC, triggered by udev, just
>> lack of documentation. If used with runlevel stacking (another under
>> documented feature of OpenRC), it can cover all the use cases I could
>> imagine.
>>
>> That's enough. upstart features a udev-upstart-bridge after all. It
>> is a cool feature and we can adopt it with a combo of tools and
>> achieve sane default behavior by packaging with, e.g., our beloved
>> ebuild. The revolutionary event based init design is more of
>> propaganding, IMHO.
>
> I'd like to see a wiki page or some more on that =)
Got it, underway...
>> 6. OpenRC introduction to debian
>>
>> documented at
>> http://wiki.debian.org/OpenRC
>>
>> git repo:
>> http://git.heroxbd.z.tuna.tsinghua.edu.cn/openrc.git?p=openrc.git;a=shortlog;h=refs/heads/debian
>>
>> ITP bug:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684396
>>
>> on going debian packaging collaboration
>> http://anonscm.debian.org/gitweb/?p=collab-maint/openrc.git;a=shortlog;h=refs/heads/debian
>>
>> I will work closely with the debian team. Hope debian can stand
>> against the gigantic storm of systemd.
>
> Looks great so far and coordination is great
Thanks :)
>> Tried systemd on OpenSUSE, disappointed by its ini unit files. At
>> present don't see the necessity for a parser.
>
> The unit file feature is something touted a lot, why you found it
> disappointing?
It's just plain ini, no black magic to prepare my coffee :D
BTW, any reference pointer to classical "touted" articles?
>>>> another plan for today
>>>>
>>>> install newest ubuntu to try out upstart natively. Make a draft
>>>> event driven system on my laptop(debian) by newly packaged OpenRC with
>>>> incron/inotify extension.
>>
>> incron not needed, it is for filesystem after all. udev + hotplug@OpenRC
>> do the job.
>
> More should be said on that =)
Ok, same as event driven topic as above. underway...
>> Succeeded, thinking of documenting it in wiki.
Got it.
Yours,
Benda
next prev parent reply other threads:[~2012-08-16 9:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 8:58 [gentoo-soc] report 7.16-7.23: improving OpenRC heroxbd
2012-08-07 4:53 ` [gentoo-soc] report 7.24-8.7: " heroxbd
2012-08-07 9:16 ` Luca Barbato
2012-08-08 23:24 ` [gentoo-soc] report 8.8: " heroxbd
2012-08-09 6:05 ` Luca Barbato
2012-08-10 2:56 ` [gentoo-soc] report 8.9: " heroxbd
2012-08-10 8:51 ` Luca Barbato
2012-08-11 0:31 ` [gentoo-soc] report 8.10: " heroxbd
2012-08-11 23:50 ` [gentoo-soc] report 8.11: " heroxbd
2012-08-13 8:33 ` Luca Barbato
2012-08-15 15:14 ` [gentoo-soc] (draft) final report for OpenRC soc project 2012 heroxbd
2012-08-15 21:47 ` Luca Barbato
2012-08-16 8:38 ` heroxbd [this message]
2012-08-16 11:41 ` Rich Freeman
2012-08-17 5:39 ` heroxbd
2012-08-17 7:29 ` Luca Barbato
2012-08-17 11:56 ` Rich Freeman
2012-08-20 3:04 ` heroxbd
2012-08-20 8:16 ` Luca Barbato
2012-08-20 10:25 ` Fabian Groffen
2012-08-20 16:32 ` Luca Barbato
2012-08-20 18:25 ` Fabian Groffen
2012-08-20 10:47 ` Rich Freeman
2012-08-20 16:34 ` Luca Barbato
2012-08-20 18:12 ` Rich Freeman
2012-08-20 18:28 ` Luca Barbato
2012-08-20 16:15 ` EBo
2012-08-21 14:07 ` heroxbd
2012-08-21 15:55 ` Luca Barbato
2012-08-22 2:04 ` heroxbd
2012-08-22 7:35 ` Luca Barbato
2012-08-27 10:46 ` Patrick Lauer
2012-08-27 12:37 ` Rich Freeman
2012-08-27 13:29 ` Luca Barbato
2012-08-27 14:10 ` Rich Freeman
2012-08-27 14:35 ` 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=86628jdyf6.fsf@gmail.com \
--to=heroxbd@gmail.com \
--cc=gentoo-soc@lists.gentoo.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