On 14.11.2011 09:55, Michal Kubeček wrote:
On Monday 14 of November 2011, Stefan Seyfried wrote:
On 14.11.2011 08:37, Anders Johansson wrote:
I see absolutely, literally no new functionality in systemd that we did not have before. This includes parallelized booting. Feel free to name examples
puts each service into its own cgroup => reliable stopping of services
Are you sure this is not possible with traditional init scripts? I can't see a reason why it wouldn't.
You would need to touch each and every init script. While systemd happily continues to run old-stye init scripts. I forgot a few more benefits: * lossless loging from the beginning * easy display of system state (stuff like systemctl list-units --failed - do this with sysv init!) On real work systems, nobody cares what's printed on the console - simply because there is no console attached. But people care how to find out if startup worked. And they care for logs. My customers will love to see this in SLES, too. I was also suspicious of the change at first. You know, as an old fart, you don't like learning new stunts. But the actually working code convinced me. Of course there is the occasional glitch. But hell - I have had more problems with sysvinit in the last year than I had with systemd and that even though I'm running it since its very first incantation in Factory. (Sys V init mysteriously (and no way to find out why!) not starting single init scripts even though the S* and K* links were there is just one example). So instead of complaining I decided to simply fix the stuff that's still causing troubles. But for now it is just working fine for me and I will have to find something to fix. -- Stefan Seyfried "Dispatch war rocket Ajax to bring back his body!" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org