That's how *so many* filesystems, drivers, subsystems, etc.
#ANDROID PARAGON NTFS MOUNT LOSES FUSE CODE#
They'll be dead, gone, forgotten, unsupportive, the one guy who opened the code will move to another company or whatever. And so the filesystems maintainers have to be able to review it and not accept any NTFS-only nonsense.īecause Paragon - if history is anything to go by - will not be patching this code in years to come. Filesystem detection has to be consistent so it only offers to run disks that it knows it has the support for, and tied in. Quirks have to be ironed out so they are clearly documented. It has to work internally in a similar manner. It has to use the common code that it can (so NTFS doesn't have it's own special way of allocating a file or whatever that's different to everyone else).
#ANDROID PARAGON NTFS MOUNT LOSES FUSE PATCH#
This isn't unique to NTFS, or even a particular subsystem of Linux - maintenance burden is the determining factor in a lot of the patch acceptance pipeline. They've all suffered the same fate - they might "work" but nobody maintains them, so they get bugs and get obsolete and don't work for modern versions of the filesystem, so they end up being a dead-weight in the kernel. Hell, even one that emulated enough of the programming interface to use the original Windows DLLs to access the filesystem under Linux.
![android paragon ntfs mount loses fuse android paragon ntfs mount loses fuse](https://i.pinimg.com/originals/a8/e4/1f/a8e41fc90435fa1233e82eeff0a80bfb.jpg)
There were several NTFS projects, historically. A dump-and-run is a common output from a company that doesn't WANT to maintain it any more, or deal with the user's complaining that it's unmaintained, or has a bug they haven't fixed. Literally, maintaining that code is harder than writing it in the first place. You have to understand all the code, change it often, make sure it stays secure and bug-free, deal with support from users who now have NTFS 5.1 and why are they getting corruption now when they didn't on 5.0, and so on. That maintenance burden is FAR FAR more difficult than the initial code-drop is. So a dump-and-run is really an obligation, not unlike giving someone a pet dog for Christmas when you don't live with them. The maintenance, updating, API-conversion and upheaval that happens in the Linux codebase is huge.
![android paragon ntfs mount loses fuse android paragon ntfs mount loses fuse](https://newlove413.weebly.com/uploads/1/2/5/6/125688553/585276433.jpg)
So I leave it in your garden one day with a note saying it's a gift to you.