From: Ish Rattan <ishwar@pali.cps.cmich.edu>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] replica/pull..
Date: Tue, 28 May 2002 11:30:29 -0400 [thread overview]
Message-ID: <Pine.LNX.4.33L2.0205281125500.18554-100000@pali.cps.cmich.edu> (raw)
In-Reply-To: <2777e2b088c18d8b14863fe0545323b9@plan9.bell-labs.com>
On Tue, 28 May 2002 rsc@plan9.bell-labs.com wrote:
> I think you need to
>
> mkdir /n/sources
> or
> disk/kfscmd 'create /n/sources sys sys 555 d'
I did that and it complained about /n/sources/replica dir, so I made one.
It then complained about /n/kfs/dis/replica/client/plan9.log (structure
was upto /n/kfs), so made the dirsa nd touched plan9.log too.
> You are also having authentication problems.
> What does
>
> ndb/query authdom outside.plan9.bell-labs.com auth
>
> print?
sources.cs.bell-labs.com
I can't ping outside.plan9.bell-labs.com, maybe it is not relevant?
The error message is now
srv tcp!sources.cs.bell-labs.com: mount failed: authentication failed
rm: /n/kfs/dist/replica/client/plan9.log: '/n/kfs/dist/replica/client/plan9.log' does not exist
rm /n/kfs/dist/replica/client/plan9.log: rm 432: '/n/kfs/dist/replica/client/plan9.log' does not exist
-ishwar
next prev parent reply other threads:[~2002-05-28 15:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 16:53 rsc
2002-05-28 15:30 ` Ish Rattan [this message]
2002-05-29 5:49 ` Adrian Tritschler
-- strict thread matches above, loose matches on Subject: below --
2002-12-26 1:28 [9fans] Replica/pull Ish Rattan
2002-12-26 2:03 ` Russ Cox
2002-12-26 2:04 ` Russ Cox
2002-12-26 2:21 ` Ish Rattan
2002-12-26 2:32 ` Russ Cox
2002-05-29 5:57 [9fans] replica/pull rsc
2002-05-28 19:48 rsc
2002-05-28 19:24 rsc
2002-05-28 15:58 ` Ish Rattan
2002-05-28 16:00 ` Ish Rattan
2002-05-28 16:05 [9fans] 9660srv Russ Cox
2002-05-28 12:37 ` [9fans] replica/pull Ish Rattan
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=Pine.LNX.4.33L2.0205281125500.18554-100000@pali.cps.cmich.edu \
--to=ishwar@pali.cps.cmich.edu \
--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).