Ben Hutchings wrote: > [Cc'ing the bug, not the lists.] > > If the two labels (boot sector and root directory) are inconsistent then > different tools might reasonably disagree.
(I'm going to guess the blkid labels are "boot" and the problem ones are "root".) My odd results were coming from file systems that had been given both kinds of label last year; dosfslabel was showing the "root label" that it had set, not the "boot label" I needed. Booting Lenny and using old dosfslabel to generate new clashing labels I can repeat this; even on Squeeze, dosfslabel always prefers to report "root labels", ignoring one of the two kinds of label that it now sets. That's a defensible behaviour (after all, what else have I got that can read root labels?) but users who are unaware of the distinction would benefit from some sort of man page tweak: If boot sector and root directory labels differ, dosfstools will report the root directory label. The boot sector labels needed for "mount LABEL=" can be read with other tools such as blkid. > If you can come up with a test case where dosfslabel is still doing the > wrong thing (starting from a blank disk, like my test case in #559985) > then I will try to fix it. I can't make it *create* label discrepancies, so it's safe for use in the linux-base upgrade, and #506786 counts as fixed. -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
