Stefan Reinauer wrote:
Vesa Jääskeläinen wrote:
Stefan Reinauer wrote:
Vesa Jääskeläinen wrote:
Idea of the rescue shell is load other modules in case grub itself
cannot find them. It provides thin layer of tools so user is able to
find them.

Personally I would like to keep this functionality in core.img.
So, how is the "rescue shell" different that "grub itself". Why would it
find modules that "grub itself" does not find?
User can use ls and insmod commands to load those modules from disk.
Most common problem with GRUB legacy is that it just prints GRUB on
screen. This will kinda remove that problem as user still has a way to
boot his system with some keypresses.
So the rescue shell has filesystems and a shell? Is the "advanced
console interface" so huge that it can't live with the shell and the
filesystems in the rescue shell?

It has anything what core provides. If by this you get core smaller then I am all for it. If it makes it larger then I would propose to find free space from somewhere else. Core.img just have to be standalone application so user can do recovery if something gets wrong in installation or something else.

I do not know how well grub scripting is integrated to normal mode so check that out first.



_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to