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