Those are already part of it :) Glad I know I knew what to include.
It will require hosing your system with no backups for it to be a true test though.
Just kidding, no one has to do anything during the testing they don't want to. The creation of restore points is entirely safe, unless you have a file named the same as the system restore files do which is unlikely, because they have a funny name, a custom section and the date in their title.
I can hose this system, nothing on it, so at most if the restore fails I'll just reinstall it.
anything that is important is already saved externally, so no worries.
would this be something like...create a resore point, maybe install some stuff, then try to restore it to before the install??
If one manages to bork their xorg.conf, menu.lst, or their gnome settings, this could restore it.
It basically mimics the Windows System Restore (which just backups the registry) and saves system settings.
Ok, I think I can manage that. ;)Quote:
If one manages to bork their xorg.conf, menu.lst, or their gnome settings
Wouldn't it be useful for testing purposes if the application had a separate option 'bork system' with sub-options offering to bork specific parts?
Right now, I haven't written the code to restore, just everything up to that with just a message saying it isn't done.
I also ran into GUI problems, and I have to fix that. Of course, if anyone wants to test the CLI code I will give that to. The code for the core of it is separate from the use of it.
It would not be a perfectly complete test accounting for all imaginable situations. Still it would reliably test the basic functionality.
Besides, intentionally borking the system with carefully designed code can do it in a way which is recoverable, while manually doing so might leave your system in an unpredictable state.
This is meant to restore still working, if damaged systems.
Perhaps a rename script would be in order, which can undo everything easily. (It would effectively backup the files too)