Jim Henderson wrote:
It's useful to discuss things to a point, but a decision needs to be made (regardless of the topic) and we need to move on to the next thing. Trying to come to a group consensus is a useful decision making process, but not something that should be employed for every single decision being made - the community can't micromanage every aspect of the project - that's part of the reason we elected a leadership team in the project.
I was not aware that we had elected a leadership team.
With regards to the topic under discussion, maybe someone could (if it hasn't already been done) post a high-level comparison of the two components and identify what a migration path would look like to get from sysvinit to systemd.
I think that is what part of what we are asking. Overall, switching to systemd sounds like a good idea to me, although I don't think we should make it default in 12.1. systemd comes with certain new features (e.g. cgroup support) which will no doubt be attractive to some more than others. Let the keen, early adopters iron out whatever wrinkles might be left after Factory, then let the regular user get a system (in 12.2) that "just works".
If we are going to switch, we need to provide a migration path for those who have created custom init scripts.
systemd is, as far as my own tests have shown, virtually sysvinit compatible, i.e. custom init scripts will quite likely continue to work. -- Per Jessen, Zürich (24.2°C) -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org