On Wed, May 25, 2011 at 7:09 PM, Bill Burdick <bill.burd...@gmail.com>wrote:
> Backup systems have to deal with these things. AFAIK, they usually store > users and groups by ID, not by name. > Which is portable across one system, but not arbitrary systems. Backups are played back onto the same system or a replacement. tar handles it like (for unpacking): - non-root users cause unpacked files to belong to that user - use root will keep the user mappings (i'm fairly sure, but not certain, that it uses names, as opposed to IDs). i have no idea what it does when root unpacks a file and it cannot find the id (probably assigns ownership to root). > Etckeeper does what Joan wants, using Git, Bzr, DARCS, or Mercurial: >> http://kitenet.net/~joey/code/etckeeper/ Of course you run this as root >> as you would with any other backup tool. Can't restore a backup, in >> general, unless you're root. >> > ... > A lot of people seem to be able to use etckeeper just fine. >> > i'm not aware of etckeeper, but judging by the name its a tool specialized for the job, whereas fossil alone tends to specialize on the needs of source trees (or, specifically, the needs of sqlite3's source tree, as Richard pointed out). -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
