On Wednesday, 6 December 2023 14:27:21 GMT [email protected] wrote: > On 12/6/23 04:31, Michael wrote: > > On Tuesday, 5 December 2023 23:53:23 GMT Peter Humphreey wrote: > >> On Tuesday, 5 December 2023 19:35:11 GMT Michael wrote: > >>> Your boot partition is /dev/nvme0n1p1 and its mountpoint is /boot. You > >>> must create this partition with the appropriate EFI System type (in > >>> gdisk > >>> use EF00). > >>> > >>> The /efi directory must be at the top of the /boot partition filesystem, > >>> accessible via /boot/efi. > >> > >> I've been operating that way for some years, but I have reason to believe > >> that things have changed. I'll start a new thread tomorrow. > > > > Both Peters are right and my previous answer was wrong for Thelma's > > usecase, the /boot directory must be on a linux fs which understands > > symlinks *if vmlinuz is used* - this is because the ESP partition's FAT > > fs cannot use symlinks. > > > > The /efi directory *must* be on a FAT fs and contain the grubx64.efi, or > > any other bootloader *.efi image. > > > > If kernels are copied manually and vmlinuz symlinks are not used then a > > FAT > > partition with mountpoint on /boot and containing the /boot/efi directory > > will work as intended. > > Thanks for Peters explanation now it is clear to me how it works.
I think there's some misattribution here: I haven't explained anything in this area - indeed I have some questions of my own. > But I have a question, in Gentoo manual hand book > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks > the instruction is to create 1 GiB partition for /efi It's a suggestion, not an instruction; you don't have to follow it. > Why so large, do others file system need it so much? > In my case /efi take only 1% > Filesystem Size Used Avail Use% Mounted on > /dev/nvme0n1p1 1022M 280K 1022M 1% /efi The idea is that you may want to install another system later, which may want to install its own code in /efi. By all means shrink it if you think that's unlikely and you need the space. Gparted on SysRescCD is ideal for this. -- Regards, Peter.
