sorry, my submission below was corrupt due to wrong EOL
representations in on of the diff'ed files.
This one is hopefully better ... thanks to phcoder ...
--
Bernhard
> -----Original Message-----
> From: Treutwein Bernhard
> Sent: Monday, April 18, 2011 1:00 PM
> To: '[email protected]'
> Subject: Patch re-submission: documentation update
>
>
> grub.texi has changed since my first submission last week, so
> I try again.
>
> To somebody with write access to the repo:
>
> my attempt to cointribute a little bit:
>
> 1. name and shortly explain the commands lsmod and rmmod
> 2. some corrections in the install section (drop the claim
> that Grub can be installed "by running GRUB itself from a
> floppy" which is as far as I know not possible any more
> (see
> http://lists.gnu.org/archive/html/grub-devel/2010-11/msg00007.html
> and
> http://lists.gnu.org/archive/html/grub-devel/2010-09/msg00105.html).
>
> I tried to produce unified diffs (this time in the hopefully correct
> sequence) by:
>
> diff -pruN grub.texi mygrub.texi
>
> The original is grub.texi at Revision 3218 fetched from the
> launchpad mirror
> this morning:
>
> http://bazaar.launchpad.net/~vcs-imports/grub/grub2-bzr/files/
head:/docs/)
regards
--
Bernhard Treutwein
--- grub.texi 2011-04-18 10:49:48.180220300 +0200
+++ mygrub.texi 2011-04-18 15:48:11.042181500 +0200
@@ -1487,13 +1487,12 @@ reside anywhere on the file system, and
After the embedded configuration file (if any) is executed, GRUB will load
the @samp{normal} module (@pxref{normal}), which will then read the real
-configuration file from @file{$prefix/grub.cfg}. By this point, the
+configuration file from @file{$prefix/grub.cfg}. By this point, the
@code{root} variable will also have been set to the root device name. For
example, @code{prefix} might be set to @samp{(hd0,1)/boot/grub}, and
@code{root} might be set to @samp{hd0,1}. Thus, in most cases, the embedded
configuration file only needs to set the @code{prefix} and @code{root}
-variables, and then drop through to GRUB's normal processing. A typical
-example of this might look like this:
+variables, and then drop through to GRUB's normal processing. A typical
example of this might look like this:
@example
@group
@@ -3089,6 +3088,7 @@ you forget a command, you can run the co
* load_env:: Load variables from environment block
* loopback:: Make a device from a filesystem image
* ls:: List devices or files
+* lsmod:: List loaded modules
* normal:: Enter normal mode
* normal_exit:: Exit from normal mode
* parttool:: Modify partition table entries
@@ -3098,6 +3098,7 @@ you forget a command, you can run the co
* pxe_unload:: Unload the PXE environment
* read:: Read user input
* reboot:: Reboot your computer
+* rmmod:: Remove named module
* save_env:: Save variables to environment block
* search:: Search devices by file, label, or UUID
* sendkey:: Emulate keystrokes
@@ -3547,6 +3548,14 @@ name syntax}), then list the contents of
@end deffn
+@node lsmod
+@subsection lsmod
+
+@deffn Command lsmod
+List the currently loaded modules.
+@end deffn
+
+
@node normal
@subsection normal
@@ -3676,6 +3685,14 @@ Reboot the computer.
@end deffn
+@node rmmod
+@subsection rmmod
+
+@deffn Command rmmod module
+Unload/remove the dynamic GRUB module called @var{module}.
+@end deffn
+
+
@node save_env
@subsection save_env
_______________________________________________
Grub-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/grub-devel
