برنامه‌نویسی به زبان پایتون |‌ How the File System Works in Unix-Based Systems

Main ideas and concepts

Unix-based systems and where this course fits

• The lesson focuses on how the Unix file system works for Unix-based operating systems.
• Unix originated in 1970, and many operating systems branched from it, including:
  • Linux
  • macOS
  • FreeBSD
• Later lessons will cover terminal commands and file operations in more detail (especially for Linux/Python specialization).

Using a terminal across operating systems

• The video emphasizes using a terminal—a black-screen interface.
• This applies across multiple environments, including:
  • Windows (e.g., dual-boot or other setups)
  • Linux
  • macOS
• In “99%” of cases, what’s taught will work similarly across Unix-like terminals; if exceptions exist, they’ll be noted.

Core Unix file system mental model: one root

• Unlike Windows, Unix has no drive letters (no C:, D:, etc.).
• Instead, everything is organized under a single root directory:
  • The root directory is / (a forward slash).
  • Think of it like a “Big Bang”: the entire filesystem tree branches from /.
• Key implication:
  • When you “navigate,” you move through directories that are all ultimately under /.

Typical top-level directories in Unix-like OSes

Under /, common directories help organize system functions and user data. Examples include:

• bin: binary executables
• boot: boot-related files
• dev: device-related files
• etc: system configuration
• lib: libraries needed by the system/programs
• home: per-user workspaces (most used by users)
• media: mounted media locations
• mnt (mentioned later): mount point for external devices (e.g., flash drives)
• usr: additional user/system program resources

Each directory exists for a specific purpose, somewhat analogous (loosely) to how Windows organizes folders.

Home directory and the per-user structure

• /home contains individual user directories.
  • For users like John and Mary, you’d see:
    • /home/John
    • /home/Mary
• The video contrasts Linux vs macOS slightly:
  • Linux typically uses /home/<username>
  • macOS uses a similar concept, but the internal placement/mapping may differ slightly
• The lesson introduces:
  • ~ (tilde) meaning the current logged-in user’s home directory
  • Example concept: cd ~ moves to the current user’s home directory

Directory navigation equivalence

The lesson conveys this conceptual equivalence:

• cd ~ ≈ cd /home/<current-username> (for the user whose shell is currently logged in)

Filesystem tree visualization

• The filesystem is described as a tree:
  • / is the top/root
  • Other directories (like bin, etc, boot, home, etc.) branch “below” it

---

Windows vs Unix differences emphasized

Path separator

• Windows uses backslash \.
• Unix-like systems use forward slash /.

Drive letters vs mounts

• Windows typically shows storage as drive letters (e.g., C:, D:).
• Unix-like systems use mounts instead of drive letters:
  • External drives (e.g., USB) appear as mounted subdirectories
  • Commonly under /mnt (as mentioned in the video)

Case sensitivity

• Windows: names are typically not case-sensitive.
• Unix-like systems: names are case-sensitive.
  • Example implication: Ali and ali can be different directories.

Permissions / access control

• Unix permissions determine things like:
  • read, write, modify, move, etc.
• The video relates this to controlled access (e.g., read-only vs edit permissions for a shared document).
• It notes permissions differ from Windows, though details aren’t expanded here.

---

Instructions / methodology presented (navigation concepts)

Even though exact commands come later, the video establishes a few navigation practices:

• Assume one unified filesystem
  • Treat every path as rooted at /
• Use terminal navigation under /
  • To go to root: cd / (example shown conceptually)
• Understand the home directory
  • Typical Linux-like home: /home/<username>
  • Current user’s home: cd ~
• Recognize /home vs macOS mapping differences
  • The idea of per-user home is the same, but internal placement can differ slightly between Linux and macOS
• Expect no drive letters
  • Don’t look for C:/D:; storage shows up via mount points (e.g., /mnt)

---

Lessons / takeaways for learners

• The main challenge for beginners is shifting from Windows-style thinking (drives and graphical structure) to Unix-style thinking:
  • single root
  • forward slashes
  • case sensitivity
  • permissions
• Understanding these differences helps reduce intimidation:
  • Initial fear is normal, and practice usually makes it fade.
• The next session will focus on what common commands mean and how to work effectively in the terminal (e.g., changing directories and creating/moving files or directories).

---

Speakers / sources featured

• No specific speaker name is provided in the subtitles.
• Source: the course/instructor delivering the lesson (implied as the video narrator/instructor).