https://bugs.kde.org/show_bug.cgi?id=487650
Andrius Štikonas <andr...@stikonas.eu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #6 from Andrius Štikonas <andr...@stikonas.eu> ---
(In reply to AF from comment #5)
> "id": "0x00000000",
Hmm, that's definitely regression due to that commit. We need some other way of
distinguishing between MBR partition table and FAT file systems...
Looks like sfdisk for partition tables reports exactly the same output as for
FAT file systems :(
E.g. this is exFAT whole device partition:
sudo sfdisk --json /dev/sdb
{
"partitiontable": {
"label": "dos",
"id": "0x00000000",
"device": "/dev/sdb",
"unit": "sectors",
"sectorsize": 512
}
and this is MBR that I just created
sudo sfdisk --json /dev/sdb
{
"partitiontable": {
"label": "dos",
"id": "0x69badb1c",
"device": "/dev/sdb",
"unit": "sectors",
"sectorsize": 512
}
}
Unfortunately, it looks like you can still have MBR with id that is 0x0...
--
You are receiving this mail because:
You are watching all bug changes.
