The following hopefully is not too far from the truth, memory is somewhat
> It says "Install GRUB with GRUB.CFG on DEVICE, which is assumed
> to be mounted on MOUNT-POINT."
> Does it mean "Install GRUB (with GRUB.CFG on DEVICE), which is
> assumed to be mounted on MOUNT-POINT"
> or "Install (GRUB with GRUB.CFG) on DEVICE, which is assumed to
> be mounted on MOUNT-POINT"?
I'm not sure I understand your question, but I guess it would be the second
> Usually I install grub to a drive, not a specific partition. My bootloader
> says (grub-configuration (device "/dev/sda")) and that seems to work fine.
Yep, grub is installed as a MBR (Master Boot Record, first 512 bytes of the
> But the GRUB.CFG is on a partition. Which one?
The one holding (typically) /boot (which often is a separate
partition, or / if not),
but that is only default values, /path/to/grub.cfg can be specified by CLI args.
> It seems certainly able to find out where - and it all works fine.
> So if someone knows how that works, exactly, please clarify the comment :)
Grub knows filesystems, and has find functionality, unlike its
which at update time registered the disk block numbers to read at boot time, it
was fragile, and you better remember to update it when you changed anything
> It's a similar situation with U-Boot - only I don't think that it's
> permissible to
>install u-boot onto a partition at all. Its config file yes. Its executable?
I'm new to uboot, so can't help with that one.
Hope it helps.