Hi, I was bitten by this as well. While I appreciate that the new default should be UUID-based, I think this should be taken care of in the hooks of the grub package. I think it's absolutely wrong that running update-grub (which typically occurs after installing a new kernel, as you all know) after having manually reset kopt to
#kopt=root=/dev/hda5 forces this back to #kopt=root=UUID=some-hex-gibberish This in effect means that there's no way to avoid having to manually re- edit menu.lst after each update-grub. To be explicit: If I put # kopt=root=/dev/hda5 ro in the right place in menu.lst, then run update-grub, I get # kopt=root=UUID=7138f191-499e-4b7e-8f68-c1019f785215 ro in that same place back, and consequently kernel /vmlinuz-xyz root=UUID=7138f191-499e-4b7e-8f68-c1019f785215 ro quiet splash in the boot stanzas. This is in contradiction to the man page of update- grub, which states that this is one of the two options that I should configure. So in particular, I think that the function convert_kopt_to_uuid in /sbin/update-grub should be ripped out and moved into somewhere in the hook scripts. -- edgy update-grub destroys kopt https://launchpad.net/bugs/62195 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
