Lennart Poettering, the controversial open-source developer behind PulseAudio
among other projects, has written a lengthy blog post as he attempts to battle some myths about his Linux init daemon.
Lennart in a new blog post entitled "The Biggest Myths" he points out what he calls are the biggest myths concerning systemd and attempts to debunk them.
Below is a partial list of what Lennart describes as the biggest myths and then a brief synopsis of why he doesn't believe they are true statements.
Systemd Is Monolithic
- Lennart says this is false since the init daemon is comprised of 69 individual binaries.
Systemd Is About Speed
- Lennart says that systemd's speed is just a side-effect of designing things right...
Systemd's Fast Boot-Up Is Irrelevant For Servers
- Many administrators like to keep system downtime to a minimum. It's also important for the cloud with booting VMs quickly.
Systemd Is Incompatible With Shell Scripts
- It is compatible, but thjey just don't use them for the boot process out of the developers' beliefs.
Systemd Is Difficult
- Lennart says no because it's a unified platform, the configuration file language is easy, and there's uniform tools. He does acknowledge though there's a bit of a learning curve from his views.
Systemd Is Not Modular
- There's configure switches to select what you want to build.
Systemd Is The Result Of NIH Syndrome
- Originally they were pushing for Canonical's Upstart, but then decided that its design was "inherently flawed at its core." The major flaw in Lennart's mind with Upstart is "it leaves dependency management to the admin/developer, instead of solving this hard problem in code."
Systemd Is A FreeDesktop.org Project
- FreeDesktop.org is little more than a hosting infrastructure.
Systemd Is Complex
- Lennart admits again there is some truth, but that modern computers are complex too. He even argues that systemd is simpler and has less redundancy.
Systemd Is Bloated
- "Systemd is probably the opposite of bloat" and Lennart brought up again that it's modular. The required dependencies of Systemd are just Glibc, libcap, and DBus.
Systemd Is Linux-only & Not Nice To BSDs
- Lennart claims that it's the BSD folks who are uninterested in systemd. In terms of systemd being Linux-only being a problem for Debian's adoption of it, Lennart claims that maintaining systemd unit files and the traditional init scripts is nominal compared to the work done by Debian developers who ported the operating system to non-Linux kernels.
Systemd Is Not Portable For No Reason
- "Non-sense! We use the Linux-specific functionality because we need it to implement what we want. Linux has so many features that UNIX/POSIX didn't have, and we want to empower the user with them."
Systemd Forces You To Do Something
- The software is not the mafia but Free Software where you can do what you want.
Systemd Makes It Impossible To Run Syslog
- While systemd introduced its own journal method, developers made sure to maintain syslog daemon compatibility.
Systemd Is Incompatible
- "We try very hard to provide the best possible compatibility with sysvinit."
Systemd Is Unstable & Buggy
- Not according to their data based upon the Fedora bug tracker.
Lennart attempted to address thirty myths about systemd in his posting, which can be in full on his blog