[arch-dev-public] [RFC, after the fact] initscripts config
stephane at archlinux.org
Thu Jul 26 08:00:48 EDT 2012
Le 2012-07-22 10:59, Tom Gundersen a écrit :
> h) The major one: systemd is here to stay, more and more Arch devs and
> users switch to systemd and we will increasingly struggle to get
> enough testers and reviewers for initscripts. However, I really want
> to support initscripts as long as I can. To make this doable for me,
> we need to unify. We need to share code, configuration and behavior to
> make initscripts sustainable even with very few testers. You might
> argue that what we should do is to block systemd in order to support
> initscripts. However, I think that would be a huge error as systemd is
> simply too superior in every way, so preventing our users from using
> it is not doing anyone any favors.
> I must admit I'm a bit exasperated by the shortsightedness of most of
> the flames on BBS/IRC/MLs. So if you are going to veto this, please
> also outline an alternative long-term plan.
I am joining the party a little late.
I do not use systemd, but I support and appreciate your efforts to
improve our initscript. However, I think that most of dissatisfaction
that was recently expressed is caused by the lack of clarity surrounding
our plans about systemd.
My understanding is that systemd is truly superior and will inevitably
become our default system. On the other hand, our traditional init will
need to lose some of his "personality" during a transition that might be
short or long (not clear). In this context, I wonder why don't we avoid
duplication of effort and move to systemd right away?
If we consider that systemd is not yet ready for Arch, I wouldbe more
comfortable if we had a clear plan and timeline for the future transition.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 554 bytes
Desc: OpenPGP digital signature
More information about the arch-dev-public