From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] FUSE on Plan9
Date: Fri, 12 Dec 2014 09:22:31 -0500 [thread overview]
Message-ID: <0923EE8C-D874-4910-8FCD-AD7A265E8B03@9srv.net> (raw)
In-Reply-To: <2225996.gtUr9J9EkY@krypton>
On Dec 12, 2014, at 05:49, Jens Staal <staal1978@gmail.com> wrote:
>
> 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's been a few years since I really looked at fuse, so I could be misremembering things, but wouldn't you then have the port the individual plugs into each system anyway? Fuse gives you an interconnect, but not all of that functionality automatically. It's narrower then NDIS, which is nice, but I don't know how much it's going to buy you on its own.
next prev parent reply other threads:[~2014-12-12 14:22 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 [this message]
2014-12-12 14:28 ` Anthony Sorace
2014-12-12 15:47 ` Skip Tavakkolian
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=0923EE8C-D874-4910-8FCD-AD7A265E8B03@9srv.net \
--to=a@9srv.net \
--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).