On Sun, Nov 14, 2010 at 10:07 AM, Gour <g...@atmarama.net> wrote: > Ron> For /etc, you probably don't really want to back up everything.
> Well, *I* don't need, but it's the question what my *system* does > need. > If the system is missing required files from /etc then it's probably hosed and it's quicker to re-install it than try to figure out what's broken. At least, that's my experience. > Iow, etckeeper uses hooks available in package manager, so that it is > easy to roolback if the system update fails for whatever reason. > If a system update fails then _arbitrary_ data, not necessarily just under /etc (etc /usr/share, or app config files under /opt/appName/...), can be left in an undefined state. Since /etc does not capture all the state, recovering the complete state of /etc is not necessarily going to get the machine back online. Nowadays it's faster to simply put in the system install CD and re-install, rather than poke around for 1+ hours (Ubuntu is installed on online in well under an hour). (There's a big advantage in keeping /home on its own partition or drive, to keep it intact during system reinstalls.) > The main point is that with e.g. darcs it was problem due to it being > perms-agnostic which is huge fossil's advantage here. > Unless i recently missed a big change, fossil doesn't maintain any perms except the +x bit, so if you restore /etc completely from fossil, a lot of files might have wrong permissions. e.g. some files are not allowed to be world-readable (e.g. /etc/shadow). -- ----- 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
