You are not logged in.
Just wondering if a FUSE driver in community means a kernel module also belongs there. Seems like the rationale for kernel module support by official repos is stronger unless I am missing something.
Offline
Not a Sysadmin issue, moving to Kernel & Hardware (for the time being)...
Offline
That kernel module has had a bit of controversy. It was originally leaked and distributed illegally, being licensed under a closed license. It was found to contain GPL code, forcing Samsung to relicense it and release it under the GPL. Even then, there's still a patent issue: In order to legally use this module in countries where US software patents are recognized, the device you use it on must be licensed by Microsoft. I think there's other patent encumbered software in the repos, though, so maybe that's not a blocker. In fact, the fuse driver probably falls under the same restriction.
Last edited by Scimmia (2013-08-24 06:49:52)
Offline
Thanks Scimmia. Any Samsung controversy now seems irrelevant? Their code is GPL. Thanks for the history.
The patent issue is orthogonal. The old FAT patent expires in 2013 and was already beaten down. I don't know about exFAT but see TechRights.
Given Microsoft's cross-patent agreements with Apple, Samsung, and the whole tech universe, it's likely wrong to say you need a Microsoft device. You need a device from any vendor with a license. Like motherboard manufacturers....cell phone manufacturers....etc. etc. etc. etc.
Be that as it may or not, I think you're right that any patent implications would affect the FUSE suite as much as the kernel one? Therefore my original argument stands, I would say. Arch should give official support to the kernel module (since it already does the FUSE version which is inferior quality by definition).
Thanks
Offline
Apparently the Samsung controversy was only recently resolved (in favor of GPL). It's "breaking news."
Offline
I didn't say you needed a Microsoft device, just that the device has to include a license purchased from Microsoft. The licenses in this case are per-device, not licensed to a particular manufacturer for all of their devices.
I brought up the history because it's very recent history. All of this just happened in the last few weeks. I doubt the Devs/TUs would put something like this into the repos without letting the dust settle a bit.
Offline
My point was the same, I think. It's now just that, recent history. The dust has settled. Legal matters ended amicably. It's GPL code without contention. The press was alerted. The fat lady sang. As far as stability goes, the code has been out a good long while, commercially and in AUR. It's stable.
Sorry to misunderstand on devices. I'm no patent expert. I know deals take many forms.
Arch Linux has long supported old-school FAT with MS patents in effect. So kernel exFAT would just follow current practice, patents and all.
Last edited by DaveCode (2013-09-03 20:18:18)
Offline
I think the part that you are missing here is that although it might fit into the repos as being similar to other packages in terms of licensing and functionality, it still takes the interest of a dev or TU to actually make its way there. Without someone to maintain it, there is no package in the repos, and it will remain in the AUR.
Offline