It's time to put on the brakes

It's time to put on the brakes

I'm running Jessie with systemd on a Haswell system just fine. I'm curious what you're doing differently, or if you have a bug reference.

I've been running Jessie/systemd for months now, on a couple of different systems, and the only systemd related issue I've encountered was a race in which cups left dangling symlink that had previously been valid, which caused systemd to crash; however, I was able to gracefully kill off important processes and sync, then reboot, everything worked fine afterwards, and the bug was fixed not too long afterwards. And this is the kind of issue you expect when running a testing distro that's in the middle of transitioning init systems and using the much more advanced capabilities of the new one.

So far, systemd has helped me debug some other issues, as "systemctl status" and the status output for individual services is much more informative than sysvinit, and journald has helped capture early boot message that were lost by dmesg because I had enabled some verbose DRM debugging messages without increasing the ring buffer size.

systemd is probably not my ideal init system. It is a bit more complex and monolithic than I would prefer. But it's so much better than sysvinit and upstart. I haven't tried other new or alternate init systems, but systemd is the only one that has real buy-in from a large number of other upstream projects, has full stable distros running on it, and actually provides the facilities to do proper multi-user login management (at least, as far as I know; please correct me if I'm wrong).