On Thu, 15.05.14 18:13, Matthew Garrett (mjg59@xxxxxxxxxxxxx) wrote: > On Wed, May 14, 2014 at 09:54:58PM +0200, Lennart Poettering wrote: > > On Wed, 14.05.14 19:47, Matthew Garrett (mjg59@xxxxxxxxxxxxx) wrote: > > > > > On Tue, May 13, 2014 at 10:27:54AM -0400, Matthias Clasen wrote: > > > > > > > We really need to use the boot loader spec by default. Is there any > > > > reason why the support for it was added to grub, but not enabled ? > > > > > > The full spec is incompatible with standard practices for the EFI system > > > partition, > > > > Humm, is it? Is this about loving /boot/efi so much? > > Basically. There's a bunch of places that would need to be changed, and > doing it meaningfully involves doing that across multiple distributions. > I mean, we *could*, but it's a pain. Well, thankfully the boot loader is a giant pale of chaos anyway... Also, we kinda have experience with correcting these kind of things cross-distro thee days... > > > and especially incompatible with the way we handle Mac > > > hardware, so adoption is unlikely. > > > > Humm, what? the spec is used (in its gummiboot implementaiton) everyday > > on macs, not sure what you are referring to. > > The bootloader needs to be on an HFS+ partition to appear in the OS X > boot preferences. dunno. gummiboot appears to work fine to cross boot between osx and linux. It will automatically discover macos installations even, so everything should be totally fine... > > > The boot fragments are more > > > attractive, but don't currently let us express the full set of > > > configuration that we support (there's no way to specify chainloading > > > another bootloader, for instance). These seem fixable, but nobody's > > > currently fixing them. > > > > The boot load spec stuff is not supposed to be necessarily exclusive. If > > you want stuff like chainloading or memory checking or whatever else, > > then i recommend simply doing that outside of the spec/drop-ins, and > > leave the drop-ins for kernels and EFI binaries only. > > Then we have configuration split over two completely different formats. > It's kind of unappealing. Nope. Because the chainload/memcheck stuff never changes after you installed the boot loader once. The kernel stuff changes all the time... This means the first distro (the one that owns the boot loader) has to create the chanload/memcheck config once, and from then one everything else is just done via BLS snippets, and all the distros can drop things to the right place without ever touching the original chainload/memcheck stuff... Note that the chainload thing is a hack for MBR systems. On EFI boot loaders like gummiboot actually automatically discover windows and macosx and add it to its menu, not requiring any manual config for that. Lennart -- Lennart Poettering, Red Hat -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/desktop
