From: Matthias Teege <mtg@crn.mteege.de>
To: 9fans@hamnavoe.com, 9fans@cse.psu.edu
Subject: Re: [9fans] nfsserver no mapping
Date: Mon, 31 Jan 2005 13:06:22 +0000 [thread overview]
Message-ID: <7bc39fde9945272fe73889a9e866828b@crn.mteege.de> (raw)
In-Reply-To: <01db1b7d580db9b1364b20b1cc200ac5@hamnavoe.com>
> The xxx:yyy pair names the host running nfsserver and the host with
Ah, thanks
> the filestore being served. In your case they are both crn, so you
> should try
> mount -o soft,intr crn:crn /n/crn
I've got the same error message. Is it necessary to prepare somthing
on the fileserver?
Matthias
next parent reply other threads:[~2005-01-31 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01db1b7d580db9b1364b20b1cc200ac5@hamnavoe.com>
2005-01-31 13:06 ` Matthias Teege [this message]
2005-01-31 14:19 ` Richard Miller
[not found] <fbcfa173833558cd93d5a581cdf62e94@hamnavoe.com>
2005-01-31 14:50 ` Matthias Teege
2005-01-31 15:52 ` Richard Miller
2005-01-31 7:29 Matthias Teege
2005-01-31 9:47 ` Richard Miller
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=7bc39fde9945272fe73889a9e866828b@crn.mteege.de \
--to=mtg@crn.mteege.de \
--cc=9fans@cse.psu.edu \
--cc=9fans@hamnavoe.com \
/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).