9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] sources/contrib
Date: Tue, 20 Nov 2007 22:36:39 +0100	[thread overview]
Message-ID: <5d375e920711201336t6eaeba6fi35151042bd22194c@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60711201221r73e8f8a9t7587391782ba6af4@mail.gmail.com>

Read 9fans archives, replica/pull has wiped out more than a handful of systems,
if you run venti you can recover, but it is not fun.

And as erik points out, replica also has trouble with many corner cases.

And finally, it is incredibly slow, but that is probably mostly due to
9p's latency sensitivity.

uriel

On Nov 20, 2007 9:21 PM, David Leimbach <leimy2k@gmail.com> wrote:
> On Nov 20, 2007 10:31 AM, Uriel <uriel99@gmail.com> wrote:
> > On Nov 20, 2007 4:57 PM, Federico Benavento <benavento@gmail.com> wrote:
> > > lsr, replica, for me are the same.
> > > I don't wan't people to have to download
> > > a big .tgz just because I edited one line
> > > of code. Plus with the ported stuff it gets
> > > worst, there are people that because
> > > of lack of memory, or whatever can't
> > > even build the libs, that's why I'm
> > > including binaries
> >
> > Maybe we could fix swap instead so people could actually build stuff
> > without crashing their kernels?
> >
> > > replica was already there,
> >
> > I don't like replica, it is too fragile and too slow, but I don't
> > think my opinion on this matters much.
> >
>
> What fragility are you referring to?  I've heard about it being
> fragile but am unable to find anything to back up the claim.
>
> Dave
>


  parent reply	other threads:[~2007-11-20 21:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 15:46 Federico Benavento
2007-11-20 15:53 ` erik quanstrom
2007-11-20 15:57   ` Federico Benavento
2007-11-20 18:31     ` Uriel
2007-11-20 18:58       ` erik quanstrom
2007-11-21  3:08         ` lucio
2007-11-20 19:30       ` Gabriel Diaz
2007-11-20 20:21       ` David Leimbach
2007-11-20 21:09         ` erik quanstrom
2007-11-20 21:36         ` Uriel [this message]
2007-11-20 21:46           ` erik quanstrom
2007-11-20 22:04             ` anyrhine
2007-11-20 23:57             ` Federico Benavento
2007-11-21  0:01               ` erik quanstrom
2007-11-20 22:42           ` David Leimbach
2007-11-20 23:09             ` dave.l
2007-11-20 23:59               ` David Leimbach
2007-11-21  8:23             ` Uriel
2007-11-21 10:06               ` Robert Raschke
2007-11-21 14:30                 ` David Leimbach
2007-11-21 15:33                   ` Uriel
2007-11-21 21:08                   ` Navin Johnson
2007-11-21 22:59                     ` Uriel
2007-11-21 20:55               ` Navin Johnson
2007-11-22 15:44                 ` Russ Cox
2007-11-22 19:48                   ` Uriel
2007-11-21  0:04 ` Steve Simon
2007-11-20 19:29 Erik Quanstrom
2021-01-26 22:01 Pouya Tafti
2021-01-26 22:23 ` sirjofri
2021-01-26 23:10   ` Pouya Tafti
2021-01-26 23:28   ` Pouya Tafti
2021-01-26 22:33 ` David du Colombier

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=5d375e920711201336t6eaeba6fi35151042bd22194c@mail.gmail.com \
    --to=uriel99@gmail.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).