Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
[9fans] exportfs -r vs /rc/bin/service/!tcp564
13 views
Skip to first unread message
erik quanstrom
May 6, 2013, 4:41:10 PM5/6/13
to
exportfs(4) claims that -r skips the initial protocol. but it appears that
it only skips the initial part of the intial protocol, making
; cat /n/sources/plan9/rc/bin/service/!tcp564
#!/bin/rc
mount '#s/boot' /root $rootspec
exec /bin/exportfs -r /root
incompatable with real file servers. it appears that the
linux 9p file module requires this behavior, and it is not
capable of connecting to regular file servers.
so my question is, should the manual page or the code
be corrected?
- erik
it only skips the initial part of the intial protocol, making
; cat /n/sources/plan9/rc/bin/service/!tcp564
#!/bin/rc
mount '#s/boot' /root $rootspec
exec /bin/exportfs -r /root
incompatable with real file servers. it appears that the
linux 9p file module requires this behavior, and it is not
capable of connecting to regular file servers.
so my question is, should the manual page or the code
be corrected?
- erik
a...@9srv.net
May 6, 2013, 6:00:17 PM5/6/13
to
Alternately, see /n/sources/patch/import-z. That seems like
the right answer to me.
I assume you mean the !tcp564 example is incompatible
with real *9p clients*.
the right answer to me.
I assume you mean the !tcp564 example is incompatible
with real *9p clients*.
erik quanstrom
May 6, 2013, 6:17:02 PM5/6/13
to
On Mon May 6 18:01:45 EDT 2013, a...@9srv.net wrote:
> Alternately, see /n/sources/patch/import-z. That seems like
> the right answer to me.
isn't this trying to solve a problem already solved by srv(1)
> Alternately, see /n/sources/patch/import-z. That seems like
> the right answer to me.
in an incompatable way?
> I assume you mean the !tcp564 example is incompatible
> with real *9p clients*.
- erik
0 new messages