3 ms·
> They would also have to drop support for FAT32 as you pointed out. This is a little dubious. When you load a FAT driver on a *nix system, you get the limita
by asveikau 12y ago
> They would also have to drop support for FAT32 as you pointed out.
This is a little dubious. When you load a FAT driver on a *nix system, you get the limitations of FAT. Likewise there are lots of fancy filesystem APIs in Windows that fail on a FAT volume and work on NTFS.
That said, there are a lot of quirky NTFS behaviors that are ultimately rooted in FAT. I used to get frustrated by a lot of them, then I started writing a FAT driver just for fun ... and it made sense. All the goofy things about naming start to make sense if the direntry "is your inode" and the extra space in the name is padded with spaces...