Linked by jessesmith on Wed 5th Nov 2014 10:39 UTC
Linux Over the past year I've been reading a lot of opinions on the new init technology, systemd. Some people think systemd is wonderful, the bee's knees. Others claim that systemd is broken by design. Some see systemd as a unifying force, a way to unite the majority of the Linux distributions. Others see systemd as a growing blob that is slowly becoming an overly large portion of the operating system. One thing that has surprised me a little is just how much people care about systemd, whether their opinion of the technology is good or bad. People in favour faithfully (and sometimes falsely) make wonderful claims about what systemd is and what it can supposedly do. Opponents claim systemd will divide the Linux community and drive many technical users to other operating systems. There is a lot of hype and surprisingly few people presenting facts.
Permalink for comment 599074
To read all comments associated with this story, please click here.
Okay.. gave it a fair go..
by uridium on Thu 6th Nov 2014 04:00 UTC
Member since:

Okay. Usually with things like this, I keep an open mind and try to adopt new tech in experimental distro's because it's going to make it's way to the big end which I do have to support at work. I've fidgeting with linux since the 0.9 announcement on usenet so it's not my first bbq.

Systemd in my opinion, has too many moving parts. When a system breaks, I like to be able to pull up single user mode, check the logs. Stroke my chin, pivot root and go fix it. Move on with the important tasks I'm both paid and interested in.

That's my most important basic requirement with init and logging systems. I've had over the last 5 or so months, three systemd systems that've bricked during updates requiring a re-install. There has been others that've bricked, and been fixable. Of the three bad brickings that necessitated mode +clobber && re-install, okay, it's experimental I can partially agree that it's acceptable. What I hated was:

a) binary log format
b) zero-byte log files.
c) no other indicator of "what broke" and being told in a loop which useless commands to issue to interrogate it.

It's not simple by design. Too many moving parts. One part goes Fut (tm) .. and your blind, in the dark and generally otherwise porked.

This has cost me massive amounts of time. Think 'experimental cluster' with heavy emphasis on testing. You'll know where I'm coming from.

I've *REALLY* wanted to like systemd and to learn new things, but frankly with the amount of time it's caused me and more importantly how brittle it is, sorry, your off the Christmas card list. F#$% it.

Reply Score: 3