Szabolcs Szakacsits wrote: > > > > > How old? The out of tree fuse module (hoping to get rid of it soon) > > > > > works down to 2.6.9. Beyond that it does probably require a fair > > > > > amount of porting work. > > > > > > > > I imagine that backporting FUSE to 2.4 no-mmu will be more work than > > > > backporting a filesystem, but I could be mistaken. Moving my project > > > > to a 2.6 kernel (*any* 2.6 kernel) would be much more work than > > > > either. > > > > > > Fuse-2.5 still supported linux-2.4. Although I have no idea if it > > > works with no-mmu, maybe it's worth a try. > > > > > > Backporting ntfs-3g to an older version of fuse shouldn't be a big > > > problem, as the fuse interface didn't change very much since then. > > > > Thanks for your advice. I will look into all these possibilities. > > Fuse working would be quite useful in many other ways too. > > ntfs-3g was reported to work on 2.4 no-mmu kernels six months ago (though > it had no our QA). Please see http://ntfs-3g.org/support.html#kernel24 and > search for nommu on fuse-devel for the details. Ah, wonderful! 2.4 kernel support has been _added_ to NTFS-3g's "FUSE-lite" since I last looked! Nice to see 2.4 kernel support is still an active priority ;-) Thanks for the info, it's really useful. I would never have thought to check for 2.4 support being added back, since an earlier announcement said it was no longer supported. (Btw, The NTFS-3g release notes, on it's decision to replace the FUSE userspace libs (which is what makes it work with 2.4 kernels too), suggest there may be serious problems in the standard FUSE libs, especially on small devices. It doesn't bother me, as I only need NTFS-3g, not other FUSE capabilities, but perhaps FUSE developers would like to take a look at those problems.) Thanks again, -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
