This always remembers me of a certain old-school Linux administrator who got stuck in a large company and failed to keep up with the latest tools. He actually made a case for LILO, convinced that GRUB corrupts your data and should not be used, when RHEL7 with GRUB2 have been shipping their alpha. The same guy adjusted volume in alsamixer on a machine with hardware volume buttons.
I don’t care what people say about systemd anymore. For me it means that I get reliable information about my system. I get better logging with fast filtering. And most importantly, I don’t need to write any more init scripts and double-fork my Python or Racket services. Socket initialization is also extremely cool, because I don’t need to handle the accept race condition in every trivial TCP service with a handful of potential peers.
Other people probably like systemd for other reasons. I can see why. It solves a lot of real-life problems.
systemd has made some choices that I really don’t agree with, but I think the thing I like least is the mandatory binary logging with journald/journalctl. It seems like a very solid improvement in other areas though.
However, I still prefer bsd style init with daemontools or runit for services. I use FreeBSD these days for personal stuff though, so I get to have what I want. :)
Just not at work – work uses centos 6 and probably will for quite a while…. :(
Oh, systemd is evil all over again.
This always remembers me of a certain old-school Linux administrator who got stuck in a large company and failed to keep up with the latest tools. He actually made a case for LILO, convinced that GRUB corrupts your data and should not be used, when RHEL7 with GRUB2 have been shipping their alpha. The same guy adjusted volume in alsamixer on a machine with hardware volume buttons.
I don’t care what people say about
systemdanymore. For me it means that I get reliable information about my system. I get better logging with fast filtering. And most importantly, I don’t need to write any more init scripts and double-fork my Python or Racket services. Socket initialization is also extremely cool, because I don’t need to handle theacceptrace condition in every trivial TCP service with a handful of potential peers.Other people probably like
systemdfor other reasons. I can see why. It solves a lot of real-life problems.systemd has made some choices that I really don’t agree with, but I think the thing I like least is the mandatory binary logging with journald/journalctl. It seems like a very solid improvement in other areas though.
However, I still prefer bsd style init with daemontools or runit for services. I use FreeBSD these days for personal stuff though, so I get to have what I want. :)
Just not at work – work uses centos 6 and probably will for quite a while…. :(
Well, you can’t disable journald, but you can always set it to not store data at all, and just use (or don’t) syslog.
http://www.freedesktop.org/software/systemd/man/journald.conf.html