Slashdot Mirror
Systemd's Lennart Poettering: 'We Do Listen To Users'
M-Saunders writes: Systemd is ambitious and controversial, taking over a large part of the GNU/Linux base system. But where did it come from? Even Red Hat wasn't keen on it at the start, but since then it has worked its way into almost every major distro. Linux Voice talks to Lennart Poettering, the lead developer of Systemd, about its origins, its future, its relationship with Upstart, and handling the pressures of online flamewars.
My RHEL servers and VMs boot just fine, thank you. syslogd just works.
Go away, work on something else, get a hobby, masturbate, do something... just not this.
Because somewhere back down this little road between windows and Linux I got the idea that Linux is about choice and freedom. Crazy concept, I know.
Linux is all about choice. You're just confused about the choice to be made. Linux was never about the choice in what software others make for you. It is instead about the choice to make the software for yourself.
In other words, if you dont like it, you're free to rewrite any part of the software you want. You have the freedom to replace any part of the system with anything you like, but there is no good reason in the world anyone else should have to put the system together for you the way you want.
I wish I had a good sig, but all the good ones are copyrighted
Well in this case, get some education before you post in ignorance. No it doesn't require a lot of code changes for applications to work. Why would you say that? Did you even bother to read the interview? Daemons don't require any changes either, though you can compile your daemon to use libsystemd to do backwards-compatible socket registration. In other words a daemon can be configured to use socket registration if it runs under systemd, but it will fall back to normal sockets without. So no backwards compatibility is lost.
Systemd requires only 3 parts to run: the init process, udev, and journald (which can write to syslog still) for early boot debugging. NOTHING else is required. And none of this pushes *any* special requirements on applications. Pottering himself says he has no idea where this notion that Gnome depends on systemd comes from. It should work fine on ConsoleKit. The problem could be that the Gnome devs haven't been maintaining the ConsoleKit code.