<?xml version="1.0" encoding="UTF-8"?>

<rdf:RDF 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns="http://purl.org/rss/1.0/"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
>

  <channel rdf:about="http://lwn.net/headlines/68104/">
    <title>LWN: Comments on "FUSE - implementing filesystems in user space"</title>
    <link>http://lwn.net/Articles/68104/</link>
    <description>
This is a special feed containing comments posted
to the individual LWN article titled &quot;FUSE - implementing filesystems in user space&quot;.

    </description>

    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>2</syn:updateFrequency>
    <items>
      <rdf:Seq>
	<rdf:li resource="http://lwn.net/Articles/69913/rss" />
	<rdf:li resource="http://lwn.net/Articles/69911/rss" />
	<rdf:li resource="http://lwn.net/Articles/69054/rss" />
	<rdf:li resource="http://lwn.net/Articles/68634/rss" />
	<rdf:li resource="http://lwn.net/Articles/68629/rss" />
	<rdf:li resource="http://lwn.net/Articles/68572/rss" />
	<rdf:li resource="http://lwn.net/Articles/68565/rss" />
	<rdf:li resource="http://lwn.net/Articles/68560/rss" />
	<rdf:li resource="http://lwn.net/Articles/68550/rss" />
	<rdf:li resource="http://lwn.net/Articles/68541/rss" />
	<rdf:li resource="http://lwn.net/Articles/68535/rss" />
	<rdf:li resource="http://lwn.net/Articles/68527/rss" />
	<rdf:li resource="http://lwn.net/Articles/68523/rss" />
	<rdf:li resource="http://lwn.net/Articles/68520/rss" />
	<rdf:li resource="http://lwn.net/Articles/68513/rss" />
      
      </rdf:Seq>
    </items>

  </channel>
    <item rdf:about="http://lwn.net/Articles/69913/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/69913/rss</link>
      <dc:date>2004-02-06T04:59:59+00:00</dc:date>
      <dc:creator>mcatkins</dc:creator>
      <description>
      Ron Minnich had a good go at it, but I don't think it was really&lt;br&gt;completed - pitty, because as you say, it would &amp;quot;let you implement&lt;br&gt;almost anything you like...&amp;quot;&lt;p&gt;Some stuff is on his homepage at:&lt;br&gt;  http://public.lanl.gov/rminnich/&lt;br&gt;and there is an inactive sourceforge site at:&lt;br&gt;  http://v9fs.sourceforge.net/&lt;p&gt;There was also work on private namespaces for Linux and BSD, which is&lt;br&gt;the other key technology to getting this all to work properly!
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/69911/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/69911/rss</link>
      <dc:date>2004-02-06T03:47:55+00:00</dc:date>
      <dc:creator>xoddam</dc:creator>
      <description>
      Has anyone ever written a 9P (aka 9fs) client for Linux?  I know there are a couple of servers but I can't see anything obvious on Google.&lt;p&gt;a kernel-space 9P client would let you implement almost anything you like in terms of filesystems as userspace servers.&lt;br&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/69054/rss">
      <title>Userspace NFS</title>
      <link>http://lwn.net/Articles/69054/rss</link>
      <dc:date>2004-01-31T21:19:34+00:00</dc:date>
      <dc:creator>kamil</dc:creator>
      <description>
      That has always been my recollection, as well.  NFS server in user space, using Linux-specific calls like setfsuid(2), client in the kernel.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68634/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68634/rss</link>
      <dc:date>2004-01-29T14:17:43+00:00</dc:date>
      <dc:creator>mszeredi</dc:creator>
      <description>
      OK, so making homepages is not my strong point :).  This is not the first time somebody complains, and it's now being worked on by a brave volunteer (SF job recruitment is cool).&lt;p&gt;Anyway here's a link to a list of filesystems (that I know of) that are using FUSE:&lt;p&gt;http://www.inf.bme.hu/~mszeredi/fuse/Filesystems&lt;br&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68629/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68629/rss</link>
      <dc:date>2004-01-29T14:00:40+00:00</dc:date>
      <dc:creator>mszeredi</dc:creator>
      <description>
      Security is one of the main design principles of FUSE.  The only operation that requires root access is the mounting, and that can be done fairly securely by a non-root user with the help of a suid program (fusermount).
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68572/rss">
      <title>SieFS</title>
      <link>http://lwn.net/Articles/68572/rss</link>
      <dc:date>2004-01-29T10:55:25+00:00</dc:date>
      <dc:creator>hensema</dc:creator>
      <description>
      SieFS is an example of a filesystem implemented with FUSE. SieFS can mount the filesystems of recent Siemens mobile phones (such as the S55) on Linux. Site: http://mirror01.iptelecom.net.ua/~dmitry_z/siefs/
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68565/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68565/rss</link>
      <dc:date>2004-01-29T10:03:17+00:00</dc:date>
      <dc:creator>mjr</dc:creator>
      <description>
      &lt;p&gt;
