On Sun, 13 Jun 2021 22:34:30 -0400, Walter Dnes wrote: > > > 1) Is "insmod extfs3" necessary? I've built extfs3 into the > > > kernels. > > > > If the kernel is on an ext3 filesystem, yes. This is GRUB's module, it > > uses it to read an ext3 filesystem in order to load the kernel. > > Some confusion here. "fdisk -l" on my new machine gives... > > Device Start End Sectors Size Type > /dev/sda1 2048 526335 524288 256M EFI System > /dev/sda2 526336 1886416303 1885889968 899.3G Linux filesystem > /dev/sda3 1886418352 1953523119 67104768 32G Linux filesystem > > The EFI Systen partition is fat32. The web examples I read show > "insmod <filesystem>" matching the filesystem of the linux system being > booted. But all entries in grub.cfg on my new machine are "insmod fat". > I wonder if the web documentation was referring to BIOS-booting > machines. grub.cfg would be sitting on an xfs or extfs3 or whatever > file system, and would need to read it off that filesystem.
If /boot is on the ESP, i.e. FAT, you won't need the ext3 module. I suspect part of the auto-configuration setup is "load everything we might need". It's not really an issue since the memory used by the modules should be freed when GRUB exits. The bloatedness is a combination of the must run everywhere defaults and using a full bootloader when you only need a minimal boot manager. These days, I only use GRUB on BIOS systems. -- Neil Bothwick No, you *can't* call 999 now. I'm downloading my mail.
pgpIc98Xe9Yze.pgp
Description: OpenPGP digital signature
