9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: johnny@sorosj.hd.free.fr
To: 9fans@cse.psu.edu
Subject: [9fans] Authenticated mounts from non-plan9 systems
Date: Tue, 30 Oct 2007 12:05:30 +0100	[thread overview]
Message-ID: <bfa9fd3d25faaeb3b22f1bc516fce2d1@sorosj.hd.free.fr> (raw)

Hi eveyone!
I've been a fan of plan9 for quite a while, using it whenever I had a machine that would run it.
Now I have a small network of machines at home, with one plan9 auth+cpu+fs server (yeah, I know that's not much, but I don't have any more hardware that would run it).
I'd like to be able to mount the exports on that machine to other machines (mostly linux): I've been able to get a non-authenticated mount via p9p, but I can't seem to be able to get an authenticated mount. srv says there is no authentication needed. I was wondering if this was a p9p limitation or wether my cpu+auth+fs server was missing something, or if I was doing something wrong.
Here is how I am mounting it right now:
$ srv -a sorosj.hd.free.fr
rx: exportfs: authentication not required

so there is no authentication, though I can do
$ 9 mount `namespace`/sorosj.hd.free.fr /tmp/tmp

and then I can see my root, but I can't write to it. This is regardless of wether I supply mount with authentication parameters or not (eg. -o user=$USER,....,proto=UNIX )
Any help would be greatly appreaciated.
Thanks!
Johnny


             reply	other threads:[~2007-10-30 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30 11:05 johnny [this message]
2007-10-30 13:44 ` Eric Van Hensbergen
2007-10-31  9:54   ` johnny
2007-10-30 14:08 ` Anthony Sorace
2007-10-31  9:55   ` johnny
2007-10-31 10:05     ` johnny
2007-10-31 11:15       ` Russ Cox
2007-10-31 11:18         ` johnny

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=bfa9fd3d25faaeb3b22f1bc516fce2d1@sorosj.hd.free.fr \
    --to=johnny@sorosj.hd.free.fr \
    --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).