</>EmbeddedInterview

What is the difference between systemd, SysVinit and BusyBox init?

EasyEmbedded Linux & Boot

Short answer: All three are implementations of PID 1, the first user-space process that starts and supervises the rest of the system. BusyBox init is tiny and reads a simple /etc/inittab. SysVinit runs ordered shell scripts per runlevel. systemd starts services in parallel from a dependency graph and also supervises, logs and manages them, at the cost of size and complexity.

BusyBox init SysVinit systemd
Config /etc/inittab + rcS script /etc/inittab, /etc/init.d/*, runlevel links unit files (.service, .socket, .timer, .mount)
Start order sequential script sequential, numbered scripts parallel, based on dependencies (After=, Requires=)
Service supervision respawn entries only none built in restart policies, cgroups track every process
Logging syslogd (BusyBox) syslog journald
Extra features – – watchdog support, socket activation, timers, device and mount management, resource limits
Size tens of KB small several MB plus dependencies
Typical use small Buildroot images legacy systems Yocto/Debian-based products, larger devices

A systemd service for a product application

[Unit]
Description=Sensor daemon
After=network-online.target
Wants=network-online.target

[Service]
ExecStart=/usr/bin/sensord
Restart=on-failure
WatchdogSec=10s

[Install]
WantedBy=multi-user.target

WatchdogSec means the app must call sd_notify("WATCHDOG=1") regularly or systemd restarts it; systemd itself can pet the hardware watchdog (RuntimeWatchdogSec= in system.conf).

How to choose: BusyBox init when flash is tiny and the system only runs a few processes; systemd when you need robust supervision, dependency handling, timers and watchdog integration, and you can afford a few MB. Mention boot time: systemd's parallel start helps, and systemd-analyze blame shows what is slow.