There's also &lt;a href=&quot;http://lufs.sourceforge.net/lufs/&quot;&gt;LUFS&lt;/a&gt;
(which incidentally supports gnome-vfs modules like fuse supports
kioslaves - can't have one doing both, it seems ;).
I'd really like to see &lt;em&gt;one&lt;/em&gt; of these make it to the default kernel...
&lt;/p&gt;

&lt;p&gt;
Anyway, anyone know if the fuse kernel interface is secure nowadays,
in a sense that one can safely allow users to freely use even their own
filesystem code to mount things? I asked basically the same on the lufs list
a good while back, and there were, in effect, no answers, and the
lufs daemons seem to run as root which is a kind of telltale sign
that one doesn't want arbitrary user code there...
&lt;/p&gt;

      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68560/rss">
      <title>Userspace NFS</title>
      <link>http://lwn.net/Articles/68560/rss</link>
      <dc:date>2004-01-29T09:18:19+00:00</dc:date>
      <dc:creator>Ross</dc:creator>
      <description>
      I thought only the NFS server was in userspace but the client was always&lt;br&gt;in the kernel.  Or am I just not remembering correctly?
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68550/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68550/rss</link>
      <dc:date>2004-01-29T08:38:30+00:00</dc:date>
      <dc:creator>stuart2048</dc:creator>
      <description>
      One of the cool features of userland isolation is that it's much easier to watch behaviour and resource consumption.  Curious about how much memory or CPU your protocol stack is consuming?  Easy...&lt;p&gt;--Stuart
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68541/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68541/rss</link>
      <dc:date>2004-01-29T06:56:09+00:00</dc:date>
      <dc:creator>aleXXX</dc:creator>
      <description>
      KIO fuse &amp;quot;gateway&amp;quot;:  &lt;br&gt;  &lt;br&gt;http://kde.ground.cz/tiki-index.php?page=KIO+Fuse+Gateway  &lt;br&gt;  &lt;br&gt;And it works :-)  &lt;br&gt;Only the file mode flags (for opening) are still ignored, mainly I need more  &lt;br&gt;users/testers now :-)  &lt;br&gt;  &lt;br&gt;Bye  &lt;br&gt;Alex &lt;br&gt;&amp;lt;neundorf at kde dot org &amp;gt;  
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68535/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68535/rss</link>
      <dc:date>2004-01-29T05:45:16+00:00</dc:date>
      <dc:creator>mcatkins</dc:creator>
      <description>
      Unfortunately, this seems to be something of a graveyard of projects, I also know of (at least):&lt;p&gt;Podfuk: http://atrey.karlin.mff.cuni.cz/~pavel/podfuk/podfuk.html&lt;br&gt;userfs: http://www.penguin.cz/~jim/userfs/&lt;br&gt;uvfs: http://www.sciencething.org/geekthings/index.html&lt;br&gt;virtualfs: http://www.solucorp.qc.ca/virtualfs/&lt;p&gt;(although the last subverts libc, rather than using a kernel module)&lt;p&gt;as well as my own effort (not yet released!) allowing filesystems to be written in Python (as does fuse), but without requiring a non-standard kernel module.&lt;br&gt;
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68527/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68527/rss</link>
      <dc:date>2004-01-29T03:54:46+00:00</dc:date>
      <dc:creator>iabervon</dc:creator>
      <description>
      I think it's a good idea to support microkernel-like behavior, so that &lt;br&gt;users can trade off performance for isolation. I'd certainly prefer that &lt;br&gt;drivers be in userspace when performance isn't an issue; if my PDA sync &lt;br&gt;takes twice as many context switches, I probably won't even notice the &lt;br&gt;difference, but I will be glad if it doesn't take the system down if it &lt;br&gt;is buggy. On the other hand, I don't think that Linux will get &lt;br&gt;particularly micro; just because you can have filesystems and drivers in &lt;br&gt;userspace doesn't mean that having your root filesystem or video drivers &lt;br&gt;in userspace is going to be a good idea. &lt;br&gt; &lt;br&gt; 
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68523/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68523/rss</link>
      <dc:date>2004-01-29T02:50:25+00:00</dc:date>
      <dc:creator>marduk</dc:creator>
      <description>
      It certainly does seem like Linux is becoming more and more microkernel-like every day.  One wonders what Linus says about this.
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68520/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68520/rss</link>
      <dc:date>2004-01-29T02:41:01+00:00</dc:date>
      <dc:creator>pynm0001</dc:creator>
      <description>
      Actually, there is a project to implement the KIO protocol using FUSE.  &lt;br&gt;This would enable GTK/GNOME applications to use the KIO slaves, for &lt;br&gt;example. &lt;br&gt; &lt;br&gt;I don't know the link offhand, but I think http://dot.kde.org/ has news &lt;br&gt;about it. 
      
      </description>
    </item>
    <item rdf:about="http://lwn.net/Articles/68513/rss">
      <title>FUSE - implementing filesystems in user space</title>
      <link>http://lwn.net/Articles/68513/rss</link>
      <dc:date>2004-01-29T02:17:57+00:00</dc:date>
      <dc:creator>flewellyn</dc:creator>
      <description>
      Interesting.  So, how long before Linux becomes a microkernel, then?  :-)
      
      </description>
    </item>
</rdf:RDF>

