Filesystem Hierarchy

Linux presents mounted filesystems as one directory tree rooted at /. The Filesystem Hierarchy Standard, or FHS, gives many directories conventional roles, but distributions, containers, immutable systems, and local policy can differ. Inspect the actual host before relying on a path.

$ ls -ld /*

Root and Essential System Paths

• / is the root of the visible filesystem tree.
• /etc holds host-specific system configuration. It can contain executable helper or startup scripts, so it is inaccurate to say it never contains executable content.
• /boot holds boot-related files such as boot-loader data and, on many systems, kernels and initial RAM filesystem images.
• /bin and /sbin traditionally contain essential user and system-administration commands.
• /lib and architecture-specific variants traditionally contain essential shared libraries and loader components.

Many current distributions use a merged /usr layout in which /bin, /sbin, and /lib are symbolic links into corresponding /usr directories. Use command discovery and package records rather than assuming whether a path is a physical directory or link.

CheckWhich directory conventionally contains host-specific system configuration?

/proc /etc /dev

Distribution and Local Software

• /usr contains the main shareable, largely read-only operating-system and application hierarchy, including commands, libraries, and architecture-independent data.
• /usr/local is reserved for software and data installed by the local administrator outside the distribution's normal /usr management.
• /opt can hold add-on application packages in self-contained subtrees.

Despite its name, /usr is not where individual users' personal files normally live. Distribution package managers commonly own large parts of it, so copying locally compiled files into /usr/bin can conflict with managed packages.

CheckWhich prefix is conventionally reserved for software installed locally outside distribution-managed /usr content?

/usr/local /proc/local /dev/local

User and Service Data

• /home conventionally contains non-root users' home directories, though directory services and local policy can place them elsewhere.
• /root is the root account's conventional home directory.
• /srv is intended for site-specific data served by this system.

A home path comes from account information, not merely from joining /home with a username. Use getent passwd USER or the shell's resolved home rather than hard-coding assumptions.

CheckWhat is the root account's conventional home directory?

/home/root /root /usr/root

Variable, Runtime, and Temporary Data

• /var contains variable data such as logs, caches, spools, and application state. System logs commonly appear under /var/log, though some systems rely primarily on a journal interface.
• /run contains volatile runtime state for the current boot, such as sockets, service state, and PID files. It is normally recreated at boot.
• /tmp is for temporary files and is commonly writable by all users with sticky-bit protection.
• /var/tmp is intended for temporary files that should survive longer than files in /tmp.

Cleanup policy for /tmp varies; do not assume files persist until reboot or are always deleted at reboot. Applications should use secure temporary-file creation rather than predictable names.

CheckWhich path conventionally stores system log files?

/etc/log /var/log /boot/log

Devices, Kernel Interfaces, and Mount Points

• /dev contains device nodes and related runtime links.
• /proc exposes process and kernel interfaces through procfs.
• /sys exposes kernel objects, devices, drivers, and attributes through sysfs.
• /media is commonly used for automatically mounted removable media.
• /mnt is a conventional location for temporary administrator mounts.

These are conventions, not permission grants. Mounting another filesystem on a nonempty directory temporarily hides the directory's previous contents until unmounted.

CheckWhich path normally exposes the kernel device model through sysfs?

/srv /sys /opt

Use Navigate the Filesystem in Linux to inspect these paths, and Find Files and Commands in Linux to avoid relying on guessed locations.

Summary

You can now relate major Linux paths to their intended roles while allowing for real system variation.

1. Start from the unified tree rooted at /.
2. Separate configuration, managed software, local software, and variable data.
3. Distinguish homes and service data from runtime state.
4. Recognize /dev, /proc, and /sys as special runtime interfaces.
5. Inspect symlinks, mounts, account data, and distribution policy before assuming a layout.