How To Become Root User In Linux : Sudo Privileges And Password Setup

by

Switching to the root user in Linux gives you full system control, but you need to know the correct command syntax. Understanding how to become root user in Linux is essential for system administration tasks like installing software, modifying system files, or managing user accounts. This guide covers all methods, from the classic su command to modern sudo setups, with clear steps for beginners and pros alike.

Let’s jump right in. The root user, also called the superuser, has unrestricted access to every part of the system. Without proper knowledge, you risk breaking things—but with the right commands, you’ll manage your Linux box like a pro.

How To Become Root User In Linux

There are several ways to gain root privileges. The most common are using the su command, the sudo command, or logging in directly as root. Each method has its own use case and security implications. We’ll cover all of them in detail.

Using The Su Command

The su command stands for “switch user” or “substitute user.” When used without a username, it defaults to root. This is the traditional way to become root.

  1. Open a terminal window.
  2. Type su and press Enter.
  3. Enter the root password when prompted.
  4. You’ll see the shell prompt change to #, indicating root access.

If you need to run a single command as root without staying in the root shell, use su -c "command". For example: su -c "apt update". This runs the command and returns you to your normal user.

One common issue: if you get “Authentication failure,” you probably don’t have the root password set. Many modern Linux distributions (like Ubuntu) disable the root account by default. In that case, you’ll need to use sudo instead.

Using The Sudo Command

sudo (superuser do) lets authorized users run commands with root privileges using their own password. It’s more secure than su because it logs all commands and limits access.

To become root with sudo, you can run sudo -i or sudo su. Here’s how:

  • sudo -i: Starts a root login shell. It loads root’s environment variables and profile.
  • sudo su: Switches to root using your own password (if you have sudo rights).
  • sudo -s: Starts a root shell but keeps your current user’s environment.

For a single command, just prefix it with sudo: sudo apt update. You’ll be prompted for your user password, not the root password.

To check if you have sudo access, run sudo -l. This lists the commands you’re allowed to run as root. If you see “user is not in the sudoers file,” you’ll need to add yourself to the sudo group (more on that later).

Logging In Directly As Root

Some systems allow you to log in as root directly from the login screen or via SSH. This is generally discouraged for security reasons, but it’s possible.

For SSH: ssh root@your-server-ip. You’ll need the root password. Many cloud providers disable root SSH login by default. To enable it, edit /etc/ssh/sshd_config and set PermitRootLogin yes, then restart SSH.

For local login: At the login prompt, type “root” as the username and enter the root password. This is rare on modern desktops because the root account is often locked.

Direct root login is risky. Every command runs with full privileges, and a typo like rm -rf / can destroy your system. Stick with sudo for daily tasks.

Setting Up Root Access On Different Distributions

Linux distributions handle root access differently. Here’s what you need to know for the most popular ones.

Ubuntu And Debian

Ubuntu locks the root account by default. You cannot use su without first setting a root password. Instead, use sudo. The first user created during installation is automatically added to the sudo group.

To set a root password (if you really need it): sudo passwd root. Then you can use su with that password. But it’s safer to stick with sudo.

On Debian, the root account may have a password set during installation. If not, use sudo passwd root to set one.

Red Hat, CentOS, And Fedora

These distributions set a root password during installation. You can use su directly. However, Fedora now defaults to sudo for the first user. CentOS 8+ also encourages sudo usage.

To add a user to the sudo group on RHEL-based systems: usermod -aG wheel username. Then that user can use sudo.

Arch Linux

Arch gives you full control. During installation, you set the root password. You can use su right away. To enable sudo, install sudo and edit /etc/sudoers with visudo to uncomment the wheel group line.

Add your user to the wheel group: usermod -aG wheel username. Then log out and back in for changes to take effect.

Common Commands For Root Tasks

Once you have root access, you’ll use these commands frequently. Always double-check before running destructive commands.

  • apt update && apt upgrade (Debian/Ubuntu): Update all packages.
  • dnf update (Fedora/CentOS): Same but for RPM-based systems.
  • systemctl restart service: Restart a service like Apache or SSH.
  • useradd -m newuser: Create a new user with a home directory.
  • passwd username: Change a user’s password.
  • chmod 755 file: Change file permissions.
  • chown user:group file: Change file ownership.

Remember: with great power comes great responsibility. Always verify commands before running them as root.

Security Best Practices For Root Access

Using root carelessly can compromise your system. Follow these guidelines to stay safe.

Use Sudo Instead Of Su

sudo logs every command to /var/log/auth.log. This audit trail helps you track what happened if something goes wrong. su does not log commands. Also, sudo requires your user password, not the root password, so you don’t need to share the root password with others.

