From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Replica (partly?) stuck in time
Date: Thu, 20 May 2010 08:24:13 -0700 [thread overview]
Message-ID: <AANLkTindU39p2jJe_VSzDeTiWcfX-oWEU_ZWmtw-Y8CN@mail.gmail.com> (raw)
In-Reply-To: <AANLkTilXkeBLKI_PI5IYBXT8UGvHJKDKddV-CKSkRTJc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
On Thu, May 20, 2010 at 8:23 AM, David Leimbach <leimy2k@gmail.com> wrote:
>
>
> On Wed, May 19, 2010 at 10:45 PM, ron minnich <rminnich@gmail.com> wrote:
>
>> On Wed, May 19, 2010 at 10:08 PM, <a@9srv.net> wrote:
>>
>> > I'm stumped. Anyone have any ideas?
>>
>>
>> Yes, what I have done is stop using replica. I pull source from
>> bitbucket.org and build.
>>
>> Replica is an interesting idea that does not work in the wide area. At
>> least not for me ...
>>
>> ron
>>
>>
> Who's updating the bitbucket.org sources, and how does one get started
> doing that?
>
> I've, after quite a long break, tried to get a Plan 9 CPU server up again
> in a VM, and found the wiki instructions need some help, as they skip over a
> few details needed to get a server up and running.
>
> Maybe we need a "Guide" book.
>
> Also I epically failed to use Maht's warlock for setting up a CPU server as
> well, though I think it's a pretty great idea.
>
> Dave
>
How about a Google Wave for setting up Plan 9 CPU servers? :-)
If you gave up on Wave previously, it's gotten a lot better in the last few
months...
It's also now open to anyone without invitation.
[-- Attachment #2: Type: text/html, Size: 2090 bytes --]
next prev parent reply other threads:[~2010-05-20 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 5:08 a
2010-05-20 5:45 ` ron minnich
2010-05-20 15:23 ` David Leimbach
2010-05-20 15:24 ` David Leimbach [this message]
2010-05-20 15:46 ` ron minnich
2010-05-20 15:48 ` erik quanstrom
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=AANLkTindU39p2jJe_VSzDeTiWcfX-oWEU_ZWmtw-Y8CN@mail.gmail.com \
--to=leimy2k@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).