From 47e4d194dc36adfcfd2577fa4630c9fcded005d3 Mon Sep 17 00:00:00 2001
From: Thomas Schwinge <tschwinge@gnu.org>
Date: Sun, 27 Oct 2013 19:15:06 +0100
Subject: IRC.

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

(limited to 'hurd/libfuse.mdwn')

diff --git a/hurd/libfuse.mdwn b/hurd/libfuse.mdwn
index 78e96022..28125dd9 100644
--- a/hurd/libfuse.mdwn
+++ b/hurd/libfuse.mdwn
@@ -49,6 +49,25 @@ etc.
     <braunr> and they could almost readily use our libfuse version
 
 
+## IRC, freenode, #hurd, 2013-10-01
+
+    <pinotree> our libfuse implementation is still basic atm (there's a wiki
+      page about it)
+    <alsuren> okay... talk to me about FUSE
+    <pinotree> even with the improvements i have in my public branch, it still
+      cannot do real-world fs'es
+    <alsuren> okay, so you're the person to ask about FUSE
+    <alsuren> it strikes me that HURD not having FUSE support is a bit of an
+      architectural oversight
+    <pinotree> i'm not sure what's your point about fuse, since what fuse on
+      linux (and not only) does is done *natively* by the hurd
+    <alsuren> exactly
+    <pinotree> all of the hurd filesystems (which are just a type of servers)
+      run in userspace already
+    <alsuren> so FUSE should Just Work
+    <pinotree> well no
+
+
 # Source
 
 [[source_repositories/incubator]], libfuse/master.
-- 
cgit v1.2.3