On Tue, 04 Sep 2012 01:06:58 +0200
"Carlos E. R."
Exactly. You do not care. Don't say any more.
Nice community...
Let we put this in another perspective. All that you care is that system is running, and you are not different in this then me and all other on this list - developers or not. Now. You are not developer. You don't know what problems they have to keep sysvinit running. You don't know when sysvinit system will start breaking and fall apart because there is no more sufficient resource to keep it up. On the other side you have developers that know answer on at least first question, and some with better insight can predict when maintenance will start failing, but you don't trust them. I can understand why, as they did bring new stuff before that took long to stabilize (PulseAudio, KDE4, GNOME3. package management), or completely failed (Beagle). Problem is that we don't remember all good stuff that worked fine, and that pile is much bigger then the failed, but that is how human brain works, good stuff is not a danger that you have to watch and avoid, bad is. When you think about good and bad events, did you notice one common denominator to good ones? They all were accepted by majority of distributions in a short time and that is the case with systemd. Some of SUSE developers can be eager to have it, and if they would be alone, or even in Fedora company, I would be suspicious too, but it is not only those two, it is just about every respectable distro around. Fact is that: World is changing, and oldtimers that invested time to learn how to use sysvinit will have more trouble to get used to systemd, just as Windows power users have a more trouble to accept Linux than new computer users. World will not stop turning around because you, or me, have a problem to accept that there is something new, pull up sleeves and learn new ways. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org