Linked by Dennis Heuer on Wed 25th Aug 2010 22:23 UTC
Linux I came across a news entry at Phoronix about a new init replacement, systemd, and curiously started a read into the surprisingly heavy matter. Systemd is by no means as simple as upstart. It does far more things far more straight and in more detail. The differences are so significant that they enforce quite different configuration strategies. One can argue for both, depending on the goal to reach. However, that's not what I want to write about. After having read what systemd is capable of, and how it does it, I began to put the existence of all system daemons - in their today's forms - in question.
Thread beginning with comment 438260
To read all comments associated with this story, please click here.
Comment by mtzmtulivu
by mtzmtulivu on Thu 26th Aug 2010 03:38 UTC
mtzmtulivu
Member since:
2006-11-14

This article talks about upstart and systemd as competing solutions to a problem but did not identify the problem. What is the problem with the current linux init system that necessitated creation of these two new systems?

Reply Score: 3

RE: Comment by mtzmtulivu
by vivainio on Thu 26th Aug 2010 05:23 in reply to "Comment by mtzmtulivu"
vivainio Member since:
2008-12-26

What is the problem with the current linux init system that necessitated creation of these two new systems?


It's slow.

Reply Parent Score: 2

RE[2]: Comment by mtzmtulivu
by sorpigal on Thu 26th Aug 2010 16:49 in reply to "RE: Comment by mtzmtulivu"
sorpigal Member since:
2005-11-02

If that were the only problem then any one of the init replacements created in the last 15 years would be an improvement.

Speed is secondary. An init replacement primarily needs to solve initialization sequencing. Building an init sequence in which the appropriate things are started at appopriate times, and not before other things that may be needed first, is a highly non-trivial process. Upstart and systemd try to solve this problem and the different approaches define more than anything else the differences between the systems.

After that there are some nice to have things which are lacking on linux. Here I primarily mean service control; it's embarrassing that Windows does this better (yes, better). Both upstart and systemd try to address this in fairly similar ways.

Both (but systemd in particular) do other things, of course, which I consider nonessential but still worthwhile and improvements on current systems. I have to give a great deal of credit to Lennart for not trying to solve just one tiny technical problem but aiming for a holistic approach, while still not greatly violating the *nix philosophy.

Reply Parent Score: 2