Every Linux Directory Explained

Windows has C: drives, recovery partitions and the desktop full of shortcuts pointing to folders buried six levels deep. Linux has none of that. Instead, it has one single starting point and everything, every file, every program, every connected device, every USB drive you'll ever plug in lives somewhere inside it. If you've ever opened a Linux terminal and felt completely lost, this is the video that fixes that. Every major Linux directory, what it actually contains and why it exists. The root directory, the trunk of the tree that everything else grows from. Unlike Windows, which assigns separate letters to separate drives, C: for your main disk, D: for a second drive, E: for a USB, Linux absorbs everything into one unified structure. Plug in a USB drive, it doesn't become its own drive, it gets attached somewhere inside the existing tree. Every file, every application, every hardware device, every partition on every hard disk in the machine, your USB drive, eventually connects back to this single slash. It is the starting point of everything. Slash home. This is the directory most users spend their entire time inside without realizing it. Every user account on a Linux system gets its own personal folder under slash home. If your username is Joe, your folder is slash home slash Joe. And inside it lives everything personal: documents, downloads, pictures, projects, configuration files for your apps, your bash history. The system keeps each user's files completely separate from every other user's files, which is why a standard user account can't accidentally delete another user's data. Think of slash home as your personal workspace inside a shared building. The building belongs to everyone, but your office is yours alone. Slash root. This one trips up almost every beginner. There's a folder called slash root inside the file system, and it has nothing to do with the root directory. The slash root is simply the home folder of the root user, the administrator account that has unrestricted access to everything on the system. A regular user's home is slash home slash username. The root user's home is slash root. Two completely different things, sharing a similar name. Slash etc. If you need to change how anything on your Linux system behaves, the answer is almost always inside slash etc. This directory stores configuration files for the operating system and nearly every application installed on it. Network settings, DNS configuration, SSH settings, user account information, scheduled tasks. All live here as plain text files you can open and edit. There are no hidden menus, no registry editors, no graphical panels required. The design philosophy behind slash etc is transparency. Every setting the system uses is a readable file sitting in one place. That's exactly why Linux system administrators can configure a server in minutes once they know where to look. Slash bin and slash usr. Programs have to live somewhere. Slash bin, for binaries, contains the essential command line tools that Linux needs to function at a basic level. Commands like LS, CP, MV, CAT, and MKDIR all live here. These are the tools the system needs even before anything else is loading. Slash usr, Unix system resources, and not user as most people assume, contains the much larger collection of software installed on top of the base system. Thousands of executable programs, libraries, documentation and development tools all live under slash usr. Think of slash bin as the emergency toolkit and slash usr as the entire workshop. Slash var. The name stands for variable. The contents change constantly. Log files, application cache, email queues, database files, printer queues, anything that grows or updates while the system is running lives in slash var. The most useful subfolder for anyone managing a Linux system is slash var slash log, which contains log files for everything the system does. When something breaks, a service crashes, a login fails, a disk error appears, slash var slash log is the first place to look. Slash tmp. Exactly what it sounds like. Temporary files created by applications while they're running land here. Most Linux systems automatically wipe slash tmp on every reboot, which means anything stored here has a lifespan measured in sessions, not days. Applications use slash tmp constantly to write something quickly without committing it to permanent storage. Don't use slash tmp for permanent data. Slash dev. This changes how you think about Linux entirely. In Linux, almost everything is treated as a file. Your hard disk might appear as slash dev slash SDA. Your USB drive as slash dev slash SDB. Your keyboard, your mouse, your terminal, all files living inside slash dev. This design means that programs interact with hardware using exactly the same file-based methods they use for regular data, which gives Linux a consistency and flexibility that Windows has never fully matched. It's abstract until the first time you redirect output to a device file and realize the entire operating system just made sense. Slash proc. Slash proc doesn't exist on your hard disk. It is a virtual directory created by the Linux kernel. It contains real-time information about everything currently running, active processes, CPU usage, memory consumption, system configuration, hardware details, monitoring tools, performance analyzers and diagnostic scripts. All read from slash proc to get a live picture of what the system is doing right now. Shut the machine down and slash proc disappears. Boot it back up, and it's recreated from scratch. It is less a folder and more a live window directly into the kernel itself. And that's every major Linux directory, finally.