From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P clients for other OSes?
Date: Tue, 18 Jun 2002 11:56:48 -0400 [thread overview]
Message-ID: <e0818375af20e9fdc2d5933eec1508b2@plan9.bell-labs.com> (raw)
> I came across Ronald Minnich's 9P work for Unixes, but I'm just
> curious, has anyone attempted the same for Windows, Macintosh, etc? I
> realize the uses might be more limited, but it would seem that if a 9P
> client is easier to write than, say, an SMB server for Plan 9, it
> could be extremely useful for file service in a heterogenous
> environment.
someone in france (at inria or univ-paris8?) announced an smb
client, though i haven't seen the code.
i'm thinking hard about writing a translator for plan 9
and unix to go between smb, 9p, nfs, sfs, and maybe afs.
(i have too many file services i'd like to connect to.)
we'll see. probably in the fall.
russ
next reply other threads:[~2002-06-18 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 15:56 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-18 9:31 Jack Johnson
2002-06-18 21:48 ` Ronald G Minnich
2002-06-19 16:17 ` Douglas A. Gwyn
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=e0818375af20e9fdc2d5933eec1508b2@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).