grub-reboot does not restore previous default after reboot
Bug #497326 reported by
Jordan
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub |
Unknown
|
Unknown
|
|||
grub2 (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
Karmic |
Won't Fix
|
High
|
Unassigned |
Bug Description
Binary package hint: grub2
grub-reboot is currently effectively equivalent to grub-set-default in karmic's grub2.
Because of this bug, grub-reboot in karmic is worse than useless: It will not work properly in any configuration and since the standard use case for grub-reboot is to reboot a remote server into a non-default configuration and be able to fall back to the default ( known working ) configuration where the user can fix things via ssh, not restoring the default is very likely to cause people to completely lose access to remote servers. This has happened at least once that I know of. More details @ http://
Related branches
description: | updated |
Changed in grub2 (Ubuntu): | |
status: | Triaged → Fix Committed |
assignee: | nobody → Colin Watson (cjwatson) |
Changed in grub2 (Ubuntu Karmic): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in grub2 (Ubuntu Karmic): | |
status: | Triaged → Won't Fix |
To post a comment you must log in.
Howdy, and thank you for helping to improve Ubuntu by opening this ticket (and especially for attaching a patch)!