> > 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-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
