9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sources down?
Date: Sun, 24 May 2009 16:27:45 -0700	[thread overview]
Message-ID: <3e1162e60905241627m4792e33dr6d033fc56db666c9@mail.gmail.com> (raw)
In-Reply-To: <13426df10905231731n4231c573tc1c1fcc83839e10c@mail.gmail.com>

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

On Sat, May 23, 2009 at 5:31 PM, ron minnich <rminnich@gmail.com> wrote:

> On Sat, May 23, 2009 at 5:28 PM, Anant Narayanan <anant@kix.in> wrote:
> > On 24-May-09, at 2:17 AM, ron minnich wrote:
> >>
> >> On Sat, May 23, 2009 at 4:59 PM, J.R. Mauro <jrm8005@gmail.com> wrote:
> >>>
> >>> There are plenty of mirrors, I'm pretty sure the "sources is down
> >>> AGAIN" comments could be mitigated by people improving their 9fs
> >>> scripts.
> >>
> >> would be interesting to have a server that provided reliability by
> >> using whatever mirrors are out there and falling over transparently as
> >> things failed.
> >
> > This approach relies on said server being up all the time. Much easier to
> > fix client-side 9fs scripts :)
>
> Sorry, by "server" I did not mean "a server machine" I meant "a 9p
> server program which you could run"
>

How would one know one wasn't getting old data?  I've not really looked into
replica much though honestly to know how it works, I've just followed the
wiki about "staying up to date".  Perhaps the wiki could be mirrored as
well, and we could get a distributed update script?

Perhaps this is an area of improvement for Plan 9 in general.


>
> ron
>
>

[-- Attachment #2: Type: text/html, Size: 1975 bytes --]

  reply	other threads:[~2009-05-24 23:27 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 16:34 Rudolf Sykora
2009-05-22 16:51 ` ron minnich
2009-05-22 17:12   ` erik quanstrom
2009-05-22 17:23   ` Rudolf Sykora
2009-05-22 20:52     ` dave.l
2009-05-22 21:15       ` Uriel
2009-05-22 22:13         ` Noah Evans
2009-05-22 22:18         ` Eric Van Hensbergen
2009-05-22 23:06           ` Rudolf Sykora
2009-05-22 23:42             ` Eric Van Hensbergen
2009-05-22 23:54               ` Francisco J Ballesteros
2009-05-23  2:28                 ` Anant Narayanan
2009-05-22 21:09     ` Uriel
2009-05-22 21:31     ` ron minnich
2009-05-22 21:43       ` Uriel
2009-05-22 22:59         ` Latchesar Ionkov
2009-05-22 21:05   ` Uriel
2009-05-22 21:13     ` Eric Van Hensbergen
2009-05-23  3:57     ` Skip Tavakkolian
2009-05-23 23:59 ` J.R. Mauro
2009-05-24  0:17   ` ron minnich
2009-05-24  0:28     ` Anant Narayanan
2009-05-24  0:31       ` ron minnich
2009-05-24 23:27         ` David Leimbach [this message]
2009-05-24 23:38           ` jt
2009-05-25  0:22             ` Federico G. Benavento
2009-05-25  0:28             ` David Leimbach
2009-05-25  0:44               ` Federico G. Benavento
2009-05-25  6:05                 ` andrey mirtchovski
2009-05-25  8:28                   ` Rudolf Sykora
2009-05-25 10:07                   ` Federico G. Benavento
2009-05-25 10:39                   ` cinap_lenrek
2009-05-25 18:27                     ` Steve Simon
2009-05-25 19:25                       ` J.R. Mauro
2009-05-24  1:59     ` J.R. Mauro
2009-05-24  1:26   ` Lyndon Nerenberg
  -- strict thread matches above, loose matches on Subject: below --
2015-08-24 16:42 KADOTA Kyohei
2015-08-24 17:02 ` stevie
2015-08-24 18:04   ` KADOTA Kyohei
2008-11-02 18:51 Skip Tavakkolian
2008-11-02 19:04 ` Pietro Gagliardi
2008-11-02 21:35   ` geoff
2008-11-02 21:58     ` michael block
2008-11-02 23:46       ` Pietro Gagliardi
2006-11-29 21:55 james.cook
2006-11-29 22:20 ` Lyndon Nerenberg
2006-11-29 22:30 ` geoff
2006-11-29 22:49   ` Charles Forsyth
2006-11-30  4:41   ` James Cook

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=3e1162e60905241627m4792e33dr6d033fc56db666c9@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).