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: 3, Interesting) by progo on Thursday March 26 2020, @02:39PM (1 child)
Also ExFAT is the best way I can think of to share data on physical media between separate Linux systems with different user IDs. ExFAT doesn't support ownership metadata, so when you plug it into a new system, any user IDs that created files, that don't match your current user ID, are irrelevant because the whole filesystem is owned CURRENT user.
Why can't you disable ownership in ext4?
(Score: 2, Interesting) by Bot on Thursday March 26 2020, @09:58PM
I remember having made a tar directly to the raw device file (using dd but maybe output redirection is sufficient) and extracting with --no-same-owner. Note it will erase any other file in the device. Maybe you can pass dd parameters to append other tars if you recall how many records the first tar ate up.
Did that because the device was ext4 and the target pc recognized up to ext3 and I saw no reason to spend time reformatting. I had to reformat specifying sector size later, though, because grub had barfed, probably related to the crap found in the first sectors.
Earlier debian and mx didn't complain and automounted unpartitioned drives too (that is mkfs and mount the dev file), not anymore.
Account abandoned.