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 599194
To read all comments associated with this story, please click here.
RE[2]: A cople of comments.
by hobgoblin on Thu 6th Nov 2014 18:34 UTC in reply to "RE: A cople of comments."
Member since:

And here is the thing. In the past, deciding what kind of init to use was up to the admin in charge.

But with systemd and the ongoing feature creep and near insistence that if you want to play you need to use APIs (the alternatives are rickety: result in a removal of choice.

I am right now running a distro with a somewhat esoteric boot system. But i can still get things like consolekit up and running. but if i want to upgrade to a more recent Gnome i need to bring in logind and therefore systemd.

Now if i could set systemd to run in a minimal fashion on top of what i already have, i would not be sitting here commenting. But all of a sudden i have to redo my setup from the init up because i want to upgrade the point release of Gnome?!

Reply Parent Score: 2