> > > > > Yes, that's quite annoying as FUSE doesn't work with my architecture,
quoted text
> > > > > so I can't use the only good NTFS driver.... grr! :-)
> > > > 
> > > > I'm not quite getting this joke :)
> > > 
> > > It's not really a joke.  It really is a problem: I'm supposed to
> > > provide NTFS support for a project, but the kernel I'm using doesn't
> > > work with FUSE (too old for the FUSE version needed by ntfs-3g),
> > 
> > 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.

Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html