[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1JljQD-0008Ae-5H@pomaz-ex.szeredi.hu>
Date: Tue, 15 Apr 2008 13:33:57 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: jamie@...reable.org
CC: dwmw2@...radead.org, hch@...radead.org, akpm@...ux-foundation.org,
me@...copeland.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/7] OMFS filesystem version 3
> > > > > Yes, that's quite annoying as FUSE doesn't work with my architecture,
> > > > > 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists