|
Do you think the method is publically feasable?
I think that every "brick" situation is different and needs to be analyzed and then (if all necessary "back changes" are known) a specific solution could be created.
Or do you think a common solution is possible?! (something like sending automatical upstart events)
Hmm, maybe we should create tar files of the whole system partition which can then be put as data.tar.gz files to /mnt/us?
Then at least hanging systems with changed files could be brought back to life.
But what about files which have been additionally added?
You have to know which files you added to remove them!?
At least a syslog to /mnt/us could always be made so that the reason for the hangig could be detected...
|