I mean, the expected workflow is: I hook up the device to the computer, it shows up as a storage medium in my system. I can move files between the device and my computer as if it was an external disk or USB drive.
Anything on top of that is designed to be annoying.
FAT32 is a terribly outdated filesystem and should just not be used today, period. The filesize and name restrictions are awful. Mrkrabo does have a point.
The question about FAT32 was honest; thanks for the explanation. The rest of the comment (presenting storage in a normal, non-surprising way) is separate, and still stands.
What's wrong with emulating a FAT32 disk?
I mean, the expected workflow is: I hook up the device to the computer, it shows up as a storage medium in my system. I can move files between the device and my computer as if it was an external disk or USB drive.
Anything on top of that is designed to be annoying.
FAT32 is a terribly outdated filesystem and should just not be used today, period. The filesize and name restrictions are awful. Mrkrabo does have a point.
The question about FAT32 was honest; thanks for the explanation. The rest of the comment (presenting storage in a normal, non-surprising way) is separate, and still stands.
1 reply →
Ethernet over USB, FTP/SCP/SMB?