9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] patch(1)
Date: Thu, 18 Mar 2004 12:06:01 -0500	[thread overview]
Message-ID: <4059D6F9.4030600@swtch.com> (raw)
In-Reply-To: <046e01c40cf2$203b1b60$8ed97d50@SOMA>

boyd, rounin wrote:

>>what's wrong with them?
>>    
>>
>
>read the archives:
>
>    pull smashed X
>
>read the prusker/wobber paper(s).
>  
>

i'm not convinced you've actually used replica/*.
you have to explicitly ask it to smash your files.
it's very careful not to smash any local changes unless
you explicitly request that.  much safer than rm, for example.

the problem is that it's too easy to think "well, i haven't made
any changes that i really care about", blindly run "pull -s"
and then all of a sudden your /lib/ndb/local has none of your
useful modifications anymore.  a good (g)ui would help here
considerably.  and maybe overwritten files should get backed up
somewhere.  but the architecture of the system is sound.

siphon is intended for a very different task.  the main difference
is that they're trying to present a single file system, just distributed.
as such the changes propagate in both directions and all the replicas
are assumed to be continuously connected.

replica does software distribution, which is one-way.
usually, i don't want to see the changes that other 9fans make -- if
you edit your /lib/ndb/local, those changes shouldn't go back
to sources.  and there's no way that everyone who downloads
a distribution can be expected to be online 24/7.

russ



  reply	other threads:[~2004-03-18 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 18:47 Russ Cox
2004-03-18  7:41 ` boyd, rounin
2004-03-18 12:37   ` Russ Cox
2004-03-18 13:00     ` boyd, rounin
2004-03-18 13:38       ` Russ Cox
2004-03-18 14:05         ` boyd, rounin
2004-03-18 17:06           ` Russ Cox [this message]
2004-03-18 20:38             ` boyd, rounin
2004-03-18 14:45 ozan s. yigit
2004-03-18 20:09 ` boyd, rounin

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=4059D6F9.4030600@swtch.com \
    --to=rsc@swtch.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).