Could someone test this on an OpenFirmware machine for which nvsetenv works?
The idea is that for those machines in which nvsetenv isn't usable, at least
user gets to know what command to type.
--
Robert Millan
My spam trap is [EMAIL PROTECTED] Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
diff -ur grub2-1.95+20070626.old/util/powerpc/ieee1275/grub-install.in grub2-1.95+20070626/util/powerpc/ieee1275/grub-install.in
--- grub2-1.95+20070626.old/util/powerpc/ieee1275/grub-install.in 2007-05-05 13:55:20.000000000 +0200
+++ grub2-1.95+20070626/util/powerpc/ieee1275/grub-install.in 2007-06-29 20:51:41.000000000 +0200
@@ -180,9 +180,11 @@
}
# Point boot-device at the new grub install
- "$nvsetenv" boot-device "$ofpath:$partno,"'\grub' || {
+ boot_device="boot-device $ofpath:$partno,\\grub"
+ "$nvsetenv" "$boot_device" || {
echo "$nvsetenv failed."
- echo "You will have to set boot-device manually."
+ echo "You will have to set boot-device manually. At the OpenFirmware prompt, type:"
+ echo " ok setenv $boot_device"
exit 1
}
fi
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
