Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internal No. As the systemd people themselves wrote twice over, once in their telinit manual and once in their runlevel manual, runlevels are "obsolete". You can forget about runlevels.
These things do not actually exist in systemd at all, outwith a few compatibility shims.
These things do not actually exist in systemd at all, outwith a few compatibility shims.
No. As the systemd people themselves wrote twice over, once in their telinit manual and once in their runlevel manual, runlevels are "obsolete". You can forget about runlevels.
These things do not actually exist in systemd at all, outwith a few compatibility shims.
No. As the systemd people themselves wrote twice over, once in their telinit manual and once in their runlevel manual, runlevels are "obsolete". You can forget about runlevels.
These things do not actually exist in systemd at all, outwith a few compatibility shims.
No. As the systemd people themselves wrote twice over, once in their telinit manual and once in their runlevel manual, runlevels are "obsolete". You can forget about runlevels.
These things do not actually exist in systemd at all, outwith a few compatibility shims.
These things do not actually exist in systemd at all, outwith a few compatibility shims.
No. As the systemd people themselves wrote twice over, once in their telinit manual and once in their runlevel manual, runlevels are "obsolete". You can forget about runlevels.
These things do not actually exist in systemd at all, outwith a few compatibility shims.
default.target (and thence one or both of a graphical.target and a multi-user.target), a rescue.target, or an emergency.target. And the shutdown process involves a shutdown.target, a reboot.target, a halt.target, or a poweroff.target. No run-level targets are involved in either bootstrap or shutdown.telinit command, which one might think uses the compatibility symbolic links to map its command-line arguments, does not do that either. There's a hardwired table in the source code of the telinit program, and the numbers 2, 3, 4, and 5 as arguments to the command are hardwired to map to multi-user.target and graphical.target.systemd-update-utmp also has an internal hardwired table.rc, not with van Smoorenburg init.systemd-update-utmp command operates internally in terms of the activation states of rescue.target, multi-user.target, and graphical.target.systemd-sysv-generator, systemd's backwards compatibility service unit generator, merges the /etc/rc[234].d directories into just the one Wanted-By relationship to multi-user.target in generated service units. There is no actual reference to run levels in the generated service units. (There used to be, years ago, but the systemd people found that this went wrong, because they weren't being referenced anywhere else.)If one is a user of a system that builds systemd as did Arch Linux for the questioner at "https://unix.stackexchange.com/questions/389289/", one does not even get the compatibility shims, and commands such as init 0 result in the "native" systemd behaviour, which is to complain that the command has been incorrectly invoked.
runlevel. systemd manual pages. Freedesktop.org.telinit. systemd manual pages. Freedesktop.org.bootup. systemd manual pages. Freedesktop.org./etc/inittab is a thing of the past.. Frequently Given Answers.