From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica/pull..
Date: Tue, 28 May 2002 15:24:37 -0400 [thread overview]
Message-ID: <ad761b4d30205ee694f11d9da8a51006@plan9.bell-labs.com> (raw)
> > 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 didn't want to do that.
/n/sources and /n/kfs are mount points
that will get things mounted on them.
If you type 9fs kfs you should then see
many files in /n/kfs/dist.
You should probably remove the files
you created; they'll just confuse things.
9fs kfs
rm -r /n/kfs/n/kfs/dist # NOTE THE DOUBLED /n/kfs !!!
Don't worry about messages about directories or files
not existing in /n/kfs or /n/sources until we settle
the auth problems.
Maybe you typed the wrong password.
Try this:
auth/factotum
srv -m tcp!sources.cs.bell-labs.com sources /n/sources
Be sure to type the password you used when you
created the account. What user name did you use?
I don't see any obvious variants of ishwar in the
user list.
Russ
next reply other threads:[~2002-05-28 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 19:24 rsc [this message]
2002-05-28 15:58 ` Ish Rattan
2002-05-28 16:00 ` Ish Rattan
-- 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 16:53 rsc
2002-05-28 15:30 ` Ish Rattan
2002-05-29 5:49 ` Adrian Tritschler
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=ad761b4d30205ee694f11d9da8a51006@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).