Hi Pascal,
I wonder if it is possible to make Grub self documenting in a useful
way?
Even as a very low level coder, I have been confused as to what Grub is
doing and trying to do and what options are available and how to use them
and why the boot process did not do what I expect and how to fix it?
Another 'problem' that would be very useful to 'solve' is what I call
the 'chain' problem.
I have a memory stick or hard drive with a bunch of say .isos or saved
binary images on it. I am running in Linux version A. I would like to say,
'boot this .iso', as the main OS.
I also design low level hardware. So far, I have only been able to get
the latest version of Kicad to compile and run under antiX!
So I want to start with say Knoppix and then 'chain' to antiX to do
some PCB work. It would be nice to 'chain' back to the original OS, but a
reboot is probably a much simpler and more reliable way to do that!!
Kinda off thread I suppose?
Playing with Grub as got to be a real nightmare!!
Anyways, thanks for your considerable efforts and help.
warm regards,
John - Concord, NH
On Sun, 8 Oct 2017, Pascal Hambourg wrote:
Note : "stages" are GRUB legact concepts which do not exist any more in
GRUB. What you are referring to is the core image.
Le 06/10/2017 ? 22:05, Quard a ?crit :
I'm assuming this extra code comes from the appropriate GRUB2 modules
located in /boot/grub/i386-pc/ folder i.e. luks.mod, cryptodisk.mod,
gcry_sha512.mod, etc. If so, am I safe to assume that other modules can
also be exported into the embedded area (provided they are needed)?
Yes, with the --modules= option passed to grub-install.
The following line was added to /etc/default/grub:
GRUB_TERMINAL_INPUT="at_keyboard"
I am not sure that grub-install uses that variable.
Custom commands were added to /etc/grub.d/40_custom:
#!/bin/sh
exec tail -n +3 $0
insmod keylayouts
keymap /boot/grub/si.gkb
This has not effect on the core image, only on grub.cfg generated by
update-grub.
If you want the core image to use an embedded config file, I you can
generate the core image with grub-mkimage with the option --config=.
IIUC, the embedded config file must end with
insmod normal
normal
which is what the core image normally does without an embedded config file.
To include other files (such as si.gkb) in the core image you can embed
a memdisk image with --memdisk=. The device name is (memdisk).
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
