From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port lacks exportfs server
Date: Mon, 6 Oct 2008 20:43:54 -0700 [thread overview]
Message-ID: <1223351034.19902.17.camel@goose.sun.com> (raw)
In-Reply-To: <ee9e417a0810060924p7db19386s8b28dbc1ed2254b2@mail.gmail.com>
Hi Russ!
First of all -- thanks a lot for answering.
On Mon, 2008-10-06 at 09:24 -0700, Russ Cox wrote:
> > somehow it dawned on me that plan9port lacks
> > an application to serve a local filesystem
> > over 9P. Is this on purpose? Am I missing
> > something fundamental that would allow
> > for a moral equivalent of exportfs?
>
> I pull things in as they are needed.
> I have not needed to serve 9P.
> Adding u9fs sounds reasonable, but of
> course it is already in Unix-compilable
> form elsewhere.
Of course, although the utility of plan9port
as a one stop shop for everything Plan9
on UNIX platforms is quite significant.
Hence the question -- would you be in favor
of continue adding things as needed. And
if so, what kind of of groundwork would
you expect from the contributors?
Thanks,
Roman.
P.S. I see that sqweek has the 9pcon
and (not to overcommit myself ;-))
I also might be able to contribute things
like u9fs and nfsserver.
next prev parent reply other threads:[~2008-10-07 3:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 22:15 Roman Shaposhnik
2008-10-06 16:24 ` Russ Cox
2008-10-07 0:36 ` sqweek
2008-10-07 3:43 ` Roman V. Shaposhnik [this message]
2008-10-18 17:20 ` Russ Cox
2008-10-23 5:26 ` Roman V. Shaposhnik
2008-10-23 17:39 ` Russ Cox
2008-10-30 18:07 ` Enrico Weigelt
2008-10-30 21:15 ` Roman V. Shaposhnik
2008-11-01 19:05 ` Enrico Weigelt
2008-11-01 20:40 ` Roman Shaposhnik
2008-11-03 0:15 ` Enrico Weigelt
2008-11-04 1:23 ` Roman V. Shaposhnik
2008-11-04 1:23 ` Roman V. Shaposhnik
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=1223351034.19902.17.camel@goose.sun.com \
--to=rvs@sun.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).