From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] user-level file systems for Linux
Date: Thu, 19 Feb 2004 03:19:21 +0100 [thread overview]
Message-ID: <03f801c3f68e$ca76ad30$67844051@SOMA> (raw)
In-Reply-To: <2188d527e30fa4f76b933b52ede07d9e@plan9.bell-labs.com>
> I'm optimistic about FUSE because it's almost
> an exact translation of the VFS layer, meaning that it's
> simple and as expressive as possible.
hmm, interesting. i'd like to code some f/s interface to some
PCI FPGA boards, which would make life a lot easier.
next prev parent reply other threads:[~2004-02-19 2:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 1:57 Russ Cox
2004-02-19 2:19 ` boyd, rounin [this message]
2004-02-19 2:20 ` ron minnich
2004-02-19 2:35 ` boyd, rounin
2004-02-19 4:45 ` Martin C.Atkins
2004-02-19 4:58 ` ron minnich
2004-02-19 9:20 ` Charles Forsyth
2004-02-19 14:46 ` ron minnich
2004-02-19 14:50 ` boyd, rounin
2004-02-19 14:57 ` Stephen Wynne
2004-02-19 3:10 YAMANASHI Takeshi
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='03f801c3f68e$ca76ad30$67844051@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.edu \
/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).