Every Linux system has exactly one filesystem tree, and it starts at a single point: the root directory, written as /. There is no C: drive, no D: drive, no separate namespace for each disk. Every file you will ever touch on a Linux machine, whether it lives on the internal SSD, a USB stick, or a network share, has a path that begins by walking down from /.

This is one of the first things that trips up people coming from Windows, and it is worth understanding properly because it explains a lot of Linux behavior that otherwise looks arbitrary.

What root actually is

Root is not a folder you created. It is the base of the filesystem, mounted by the kernel during boot before anything else happens. Every other directory, whether it is /home, /etc, or a USB drive you plugged in five minutes ago, is either a direct child of root or nested somewhere further down inside that tree.

# List what lives directly under root
ls -la /

# See the whole mount hierarchy, including what is mounted where
findmnt --tree

# Check disk usage of the filesystem that backs root
df -h /

A typical ls -la / shows a short, predictable list of directories: bin, boot, dev, etc, home, lib, media, mnt, opt, proc, root, run, sbin, srv, sys, tmp, usr, and var. This list looks almost identical whether you are on Ubuntu, Fedora, Arch, or Debian, because it follows the Filesystem Hierarchy Standard (FHS), a specification that defines what belongs where.

Root the directory vs root the user

This is the single most common point of confusion for new Linux users. The word “root” refers to two unrelated things:

1. The root directory (/): a location in the filesystem, the top of the tree.
2. The root user: the superuser account with unrestricted access to the system.

The two intersect at exactly one point: the root user’s home directory is /root, which sits directly under the root directory rather than inside /home like every other user’s home folder. This placement is intentional. If /home lives on a separate partition that fails to mount for some reason, an administrator can still log in as root and fix the problem because /root does not depend on /home being available.

# Go to the top of the filesystem
cd /

# Go to root's home directory (requires root privileges to view contents)
sudo -i
cd /root
ls -la

No drive letters, just mount points

On Windows, plugging in a second drive gives you a new letter: D:, E:, and so on. Linux does something different. Every additional storage device, whether it is an internal partition, an external USB drive, or a network share, gets mounted as a directory somewhere inside the existing tree. This is called a mount point.

# See every mounted filesystem and where it lives
lsblk

# See it as a tree, which makes nesting obvious
findmnt --tree

# A common layout on a desktop machine
# /                the root filesystem, usually on the main SSD
# /boot            a small separate partition for boot files
# /home            sometimes its own partition
# /media/usb-drive an automatically mounted external drive
# /mnt/nas         a manually mounted network share

Because everything hangs off a single tree, a path like /home/colton/Documents/report.pdf works the same way no matter which physical disk actually stores /home. Applications never need to know or care whether /home is on the same disk as / or a completely separate one. This abstraction is a large part of why Linux storage is so flexible: you can move /var to its own disk, mount a fast NVMe drive at /opt, or add network storage at any point in the tree, and every program that reads paths keeps working exactly as before.

Why the top-level layout is standardized

The Filesystem Hierarchy Standard exists precisely so that software, documentation, and administrators can rely on consistent locations. A package manager installing a program on Debian expects to be able to write binaries to /usr/bin and configuration templates to /etc. That same expectation holds on Fedora, Arch, and virtually every other mainstream distribution, because they all follow the same standard for the top level of the tree, even though they differ significantly in what happens further down.

This consistency is why a command like cat /etc/os-release or ls /var/log works regardless of which distribution you are sitting in front of. The paths are not a convention followed loosely; they are effectively guaranteed by the standard.

Practical things to know about root

You cannot delete or rename the top-level directories safely. Unlike a personal project folder, bin, etc, usr, and their siblings are load-bearing. Removing /lib or /usr can leave a system that will not boot, because the kernel and init system expect to find specific files at specific paths during startup.

Disk space at the root level is not always disk space everywhere. If /home or /var lives on its own partition, df -h / will only report space on the partition backing the root directory itself, not the whole system. Running df -h without an argument lists every mounted filesystem and its own usage.

Full disk protection matters most at root. If the partition backing / fills up completely, the system can become unstable: services fail to write logs, temporary files cannot be created, and in severe cases the machine may not boot cleanly on the next restart. This is one reason administrators often put /var (which holds logs and caches that grow over time) on a separate partition, so a runaway log file fills /var instead of taking down the root filesystem.

Frequently Asked Questions

What is the root directory in Linux?

The root directory, written as a single forward slash /, is the top of the entire Linux filesystem tree. Every file, directory, disk, and mounted device on the system exists somewhere underneath it. There is no level above /. It is the ancestor of every other path on the machine, including /home, /etc, and /var.

Is the root directory the same as the root user?

No, these are two different things that happen to share a name. The root directory (/) is a location in the filesystem. The root user is the superuser account with unrestricted permissions. They are related only in that the root user historically has a home directory at /root, which sits directly under the root directory rather than under /home with everyone else.

Why does Linux use / instead of drive letters like C:?

Linux inherited a single unified filesystem tree from Unix. Instead of assigning a new letter to each disk or partition the way Windows does, Linux mounts every additional disk, partition, USB drive, or network share as a directory somewhere inside the existing tree. A second hard drive might appear as /mnt/data or /media/backup rather than as a new top-level entity. This means the path to a file never has to change just because the underlying storage device changed.

What is the difference between / and /root?

/ is the root directory, the base of the whole filesystem. /root is the home directory belonging to the root user, comparable to /home/colton for a regular user named colton. Confusing the two is a common beginner mistake: cd / takes you to the top of the filesystem, while cd /root takes you into the superuser account home directory, which normal users cannot even list without elevated privileges.

Can I delete files directly inside the root directory?

You can, if you have root privileges, but you should not without knowing exactly what each entry does. The directories directly under / (bin, etc, var, usr, and so on) are load-bearing: removing or renaming them can make the system unbootable. Unlike a personal folder, nothing in / is safe to delete casually. Any cleanup at this level should be done through the package manager or with a clear understanding of the Filesystem Hierarchy Standard.

How do I see what is mounted under the root filesystem?

Run findmnt —tree or lsblk to see the full mount hierarchy, including which physical partition backs the root filesystem itself and what other filesystems (like a separate /home partition, a tmpfs at /tmp, or a network share) are mounted at various points beneath it. df -h / shows how much space is used specifically on the partition that backs the root directory, which may be smaller than the total disk if other paths are mounted on separate partitions.