From: Chris Silva <ack@xmission.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dist updates from sources.cs.bell-labs.com
Date: Wed, 23 Oct 2002 17:14:32 -0600 [thread overview]
Message-ID: <303B5B4A-E6DD-11D6-B1C2-0030659642C4@xmission.com> (raw)
In-Reply-To: <20021023123657.B37809-100000@fbsd.acl.lanl.gov>
this is what happens:
term% srv -m tcp!sources.cs.bell-labs.com sources /n/sources
post...
!Adding key: dom=outside.plan9.bell-labs.com proto=p9sk1
user[acmesucks]:
password:
!
term% bind /n/sources/plan9 /n/dist
term%
term% replica/pull -v $home/tmp/network
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 184:
'/n/kfs/dist/replica/client/plan9.log' does not exist
term%
Thanks,
Chris
On Wednesday, October 23, 2002, at 12:43 PM, andrey mirtchovski wrote:
> you should do a:
>
> bind /n/sources/plan9 /n/dist
>
> before the replica/pull part and after the 'srv part'
>
> see the Russ Cox' script:
>
> http://groups.google.com/groups?selm=8aa0fc5d47540ca24e1a89f6336a7564%40plan9.
> bell-labs.com&oe=UTF-8&output=gplain
>
> at any rate, you should be able to cd to and list the contents of
> /n/sources after doing a:
>
> srv -m tcp!sources.cs.bell-labs.com sources /n/sources
>
> andrey
>
> On Wed, 23 Oct 2002, Chris Silva wrote:
>
>> term% disk/kfscmd allow
>> term% 9fs kfs
>> term% srv -m tcp!sources.cs.bell-labs.com sources /n/sources
>> post...
>>
>> !Adding key: dom=outside.plan9.bell-labs.com proto=p9sk1
>> user[acmesucks]:
>> password:
>> !
>> term% replica/pull -v /dist/replica/network
>> 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 182:
>> '/n/kfs/dist/replica/client/plan9.log' does not exist
>> term%
>>
>> Any clear fix for this problem?
>>
>> Russ Cox wrote:
>>
>>> Can you send the output of:
>>>
>>> 9fs kfs
>>> srv -m tcp!sources.cs.bell-labs.com sources /n/sources
>>> replica/pull -v /dist/replica/network
>>>
>>> ?
>>
>
>
next prev parent reply other threads:[~2002-10-23 23:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 13:50 Russ Cox
2002-10-23 16:43 ` Chris Silva
2002-10-23 18:43 ` andrey mirtchovski
2002-10-23 18:52 ` Dan Cross
2002-10-23 19:01 ` andrey mirtchovski
2002-10-23 23:14 ` Chris Silva [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-29 1:57 YAMANASHI Takeshi
2002-10-28 23:21 Russ Cox
2002-10-29 1:48 ` Chris Silva
2002-10-28 21:19 Russ Cox
2002-10-28 22:21 ` Chris Silva
2002-10-26 18:20 Russ Cox
2002-10-28 20:01 ` Chris Silva
2002-10-26 16:21 Chris Silva
2002-10-23 20:12 Russ Cox
2002-10-23 9:56 Chris Silva
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=303B5B4A-E6DD-11D6-B1C2-0030659642C4@xmission.com \
--to=ack@xmission.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).