libfuse is an Hurd-specific implementation of FUSE,
initially written by Stefan Siegl.
The implementation takes advantage of the translators facilities of Hurd: this means that applications that implement a FUSE filesystem, when compiled against libfuse-hurd, become translators to be set with usual settrans etc.
- Only part of the API is implemented
- lowlevel API not implemented
- Options handling (
fuse_opt_*) not implemented
- CUSE lowlevel not supported (compatibility level 29)
- Supports up to the compatibility level 25 (while current libfuse 2.9.x provides 26)
- File I/O is quite slow.
IRC, freenode, #hurd, 2013-05-31
<zacts> well the reason I'm asking, is I'm wonder about the eventual possibility of zfs on hurd <pinotree> no, zfs surely not <zacts> *wondering <zacts> pinotree: would that be because of license incompatabilities, or technical reasons? <pinotree> the latter <taylanub> It's just a matter of someone sitting down and implementing it though, not ? <pinotree> possibly <braunr> zacts: the main problem seems to be the interactions between the fuse file system and virtual memory (including caching) <braunr> something the hurd doesn't excel at <braunr> it *may* be possible to find existing userspace implementations that don't use the system cache (e.g. implement their own) <braunr> and they could almost readily use our libfuse version