From: Jamie Lokier Subject: Re: [PATCH 0/7] OMFS filesystem version 3 Date: Tue, 15 Apr 2008 16:23:13 +0100 Message-ID: <20080415152313.GB8513@shareable.org> References: <20080413082815.GA20108@infradead.org> <1208121358.2700.4.camel@shinybook.infradead.org> <20080414094215.GD2076@shareable.org> <20080414115540.GA5802@shareable.org> <20080414223556.GA21340@shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dwmw2@infradead.org, hch@infradead.org, akpm@linux-foundation.org, me@bobcopeland.com, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Miklos Szeredi Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Miklos Szeredi 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. -- Jamie