Comment 23 for bug 62195

Oh, and let's not forget -- menu.lst now lies. It provides a number of options, with instructions on how to use them -- which are then messed with by update-grub.

And update-grub, by the way, contains a hardcoded switch statement -- looks like /dev/md[0-9] is now supported. Great. I run a partitioned raid, which means the raid device is /dev/md_d0, and the actual partition is /dev/md_d0p2. I can now look forward to an upgrade, every now and then, requiring manual intervention to keep my system bootable.

Attaching a patch for gutsy.

Here's the essential problem: Even assuming the uuid stuff works flawlessly, every time (which would be nice), and even assuming nobody ever wants to manually set a device name, there are certain devices which apparently aren't detected by uuid. Rather than having a list of device names known to work by uuid, the update-grub script instead assumes that anything it doesn't recognized as incompatible with uuid is, in fact, compatible. That's just reckless.

Unfortunately, I don't know enough about how things are looked up by uuid to know exactly which devices are supported, and which aren't, or how update-grub should know that. And I do think that at the very least, a manual disable should be allowed.