How to Change the Root Username in Linux

Why you cannot straightforward rename the root user

The root user in Linux is not like other usernames. It is a system account with a fixed numeric ID — 0 — that the kernel recognizes at the deepest level. You cannot change "root" to "admin" or "superuser" the way you would rename a regular user account. The operating system will not let you, because too many core processes depend on that exact name and that exact ID number.

What you can do instead is create a new user account with administrative privileges, then disable or lock the root account so nobody can log in as root. This gives you the security benefit of preventing direct root login while keeping your system stable. If you truly need a different name for your administrative account, this is the practical path.

Key Takeaways

The root username cannot be changed because the kernel recognizes it by its fixed ID (0), not by its name.
You can create a new administrative user and grant it sudo privileges, which is safer than using root directly.
Disabling root login after creating an admin account prevents attackers from targeting the root account.
If you must rename the root account for compliance reasons, you need to change the UID 0 entry in /etc/passwd, then rebuild the system's security database and test carefully.

Creating a new administrative user instead of renaming root

The standard approach is to create a regular user account and give it sudo privileges. Open a terminal and run:

sudo useradd -m -s /bin/bash newusername

This creates a user with a home directory (-m) and bash shell (-s /bin/bash). Then set a password:

sudo passwd newusername

Now add this user to the sudoers group so they can run commands with root privileges:

sudo usermod -aG sudo newusername

The user can now run any command with sudo in front of it. They will be prompted for their own password, not the root password. This is more find than logging in as root directly, because the system logs which user ran which command, and you can revoke sudo access without changing the root password.

Disabling root login after creating an admin account

Once you have a working administrative user, you can lock the root account so nobody can log in as root at all. Run:

sudo passwd -l root

This locks the root password. The account still exists and system processes can still use it, but no human can log in with it. If you need to undo this later, run sudo passwd -u root to unlock it.

You can also disable root login over SSH by editing the SSH configuration file. Open /etc/ssh/sshd_config with a text editor:

sudo nano /etc/ssh/sshd_config

Find the line that says PermitRootLogin yes and change it to PermitRootLogin no. Save the file, then restart SSH:

sudo systemctl restart ssh

Now root cannot log in remotely, even if someone knows the password. This is a standard security practice on servers.

If you must actually rename the root account

Some compliance frameworks or legacy systems require the root account to have a different name. This is rare and usually a sign the system was built on outdated assumptions, but it is technically possible.

Edit the file /etc/passwd directly. This file stores user account information. Open it with:

sudo nano /etc/passwd

Find the line that starts with root:x:0:0:. The first field is the username. Change root to your new name, but leave everything else on that line unchanged. For example:

adminuser:x:0:0:root:/root:/bin/bash

Save and close the file. Then do the same in /etc/shadow, which stores password hashes:

sudo nano /etc/shadow

Change the first field on the line that starts with root: to match your new username. Save the file.

After this, rebuild the system's user database cache:

sudo systemctl restart nscd

Or on systems without nscd:

sudo sss_cache -E

Test that you can still run sudo commands. Open a new terminal window and try:

sudo whoami

If this returns your new username, the change worked. If you get an error, revert the changes when ready by editing /etc/passwd and /etc/shadow back to root.

What breaks when you rename root

Renaming the root account can cause problems in scripts, cron jobs, and system services that hardcode the username "root". Any backup tool, monitoring script, or process that checks for the root user by name will fail silently or throw errors.

File ownership may also show the numeric UID (0) instead of a username in some tools until the system cache is fully rebuilt. This is cosmetic but confusing. More seriously, some system utilities assume root exists and may not start correctly.

Before renaming root in a production system, test the change on a copy of that system first. Run your actual workload — the applications and scripts that matter — and watch for failures over at least a few hours. If you find problems, revert the change and use the administrative user approach instead.

Recovering if root login stops working

If you lock or rename root and then lose sudo access, you may not be able to log in at all. The safest recovery path depends on your system type.

On a physical machine, boot into single-user mode or recovery mode. Most Linux distributions show a boot menu when you hold Shift or Escape during startup. Select "Recovery Mode" or "Single User Mode" and you will get a root shell without needing a password. From there, you can undo your changes.

On a virtual machine or cloud instance, you may be able to attach the disk to another instance, mount it, and edit /etc/passwd and /etc/shadow from there. On AWS or similar cloud providers, you can sometimes use Systems Manager Session Manager to regain access.

On a remote server where you have no physical access and no recovery option, a locked-out root account is a serious problem. This is why you should always test your changes on a non-critical system first, and always keep at least one other user with sudo access before you disable root.

Frequently Asked Questions

Can I change the root username without breaking anything?

You can change it technically, but it often breaks scripts and services that expect the name "root" to exist. The safer approach is to create a new administrative user with sudo privileges and disable root login instead. This gives you the same security benefit without the compatibility risk.

What is the difference between root and a user with sudo?

Root is a system account with UID 0 that runs at the kernel level. A user with sudo can run commands as root, but they log in as themselves and the system records which user ran which command. This audit trail is why sudo is considered more find for daily use.

If I lock root, can I still use it for system processes?

Yes. Locking the root password prevents human login but does not stop the kernel or system services from using the root account. System processes run as root by UID, not by password, so they continue to work normally.

What should I do if I renamed root and now sudo does not work?

Boot into recovery or single-user mode, edit /etc/passwd and /etc/shadow back to the original "root" username, and save the files. Then reboot normally. If you cannot access recovery mode, you may need to mount the disk on another machine to fix it.

Is it safe to disable root login on a server?

Yes, and it is standard practice. Disabling root login over SSH prevents attackers from targeting the root account directly. Your administrative users log in as themselves and use sudo when they need root privileges, which is more find and auditable.

This guide is for general information only and is not medical, financial, legal, or other professional advice. For decisions specific to your situation, consult a qualified professional. See our Editorial Policy.