Files attributes are not really supported: permissions are all assumed
rwx for everything: if you try to write or read on the (mostly system)
files which doesn't allow that, you end up with a (non descriptive)
error.
More of the same about strange files attributes like "compressed", "system" and "ram" that i found on the RAPI specification and about what i have no clue: i simply assume that they don't exist at all. Just be a nice girl/guy, and don't go messing in the /windows directory, ok?! ;-)
The proc-like filesystem doesn't work on the newer devices
At the moment i have only a HTC Dash (where FUR works fine) to test the code with: i don't have a broad picture of what happens with other devices.
A final note about performances: i didn't tried to speed up FUR very much, however being a filesystem on top of userlevel libraries implies that FUR will always be slower than high level utilities like raki, synce or the command line tools (pcp,pls and so on)
For the way it's constructed, FUR will do dozens of RAPI calls (which are the real bottleneck for the PC/PPC operations) each time you list a directory or transfer even a medium sized file (transfers are done in chunks) where the aforementioned utilities need only 1 RAPI call for each transfer. This gap is particularly evident with the old Pocket PC 2003 devices (newer ones work remarkably well).
If you don't care about the whole "i have my device on the file system" thing and you simply need a way to copy and access files on/from the Pocket PC with Linux as fast and effortless as possible, you should definitely use the aforementioned utilities (which are probably more stable than FUR as well, since better supported by the Synce team).
I'd like also to mention SynceFS, a file system
created by Laurent Vivier by
modifying coda: it's a
kernel module, and therefore a different approach than FUR, but you
might well be interested in trying it.
Prev | Home | Next |