The exFAT filesystem is coming to Linux:
When software and operating system giant Microsoft announced its support for inclusion of the exFAT filesystem directly into the Linux kernel back in August, it didn't get a ton of press coverage. But filesystem vendor Paragon Software clearly noticed this month's merge of the Microsoft-approved, largely Samsung-authored version of exFAT into the VFS for-next repository, which will in turn merge into Linux 5.7—and Paragon doesn't seem happy about it.
Yesterday, Paragon issued a press release about European gateway-modem vendor Sagemcom adopting its version of exFAT into an upcoming series of Linux-based routers. Unfortunately, it chose to preface the announcement with a stream of FUD (Fear, Uncertainty, and Doubt) that wouldn't have looked out of place on Steve Ballmer's letterhead in the 1990s.
Paragon described its arguments against open source software—which appeared directly in my inbox—as an "article (available for publication in any form) explaining why the open source model didn't work in 3 cases."
All three of Paragon's offered cases were curious examples, at best.
Case one: Android
Case two: MacOS
Case three: SMB
We congratulate Paragon on closing their timely exFAT deal with Sagemcom. Although there's good reason to believe that the Samsung-derived and Microsoft-approved exFAT implementation in Linux 5.7 will be secure, stable, and highly performant, it's not here yet—and it isn't even in the next upcoming Linux kernel, 5.6, which we expect to hit general availability in late April or early May.
(Score: 5, Interesting) by Runaway1956 on Thursday March 26 2020, @02:11PM
I pretty much have to use a file system that MS recognizes, if I want to move files among machines that use MS OS. I mean, you just don't have much choice, right?
But, I've found that NTFS is pretty robust. Someone grabs it and pulls it out without ejecting or dismounting it - NTFS generally comes back perfectly healthy after chkdsk. FAT file systems? My luck hasn't been so good. File system gets mounted read-only, chkdsk claims to have fixed the problem but you still have to select folders and change it to read/write. Worse, despite telling Windows to apply the changes to this folder and all subfolders, you still have to check properties of all subfolders.
I'll pass on all the FATs, thank you very much.
“I have become friends with many school shooters” - Tampon Tim Walz