Re: disklabel generating wrong fstype

[mlh%goathill.org@localhost (MLH)]

Interesting. after writing a disklabel and using newfs_msdos,
fdisk showed:

Partition table:
0: <UNUSED>
1: <UNUSED>
2: <UNUSED>
3: <UNUSED>

So I used fdisk to modify to what the other exFAT cards were showing:
0: Primary DOS with 32 bit FAT (sysid 11)
    start 32768, size 250052608 (122096 MB, Cyls 2/10/9-15567/24/9)
1: <UNUSED>
2: <UNUSED>
3: <UNUSED>

and used newfs_msdos. Then I took to a Windows laptop and did a
fast format with exFAT and it is back to the beginning again
where I can't mount but it does stil have the disklabel:

 d: 250085376         0     unused      0     0        # (Cyl.      0 - 122111)
 e: 250052608     32768      MSDOS                     # (Cyl.     16 - 122111)

However, fdisk now reports :
0: NTFS, OS/2 HPFS, QNX2 or Advanced UNIX (sysid 7)
    start 32768, size 250052608 (122096 MB, Cyls 2/10/9-15567/24/9)
1: <UNUSED>
2: <UNUSED>
3: <UNUSED>

So Windows is setting the NTFS filesystem on this card when formatting
with exFAT. Would be nice to determine how to get this card to act
like other exFAT cards...

Looks like fdisk might be the better way to set up these "broken"
cards than using disklabel (and easier). Be nice if Windows used
that partitioning.