Fedora40: Change Run-Level

Introduction

Changing the run-level in Fedora 40 is a fundamental task for system administrators to control the state and behavior of the operating system. Run-levels are predefined modes that the system operates in, each with its own set of processes and services.

Overview Change Run-Level

Navbar

• Overview
• Change Run-Level

Overview

What

Changing the run-level involves modifying the state in which the Fedora 40 operating system operates. Each run-level provides a different set of services and processes.

Who

System administrators and advanced users are typically responsible for changing run-levels to manage system states effectively.

Where

Run-level changes can be performed on any system running Fedora 40, whether it's a personal computer, server, or virtual machine.

When

Run-level changes are made when there is a need to alter the system state, such as switching to single-user mode for maintenance or multi-user mode for regular operations.

Why

Changing run-levels allows administrators to control which services and processes are running. This can be necessary for troubleshooting, maintenance, or optimizing system performance.

Pros	Cons
Enables fine control over system states.	Requires knowledge of system internals.
Improves troubleshooting capabilities.	Can disrupt running services if not done carefully.
Allows maintenance in a minimal environment.	May lead to system downtime.

How

Changing run-levels in Fedora 40 involves editing the system's default target in systemd. This can be done by using the `systemctl` command to set the desired target, such as multi-user.target or graphical.target.

Consequences

Changing run-levels can have several consequences, both positive and negative.

Positive	Enhanced control over system operations. Improved system maintenance capabilities. Better resource management and performance optimization.
Negative	Potential disruption of services during the change. Requires expertise to avoid configuration errors. May cause temporary system downtime.

Conclusion

Changing run-levels in Fedora 40 is a critical task for system administrators to manage the operational state of the system. While it provides significant control and maintenance benefits, it requires careful handling to avoid disruptions and ensure smooth system performance.

Change Run-Level

If you would like to change System Run-Level, set like follows.

Step [1]Run-Level is set with linking to [/etc/systemd/system/default.target]. For example, the default setting without GUI is set like follows.

                     
[root@dlp ~]# systemctl get-default
multi-user.target
[root@dlp ~]# ll /etc/systemd/system/default.target
lrwxrwxrwx. 1 root root 41 May 7 10:37 /etc/systemd/system/default.target -> /usr/lib/systemd/system/multi-user.target
[root@dlp ~]# ll /lib/systemd/system/multi-user.target
-rw-r--r--. 1 root root 540 Feb 28 02:26 /lib/systemd/system/multi-user.target
                    
                

Step [2]For example, if you'd like to change Run-Level to Graphical-Login, set like follows.

                     
[root@dlp ~]# systemctl set-default graphical.target
Removed "/etc/systemd/system/default.target".
Created symlink /etc/systemd/system/default.target → /usr/lib/systemd/system/graphical.target.
[root@dlp ~]# systemctl get-default
graphical.target
[root@dlp ~]# ll /etc/systemd/system/default.target
lrwxrwxrwx. 1 root root 40 May 7 10:47 /etc/systemd/system/default.target -> /usr/lib/systemd/system/graphical.target