From: Michael Grunditz <migu@telia.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] nfsserver problems
Date: Mon, 28 Apr 2003 13:06:25 +0100 [thread overview]
Message-ID: <7e4737ea4b.micken@privat.utfors.se> (raw)
In-Reply-To: <6b1c3250.0304262249.444616d3@posting.google.com>
Oh no new lines , :)
This is a fixed version ..
In message <6b1c3250.0304262249.444616d3@posting.google.com> you wrote:
> Hi
I finaly got a x86pc again to run Plan9. My primary workstation is a
> Acorn RiscPC running RISCOS. I want to use the plan9 box as a
> fileserver using nfs. RISCOS isnt unix and doesnt have any passwd or
> group files , and relies on pcnfsd for authentication.When I start the
> nfsserver I get "something" like this
aux/nfsserver -v -a il!plan9
xmesg 104 - attach failed - authentification failed
The plan9 pc is a standalone cpu/authserver with kfs.The auth server
works just fine for telnet, ftp etc.I can do con -l .
I can mount the cpuserver from the cpuserver
/Michael Grunditz
next prev parent reply other threads:[~2003-04-28 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 9:11 Michael Grunditz
2003-04-28 12:06 ` Michael Grunditz [this message]
2003-04-28 15:16 ` Russ Cox
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=7e4737ea4b.micken@privat.utfors.se \
--to=migu@telia.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).