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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 14 Apr 2008 23:35:56 +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:
> > > > 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.

All other filesystems I care about are in-kernel - NTFS is quite
exceptional in needing FUSE just to get ordinary, stable file access.
(The in-kernel NTFS is regarded as unstable and missing essential
basic features.)

None of this should be taken as any kind of criticism.  I love what
you guys have done.

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

Powered by blists - more mailing lists