News for hackers. Stuff that matters.
Re:Vboxsf fixes for 5.14-1 by beermonster on Monday July 19, 2021 @06:48AM (#27881069)
NTFS has journaling,compression, encryption, max 255 character filenames, max partition size is hundred of TB rather than 2GB, generally faster performance wise.

Trouble is , FAT32 has more OS compatibility.

Would be nice if Linux did have first class support for NTFS as it’s superior. But right now for maximum compatibility you need FAT32

Re:Vboxsf fixes for 5.14-1 by gattilorenz on Monday July 19, 2021 @09:34AM (#27882478)
> max partition size is hundred of TB rather than 2GB

FAT16 is limited to 2GB, FAT32 can extend to 2TB (but the max file size for a single file is 4GB, as the parent stated)

Re:Vboxsf fixes for 5.14-1 by sascha_sl on Monday July 19, 2021 @07:16AM (#27881284)
> max 255 character filenames

it doesn't in spec, that's just the win32 API

Re:Vboxsf fixes for 5.14-1 by jasode on Monday July 19, 2021 @07:49AM (#27881538)
>it doesn't in spec, that's just the win32 API

NTFS filename length is limited to 255 Unicode chars.

You may be thinking of full path lengths of 32,767 Unicode chars but the filename component is still limited to 255.

If you look at the NTFS data structure "$FILE_NAME (0x30)" at byte offset 0x40: https://www.google.com/search?q=ntfs+%22%24FILE_NAME%22+byte

... there's only 1 byte used to describe the filename length. Hence max of 255 chars.

Wikipedia page about NTFS also mentions 255 max length for filename: https://en.wikipedia.org/wiki/NTFS

Re:Vboxsf fixes for 5.14-1 by ziml77 on Monday July 19, 2021 @07:54AM (#27881569)
You're confusing the filename length limit with the limitation on the entire path length in the Windows API. NTFS allows paths to be up to 32k characters long, but each path component tops out at 255 characters.
Re:Vboxsf fixes for 5.14-1 by wyuenho on Monday July 19, 2021 @07:35AM (#27881423)
The Paragon driver cannot recognize encrypted NTFS volumes AFAIK