19) rescue and exit failure on qemu
==============================
I think that booting from my computer does not give this error.
If I boot from QEMU and type:
grub> rescue
and then :
grub rescue> exit
it says: FATAL: INT18: BOOT FAILURE
Weird. Can you debug this?
I've checked this again.
If I do this booting from my pc I get the grub2 floppy booting again.
If I do this from qemu the FATAL: INT18: BOOT FAILURE appears again.
I would bet that it is a qemu bios's lack of the 18 interruption.
20) grub rescue help
========================
help : Types the commands and a minimal explanation: OK
help any_command : Types the commands and a minimal explanation: NOT OK
help not_a_command : Types the commands and a minimal explanation: NOT OK
huh?
You boot grub2 and you see
grub>
you type rescue and you see
grub rescue>
and now what it is funny that if you type the help command, an space,
and whatever you want to write it always shows all the commands help.
It may confuse some users as "Grub is not working".
21) grub rescue exit help
===========================
When you are in grub rescue mode and you type help the exit line it's
the following one:
exit exit from GRUB
Should it not prompt ?
exit exit from GRUB rescue
The exit command terminates GRUB and continues the boot process, IIRC.
You are right. Exit from GRUB is right, then.
22) copyright message missing
================================
Why isn't there (when Grub is running) any message about the GRUB
Copyright and the GPL license and that you should have received and this
and that?
Why should there be such message?
This comes from GPL 2:
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type
`show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
Maybe we should implement an 'about' command and run it when booting :) ?
Perhaps, but I don't see the added value.
See above about the GPL.
23) set read only variables
==============================
unset prefix lets me "delete" the prefix variable.
unset root does not let me the "root" variable.
I remember that bash has an option to set read only variables.
Maybe the root variable is a read only variable?
You can easily modify the code. But I do not like making such
variables read-only.
I did not want to make any variable read only. I only wanted to make you
know that the "root" variable was actually a read only variable because
there is no way to delete (unset) it. It always comes to live again.
Is it a normal thing?
adrian15
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel