[Mono-dev] [Mono-list] Announce: Mono.Fuse 0.2.0 (+ Required mcs & mono patches)

[Valient Gough]

On 9/12/06, Jonathan Pryor <jonpryor at vt.edu> wrote:
> Is there a known issue with FUSE, fsx-linux & mmap testing, or am I
> wrong about this?

Yes, this is a known issue.  Writable mmap support has been on the
wishlist for probably a year, but I gather that it's a tough problem.
 Locking is another one that comes up often, but it looks like that's
been added in 2.6 beta.

> Do you have any other easily runnable tests?  Or is hand-crafting test
> cases and throwing programs at a filesystem the only way to go?

I think I've found more bugs in my own filesystem by running programs.
 My tests are just for edge cases of my filesystem that I don't think
a random program would trigger.  But the best reports I've had are
from people running programs I've never used.  It is a typical test
problem - if you write custom tests then you're only going to test for
things you know about.  I would have never guessed the behavior of
Mutt, or rsync, or Evolution until I saw the filesystem debug traces..

You could also try creating a user on your system with the home
directory in a virtual filesystem.  Some people run their systems like
this (to get an encrypted home dir, for example), and those people
were the biggest source of bug reports for me.  But you may find that
Mono applications don't work, because Mono expects to be able to make
writable mmap mappings for various files in the home directory (at
least that was the case a year ago).

And by the way, maybe you know, why does every Mono app need a
writable mmap of things from ~/.wapi ?

regards,
Valient