About systemd itself: I guess so far it's really hard to say if it's worth the hassle. My experience is limited to two installations: One on a (admittedly beta level) Fedora image and running Arch on my Pi.
The latter was really pleasant, _including_ the systemd migration. I never used it before and definitely fell in love with a couple of features (The status, unifying log messages and the service status, for one).
I'd be the first to agree that there's quite a bit of room to improve. Some design decisions are questionable imho (like the stated opinion that systemd shouldn't write a text-only /var/log/messages file by default).
In the end it's always the same though: Some people are having a vision of how things should work and try to promote it. If they are successful, I'd argue that their idea has merit (or everyone else doesn't care).
"Some design decisions are questionable imho (like the stated opinion that systemd shouldn't write a text-only /var/log/messages file by default)"
I think that may have changed in the latest release (or maybe it's in the next release, but I'm pretty sure Lennart said the default was going to be to write logs).
I think that may have changed in the latest release (or maybe it's in the next release, but I'm pretty sure Lennart said the default was going to be to write logs).
See, the problem with the sentence "shouldn't write a text-only /var/log/messages file by default" wasn't the "shouldn't write a [log] by default" part, it was the "shouldn't write a text-only [log]" part. As a CLI jockey/junky/sysadmin, I for one will not accept any solution I can't grep.
As a long time Linux user, I can't but agree with the OpenBSD folks: systemd is a "solution" in search of a problem, and the only reason it is gaining any traction appears to be the same shove-it-down-the-user's throat attitude that the GNOME devs have.
Granted, there has been a proliferation of parallelized boot schemes cropping up in Linux, but systemd seems to take too much on itself. And while PulseAudio eventually settled down and solved the proliferation of audio multiplexing systems, it was a very bumpy ride getting there. I only bring that up because that was another Poettering project.
About systemd itself: I guess so far it's really hard to say if it's worth the hassle. My experience is limited to two installations: One on a (admittedly beta level) Fedora image and running Arch on my Pi.
The latter was really pleasant, _including_ the systemd migration. I never used it before and definitely fell in love with a couple of features (The status, unifying log messages and the service status, for one).
I'd be the first to agree that there's quite a bit of room to improve. Some design decisions are questionable imho (like the stated opinion that systemd shouldn't write a text-only /var/log/messages file by default).
In the end it's always the same though: Some people are having a vision of how things should work and try to promote it. If they are successful, I'd argue that their idea has merit (or everyone else doesn't care).