When designing a computer system, developers must determine a fundamental anchor point for users to manage internal computer resources. This anchor dictates how user interfaces are designed, what operations users can perform, and how those operations are executed. Designers have four potential anchor options: The CPU Memory (RAM) External storage Input/output (I/O) devices Early computer architects chose external storage as the anchor for both user operations and system interfaces. The reasoning is straightforward: external storage persistently retains critical data resources, including executable program files and various other data files. To simplify user interaction and streamline management of resources on external storage, designers created a dedicated management mechanism known as the file system. A file system organizes external storage resources in a way that aligns naturally with human thinking patterns, modeled after physical office folder logic: a folder can hold both individual files and additional subfolders, and files/folders can be assigned attributes for administrative purposes. This matches the familiar layout you see when browsing files on the Windows operating system, as illustrated in the corresponding diagram. Both logically and visually, this structure closely mirrors physical folders from everyday life. That said, the file system implemented within an operating system can store