I was hit by the same problem when upgrading to Karmic today (detected vfat and ext3). Git version also works here
# blkid -p /dev/sda1
/dev/sda1: ambivalent result (probably more filesystems on the device)
# ./blkid -p /dev/sda1
/dev/sda1: UUID="a7b855d8-8d49-494f-b24d-dfa26c4a5916" VERSION="1.0" TYPE="ext3" USAGE="filesystem"
I guess this is caused by the windows shipped with this computer and I'm pretty sure this will cause huge problems to "beginners" who will be left with an unusable system.
Isn't there some type of hotfix possible like cleaning the vfat signature from these partitions when upgrading to util-linux-ng?
I was hit by the same problem when upgrading to Karmic today (detected vfat and ext3). Git version also works here
# blkid -p /dev/sda1 8d49-494f- b24d-dfa26c4a59 16" VERSION="1.0" TYPE="ext3" USAGE="filesystem"
/dev/sda1: ambivalent result (probably more filesystems on the device)
# ./blkid -p /dev/sda1
/dev/sda1: UUID="a7b855d8-
I guess this is caused by the windows shipped with this computer and I'm pretty sure this will cause huge problems to "beginners" who will be left with an unusable system.
Isn't there some type of hotfix possible like cleaning the vfat signature from these partitions when upgrading to util-linux-ng?