When I have submitted patches in the past, to fix problems such as the one that kicked off this thread (an ext3 filesystem erroneously getting reported as a FAT filesystem), it was rejected by the libvolume_id maintainer. I've been very busy trying to get ext4 production ready, and decided I didn't have time to waste trying to get them to listen to me. If you have an ext3 filesystem, and libvolume_id returns the FAT UUID, it is a bug with libvolume_id. Keeping them consistent may be slightly better, but returning the wrong type means that "mount /dev/sda1" won't work because mount will be given the wrong filesystem type by libvolume_id --- and the libvolume_id folks have rejected patches I've sent in the pass to correctly probe the device correctly.
So what the hell am I supposed to do? -- tools should use libvolume-id instead of libblkid https://bugs.launchpad.net/bugs/235165 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
