Hi Marcel,
Yes, you are correct; if after a kernel upgrade in hardy you have the wrong
UUID in your boot config, then two things must be true here:
- the wrong UUID is present in the kopt line in menu.lst
- the user must have overidden the default choice when prompted during the
upgrade, and chosen to use the config autogenerated by the system instead of
the one preserving the local changes to the boot options
As you noted, both of these applied in your case, and I believe this
also applies in the case of the original submitter.
Ideally, it would be great if we could magically detect when the wrong
UUID is used and automatically fix everything up, but that's simply not
feasible here; so I'm closing this bug as 'wontfix'.
** Changed in: grub (Ubuntu)
Status: New => Won't Fix
--
wrong UUID in menu.lst after upgrade to hardy
https://bugs.launchpad.net/bugs/234720
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
