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 599049
To read all comments associated with this story, please click here.
RE: A cople of comments.
by gilboa on Wed 5th Nov 2014 22:15 UTC in reply to "A cople of comments."
gilboa
Member since:
2005-07-06

I wanted to add something:

My company develops a complex network security system that has a large number components (some user space, others kernel space, with multiple processes, users and capabilities).
Needless to say, all of this must be started in-order and there are a lot of inter-dependencies.
Back in the pre-systemd days we had a huge arrays of bash scripts that used ugly waits, sleeps and cat /proc/pids to get the system running. (I was the idiot who wrote many of them).
The scripts never worked - mostly due to external problems. (E.g. You can never reliably check if /etc/init.d/network actually managed to initialize the [many] network devices correctly.)
We actually reached the point that we actually had helper C-based init services, to help us circumvent system initialization issues. (Upstart was no better).
But then came systemd, and we simply throw out all the ugly, never-really-working scripts and replaced them with (simple!) unit files.
Suddenly, I don't have to worry about ulimit, chroot, init.d/network not being set or initialized correctly, suddenly I don't need to manually manage the order in which each component is started, stopped and restarted.
I simply write a 10-20 line unit file, maybe add a small bash script to set some environment switch that systemd doesn't support and I'm done. Heck, we reached the point that we actually have a helper bash script that automatically write most of the systemd unit file based on a template file and a configuration file.
It works in the first time. It works in the 1000'th time and I no longer need to worry about it.

As the saying goes, you'll have to prey systemd out of my cold dead hands.

- Gilboa

Edited 2014-11-05 22:18 UTC

Reply Parent Score: 4