• Undesirable behaviour for manual partitioning with GPT+UEFI


    When running the installer in UEFI mode and using manual partitioning with a gpt table, the installer insists on having the fat32 efi system partition mounted as /boot

    I don’t think this is the desired behaviour, as it means that also grub config files, kernel, ramdisk image etc go on the fat32 partition. Instead the usual thing is for the system partition to be mounted at /boot/efi such that it only contains the efi images/etc needed to start grub. (Which can then either live on a seperate /boot partition with a more modern file system or else simply in /boot on the root filesystem)

  • When running the installer in UEFI mode and using manual partitioning with a gpt table, the installer insists on having the fat32 efi system partition mounted as /boot

    I don’t think this is the desired behaviour, as it means that also grub config files, kernel, ramdisk image etc go on the fat32 partition. Instead the usual thing is for the system partition to be mounted at /boot/efi such that it only contains the efi images/etc needed to start grub. (Which can then either live on a seperate /boot partition with a more modern file system or else simply in /boot on the root filesystem)

  • Actually that is the intended behavior. It may change in the future but for now it’s what we’ve chosen.

    Cheers!

Posts 3Views 799
Log in to reply