I'm the owner of the github page and of the native exFat linux read-write driver.
I'm impressed that the Phoronix community has created a two-page discussion the same day the drivers got released.
I would like to reveal a few things about the driver.
It's an android exFat driver which I found on github about a month ago.
I highly dislike Microsoft's attempts to bring the reputation of linux and similar open-source projects down.
I've needed a way to interact with my external 1TB HDD via linux and store large files on it, and there was no non-fuse ntfs driver available for linux either, so I decided to do a good thing and write a native kernel rw exFat driver for linux.
There was a ro driver and a fuse implementation before.
The first that came up in my mind is to find if it was available on the net already: I've checked android source codes from one of the manufacturer's website, but they did not release any parts of the exfat modules there.
Then I made a simple search on github and there was a couple of repos of some tablet's kernel. There was it.
The version of that kernel was 3.0 so I had to put some effort (literally, 4 hours) to make it work on the version 3.8.
This driver has not been written by me, I just ported it to the newer kernel version, with minimal adjustments.
That is a good thing, because I can state that the driver will work with all 3.x versions of kernel, if only you could spend an hour fixing a couple of lines of code for that version.
The reason I did not port it to 3.9 is because I wanted to make a release ASAP and the community to pick this code to do whatever you like: patches/ports/improvements; and release that as branches on github or somewhere else. It is a work of an hour or less for any programmer to make it work with the latest kernel.
And it's even a good source to create a driver for other platforms.
I used tor all the time and using it right now because I don't want to waste any more time on dealing with microsoft's idiotic policies, that's why I've uploaded the code in 1 hr on github, via the on-site editor.
This driver is guaranteed to provide full exFat support on linux, on the same level as it's available on all android tablets with the kernel version 3.0.
I am not planning on supporting this driver because I believe I've done enough for the community to have the full linux exFat support.
Feel free to fork and port as you like.
It's not a patch, and can be installed as a separate module by running just one command: `make install`. It's like the vboxdrv, same principle.
I may find more native drivers (ntfs?) from that tablet's source code and release them later.
Free software for the free Minds!
I dont care exFAT but i need an fast NTFS kernel Driver or an WORKING ext3/4 Driver for Windows.
PS: I know there is currently an unstable driver but he is Managed by an creepy unstable Tool.
Github user ksv1986 just submitted a patch and resolved the 3.9 compatibility issue.
Now this module is confirmed to work on both 3.8 and 3.9 kernels.
To those who were complaining on the first page: It was literally one line of code!
Phoronix: please, update the post on the main page.
Thank you all!
Last edited by rzrx; 06-26-2013 at 04:16 PM.
It does. I use UDF HDDs all day to share large files between various OSes. If you format the disc with Linux just make sure you tell it to be a HDD and choose the right block size, else Windows will freak out.and Windows dont allow it to use UDF as an HDD Filesystem.
If he starts distributing the library or starts to use it, then it may be the case, but uploading the SOURCE code does NOTHING.
Also, ANY user that has a DEVICE WITH EXFAT AUTOMATICALLY PAYED THE MSTAX BY MEANS OF PURCHASING THE DEVICE.
This is the same reason why ANYONE CAN USE S3TC WITH ANY DRIVER, because ANY MODERN CARD is produced by MANUFACTURER that PAID FOR S3TC and THIS PRICE was COVERED BY CONSUMER AT TIME OF PURCHASE.
In BOTH CASES THE LICENSE WAS ALREADY PAID FOR.
So it would only be illegal to use A BINARY of this library when NOT HAVING ANY EXFAT DEVICE.
Last edited by brosis; 06-28-2013 at 10:15 AM.