Comment 0 for bug 1549064
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
[Impact]
This affects all ppc64el users whenever they upgrade grub.
[Test case]
1) run 'nvram --print-
2) upgrade grub-ieee1275
2) run 'nvram --print-
The value should not change between runs, it should also not be touched at all (even if it's set to the same value).
This can be further verified by modifying boot-device to an arbitrary value before running the grub upgrade.
[Regression potential]
This has minimal potential for regression. It removes a code path which might otherwise break booting after upgrading grub on the affected systems. One possibility for regression is that if code paths are subsequently added to register openfirmware devices, this should be guarded with an 'if (update_nvram)' test to make sure it only ever happens when the --no-nvram flag is *NOT* passed to grub-install.
---
grub-ieee1275 should call grub-install with --no-nvram in postinst, so as not to modify boot-device in OpenFirmware everytime the grub package is updated.