Linked by diegocg on Mon 23rd Aug 2010 14:10 UTC
Permalink for comment 437829
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2005-11-02
I am positive on systemd for many reasons, but I am not on board with it for one big one: init scripts. I still see no *need* to kill off init scripts, replacing them as he is with "small C programs," and I see a lot of harm in doing that.
Killing init scripts doesn't make systemd (much) easier or better and it SURE AS HELL makes inspecting what's happening during my boot process harder! What's more, making a small tweak to the init system (at present) from (say) a livecd when the system boot is b0rked is *trivial*. Prevent some services from running? Sure, just delete some symlinks. Modify what happens? Edit the appropriate shell script. Did the script author not anticipate my exact distribution or custom environment? No problem, probably just a simple tweak to the human readable source code.
If you really want to improve bootup speed (and redice your pid count) simply wrap the shell script execution in a single-shell process that has builtins for most of the common tools. This "fixes" 99% of the problems that you supposedly find with init scripts without throwing the baby out with the bathwater.
Still, it's nice to see someone at least *trying* to improve things around here in Linux-land. It's always embarrassing to have to admit that fucking-Windows has better service control.