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

Best Affordable Linux and WordPress Services For Your Business
Outsource Your Linux and WordPress Project and Get it Promptly Completed Remotely and Delivered Online.

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. Richard Alsenz says:

    Jack, You don’t seem to have the knack for understanding Henry’s marketing strategy! His marketing strategy was make available to them what they need at a reasonable price and you will not have to convince them to want what they do not need. Not much different than Sam Walton’s. This is exactly the issue here. In the future your use of the indefinite pronoun may need refinement, unless you are an attorney, then shame on you!

    As a former hesitant Microsoft User and a current Linux user, for the last 5 years, all the people behind making Linux available deserve and have my lifetime support for their valiant effort. They have accomplished a unification of intent which I would have made any wager against prior to 1995.

    Lawrence October 12, 2016 at 5:30 am … welcome/ Innovation does not have to generate risk, just always insure your not getting what you do not want.

  2. Greg says:

    I find it interesting that this is posted by Editor? I guess it is easy to push unwanted changes on people if you act anonymously? Maybe Linux folks need to start looking at history before starting to change the environment that works just so they can make a name for themselves.

    I worked on real Unix system for decades. I used to consider Linux a Unix derivative. But I am doubting that based on the past few years. Linux is starting to act like Microsoft.


  3. Allan says:

    Your history is a bit inaccurate. /sbin/init dates back at least to 3.2 release 4.2, and I’m told it dates back to System 3.1 that was fire-and-forget mailed as a digital tape to Berkeley that started BSD the *BSD variants.

    In fact, on 3.2r4.2 (Open Desktop), /etc/inittab was an aggregation of /etc/init.d/*, which is where the idea came from for Apache to read conf.d as a file-tree-walk in Apache-1.3.13 on-th-fly, which is now copied by everyone.

    /sbin/init was originally intended to restart printer services; it later was reused to restart vt100 terminal restarts when they died. The expansion to /etc/rc.d/ crap was done so that configs could be “added” as files when new software packages are installed (3.2r4.2 would “recompile” the config, svr5 — Unixware, Solaris — would read them in-place). Even using it to restart TCP services in general was seen as a stretch but /sbin/init performed well beyond its design scope.

    So, /sbin/init had very modest roots, was already performing beyond designed intents, but did its job very well. I’m not a fan of the systemd “do all the things” approach, but sometimes we need to make the bold step forward, try to iterate to improve, and see whether that gets us a benefit or a rollback.

  4. Geoff Harrison says:

    sorry, but systemd is an abomination, and so is upstart, frankly. I don’t see why we replace the one thing that SysV got right.

    -mandrake (if you’ve been in the Linux world that long, yes, that one)

  5. Samuel says:

    Systemd was a mistake to begin with. Change is coming (sinit, s6, openrc, shepherd, runit).

    You can add to systemd bottlenecks:
    bugs uncovered day in, day out (you remember about the “tweeter” thing? is that the kind of thing you would expect from /sbin/init?)

    when your root device fails, any already-opened session is rendered useless (can’t access systemd logs, can’t debug, can’t reboot, that’s something you used being able to do, when these used to be separate components, one might have broken without bringing down everything)

    AFAIU: there isn’t a single developer with a full visual on the whole project ramifications/understanding of what’s going on, what could go wrong.
    binary logs => logs corruption.

    Listing “low memory footprint” as a feature doesn’t make any sense: what are we comparing? have you looked at init?

    Saying systemd isn’t POSIX compliant is a cute euphemism. From day one: systemd didn’t comply with Unix philosophy. That should have been a red light, and I blame Red Hat here.

  6. WhatConnor says:

    easy extensible startup script row? what drugs are you on?
    have you ever written a service script for either daemons?

  7. Aman Raj says:

    Nice article brief and informative .
    Thanks , keep posting the similar things

  8. Reddy says:

    Excellent Article

  9. Lawrence says:

    Why no one start something to opposite it and use init instead. I’m new to Linux but I agree with the term no broken don’t fix it. In fact a lot of people will be able to have a stable and effective system if the system stop changing dramatically.

    More contributors and newcomer like myself would enjoy Linux centos more. Please don’t end up like ms window os.

    • Jack says:

      Henry Ford said it best:

      – “If I’d of given the people what they wanted, they would’ve got faster horses”

      Same applies here.

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.