From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] exportfs -r vs /rc/bin/service/!tcp564
Date: Mon, 6 May 2013 16:41:10 -0400 [thread overview]
Message-ID: <4f5ad5c890f7b32a04df7bb3ae1afca1@ladd.quanstro.net> (raw)
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
next reply other threads:[~2013-05-06 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 20:41 erik quanstrom [this message]
2013-05-06 22:00 ` a
2013-05-06 22:17 ` erik quanstrom
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=4f5ad5c890f7b32a04df7bb3ae1afca1@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).