Thanks to Chris Gregg for providing this lovely overview motivating the study of this particular filesystem!
Just like RAM, hard drives (or, more likely these days, solid state drives) provide us with a contiguous stretch of memory where we can store information.
Thanks to Ryan Eberhardt for the illustrations and most of the text used in these slides.
/usr/class/cs110/WWW/index.html—to seemingly magic numbers that incidentally identify where the corresponding inodes sit in the inode table.
assign1solution resides in a file named
/usr/class/cs110/staff/master_repos/assign1/imdb.cc. At 51 characters, the name wouldn't fit in an inode.
/usr/class/cs110/example.txt. First, we find the inode for the file
/(which by design is always associated with inumber 1). We search inode 1's payload for the token
usrand its companion inumber. Let's say it's at inode 5. Then, we get inode 5's contents and search for the token
classin the same way. From there, we look up the token