On Mon, Sep 3, 2012 at 2:08 PM, lynn <lynn@steve-ss.com> wrote:
systemd is a fact of life for Fedora,
Exactly. It boots fast and just works. We don't.
Does it matter if it's SystemD itself or the distribution's use of it? If "SystemD on openSUSE" doesn't work for all use cases, dropping the only other viable alternative will mean trouble. On Mon, Sep 3, 2012 at 2:13 PM, lynn <lynn@steve-ss.com> wrote:
"when it is ready" it is a non-sense argument.
We've had the whole of 12.1. How much more testing do we need?
*If* sysvinit is to be phased out in the following release, I do agree that it should be deprecated right now (early on the release cycle), because it will need as much time as possible to fix everything that is currently fixed by "switch to sysvinit". However, I expect 13.1 to be unusable to many without sysvinit. Why? Because 12.1 and 12.2's way of fixing init problems in IRC, reportedly, has been "switch to sysvinit". I've read that on the list, I don't go to IRC. Anyway, bugs may have been fixed, but with that attitude, probably not enough of them. Ditching sysvinit won't change that attitude before 13.1, and 13.1 would be unusable to those experiencing the remaining bugs. Are you willing to have a "transitional release" such as that? Because that's what it will take, IMVHO, to have a workable SystemD-as-sysvinit-replacement. Before I go on bitching... I'll go and test 12.2 - I just hope I get time for that soon ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org