On Tue, Sep 4, 2012 at 3:52 PM, Andreas Jaeger <aj@suse.com> wrote:
Why do I think so? Because sysadmins all over the place (and end users too) have a large body of scripts they will want to... not rewrite. You can't remove "rcstuff" and say it's ok, it's not on your users eyes. If you don't care, well, you're entitled not to care. As your users are entitled to be upset.
In the past there was a lot of difference on how distros booted and how you interacted with your init systems. Systemd allows to unify some of that - and I think that's good.
Yes, and that's very good. But in 12.1, service status reporting was quite lacking with SystemD, and it was a SystemD shortcoming, not a packaging or training issue. I don't know yet whether it's been improved though, but if it hasn't, it should. Thing is, the people in charge of it were quite... opposed to it. For no reason other than "we don't want to". Hence all the griping. With such a predisposition, many (including me) feel uncomfortable leaving it as the only option to a very critical subsystem. Perhaps it's such predisposition the thing that must change to improve SystemD acceptance. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org