Thomas, not every instance of UUIDs not being recognized -- at least in the way we're discussing here -- is a bug. Sometimes, it is difficult or impossible to recognize them. Sometimes, it makes no sense to recognize them anyway.
Look at the examples which the script already deliberately ignores. Crypto, for example -- you can create a mapping of /dev/mapper/some_name to an underlying UUID device. So, by the time you're trynig to mount that, you actually do want to open it by device name -- because that device name already corresponds to a real UUID device, so you already have all of the benefits of that. RAID is another example, for pretty much the same reasons. /dev/md0, or /dev/md_d0p1, are names that the admin creates, which map (somehow) to underlying block devices. The problem is, a simple regex/glob looking for known patterns is not enough. Some people compile custom kernels. Some people don't use initramfs. Some people might just be using a devicename you hadn't thought of. Either way, by the time someone's digging in menu.lst to disable the UUIDs, it seems reasonable to assume they know what they're doing. So yes, sometimes UUIDs not being recognized are their own bug, but not always. No matter how perfect we get the UUID detection, there should always be a way to disable that. -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 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
