Recent changes in masterfs started to make more
use of ResourcePath.getFile(), which it turns out
was totally broken on Unix. This would result in
the creation of files with URLs such as
file:/some/dir/home/jglick/ rather than
file:/home/jglick/ where the IDE was started with
current working directory /some/dir. Therefore the
IDE was thoroughly broken; for example, you could
not open any projects.

Hotfix is to impl getFile to behave differently on
Unix than on Windows: on Unix, make a File with
the initial '/', and on Windows, make it without
the initial '/' and with '\\' as the separator.

This looks very fragile however and I suggest the
whole representation of disk roots in masterfs be
reconsidered so as to be more robust and
platform-neutral; e.g. use an escaped version of
the disk root's absolute path as the first path
component on *all* platforms, so e.g. on Unix you
would have "/%5C/home/jglick" for /home/jglick and
on Windows you would have "/d:/temp/foo" for
d:\temp\foo.

Also masterfs unit tests failed massively on Unix.
With the patch, they pass (on Unix anyway).

Since masterfs is now critical for the
functionality of large parts of the IDE, I would
suggest its tests be given greater attention.
Every aspect of its functionality must be totally
covered by unit tests, and probably they should be
part of commit validation.