From: Yaroslav <yarikos@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx and replica/pull on OS X
Date: Thu, 30 Sep 2010 22:38:02 +0300 [thread overview]
Message-ID: <AANLkTikiqNOi6WF=EyKckP83ztrENffuG+v2S9x-jshp@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinH7XTtwSrUwGxbrwdfiHgDg0cJ3k3TkxfCoS6F@mail.gmail.com>
I use replica for several tasks besides usual system update, in
several different ways.
It (applylog) behaves very reliably when changes go to a tree hosted
by a native plan9 fs (fossil in my case), yet many glitches may arise
(like those reported by Paul) if the destination is a *nix tree over
9P (in my case it is u9fs on AIX). Problems aren't with replica but
with 9P servers on *nix.
I saw replica failing on older 9vx #Z but it went just fine when I
tried with fresh libvx32 pull some months ago.
- Yaroslav
2010/9/11 Eric Van Hensbergen <ericvh@gmail.com>:
> On Fri, Sep 10, 2010 at 10:32 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>>> > What am I doing wrong?
>>>
>>> I would argue that, while it is quite cool in principle, replica is
>>> the wrong way to solve the source distribution problem. I gave up on
>>> replica a year ago because I got tired of the kinds of problems you're
>>> having.
>>
>> while some much-needed patches have been slow in
>> being applied, i don't think bugs (or a broken 9vx #Z)
>> imply that replica is just wrong way to replicate changes
>> to sources.
>>
>
> While that may be true, my experiences with replica have been pretty
> dreadful. I'm just not smart enough to use it properly I guess. The
> other aspect with using it with 9vx is that it gives me easy rollbacks
> since my 9vx bits on my mac aren't currently protected by Venti.
>
> -eric
>
>
next prev parent reply other threads:[~2010-09-30 19:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 1:24 Paul Lalonde
2010-09-11 1:45 ` Eric Van Hensbergen
2010-09-11 2:18 ` ron minnich
2010-09-11 3:32 ` erik quanstrom
2010-09-11 15:27 ` Eric Van Hensbergen
2010-09-30 19:38 ` Yaroslav [this message]
2010-09-11 17:09 ` ron minnich
2010-09-11 22:14 ` ron minnich
2010-09-11 20:42 ` yy
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='AANLkTikiqNOi6WF=EyKckP83ztrENffuG+v2S9x-jshp@mail.gmail.com' \
--to=yarikos@gmail.com \
--cc=9fans@9fans.net \
/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).