Under the Hood
Loading visualizer…
DNSresolving host
TCPconnecting
TLShandshake
HTTPrequesting
Initializing Sorting Algorithms...
Sorting
Trees
Graphs
Preparing interactive visualizations...
Under the Hood
Loading visualizer…
Blocks, inodes, directory entries, path resolution, links, the page cache — and why fsync exists
You type /home/archi/notes.txt and a file appears. It feels like the path is an address — like the disk has folders in it. It does not. A disk is one flat array of numbered, fixed-size blocks, and absolutely nothing down there stores that string as a unit. The hierarchy is a fiction the filesystem maintains on top of a flat array.
On-disk structures
Active Recall
Where is a file's name actually stored?