From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4059D6F9.4030600@swtch.com> From: Russ Cox User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) MIME-Version: 1.0 To: 9fans@cse.psu.edu Subject: Re: [9fans] patch(1) References: <40589D28.9040806@swtch.com> <025b01c40cbc$73fdbbd0$8ed97d50@SOMA> <405997F8.2080407@swtch.com> <042a01c40ce8$fb7cc2a0$8ed97d50@SOMA> <4059A639.1030107@swtch.com> <046e01c40cf2$203b1b60$8ed97d50@SOMA> In-Reply-To: <046e01c40cf2$203b1b60$8ed97d50@SOMA> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 18 Mar 2004 12:06:01 -0500 Topicbox-Message-UUID: 3690ba58-eacd-11e9-9e20-41e7f4b1d025 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