diff options
author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-09-28 16:22:08 +0200 |
---|---|---|
committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-09-28 16:22:08 +0200 |
commit | ca39ad0592e9b99dac9d99c68bb36ef1d27f72df (patch) | |
tree | 5ad12783d506039cd440ccfacbac264085137075 /hurd/libfuse.mdwn | |
parent | be2307c1bf9aef3e22984dd298827d8e1ca18b2c (diff) | |
parent | 264b066cd313b23f6748711c6f9b4d3336e03136 (diff) |
Merge branch 'master' of braunbox:~hurd-web/hurd-web
Diffstat (limited to 'hurd/libfuse.mdwn')
-rw-r--r-- | hurd/libfuse.mdwn | 20 |
1 files changed, 20 insertions, 0 deletions
diff --git a/hurd/libfuse.mdwn b/hurd/libfuse.mdwn index 45ff97ec..78e96022 100644 --- a/hurd/libfuse.mdwn +++ b/hurd/libfuse.mdwn @@ -29,6 +29,26 @@ etc. * 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 + + # Source [[source_repositories/incubator]], libfuse/master. |