9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica/pull hungup channel
Date: Fri, 16 Aug 2002 09:30:19 +0900	[thread overview]
Message-ID: <22068de24ede5025e8b09a36e02924b5@granite.cias.osakafu-u.ac.jp> (raw)

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

Honestly, I've also been scared to use replica/pull.  ☺
So, I setup a terminal with local HDD, and it does only replica/pull
from sources.plan9.bell-labs.com.  And then, I also do replica/pull
from that local machine to our file server...   In this case, I can re-
examine with enough time to see what is different!

I just read Russ's Tra page, however, it seems to me not so easy to
grasp at a glance.   I'm now suffering from discripancy between
new control(2) library and our applications written by Yoshitatsu.
Most of the problem is comming from his confusion of channel
usage(☺), however, I have to rewrite them before the start of next
semester...

Kenji

[-- Attachment #2: Type: message/rfc822, Size: 2519 bytes --]

From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] replica/pull hungup channel
Date: Thu, 15 Aug 2002 14:49:10 +0100
Message-ID: <2b1d0337bda6deb7dd36bbcdd0eb034c@vitanuova.com>

> But next, I am a little scared by many lines of;
>                                                        ^^^^^^^^
> > 	somefile: locally created; will not update
>
> This will not happen so frequently, if you'd really changed them localy.
> It will happen only at developping site.  :-)

mind you, it's not clear what you're supposed to do when you get lots
of such messages to resolve them in a safe way.  i finally got around
to trying to use replica to synchronise from our fileserver to my
laptop, and got 22602 such lines; when i actually went through and did
a cmp of all those files, it turned out that only 192 were genuinely
different.  i didn't find replica easy to use!

then i tried tra, which was altogether easier...  and surprisingly
quick, considering the amount of data that it was shifting.  i was a
little surprised to find it indexing in directories that i thought i'd
excluded, though.

  cheers,
    rog.

             reply	other threads:[~2002-08-16  0:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16  0:30 okamoto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-16  6:35 nigel
2002-08-15 13:49 rog
2002-08-15 17:13 ` William Josephson
2002-08-15  4:13 okamoto
2002-08-15  9:51 ` arisawa
2002-08-15  0:30 YAMANASHI Takeshi
2002-08-15  0:22 Russ Cox
2002-08-15  0:18 YAMANASHI Takeshi
2002-08-14  9:40 YAMANASHI Takeshi
2002-08-14 10:31 ` Lucio De Re

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=22068de24ede5025e8b09a36e02924b5@granite.cias.osakafu-u.ac.jp \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).