Here is another patch for the commands description, where all is done is
an addition of explanations.
--
Thierry LARONDE <[EMAIL PROTECTED]>
10, rue du Bel Air, 74000 ANNECY - FRANCE/ Tel : 33.(0)4.50.67.46.61
/home du SDF (Site Debian Francophone) : http://sdf.polynum.org/
--- docs/grub-new.texi Sat Feb 3 20:56:15 2001
+++ docs/grub-new.texi Wed Feb 7 20:35:18 2001
@@ -1701,9 +1701,16 @@
In this chapter, we list all commands that are available in GRUB.
Commands belong to different groups. A few can only be used in
-the global section of the configuration file (or ``menu''); most
-of them can be entered on the command-line and can be either used
-in the menu or in the menu entries.
+the global section of the configuration file (or ``menu''), because
+these commands tell GRUB how to behave for the menu interface; thus we
+call them ``menu-specific''.
+The other ones are simply all the commands that one can use in the
+command-line. If you think about the configuration file as a ``script'',
+all the commands can be used in this script, but not all can be used
+anywhere in the file. The ones usable both on command-line and anywhere
+in the configuration file are tagged: ``command-line and menu''. The ones
+usable both in command-line and as part as an entry in the menu file are
+tagged : ``command-line and menu entry''.
@menu
* Menu-specific commands::
@@ -1814,7 +1821,7 @@
@node Command-line and menu commands
@section The list of command-line and menu commands
-Commands usable both in the menu and in the command-line.
+Commands usable both anywhere in the menu and in the command-line.
@menu
* bootp:: Initialize a network device via BOOTP
@@ -2232,8 +2239,17 @@
@node Command-line and menu entry commands
@section The list of command-line and menu entry commands
-These commands are usable in the command-line and in menu entries. If
-you forget a command, you can run the command @command{help}.
+These commands are usable in the command-line and in menu entries. What
+does this mean? Roughly speaking, when GRUB parses the configuration file,
+it splits it into different chunks. The first one is composed of all the
+commands found before any @command{title}: these are general commands,
+belonging to the ``menu-specific'' or the ``menu'' sets. The other ones
+are composed of commands found between a @command{title} and the next
+one, or the end of file. These sets of commands are what we call
+``entries'', and these commands must belong to the ``menu'' or ``entry''
+groups, the latter one being described here.
+
+Remember that if you forget a command, you can run the command @command{help}.
@menu
* blocklist:: Get the block list notation of a file
