SysVinit, a traditional Unix-style init system responsible for bootstrapping user space and managing system processes, has released version 3.16 as a small maintenance-focused update to one of the oldest init systems still used on Linux.
Many of the changes focus on the manual pages. The inittab and init documentation have been revised to correct typos and improve syntax clarity. The update also provides clearer guidance on how the /etc/inittab.d/ directory is processed.
SysVinit 3.16 also improves the conversion of systemd unit files into SysV-style init scripts, enhancing compatibility in mixed environments or during transitions from systemd-based setups.
Additional refinements include removing unnecessary debug and status messages when reading the /etc/inittab.d/ directory, as well as eliminating unused variables and code in the sulogin component.
For more details, see the changelog.
Although most mainstream distributions have adopted systemd, SysVinit remains actively used in systemd-free distributions such as Devuan, antiX, and other lightweight or legacy-focused systems.
The point is NOT legacy, the point is SECURITY and Freedom. SystemD compromises the users freedom to use and control their machine as they see fit. SysV Init does not. Runit does not. None of the real init systems compromise freedom or the UNIX Philosophy. SystemD does.
SystemD also arguably also enforces a single framework that integrates multiple single points of failure and enables multiple potential attack vectors. That is not a stopper for all operations or all users, but for those who value security and freedom the distributions that avoid SystemD are better options. (Bonus, they mostly boot faster!)