From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FUSE on Plan9
Date: Fri, 12 Dec 2014 07:47:12 -0800 [thread overview]
Message-ID: <18322945-1D97-40E2-9BDB-60F994E49D61@gmail.com> (raw)
In-Reply-To: <2225996.gtUr9J9EkY@krypton>
Drawterm exports local fs (ntfs, ext, etc.) to plan 9; you could make an exportfs only version.
Russ did 9pfuse several years ago; allows fuse fs access to Plan 9 file server. iirc worked with Linux and Mac OS X.
> On Dec 12, 2014, at 2:49 AM, Jens Staal <staal1978@gmail.com> wrote:
>
> This might not be popular among most Plan9 users, but I started thinking about
> the possibility of FUSE on Plan9 after seeing the FUSE on WebDAV [1] project.
> At least on 9front, WebDAV should be integrated in webfs.
>
> Would this theoretically work? The advantage of FUSE is access to a number of
> popular file systems (most notably ext4, NTFS, ZFS) and also many special-
> purpose file systems.
>
> It feels a bit round-about and wasteful to go via webfs, so I guess the most
> appropriate method would be to implement a FUSE library directly on top of 9P
> instead of the kernel VFS - possibly by porting the NetBSD
> librefuse/libperfused [2] or the OpenBSD libfuse [3]. The disadvantage with
> this approach is that I am far too inexperienced and have far too little time
> to actually attempt this.
>
> What are your thoughts? Should I try to get the fuse-on-webdav working on
> Plan9? Any other attempts with a more proper port/implementation already
> ongoing?
>
> 1. https://github.com/rianhunter/davfuse
> 2. http://netbsd.gw.com/cgi-bin/man-cgi?perfused+8+NetBSD-6.0
> 3. http://undeadly.org/cgi?action=article&sid=20131108082749
>
>
next prev parent reply other threads:[~2014-12-12 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:49 Jens Staal
2014-12-12 14:22 ` Anthony Sorace
2014-12-12 14:28 ` Anthony Sorace
2014-12-12 15:47 ` Skip Tavakkolian [this message]
2014-12-12 16:36 ` cinap_lenrek
2014-12-12 17:29 ` Jens Staal
2014-12-12 18:08 ` cinap_lenrek
2014-12-12 20:13 ` Quintile
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18322945-1D97-40E2-9BDB-60F994E49D61@gmail.com \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).