On Wednesday, September 05, 2012 17:09:59 Claudio Freire wrote:
On Wed, Sep 5, 2012 at 4:51 PM, Cristian Rodríguez
<crrodriguez@opensuse.org> wrote:
The systemd proponents on this list responded "then this is no service". The systemv proponents told them "but it was before". Several small shouting wars started. (Well, not a real flamewar, not like the r.a.sf-lovers split, back in 1991. :-))
That's correct, controlling VMs directly with sysvinit do not really work either, it would seem to work though. if there is no particular process to talk, then the application is unmanaged, uncontained and may do whatever it pleases.
And there, Andreas, as I was saying, the whole problem lies.
After expressing a need for controlling VMs at startup/shutdown, the answer is usually on that tone. Ie: "You're wrong, you don't need it, you should ask someone else, stop bothering."... etc. No rationale provided, no alternative way of doing it, no nothing. Just a "NOT SO".
No, the answer here was: It works somehow by SysV init but also not in an ideal way.
Then, threads read like:
There's a problem here. NOT SO YES SO NOT SO DUH STOP IT YOU STOP IT
Quite unproductive.
You're jumping the gun too early, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org