On Tue, Sep 18, 2018 at 1:01 PM, Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote: > 18.09.2018 21:57, Chris Murphy пишет: >> On Tue, Sep 18, 2018 at 12:16 PM, Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote: >>> 18.09.2018 08:37, Chris Murphy пишет: >> >>>> The patches aren't upstream yet? Will they be? >>>> >>> >>> I do not know. Personally I think much easier is to make grub location >>> independent of /boot, allowing grub be installed in separate partition. >>> This automatically covers all other cases (like MD, LVM etc). >> >> The only case where I'm aware of this happens is Fedora on UEFI where >> they write grubenv and grub.cfg on the FAT ESP. I'm pretty sure >> upstream expects grubenv and grub.cfg at /boot/grub and I haven't ever >> seen it elsewhere (except Fedora on UEFI). >> >> I'm not sure this is much easier. Yet another volume that would be >> persistently mounted? Where? A nested mount at /boot/grub? I'm not >> liking that at all. Even Windows and macOS have saner and simpler to >> understand booting methods than this. >> >> > That's exactly what Windows ended up with - separate boot volume with > bootloader related files. The OEM installer will absolutely install to a single partition. If you point it to a blank drive on BIOS it will preferentially create a "system" volume that's used for booting. But it's not mandatory. On UEFI, it doesn't create a "system" volume, just "recovery" is ~500M and "reserved" 16M. The reserved partition is blank unless you've done some resizing on the main volume. The recovery volume contains Winre.wim which is used for doing resets. If you blow away that partition, you can still boot, but you can't do resets. -- Chris Murphy
