From owner-freebsd-config Thu Oct 8 14:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21185 for freebsd-config-outgoing; Thu, 8 Oct 1998 14:11:20 -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 OAA21161 for ; Thu, 8 Oct 1998 14:11:13 -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 0zRNKs-0004zh-00; Thu, 8 Oct 1998 15:10:58 -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 PAA15923 for ; Thu, 8 Oct 1998 15:10:45 -0600 (MDT) Message-Id: <199810082110.PAA15923@harmony.village.org> To: config@FreeBSD.ORG Subject: Needed: intelisync-like functionality Date: Thu, 08 Oct 1998 15:10:45 -0600 From: Warner Losh Sender: owner-freebsd-config@FreeBSD.ORG Precedence: bulk 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. 2) To allow merging of an example file with a config file over time (ala the /etc/rc.conf problem). I maintain that if a simple program could solve both of these problems, then it would be generally useful for a huge class of things. Would it be acceptible to solve the /etc/rc.conf problem by having an /etc/img (or /var/db/sync-state or whatever) directory that kept state information about /etc/rc.conf? This would allow most changes to rc.conf the user makes to be preseved in a rc.conf updating proceedure. Comments? I can go into more detail if you'd like.. Warner P.S. I have need for something like this in many other areas, so I thought I'd see about writing something that would be useful to this long standing throny problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-config" in the body of the message