linux-kernel - Re: [PATCH 0/7] OMFS filesystem version 3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 15 Apr 2008 16:23:13 +0100
From:	Jamie Lokier <jamie@...reable.org>
To:	Miklos Szeredi <miklos@...redi.hu>
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

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
--
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/