P.Marek wrote: > On Saturday 20 December 2008 Peter Rabbitson wrote: >> my fsvs.ign >> ================ >> >> # ignore all backup/special files >> /**[-.]old >> /**.lock >> /**[-~] >> >> # we do not need/can not version anything fsvs related >> /etc/fsvs > It might make sense to keep /etc/fsvs; the URLs list gets moved to the WAA > with current trunk, and you're ignore patterns would be stored, too. >
I did that, however now I am confronted by another problem - timestamp changes on directories are constantly tracked. So I either have to commit the new mtime of the unchanged directories (thus polluting the log) or always commit files by name, excluding the changed dirs over and over again. Is there a general way to prevent fsvs from tracking timestamps, when fsvs status -CC shows no changes? >> /var/spool/fsvs > This is always ignored implicitly. Good to know > Looks good, makes sense. > IIUYC you plan to restore the system by re-installing the same packages, and > putting /etc back. > > Won't you need /**/.ssh/authorized_keys, and some other things from the home > directories? .bash_profile, .bash_rc, .vimrc or something like that? > > > Do you plan to blog about that, and your experience? If you ever do, please > send me the link, so I can mention it in the documentation. > Actually I do not plan to use fsvs a backup tool (I have separate blanket backup strategies), but as an audit log instead. This is also why I am interested in skipping the timestamp changes, as they are of no interest to me. Also (and I realise this is material for a new thread) - is there a way to separate install commits from configuration commits? Like any time I apt-get install something, I'd want to commit it to some url, and then whenever I make actual config changes - I'd like to commit it to a separate url, so I can see all manual changes just by browsing the svn log. Is this something that can be achieved with the multiurl capability of fsvs? Eventually when time permits I want to setup a new Linode from scratch with a debian bootstrap, making fsvs commits at every point where something of interest happens. I think that if I am careful enough, I can make the log actualy make sense. Then simply exposing the fsvs repository via svnweb, will yield a complete "LFS by example" reading, which will constantly evolve alongside my server. If I ever get to this point, and it starts shaping up as a viable idea, I will certainly share a link with the mailing list. Peter ------------------------------------------------------ http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=988179 To unsubscribe from this discussion, e-mail: [[email protected]].