Limit Sudo Access

Edit the sudoers file with visudo to grant specific permissions. For example, allow a user to only run apt commands:

username ALL=(ALL) /usr/bin/apt

This prevents them from running other root commands. You can also require a password for certain commands or allow passwordless sudo for specific tasks.

Disable Root SSH Login

Edit /etc/ssh/sshd_config and set PermitRootLogin no. Then restart SSH. This prevents brute-force attacks on the root account. Use a regular user with sudo instead.

Use Strong Passwords

Whether for root or sudo users, use complex passwords. Consider using SSH keys for authentication instead of passwords. Keys are much harder to crack.

Regularly Update The System

Run updates as root to patch security vulnerabilities. On Debian: sudo apt update && sudo apt upgrade. On Fedora: sudo dnf update. Set up automatic security updates if possible.

Troubleshooting Common Root Access Issues

Even experienced users run into problems. Here are fixes for common errors.

Authentication Failure With Su

This means the root password is wrong or not set. If you never set a root password, use sudo passwd root to set one. If you forgot it, you’ll need to boot into recovery mode or use a live CD to reset it.

User Is Not In The Sudoers File

This error appears when you try sudo but your user isn’t authorized. To fix it, you need root access. If you have the root password, log in as root (su -) and add your user to the sudo group: usermod -aG sudo username. On RHEL, use wheel instead of sudo.

If you don’t have root access, you’ll need to boot into single-user mode or recovery mode. At the GRUB menu, edit the boot parameters to add init=/bin/bash, then remount the filesystem as read-write and fix the sudoers file.

Permission Denied With Sudo

Even if you’re in the sudo group, you might get “permission denied” for certain commands. Check the sudoers file for restrictions. Also, ensure the command path is correct. Some systems require the full path, like /usr/sbin/reboot.

Root Shell Not Loading Profile

When you use sudo -s, you get a root shell but with your user’s environment. This can cause issues with PATH variables. Use sudo -i to load root’s profile instead. This ensures aliases and environment variables are set correctly.

Frequently Asked Questions

What Is The Difference Between Su And Sudo?

su switches to the root user (or another user) and requires the target user’s password. sudo runs a single command with root privileges and requires your own password. sudo is more secure because it logs commands and allows fine-grained permissions.

Can I Become Root Without A Password?

Yes, if your user has sudo privileges and the sudoers file allows passwordless sudo for certain commands. You can also set up SSH keys for root login, but that’s risky. The safest method is to use sudo with a password.

How Do I Know If I Am Root?

Check the shell prompt. If it ends with #, you’re root. A regular user prompt ends with $. You can also run whoami or id. If the output shows uid=0, you’re root.

What Happens If I Forget The Root Password?

You can reset it by booting into recovery mode or single-user mode. On most systems, you can edit the GRUB boot parameters to start a root shell without a password. Then use passwd to set a new one.

Is It Safe To Always Run As Root?

No. Running as root all the time is extremely dangerous. A single typo can destroy your system. Malware also gains full access immediately. Always use a regular user account and elevate privileges only when needed.

Advanced Root Access Techniques

For power users, here are some advanced methods to manage root access.

Using Sudo With Environment Variables

Sometimes you need to preserve environment variables when running sudo. Use sudo -E to keep your current environment. This is useful for scripts that rely on custom variables.

To set specific variables, use sudo VAR=value command. For example: sudo http_proxy=http://proxy:8080 wget http://example.com.

Creating A Root Shell With Sudo

If you frequently need root access, create an alias in your .bashrc: alias root='sudo -i'. Then just type root to get a root shell. This saves keystrokes and reduces errors.

Using PolicyKit For Graphical Applications

Some graphical apps (like GParted or the Software Center) need root privileges. PolicyKit handles this automatically. When you run such an app, a dialog asks for your password. This is safer than running the whole desktop as root.

To run a graphical app as root from the terminal, use pkexec appname. For example: pkexec gedit /etc/fstab. This uses PolicyKit’s authentication.

Setting Up Sudo Without Password For Specific Commands

Edit the sudoers file with visudo and add a line like:

username ALL=(ALL) NOPASSWD: /usr/bin/apt

This allows the user to run apt without a password. Be careful: this reduces security, so only do it for trusted users and non-destructive commands.

Conclusion

Mastering how to become root user in linux is a fundamental skill for any Linux user. Whether you use su, sudo, or direct login, always prioritize security. Use sudo for daily tasks, limit root access to trusted users, and keep your system updated. With the steps in this guide, you can confidently manage your Linux system like a pro. Practice these commands in a safe environment, and soon you’ll handle root access with ease.