From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] FreeBSD 9p work
Date: Fri, 13 Sep 2002 02:37:47 -0400 [thread overview]
Message-ID: <Pine.GSO.4.21.0209130235300.17064-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <54e7962c0f199b095b711d14898dbee0@collyer.net>
On Thu, 12 Sep 2002, Geoff Collyer wrote:
> The copy in /sys/src/cmd/unix/9pfreebsd was done for FreeBSD 3.2,
> which is pretty old now. But with IL being phased out, you might not
> need kernel mods at all. Using the NFS/vfs/vnode goo, you can
> probably write a user-mode file server that talks 9P to the remote
> server and NFS/vfs/vnode goo to the local client(s).
Not really - NFS semantics doesn't match 9p and writing a protocol
translator of that sort will be rather painful.
next prev parent reply other threads:[~2002-09-13 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 5:28 Geoff Collyer
2002-09-13 6:37 ` Alexander Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 8:44 nigel
2002-09-13 6:41 Geoff Collyer
2002-09-13 7:29 ` Alexander Viro
2002-09-14 0:19 ` Ronald G Minnich
2002-09-13 9:41 ` Boyd Roberts
2002-09-13 4:07 anothy
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=Pine.GSO.4.21.0209130235300.17064-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--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).