FUR filesystem 0.4.5

FUR is a application that let the user mount a Windows CE based device on your Linux file system.

  Add it to your Download Basket!

 Add it to your Watch List!


Rate it!

What's new in FUR filesystem 0.4.5:

  • Single threaded operation was enforced to comply with newer versions of Synce.
Read full changelog
send us
an update
GPL (GNU General Public License) 
2.5/5 15
Riccardo Di Meo
ROOT \ System \ Filesystems
FUR is a application that let the user mount a Windows CE based device on your Linux file system: it uses the brilliant FUSE (acronym of File system in UserSpacE of Miklos Szeredi) and the great librapi2 of the Synce Project, a unix implementation of the RAPI protocol (that your device use to communicate with your other operating $ystem ) which you can find here, along with other very nice tools.

You execute it with proper arguments, then (if everything goes fine) the entire file system of your (previously connected) handheld will appear automagically mounted like a regular Linux file system where you will be able to copy, move read and write data with your favorite programs.

FUR filesystem means FUSE use libRAPI.

What dose not?

· Not very stable, particulary if used concurrently by different processes (but should be usable).
· Not well tested.
· The source is horrible(Tm).
· The implementation is more involved than it should.
· Lack documentation.
· Not even remotely optimized.
· Configuration tools deficient.
· Random access I/O is anti-optimized.
· Write is bugged (maybe a problem with concurrent file access).
· The resource locking system (e.g. to prevent different processes to write on the same file) is only roughly implemented (there's a lot to be done).
· Total absence of a caching system of some sort (which i hope to implement, sooner or later).
· Some errors are to obscure (and maybe not well implemented).
· Some attributes (e.g. ctime) are not implemented (the needed function in the librapi2 library is not yet implemented).
· No UID/GID check: this is not a security issue: only the user that invoke the dccm demon can access the filesystem, but other users should be able to see some kind of error message (which i will implement soon).
· Lot of other things i have forgot now.
· The log reporting suck

Last updated on March 22nd, 2009


#file system #userspace filesystem #FUSE use libRAPI #FUR #filesystem #userspace #FUSE

Add your review!