The Story Behind ‘init’ and ‘systemd’: Why ‘init’ Needed to be Replaced with ‘systemd’ in Linux

If You Appreciate What We Do Here On TecMint, You Should Consider:

  1. Stay Connected to: Twitter | Facebook | Google Plus
  2. Subscribe to our email updates: Sign Up Now
  3. Get your own self-hosted blog with a Free Domain at ($3.45/month).
  4. Become a Supporter - Make a contribution via PayPal
  5. Support us by purchasing our premium books in PDF format.
  6. Support us by taking our online Linux courses

We are thankful for your never ending support.

RedHat RHCE and RHCSA Certification Book
Linux Foundation LFCS and LFCE Certification Preparation Guide

You may also like...

59 Responses

  1. Amit says:

    systemd is portable , we have ported to arm7 arm8 devices in tizen os.

  2. SSS NNNN says:

    “If you have to go along with the Ecosystem (here Linux Ecosystem) you should not say no!” If you keep resisting you will be left behind and the ecosystem will move ahead.

    This is the Microsoft attitude…a walled garden….it has no place in Free and Open Software. The objective of systemd is superimpose itself
    between the kernal and you and create a closed “ecosystem” closed off to the user and in control. We left such things when we stopped using

  3. Ganesh says:

    systemd is very useful in the case of IVI system.

  4. waqar says:

    systemd is good, its ok to have it. But imposing dependencies on other applications like DE(kde,gnome,cinnamon) etc is not good. I installed debian 8.4 today on virtualbox and removed systemd for sysvinit, i know that gnome3 has some dependencies(systemd) but i never knew that KDE plasma also depends on systemd, so i have no choice but to install systemd again and install kde though i didn’t remove sysVinit.

  5. sysdope says:

    Change is not always good, whatever happened to “If it ain’t broke why fix it?” systemd is rogue-ware disguised as an open source alternative. The only thing stopping some of us from embracing FreeBSD fully is perhaps lack of KVM support. Linux feels like a M$ nightmare of modern times. People want freedom that’s why they come to the free world, not everyone expects they’ll be handed a box of hammers. At least the lawn is still green in the GNU landscape.

  6. Rui says:

    Already some time passed since this article. There is already systemd for ARM, at least. As for SysV not having dependencies when booting, Ubuntu and Debian already had some solutions for that. The core of question of the battle of systemd vs sysV init is mainly a relative newcomers saying we have got all wrong for twenty years, and ignoring our old axiom of using the tried, tested and stable…your table sums well some of the problems, including the complexity systemd brings unnecessarily to the table.

  7. vicky says:

    Hi avishek,

    nice post.
    I have still not blogged about this controversy in debian 8. being a big fan of debian i still don’t know whether to continue support debian or go with devuan (the new debian fork)

    • Avishek Kumar says:

      Dear vicky,
      My simple Philosophy is – “If you have to go along with the Ecosystem (here Linux Ecosystem) you should not say no!” If you keep resisting you will be left behind and the ecosystem will move ahead.

      Also i never said, that change is always good.

  8. crrodriguez says:

    Systemd works on any architecture where glibc, the linux kernel and dbus are available.

  9. Mohammad says:

    Great post. Thank you.
    but I think the “wired” word should be replace with “weird”

  10. Lucio Crusca says:

    Are you sure systemd can only work on x86? I couldn’t find anything documenting that limitation except this article. On the other hand, the official systemd documentation seems to tell just the opposite:

Got something to say? Join the discussion.

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.