Exercise 2: Why UEFI's Bootloader Is an Ordinary File, and BIOS's Isn't — Possible Solution
====================================================================

Explanation:

The chapter's own compare-table names the core difference directly:
UEFI is filesystem-aware, while BIOS is not. UEFI firmware can
actually read a real filesystem -- specifically the FAT-formatted EFI
System Partition -- the same way an operating system reads a
filesystem: by understanding directories, filenames, and file
contents as structured data. Because of this, a UEFI bootloader is
stored as a genuine, named .efi file sitting inside a normal directory
structure on that partition, exactly like any other file you could
list, copy, or inspect.

BIOS has no such capability. It doesn't understand filesystems at
all -- it simply reads the raw bytes sitting in the very first sector
of the disk (the Master Boot Record) and executes them directly, with
no concept of "a file," "a directory," or "a filesystem" involved
anywhere in that process. There's no file to list or inspect in the
BIOS case -- just a fixed-size block of raw executable code sitting at
a fixed physical location on the disk, invisible to any normal
file-browsing tool because there's no filesystem structure there for
such a tool to read.

WHY THIS WORKS AS AN ANSWER
------------------------------
This traces the difference directly back to the chapter's own
filesystem-awareness distinction, explaining concretely what it means
for UEFI to "read a filesystem" versus BIOS "reading a raw sector,"
rather than just restating that one is inspectable and one isn't.