[Cerowrt-devel] Cerowrt-devel Digest, Vol 26, Issue 49
mo at ccr.org
Thu Jan 23 13:07:44 EST 2014
re: systemd vs procd vs etcd...
If other distros have largely converged to systemd,
is it worthwhile for CeroWrt to do something different?
This assumes that the daemons in question have already or
are in process of becoming systemd-compatible. If that is
indeed the case, is it really worthwhile to spend time
supporting something different?
not trying to re-open old wounds, just wondering how many
different approaches are actually "better" in some material
way and how many are just "different".
I've watched Apple go through the pains of moving all the
lifetime control of services to launchd. It took a long time to
justify it being different, but now that it's done, the fact
there is only ONE place to look is really a feature. One thing,
for instance, is that the Xserver and its helpers all start
automagically when an X11 binary is run. Likewise, making
a daemon periodic instead of continuous is changed in just
one place - not moved from one to another.
My point is that making is truly better, as opposed to "just
different, yet again" requires doing the whole job, not just
a different subset of it. So if there is a base of systemd-capable
versions of the daemons in question, just use those to avoid
the work. or do the whole job an import launchd. (which i'm
*not* lobbying for!)
More information about the Cerowrt-devel