On Tue, Sep 4, 2012 at 4:10 PM, Andreas Jaeger
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.
Can you give me an example so that we can compare with 12.2?
I'm planning to test 12.2 and let you know already. I just need to find the time.
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.
I don't think you ever interacted properly with Frederic Crozat, who's "in charge" of systemd in openSUSE and did a lot for a proper integration - and convinced upstream also in some cases to change their "we don't want to".
I could dig the archives, but you're right, I got tired of the negative responses and just stopped reading the thread at the time (and skipped 12.1 as it was too troublesome for my setup). I'm sure things improved, and my kudos to Frederic for that. I'm just saying, it was a tough time that was imprinted on users' impression of SystemD. As far as I know, there's still no integrated solution to the vmware status reporting case (which is incidentally equivalent to a few services I run). Upstream's unwillingness to provide such a simple facility is quite misterious. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org