Re: future r4 maintenance question

[Sander Sweers <sander.sweers@gmail.com>]

On Sat, 2006-07-22 at 14:42 -0500, David Masover wrote:
> Mike Benoit wrote:
> 
[...]
> 
> You would hope.  The problem is, most of the ideas we have for 
> amazing/useless/practical plugins have already been done as specialized 
> filesystems in FUSE.  What's more, FUSE doesn't usually require root 
> privileges to run, causing some people to do such useless things as 
> support for various filesystems already in the kernel (so you can 
> loop-mount filesystems without using the loop device or having root 
> privileges).
> 
> Although, there is one other thing to consider -- NTFS in the kernel has 
> stagnated for something like 10 years without write support, while 
> userspace tools like ntfsck and resize_ntfs, using libntfs, have 
> actually gotten relatively stable at dealing with all kinds of ntfs 
> oddities.  For awhile, we had captive-ntfs (also done in FUSE), but more 
> recently, someone wrote a FUSE driver for libntfs, making the first 
> reasonably stable fully featured read/write NTFS driver for Linux.
> 
> It's also reasonably fast, sometimes faster than ext2/3, I'm told.

I am using the official libntfs fuse module but it is not all that fast
if you compare how much more cpu power is needed. And even then it is
NOT faster then ext2/3. I am copying a couple of 650mb iso's and I have
100% cpu utilisation and it still takes tens of minutes to copy just 1.

Fuse is nice for things like gmailfs or beaglefs but if you really want
performance, kernelspace imho is the only place to implement a
filesystems.

Greets
Sander