GRUB_SAVEDEFAULT and grub-reboot with GRUB_DEFAULT=saved do not work if
grubenv file resides on an LVM partition or a RAID device, since those
cannot be written to. This patch adds a note regarding this issue into the
manual.

This is my first patch submission, so please let me know if I messed
something up. Thanks!

Aurimas
--- grub.old.texi	2010-09-29 00:46:17.032503438 -0500
+++ grub.texi	2010-09-29 01:25:16.722878882 -0500
@@ -1002,6 +1002,10 @@ If you set this to @samp{saved}, then th
 saved by @samp{GRUB_SAVEDEFAULT}, @command{grub-set-default}, or
 @command{grub-reboot}.
 
+Currently using @command{grub-reboot} with GRUB_DEFAULT set to @samp{saved}
+will not revert to the original entry upon subsequent reboot if the grubenv
+file resides on an LVM partition or a RAID device.
+
 The default is @samp{0}.
 
 @item GRUB_SAVEDEFAULT
@@ -1011,6 +1015,9 @@ useful if @samp{GRUB_DEFAULT=saved}; it 
 @samp{GRUB_DEFAULT=saved} is useful without this option, in conjunction with
 @command{grub-set-default} or @command{grub-reboot}.  Unset by default.
 
+Currently this option does not work if the grubenv file (generally found in
+the /boot/grub directory) resides on an LVM partition or a RAID device.
+
 @item GRUB_TIMEOUT
 Boot the default entry this many seconds after the menu is displayed, unless
 a key is pressed.  The default is @samp{5}.  Set to @samp{0} to boot
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to