| 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
| ||
|
Date: Mon, 14 Apr 2008 11:58:05 +0200 From: Miklos Szeredi <miklos@...redi.hu> To: jamie@...reable.org CC: miklos@...redi.hu, 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 > > And I didn't advocate moving > > ntfs to fuse, still that was done > > 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 :) > FUSE is great for user-mounted filesystems, though. Having to use > "su" in shell scripts which modify loopback filesystems was always > very ugly. > > I don't see why we need such a dichotomy, though. The VFS API is > sensible enough that it should be possible to compile the same > filesystem code to run in kernel or in FUSE. Well, yeah: http://lkml.org/lkml/2006/2/27/148 Oh, you mean without having to run the whole kernel around the filesystem? Well, that's a bit more tricky: filesystems use not just the VFS API, but the block, VM, SLAB, etc. APIs as well. Porting all of these to userspace and keeping them in sync with the kernel changes doesn't sound much fun. 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