On Saturday 20 December 2008 Peter Rabbitson wrote:
> > FSVS doesn't create intermediate directories *above* the base URL, only
> > within the working copy.
>
> Well this was certainly unexpected. It would be beneficial imho to
> pepper this around all existing howtos. Instead of what you propose it
> is better written as:
Ok, I'll add a note.
> Yep everything worked from this point on. I have a couple of cosmetic
> questions though
>
> 1) What is the difference between fsvs sync and fsvs update?
> Documentation is vague on this.
"update" asks the repository about the changes of BASE to HEAD (or the
revision given with -r), and applies it - that means fetching and deleting.
"sync" just replaces the local entry list with a fresh one that is fetched
from the repository; no local changes are done.
This is mostly for recovering of some errors/bugs, and normally not needed.
> 2) Could you review the following ignore/take list and tell me if it is
> sane? This is my first time really using fsvs, I just want to know I am
> not doing something rather stupid. Also it is a shame fsvs ignore load
> does not support comments. Currently I have to do:
Well, maybe I should implement that ... but they'd be ignored on loading, so
a "dump" wouldn't show them anyway.
> grep -v '^#' fsvs.ign | fsvs ignore load
Looks good.
> Thank you for the wonderful tool!
You're welcome!
> 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.
> /var/spool/fsvs
This is always ignored implicitly.
> # this is sensitive and the auto-encrypt plugin is not quite ready
> /etc/*shadow*
> /etc/ssh/*_key
> /etc/ssl/private
>
> # lvm keeps too much history
> /etc/lvm/cache
> /etc/lvm/archive
>
> # other than that we do want to version everything in /etc
> t/etc/**
>
> # version lost+found to easily spot remnants of ext3 corruption
> t/**/lost+found
>
> # we want to keep every kernel we ever used
> t/boot/**
>
> # and we want to keep the state of the apt system
> t/var/lib/aptitude/**
> t/var/lib/dpkg/**
>
> # everything else is of no interest at this point
> /**
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.
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=988098
To unsubscribe from this discussion, e-mail:
[[email protected]].
