Video Summary - LINUX isn't Hard Once You Understand This (File Directories)

Main ideas / lessons

Linux uses a single unified filesystem tree rather than separate drive letters (e.g., no C:/, D:/).
The entire filesystem starts at the “root” directory, represented by /. Everything (files, folders, devices, drives) fits somewhere in this tree.
Learning Linux folders becomes easier when you remember them by purpose/category rather than memorizing names randomly.
Many Linux concepts (like hardware access) are built on the idea that “almost everything is treated as a file.”
Some directories hold persistent data, while others hold dynamic or temporary data that may change or disappear.

/ (root directory)
- The starting point of the entire Linux filesystem tree.
- Think of it like the trunk of a tree: all paths extend from here.
- Unlike Windows, storage is attached into this tree rather than assigned separate drive letters.
/home
- Stores user files.
- Example: if the user is John, his folder is typically /home/john.
- Contains documents, downloads, pictures, videos, projects, and account-related files.
/root
- Often misunderstood: it is not the root of the filesystem.
- It is the home directory for the administrator/root user (the “root” account).

/bin
- Contains essential executable commands (binaries) needed for normal operation.
- Examples: ls, cp, mv, cat, mkdir, etc.
- Framed as a “toolbox” for Linux to operate.
/sbin
- Contains system/administrative utilities.
- Examples mentioned as categories: networking, disk management, boot, and system recovery.
- Typically used more by system administrators than regular users.
/usr
- Not “user” in origin; relates to Unix system resources.
- Holds most installed software and supporting resources:
  - applications
  - libraries
  - documentation
  - development tools
  - shared resources
- Example: /usr/bin contains many executable programs.
/lib (shared libraries)
- Stores reusable shared code that many applications use.
- Purpose: avoids duplicate code in every application and makes updates easier.
- Concept: shared “building blocks” applications borrow.

/etc
- Stores system and application configuration files.
- Examples: network settings, SSH config, DNS config.
- Memory aid: “/etc is the settings folder for your entire operating system.”
/var
- “Variable” data—files that constantly grow/change.
- Examples:
  - system logs and application logs
  - email queues
  - databases
  - printer queues
  - cache files
/var/log
- Called out as a first place to check when troubleshooting.
- Contains logs that help explain what the system has been doing.

/tmp
- For temporary files created by applications while running.
- Often cleaned automatically on reboot.
- Lesson: don’t store important data in /tmp unless you accept possible loss.

/media
- Common location for automatically mounted devices (e.g., USB drives, DVDs).
/mnt
- Common location used by administrators for manual mounting (disks, network shares, other storage).
Key conceptual difference from Windows
- Linux doesn’t assign a drive letter; it attaches storage into the directory tree.

/dev
- Devices appear as files (a file-based hardware interface).
- Example: hard drive might appear as /dev/sda.
- Lesson: allows programs to interact with hardware using the same style of interface as files.
/proc
- A virtual filesystem created by the kernel (not stored on disk as normal directories).
- Contains live runtime info:
  - running processes
  - CPU usage
  - memory
  - system configuration
- Monitoring tools often read from /proc.
- Framed as a “live dashboard.”
/boot
- Contains files required to start Linux:
  - Linux kernel
  - bootloader files
  - startup configuration
- Without /boot, the system can’t boot.