# Filesystem Hierarchy Standard

> 📌 [FHS - Filesystem Hierarchy Standard](https://refspecs.linuxfoundation.org/FHS_3.0/fhs/index.html)

![Filesystem Hierarchy Standard](/files/OATA6aHoSzd7xXQSTGK0)

* Most Linux distribution follow the [**Filesystem Hierarchy Standard**](https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard) as a reference for the layout of the Unix system.

```bash
# Show the standard with the command:
man hier
```

* All files and directories appear under the primary hierarchy root and entire file system root directory **`/`**.

**`/bin`** - stores important executable programs (binaries).

**`/boot`** - boot loader files used to boot the system (kernel, initrd).

**`/dev`** - device files for physical devices (mouse, hdds, standard in/out, standard error).

**`/etc`** - local system-wide configuration files for programs.

**`/home`** - personal directories of all users.

**`/lib`** - essential shared libraries for binaries to run

**`/media`** - mount point for removable media.

**`/mnt`** - mount point for temporary file systems.

**`/opt`** - additional software not found in the distribution repositories, custom utilities and packages, accessible to everyone.

**`/proc`** - information about running processes, the kernel and system hardware.

**`/root`** - home directory for the root user.

**`/sbin`** - essential binaries available only to the root user.

**`/tmp`** - temporary files used by the system, usually cleared on boot, not for important storage.

**`/usr`** - contains important subdirectories, read-only data programs.

**`/var`** - contains dynamic program data (logs, spool), troubleshooting log files.

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://blog.syselement.com/tcm/courses/linux-101/3-filesystem/fs-hierarchy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.