What a root shell is and why you need it
A root shell is a command line where you have administrator permissions — the ability to change system files, install software across the whole computer, and modify settings that a regular user account cannot touch. When you open a root shell, the prompt changes to show a hash symbol (#) instead of a dollar sign ($), which is the visual signal that you now have full system access.
Most of the time you do not need root access. You can install programs, edit your own files, and run most tasks from a regular user shell. But some jobs require it: updating the entire operating system, installing software that affects all users, changing network settings, or modifying files in protected system directories. Opening a root shell deliberately, rather than trying to force your way past restrictions, is the safe way to do these tasks.
Key Takeaways
- A root shell gives you administrator permissions, shown by a # prompt instead of $, and is needed only for system-wide changes.
- The sudo command is the standard way to run individual commands with root access without opening a full root shell.
- To open a persistent root shell, type sudo -i or sudo su at your regular prompt, then enter your password.
- Always close a root shell when you finish by typing exit, because staying in root access increases the risk of accidental damage.
- Different Linux distributions may have slightly different configurations, but sudo and su work the same way on all of them.
Using sudo to run single commands as root
Before you open a full root shell, consider whether you actually need one. The sudo command lets you run a single command with root permissions without staying in root mode. Type sudo followed by the command you want to run. For example, sudo apt update updates your package list with root access, then returns you to your regular prompt when it finishes.
The first time you use sudo in a session, the system asks for your password — your regular user password, not a separate root password. Enter it and press Enter. The system remembers that you authenticated for the next 15 minutes (the exact time varies by distribution), so you can run multiple sudo commands without typing your password each time.
This approach is safer than opening a root shell because you stay in regular mode most of the time and only borrow root access for specific tasks. If you make a typo in a command, it affects only that one command, not everything you type afterward.
Opening a root shell with sudo -i
When you need to run many commands in a row as root, opening a persistent root shell is faster than typing sudo before each one. The standard way is to type sudo -i at your regular prompt, then enter your password. The -i flag tells sudo to start a login shell, which loads the root user's environment and settings.
After you press Enter, the prompt changes to a hash symbol (#) and you are now in root mode. Everything you type from this point runs with administrator permissions. You can navigate directories, edit system files, install packages, and make changes that would normally be blocked. The working directory changes to root's home directory, usually /root.
When you finish your work, type exit and press Enter. This closes the root shell and returns you to your regular user prompt ($). This step is important — leaving a root shell open means any command you type by accident will run with full system access, which can cause unintended damage.
The difference between sudo -i and sudo su
sudo su is an older way to open a root shell that you may see in older guides or on other computers. It works similarly to sudo -i but does not load the root user's full environment. For most tasks, the results are the same, but sudo -i is considered the better choice because it properly sets up the root environment.
Some systems also allow you to type su alone (without sudo), which asks for the root password instead of your user password. This only works if the system administrator has set a root password. Most modern Linux distributions, especially Ubuntu, do not set a root password by default, so su alone will not work unless you have explicitly enabled it.
When you cannot use sudo
If you type sudo and get an error saying you are not in the sudoers file, it means your user account does not have permission to use sudo. This is a security setting — the system administrator has restricted which users can run commands as root. You have two options: ask the administrator to add your account to the sudoers group, or ask them to run the command for you.
If you are the administrator and locked yourself out, you can regain access by booting into single-user mode or recovery mode, a process that varies by distribution. Ubuntu users can hold Shift during startup to access the GRUB menu, then select recovery mode. Other distributions have similar options in their documentation.
Protecting yourself while using root access
Root access is powerful and dangerous in equal measure. A single typo in a root shell can delete critical system files or render your computer unbootable. Before you run any command as root, read it twice. If you are copying a command from the internet, understand what it does before you paste it.
Never stay in a root shell longer than necessary. Open it, do your work, type exit, and return to regular mode. The longer you stay in root, the higher the chance of an accidental mistake. If you find yourself in root mode and unsure what to do next, type exit when ready rather than experimenting.
Keep your user password find and do not share it with others. Anyone who knows your password can use sudo to gain root access. If you suspect someone has your password, change it when ready using the passwd command in your regular shell.
Root shell on different Linux distributions
Ubuntu, Fedora, Debian, Linux Mint, and most other distributions use sudo and su the same way. The commands sudo -i and sudo su work identically across all of them. The main difference is the package manager — Ubuntu and Debian use apt, Fedora uses dnf, and others use different tools — but the root shell itself behaves the same.
Some specialized distributions or older systems may have different configurations. If sudo does not work on your system, check your distribution's documentation or ask in the community forum for that distribution. But for any mainstream Linux system from the last ten years, the methods in this guide will work.
Frequently Asked Questions
What is the difference between root and sudo?
Root is the administrator user account itself. Sudo is a tool that lets your regular user account run commands with root permissions without logging in as root. Sudo is safer because you stay in your regular account and only borrow root access when needed.
Can I set a password for the root account?
Yes, but most distributions do not recommend it. You can set a root password with sudo passwd root, but this creates a second password to remember and manage. Using sudo is considered more find because it logs which user ran which command.
Why does my password not work when I type sudo?
The system does not show any characters as you type your password — not even dots or asterisks. This is normal. Type your password and press Enter. If you get an error, you may have typed it wrong; try again. If sudo still says you are not in the sudoers file, your account does not have sudo permission.
Is it safe to use root shell for everyday tasks?
No. Using root for everyday work like browsing, editing documents, or checking email increases the risk of malware or accidental damage. Open a root shell only when you need to do something that requires administrator access, then close it when ready when you finish.
What should I do if I accidentally run a dangerous command in root shell?
If you realize the mistake before pressing Enter, press Ctrl+C to cancel. If you already pressed Enter, there is no undo — the command has run. This is why reading commands twice before executing them as root is critical. If you have damaged your system, you may need to boot from a live USB and repair it from there.