Re: [fuse-devel] Status of FUSE port for Windows

[Evan D. <dri...@cs...>]

Miklos Szeredi wrote:
>> I am sure this is a very regular question, but in case I have missed  
>> the latest status from my Googlequest, what is the present status of  
>> a FUSE port for Windows? Is it non-existent, in-process, etc?
>>
>> I have a project that has a need which FUSE could solve, but it has  
>> to be on Windows....
> 
> I only know of this:
> 
>   http://www.osronline.com/showThread.CFM?link=105895
> 

I'm the person who sent in that email. As you can see from the replies, 
most people seemed to think that this wouldn't work in such a short time 
period. For now, we are being very optimistic and going forward with the 
project, but should know a bit better in a couple weeks where we stand 
and if we are going to stick with it or bail and go do something else.

So no promises by any means, but for now we're on.


There are also some other people who are doing something in this area. 
All of these are from the last couple months so I don't know of anything 
available yet.

  - http://apple.slashdot.org/comments.pl?sid=217284&cid=17643614
  - http://marc.theaimsgroup.com/?l=fuse-devel&m=116905556428722&w=2
I don't know where either of these people stand, or what their approach is.

  - http://asbjorn.it/blog/2007/01/fuse-for-windows/
The first response to this is correct. A Shell Namespace Extension is 
one way to do something like FUSE, but it's far from optimal. (For 
instance, it won't work with all applications.)


Finally, not FUSE, but you might look at FIFS if you need to *write* a 
file system but not necessarily use one that was already done for FUSE:
  - http://web.mit.edu/fifs/www/
It's an old project and I don't know if it still works.


Evan