On Sun, Oct 12, 2025 at 4:19 PM Casey Jao via devel <[email protected]> wrote: > > >macOS and windows are not a good example. Those systems effectively > control the full stack and dictate what is supported and allowed, > starting at the firmware level, through the boot loader, the OS, the > file systems, etc. This is very different from us, where we support > a wide range of machine types and have to work with the firmware written > with the primary goal of supporting _other_ operating systems. > > This may be true for MacOS but Windows boots from the same UEFI firmware that > boots Linux systems. Windows faces the same hardware diversity that Linux > faces. And the last time I checked, Windows allocates a mere 100mb for the > EFI system partition[1]. Everything else is NTFS. What is Windows doing right? > > [1]https://www.terabyteunlimited.com/kb/kb-articles/standard-windows-10-partitions-for-mbr-gpt-disks/
We do it the same way Windows does: the bootloader includes filesystem drivers. ReactOS does the same thing[1] as does Quibble[2]. Incidentally, macOS does the same thing: their boot chain includes APFS drivers on x86 for older Intel Macs. [1]: https://github.com/reactos/reactos/tree/master/boot/freeldr/freeldr/lib/fs [2]: https://github.com/maharmstone/quibble -- 真実はいつも一つ！/ Always, there's only one truth! -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
