What “technical” concerns do I have with systemd?
blog.lusis.org
What “technical” concerns do I have with systemd?
1–10 of 102 posts
Re: What “technical” concerns do I have with systemd?
#2systemd should really include pulseaudio, and nginx. Oh, it already has a httpd in there.
Re: What “technical” concerns do I have with systemd?
#3[deleted]
Re: What “technical” concerns do I have with systemd?
#4systemd should really include pulseaudio, and nginx. Oh, it already has a httpd in there.
And it's own database which is mentioned in http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/69...
Re: What “technical” concerns do I have with systemd?
#5Re: What “technical” concerns do I have with systemd?
#6As a user of linux on the desktop, I've never felt a moment of concern over the fact that it takes longer to boot than did Windows. I'm not sure who is panicked by this and I'm distressed that we would solve all of our problems with init by embracing systemd.
If Gnome requires systemd, lets drop Gnome.
Re: What “technical” concerns do I have with systemd?
#7Integration comes with a huge price.
I'm a beginner sysadmin, and therefore not really knowledgeable about the recent changes in Linux -- however I've seen FreeBSD in production(ish), and it was indeed a more pleasent experience. Paths, configuration, the package system, the documentation (!) all felt nicer.
Re: What “technical” concerns do I have with systemd?
#8Integration comes with a huge price. I'm a beginner sysadmin, and therefore not really knowledgeable about the recent changes in Linux -- however I've seen FreeBSD in production(ish), and it was indeed a more pleasent experience. Paths, configuration, the package system, the documentation (!) all felt nicer.
If you find FreeBSD docs nice, check out the OpenBSD manpages.
For me they set the bar for nice documentation.
Re: What “technical” concerns do I have with systemd?
#9He's hit the nail on the head - systemd's fundamental design is not appropriate for the server environment:
"I have to provide a system that runs reliably and can easily be reasoned about and yet I have to build it on distributions created by people who consider how long it takes to get to the fucking GDM login screen and if shutting the laptop lid will cause the system to hibernate properly or not."
Re: What “technical” concerns do I have with systemd?
#10Integration comes with a huge price. I'm a beginner sysadmin, and therefore not really knowledgeable about the recent changes in Linux -- however I've seen FreeBSD in production(ish), and it was indeed a more pleasent experience. Paths, configuration, the package system, the documentation (!) all felt nicer.
I believe it's more about tight vs loose coupling, not integration. The contrast is, systemd's parts are relatively tightly coupled together (in a way one can't easily pull, say, journald and use it autonomously, with other init), while, traditional init systems are bunch of loosely coupled mostly autonomous modules that happen to reliably work together thanks to standards' glue (so, they're integrated as well).
I could be wrong on this, though. Just my thoughts.