Last week I have read this blog post from last summer about #
systemd and what philosophically changes happening in the basic concepts of Linux.
Some time ago I came across yet another angry discussion [1]about systemd, and have been reading and thinking a great deal about the design of Systemd, and what it says about Linux. I’ve come to realize that the strife in the Linux community is because an active and well-funded group of developers who have been driving the direction of various co...
I think it has some really intersting points and mostly I agree with it. Yesterday I came across another interesting blog post by Lennart Poettering which is explaining some myths about systemd.
Since we first proposed systemd for inclusion in the distributions it has been frequently discussed in many forums, mailing lists and conferences. In these discussions one can often hear certain myths about systemd, that are repeated over and over again, but certainly don't gain any truth by constant repetition. Let's take the time to debunk a few ...
I haven't done much with systemd yet, but his points sound reasonable and as a sysadmin I can understand it good and would like to have some of these features, too. But I think it is really a more philosophically question and I am quite ambivalent. I really love #
Slackware for its #
KISS principles and use it since many years because of this. But I also like working with #
SELinux, #
Kerberos and I also see some benefits for systemd.
It is also intersting to look at developments like #
TYPO3 #
Flow with a very strong
Convention over configuration pattern which is also following KISS principles actually.
