From owner-freebsd-config Thu Oct 8 14:41:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25781 for freebsd-config-outgoing; Thu, 8 Oct 1998 14:41:50 -0700 (PDT) (envelope-from owner-freebsd-config@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA25763 for ; Thu, 8 Oct 1998 14:41:35 -0700 (PDT) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zRNoI-00050p-00; Thu, 8 Oct 1998 15:41:22 -0600 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id PAA16132; Thu, 8 Oct 1998 15:41:09 -0600 (MDT) Message-Id: <199810082141.PAA16132@harmony.village.org> To: Mike Smith Subject: Re: Needed: intelisync-like functionality Cc: config@FreeBSD.ORG In-reply-to: Your message of "Thu, 08 Oct 1998 14:23:47 PDT." <199810082123.OAA00754@dingo.cdrom.com> References: <199810082123.OAA00754@dingo.cdrom.com> Date: Thu, 08 Oct 1998 15:41:08 -0600 From: Warner Losh Sender: owner-freebsd-config@FreeBSD.ORG Precedence: bulk In message <199810082123.OAA00754@dingo.cdrom.com> Mike Smith writes: : > There are many applications that I've found for doing an intellegent : > syncing. I see two big classes of syncing that is needed: : > : > 1) Keeping n files on n systems the same, while allowing for : > changes on any of the n systems. This is what intellisync : > does in the Windows world. : : Rsync (mostly). No. Rsync is one changer -> many machines. What I want is many changers on many machines resyncing automatically from time to time since these machines aren't always connected. Eg, I have a checkbook database on my machine at home, on my laptop and on my wife's laptop. Over time, all three of these get entries added to them and need to be re-syncrhonized with some kind of conflict resolution. : > 2) To allow merging of an example file with a config file over : > time (ala the /etc/rc.conf problem). : : The "right" solution for this is going to be a database of some source. Yes. I agree with this. Things are changing over time and need to be resynced... However, depending on rcs ID's isn't going to work in the long run, imho. What is needed is basically a patch file based on the last point you updated to. The sync process would then apply those patches to the new file that you sync to and you go from there. I'm not 100% sure that "patch" would be the best program to use for this purpose, but I'm not sure it isn't. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message