Microsoft wants to bring exFAT to the Linux kernel
Linux - NewsThis forum is for original Linux News. If you'd like to write content for LQ, feel free to contact us.
All threads in the forum need to be approved before they will appear.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't argue against better interoperability, but I'm skeptical. Why should the Linux community adopt Microsoft technology while Microsoft is apparently reluctant to incorporate Linux technology.
For example, Microsoft could adopt the "EXT4" file system instead of pushing exFAT. Obviously Microsoft won't do that to preserve its proprietary nature, even though they are opening up exFAT.
Can't argue against better interoperability, but I'm skeptical. Why should the Linux community adopt Microsoft technology while Microsoft is apparently reluctant to incorporate Linux technology.
For example, Microsoft could adopt the "EXT4" file system instead of pushing exFAT. Obviously Microsoft won't do that to preserve its proprietary nature, even though they are opening up exFAT.
They could, but as you say they won't. It's just the scorpion promising to not sting.
If only we had the wherewithall to embrace what they're offering and then extend it...
What do they say about looking gift horses in the mouth? Microsoft announced Wednesday that it's "supporting the addition of [its] exFAT technology to the Linux kernel." The company positioned that as a win for Linux users, but developers were quick to voice their displeasure.
Quote:
Phoronix reported today that Linux developers weren't particularly enthused about what Microsoft released, with one kernel developer calling it a "pile of crap," which is exactly the kind of frankness we've come to expect from Linux developers. The primary complaint appears to be that Microsoft re-implemented much of the Linux kernel's existing FAT driver rather than building exFAT on top of that driver.
Out of curiosity. Is the exFAT file system any good?
exFat works, but would it be a case of an "old" system being patched to work today; when the better solution would be to adopt something like EXT4?
The Evil Empire Resurfaces! This time they have contributed ExFAT with a full GPL license. Could they be changing their ways? or is there more sinister plans at work.
For example, Microsoft could adopt the "EXT4" file system instead of pushing exFAT. Obviously Microsoft won't do that to preserve its proprietary nature, even though they are opening up exFAT.
As exFAT is already licensed and in use by other companies when formatting cards (for example, Canon cameras with cards over 128Gb) I'm quite happy it's going to become a public format that doesn't have to be reverse engineered.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I'm still at a loss why Google didn't choose another filesystem back when they needed drivers to connect to phones. A quick install of ext2 driver, or whatever, would not have been odd back when Android came out but, now, computers are expectd to have all kinds of useless "media" crud just to access an attached device.
As a side note I never did find out why the heck the "$" sign is so important to these old computing systems.
I'm still at a loss why Google didn't choose another filesystem back when they needed drivers to connect to phones.
The vast majority of the market was using MS windows
Quote:
A quick install of ext2 driver, or whatever, would not have been odd back when Android came out
Back then there was a third party driver for ext2/3 on Windows.. but it was horribly slow and the average user would have had little to no chance of being able to use it ( too many steps to get it working )
True, it could have been improved, but why bother when they could use a proven fs that would be seamless.
Quote:
but, now, computers are expectd to have all kinds of useless "media" crud just to access an attached device.
As a side note I never did find out why the heck the "$" sign is so important to these old computing systems.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Quote:
Originally Posted by Firerat
The vast majority of the market was using MS windows
Back then there was a third party driver for ext2/3 on Windows.. but it was horribly slow and the average user would have had little to no chance of being able to use it ( too many steps to get it working )
True, it could have been improved, but why bother when they could use a proven fs that would be seamless.
money makes the world go round
Back in the day nearly every device needed some kind of software install to user with Windows so they could have included the driver there. Now that everything needs an extra abstraction layer installing it doesn't matter which file system devices use. There was only really a small amount of time where things "just worked" using native EXFAT drivers.
As to the "$" sign I was referring to string termination and stolen software.
The code for an exFAT FS driver was accidentally released by Samsung back in 2013. It was found to be violating GPL, which forced the rest of the code to be released by Samsung under GPL, it has only ever been usable via FUSE. It was not Microsoft code.
So the idea that MS have released a GPL'd exFAT driver as being touted around by some on various blogs/youtube/tech press is nothing short of bollocks.
I'm not sure MS exfat needs to be in the kernel, but I must be missing something.
Two questions:
1. Doesn't an exfat fs already exist re'd from the fat dev base?
2. Is there an alternative to exfat for reading SD cards > 128GB?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.