From 9667351422dec0ca40a784a08dec7ce128482aba Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <tschwinge@gnu.org>
Date: Wed, 10 Jul 2013 23:39:29 +0200
Subject: IRC.

---
 hurd/libfuse.mdwn | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

(limited to 'hurd/libfuse.mdwn')

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.
-- 
cgit v1.2.3