Re^2: Munging file name, to be safe- & usable enough on Unix-like OSen & FAT32 file system

NTFS won't write to FAT32. NTFS is a filesystem just like FAT32. And so the NTFS driver will only ever write to NTFS-formatted media, as will the (V)FAT driver only ever write to (V)FAT-formatted media.

Perhaps that was bad|sloppy phrasing on my part. What do you call the operation of copying files from NTFS (Windows 10) to FAT32 (Windows knows of the removable mass storage device) then?

Comment on Re^2: Munging file name, to be safe- & usable enough on Unix-like OSen & FAT32 file system

Replies are listed 'Best First'.
Re^3: Munging file name, to be safe- & usable enough on Unix-like OSen & FAT32 file system by afoken (Chancellor) on Nov 27, 2023 at 19:03 UTC
What do you call the operation of copying files from NTFS ... to FAT32 ... then? Copying. Or, if you look at the filesystem driver level, reading from NTFS and writing to VFAT. Regarding FAT names - see also File Allocation Table: FAT-12, FAT-16, FAT-32 specify the size of a FAT entry, in bits, and thus indirectly also the maximum filesystem size. VFAT extends the FAT by adding long filenames (everything beyond "8.3", including mixed case, spaces, and more allowed characters). Linux has several closely related filesystem drivers, "fat" is a common part of the "msdos", "umsdos", and "vfat" drivers. The "msdos" driver is for plain old DOS disks, "8.3" names, no extras. "umsdos" (no longer enabled by default) implements Unix file attributes and long filenames on top of a plain, DOS-compatible FAT filesystem, by storing extra data in a special file per directory. "vfat" implements FAT with long filenames à la Microsoft. ExFAT (as found on SDXC-Cards) and FATX (Xbox) do use a FAT, but with very incompatible structures due to the very different feature set. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]

Replies are listed 'Best First'.

Re^3: Munging file name, to be safe- & usable enough on Unix-like OSen & FAT32 file system
by afoken (Chancellor) on Nov 27, 2023 at 19:03 UTC

What do you call the operation of copying files from NTFS ... to FAT32 ... then?

Copying. Or, if you look at the filesystem driver level, reading from NTFS and writing to VFAT.

Regarding FAT names - see also File Allocation Table:

FAT-12, FAT-16, FAT-32 specify the size of a FAT entry, in bits, and thus indirectly also the maximum filesystem size.

VFAT extends the FAT by adding long filenames (everything beyond "8.3", including mixed case, spaces, and more allowed characters).

Linux has several closely related filesystem drivers, "fat" is a common part of the "msdos", "umsdos", and "vfat" drivers. The "msdos" driver is for plain old DOS disks, "8.3" names, no extras. "umsdos" (no longer enabled by default) implements Unix file attributes and long filenames on top of a plain, DOS-compatible FAT filesystem, by storing extra data in a special file per directory. "vfat" implements FAT with long filenames à la Microsoft.

ExFAT (as found on SDXC-Cards) and FATX (Xbox) do use a FAT, but with very incompatible structures due to the very different feature set.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

[reply]