Init.d v/s Systemd , This is a start of era of Systemd

Systemd vs Init.d

Era of init.d is coming to an end. This is time for systemd to take the charge of new unix distributions and it takes a unix flexibility to have a system of new generation.World of Linux is dividing into two parts, The ones with with old conventional way to do stuff "Init" other is the rebel "systemd". Linus Torvalds, Chief architect of Linux kernel, feels attitude of key developer of systemd towards users and bug reports do not seems ok. It was also reported that systemd philosophy is weird and a foreign way to control system processes.

What is Init.d?

Init stands for Initilization. The init is a daemon process which starts as soon as the computer starts and continue running till, it is shutdown. In-fact init is the first process that starts when a computer boots, making it the parent of all other running processes directly or indirectly and hence typically it is assigned “pid=1“.

We will be talking here abut System V. Though we have BSD (Berkeley Software Distribution) as well. Are these two same? Basically BSD doesn't have any runlevels. This means that System V is more flexible as compared to BSD. Running System V is in one of the predetermined number of states, called runlevels. At least one runlevel is the normal operating state of the system; typically, other runlevels represent single-user mode (used for repairing a faulty system), system shutdown, and various other states. 

Understanding Runlevels

When we look at how the system is set up, and in particular at the directory /etc/rc.d. You can find either a set of files named rc.0, rc.1, rc.2, rc.3, rc.4, rc.5, and rc.6, or a set of directories named rc0.d, rc1.d, rc2.d, rc3.d, rc4.d, rc5.d, and rc6.d. Also you will find a file named /etc/inittab. The system uses these files (and/or directories) to control the services to be started.

Look at the file /etc/inittab you will see something like:

id:4:initdefault:l

0:0:wait:/etc/rc.d/rc.0l

6:6:wait:/etc/rc.d/rc.6x

1:4:wait:/etc/rc.d/rc.4

The boot process is going to use these parameters to identify the default runlevel and the files that will be used by that runlevel. As in above example, runlevel 4 is the default and the scripts that define runlevel 4 can be found in /etc/rc.d/rc.4.

When you look into rc.d directories , you are going to find services with S and K with a number followed as prefix. What does S and K means? S is for Start and K is for Kill and that number defines the order in which it will kicked of at boot. so a service like S20logger will start before S21myserv. similarly K15HTTPD will get killed before K20myserv on system shut down.

Are we talking about sequence at boot up ? Yes.. it's going to take longer time. Isn't it ?That's why we have systemmd to rescue.

Target of systemd.

• Fast parallel boot-up
• Socket activation
• Mount handling
• Controlling running services

What is Systemd?

A systemd is a System Management Daemon named with UNIX convention to add ‘d‘ at the end of daemon. So, that they can be easily recognized. Initially it was released under GNU General Public License, but now the releases are made under GNU Lesser General Public License. Similar to init, systemd is the parent of all other processes directly or indirectly and is the first process that starts at boot hence typically assigned a “pid=1“.

A systemd, may refer to all the packages, utilities and libraries around daemon. It was designed to overcome the shortcomings of init. It itself is a background processes which is designed to start processes in parallel, thus reducing the boot time and computational overhead. It has a lot other features as compared to init.

Advantages of Systemd

• Clean, stateforward and efficient design.
• Simpler boot process.
• Concurrent and parallel processing at boot.
• Better API.
• Simple Unit Syntax.
• Ability to remove optional components.
• Low memory footprints.
• Improved technique to express dependencies.
• Initialization instruction written in config file and not in shell script.
• Make use of Unix Domain Socket.
• Job Scheduling using systemd Calendar Timers.
• Event Logging with journald.
• Choice of logging System events with systemd as well as syslog.
• Logs are stored in binary file.
• systemd state can be preserved to be called later in future.
• Track process using kernel’s cgroup and not PID.
• Users login managed by systemd-logind.
• Better integration with Gnome for interoperability.

Is it coming near you ? Below systems are integrated with systemd

This is fast , and yes it has to be when we look at the comparison between init and systemd

We have more .....

Conclusion :

This change is because of boot speed which is probably the biggest reason. A big disadvantage is that Linux system administrators are going to have to learn a new way of doing things.

Systemd is a very large program that takes care of everything init does, and then a lot more. It is multithreaded and leads to much faster boot times than init. Essentially, init is just considered to be outdated. The problem bit different, which is systemd flies in the face of the UNIX philosophy where your programs should be modular, and do one thing but do it well. This is what is a new change in era of traditional unix systems.

Systemd vs init has been a huge topic for debate.

About Author:

Yadu Mathur : Open source enthusiast , 7 + years of industry experience in Unix, Linux, System programming , Automation, Tools Development, Architecture, Configuration Management and DevOps.

References :

Comparisons and stats from google , wiki and tecmint