C:\\Users\\Shekhar\\Documents\\notes.txt Windows usually starts an absolute path from a drive letter.
M04 - File System Architecture: How Your OS Organises Data
Understand the map of the file system well enough to recognize Windows drive-letter paths, Linux root-tree paths, and the difference between a file name and the data behind it.
File System
File System Architecture: How Your OS Organises Data
Understand the map of the file system well enough to recognize Windows drive-letter paths, Linux root-tree paths, and the difference between a file name and the data behind it.
35 min BEGINNER BOTH Field-verified
Before this lesson
What you should learn
- Understand the map of the file system well enough to recognize Windows drive-letter paths, Linux root-tree paths, and the difference between a file name and the data behind it.
Visual model
Concept to practice path
Each lesson is meant to move from an idea, to an example, to a safe practice step.
Open the full visualWhy This Matters Before Navigation
You are about to spend a lot of time moving around the file system.
Before that, you need a clear map in your head.
If the map is fuzzy, navigation becomes memorized movement. If the map is clear, navigation becomes reasoning.
Visual model
One idea, two path styles
/home/shekhar/Documents/notes.txt Linux usually starts an absolute path from one root tree.
The mental job is the same on both platforms: identify where you are, where the target lives, and whether the path is absolute or relative.
Windows and Linux Draw the Map Differently
Windows: separate drive trees
Windows paths usually begin with a drive letter, such as:
C:\Users\YourName\DocumentsD:\Backups
Each drive is its own top-level tree.
Linux: one root tree
Linux paths begin at exactly one place:
/home/yourname/Documents/var/log/etc/ssh
Everything hangs from root: /.
That difference is the first thing beginners need to internalize.
One simple test
If a path starts with C:\ or another drive letter, think Windows-style absolute path. If it starts with /, think Linux-style absolute path.
How Linux Handles Extra Storage
When a new drive appears in Windows, it often gets a new drive letter.
When a new drive appears in Linux, it is usually mounted into the existing tree. That means the drive becomes reachable through a folder path such as:
/mnt/usb/media/yourname/MyDrive
The important beginner idea is not the exact command yet. The important idea is:
Linux keeps one tree and attaches storage into it.
Visual model
How the OS reaches your file
Layer 1 Path
The human-readable address you type or click.
Layer 2 Directory tree
The folder structure that helps the OS find the target.
Layer 3 Filesystem
The structure that stores metadata and file contents.
Layer 4 Storage device
The physical or virtual place where the filesystem lives.
Storage Safety Model
Keep these layers separate in your head: file or folder path, mounted filesystem, partition, and physical device. Most destructive storage mistakes happen when people think they are touching one layer but are really changing another.
File Names Are Labels, Not the Whole Story
Humans care about names like project.txt.
The operating system cares about metadata and where the real data lives on disk.
On Linux that idea shows up as an inode. On NTFS there is a similar metadata structure in the file system.
You do not need to memorize low-level storage structures today. You only need this model:
- the name helps humans find the file
- the OS tracks more than the name
- permissions, ownership, timestamps, and data location matter too
Extensions and File Identity
Windows often leans heavily on file extensions such as .txt, .exe, or .jpg.
Linux tools often inspect the file content itself, not only the extension.
cmd /c assoc .txt
file /etc/passwd
The lesson is not that one system is smarter. The lesson is that file identity can be decided in different ways.
Why Hashing Belongs in a Foundation Module
Hashing matters because downloads can be corrupted or tampered with.
A hash gives you a fingerprint for a file.
If the file changes, even slightly, the hash changes too.
"hello" | Out-File test.txt Get-FileHash test.txt -Algorithm SHA256
echo "hello" > test.txt sha256sum test.txt
You will use this later for real software verification.
What To Keep and What To Ignore For Now
Keep these ideas:
- Windows often starts absolute paths with a drive letter.
- Linux starts absolute paths with
/. - Linux mounts storage into the tree instead of creating drive letters.
- A file name is only one part of how the OS tracks a file.
- Hashes help verify integrity.
Ignore for now:
- deep inode internals
- NTFS internals
- advanced mount configuration
You do not need those details yet to navigate confidently.
Before You Move On
You are ready if you can:
- tell whether a sample path is Windows or Linux
- explain what mounting means at a high level
- explain why the file name is not the whole story
That is enough for the navigation modules.
Learning loop
Recall it, check it, then practice it.
Do this before moving on. It turns reading into memory and safer action.
- Can you explain the difference between a Windows drive tree and the Linux root tree?
- Can you explain what problem hashing solves without getting lost in low-level details?
- Explain the shape of paths on Windows and Linux and identify whether a sample path is absolute or not.
- Describe what mounting means and why a file name is only one part of how the OS tracks a file.
Review again after 1, 2, 5 days.
What to do next
Best next step PracticeUse the matching lab or keep building skill in practice.