On Wed, 2014-03-19 at 15:57 -0700, Andrew Lutomirski wrote: > On Wed, Mar 19, 2014 at 3:53 PM, Lennart Poettering > <mzerqung@xxxxxxxxxxx> wrote: > > On Wed, 19.03.14 13:13, Chris Murphy (lists@xxxxxxxxxxxxxxxxx) wrote: > > > >> I agree, although I go farther. The EFI System partition doesn't > >> scale, isn't resilient, can neither be mirrored nor easily sync'd > >> (multidevice boot). It should be considered a pre-boot and OS > >> installer domain only. > > > > You know, the ESP is actually FAT, one of the simplest, best-understood, > > most used, and most stable file systems around. Sure, one can always > > break things, but it is simply misguided to believe that this is the > > part that will likely break and that we really really really need to > > stay away from, and not the later parts of the boot that involve grub > > and raid, and yuck. > > > > You know, by creating a chain of many steps where you first go for > > the ESP, and then follow that by another boot partition and so on, you > > just make things more complex. > > More complex than trying to mirror a FAT ESP partition across multiple > boot disks, keeping it properly synchronized, because RAID isn't > supported? You can in theory just have a bunch of RAID-1 (mirrored) ESPs, because of how RAID-1 works; each individual member can also be mounted as if it was just a plain old partition, which is how the firmware will mount it. The anaconda devs have thought about this, and are planning to implement it. On the UEFI side you just write entries for each of the ESPs into the EFI boot manager. If one of them fails, then the firmware will boot from the next in line. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
