Hello Phil,
thanks for your quick and extensive answer (as always)!
Philipp Marek wrote:
Hello Simon!
On Montag, 16. Juli 2007 Simon Sprünker wrote:
I ran into a problem using the recursive revert using fsvs 1.1.6 (did
not try with older versions):
I am versioning / on a machine. I uninstalled htop
but didn't commit, I think?
Correct.
and deleted
/var/spool/fsvs and /etc/fsvs.
Why did you that? To simulate a catastrophic recovery?
Exactly.
What does "fsvs st" say, just after the "sync-repos"?
Please try a "fsvs revert -R -C" - the "-C" tells fsvs to check *all*
directories for missing elements. The sync-repos is not perfect yet, in that
it (has to) take the current timestamps ... But there I could verify
something; that's possibly fixed by taking the ctime as a hint only.
[HEAD]vm-one:/# fsvs sync-repos
...
[HEAD]vm-one:/# fsvs st
.m.? 0 ./var/lib/apt/lists/lock
.m.? 6822306 ./var/cache/apt/pkgcache.bin
D... 0 ./usr/bin/htop
D... 0 ./usr/share/man/man1/htop.1.gz
D... dir ./usr/share/doc/htop
D... 0 ./usr/share/doc/htop/AUTHORS
D... 0 ./usr/share/doc/htop/changelog.gz
D... 0 ./usr/share/doc/htop/changelog.Debian.gz
D... 0 ./usr/share/doc/htop/copyright
D... 0 ./usr/share/doc/htop/README
D... 0 ./usr/share/pixmaps/htop.png
D... 0 ./var/lib/dpkg/info/htop.postinst
D... 0 ./var/lib/dpkg/info/htop.md5sums
D... 0 ./usr/share/menu/htop
.m.? 4096 ./var/lib/urandom/random-seed
.m.? 218355 ./var/lib/dpkg/available-old
.m.? 218355 ./var/lib/dpkg/available
.m.? 0 ./var/lib/dpkg/info/htop.list
.m.? 240354 ./var/lib/dpkg/status
.m.? 0 ./var/lock/aptitude
.m.? 240325 ./var/lib/dpkg/status-old
..C. dir ./usr/share/pixmaps
.m.? 0 ./var/lib/dpkg/lock
..C. dir ./usr/share/menu
..C. dir ./usr/bin
..C. dir ./usr/share/man/man1
.m.? 1668428 ./var/lib/aptitude/pkgstates.old
.m.? 1668428 ./var/lib/aptitude/pkgstates
.m.? 19463 ./var/lib/exim4/config.autogenerated
.m.? 4 ./var/lib/nfs/state
.m.? 45 ./etc/resolv.conf
.m.? 16 ./etc/network/run/ifstate
D... 0 ./usr/share/applications/htop.desktop
.m.? 349 ./etc/mtab
..C. dir ./usr/share/applications
..C. dir ./var/lib/dpkg/info
..C. dir ./usr/share/doc
.m.? 0 ./root/.aptitude/config
.m.? 0 ./lib/init/rw/.ramfs
.m.. dir .
[HEAD]vm-one:/# fsvs revert -R -C /
Reverting to revision 5:
.m.. 0 ./var/lib/apt/lists/lock
.mC. 6822306 ./var/cache/apt/pkgcache.bin
D... 73252 ./usr/bin/htop
D... 1707 ./usr/share/man/man1/htop.1.gz
Warning [id=chown-other, action=stop]:
Cannot chown "./usr/share/doc/htop" to 0:0
An error occurred: No such file or directory (2)
in up__set_meta_data
If you need anything else, I will be happy to provide it.
You may ask, why I did the above steps. I did not find anything in docs
on how to achieve the following use case: You version a machine, it
breaks, you install a minimial system and update to the latest revision
in the repository. I thought the above steps simulate this process.
Well, I'd have recommended doing something like
- Booting with a knoppix or similar
- Make fsvs available (will get easier as soon as distributions include it)
- Go to your harddisk-root (here taken as /mnt)
cd /mnt
- Do
fsvs export $URL
that restores your machine (or at least should); optionally use -rREV.
- Call "lilo", "grub-install" or whatever
- Reboot into the machine.
- Now all you have to do is restore the FSVS' filelist:
cd /
fsvs sync-repos
I am not sure, if I understood you correctly: Should the way I tried
work? I would like that, because it means less work and that I don't
need physical access to the machine that broke, once the minimal system
is running :)
Best Regards,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
